Case Studies
Slide Templates

Shortcut Org Reset

Rebuilding trust, craft systems, and activation momentum

Mike - Design Leadership | Shortcut | 2021-2022

Executive Summary: Fix the Operating System, Not Just the Screens

The product problems and org problems were reinforcing each other.

Problem (what I inherited)

Shortcut had intertwined org and product issues:

  • Low trust across EPD
  • Disorderly designer-to-developer handoff
  • Research insights were dismissed
  • No career pathing and product quality was slipping

Solution (how I treated it)

Change the operating system of design work:

  • Create clearer growth and coaching structures
  • Make design systems part of daily product delivery
  • Add rituals that make critique and iteration safer
  • Tie design improvement to measurable business outcomes

Outcome (what changed)

The team became more coherent and more effective:

  • Stronger craft systems
  • Better cross-functional confidence
  • Visible product and activation gains

summary

3

Summary

Shortcut needed more than a better ladder or a cleaner interface. The design organization and the product experience were both showing the cost of weak trust, poor handoff, ignored research, and inconsistent standards, so I treated the work as an operating-system reset for how design quality got made.

The Starting Point Was Bigger Than a Ladder Problem

The context deck made it clear that the org and the product were both signaling trouble.

  • Low trust across engineering, product, and design
  • Designer-to-developer handoff was disorderly
  • Research insights were largely dismissed
  • No career pathing existed for design roles
  • The product looked outdated
  • Activation and conversion were declining

context

5

Context

The company was small relative to its ambition, which meant the team could not pause product delivery while redesigning how design worked. Any solution had to improve coaching, cross-functional coordination, and product outcomes while teams were still shipping.

First Move: Change How Design Work Happened Every Day

The team needed a more reliable operating model before a cleaner UI could scale.

  • Made the design system part of daily design and engineering workflow
  • Argued for a UX platform layer so feature teams were not asked to fix everything alone
  • Created specialized roles including a Design System Lead and a Growth Design Lead
  • Used smaller end-to-end wins, like icon replacement, to prove the new system could ship

discovery-and-evidence

7

Discovery and Evidence

The internal context deck showed the same pattern repeatedly: trust issues, weak handoff, and ignored research were undermining product quality and activation at the same time. That evidence shaped the response: I needed to create better systems for critique, growth, and cross-functional execution rather than relying on isolated hero projects.

Second Move: Build Judgment Through Rituals, Roles, and Safer Critique

Confidence grew when expectations, review loops, and growth paths became explicit.

  • Built career journey maps and leveling across brand, product design, research, and managers
  • Elevated research to leadership level so insights could reshape priorities earlier
  • Added cross-functional design reviews, design iteration kickoffs, and an experimentation framework
  • Made work-in-progress easier to share by clarifying expectations, ownership, and review structure

implementation

9

Implementation

Implementation was iterative and deliberately practical. We introduced new roles, folded the design system into everyday delivery, and established repeatable review and experimentation rituals so teams could feel the change in how work happened, not just hear about it in an announcement.

Outcomes: Product Progress, Better Alignment, and a Stronger Team

The operating model changes translated into visible product and team results.

  • An A/B test showed an onboarding alternative improved activation by 110%
  • Created and filled specialized roles that improved growth and system focus
  • Launched a public-facing design system site and stronger design-system practice
  • Introduced rituals and processes that helped PM, PD, and Eng pull in the same direction

What This Proves for Clio

Team confidence comes from clear systems, not charisma.

  • The best craft coaching changes how work is reviewed, not only how individuals are corrected
  • Career ladders matter most when they connect to live critique, handoff, and decision quality
  • If you want designers to share unfinished work confidently, the system has to reward clarity and learning early

appendix

12

Appendix

  • Primary evidence for this case comes from Context/Shortcut/Shortcut Cast Study.pdf
  • The strongest signals include the opening problem inventory, the onboarding activation result, the role creation outcomes, and the list of rituals and process changes introduced across PM, PD, and engineering