How I lead
The systems we built became useful well beyond the design team. Executives used our value framework in funding decisions, five functions adopted our design system, and junior designers began owning work that had previously required senior specialists. These six stories show how that happened.
Decide what is worth building before the roadmap hardens.
Keep quality consistent without me in every review.
Grow designers who can own a problem end to end.
Planning
Design proposals were being read as visual improvements because nobody had priced their value. Working with product leadership, I built a taxonomy of design work, mapped it to company metrics, and wrote a rubric that weighed user value, business value, effort and risk in the same conversation.
Executives started using the design levers in funding meetings.
Three models that tied design to business metricsEveryone agreed simplicity mattered, but nobody had a way to defend it. The complexity budget scored each flow on decision, attention and orientation load, which gave product, research, design and engineering a shared way to see where scope was asking too much of users and cut it before it reached the interface.
Complexity stopped being something to polish and became a cost to justify.
A complexity budget for scope decisionsStandards
Quality was drifting across siloed teams, conflicting standards and repeated handoff failures, so I led a system of more than 200 components that connected product, engineering, creative, marketing and planning. Nobody was ordered to use it — product managers learned it, engineering mirrored it, and teams began planning around it.
A design project became infrastructure that five functions rely on.
A design system five functions chose to adoptTeams were rushing through problem definition and then polishing execution forever, so I flipped the standard: exceed the bar while you are defining the problem, and defend “good enough” once the work has done its job.
The team got more rigorous up front and stopped sooner at the end.
Knowing when to stop buildingPeople
After the pandemic shrank the team, a structure built on handoffs between UX and visual specialists was too brittle for the pace of the work. I rebuilt the group around junior product-design generalists and coached them to own everything from first framing to final delivery.
Junior designers delivered what senior specialists once had, faster and with fewer dependencies, then grew into planning and mentorship.
Rebuilding the team from specialists to generalistsThe career path rewarded execution, which kept capable designers out of strategic conversations. I made problem framing, recommendations, influence and mentorship count toward advancement, and gave designers room to practice them in roadmap and tradeoff meetings rather than only in critique.
Designers advanced by shaping direction, not by shipping more.
Promoting designers for influence, not output
