Design LeadershipTeams

What a design career ladder actually measures

Career ladders describe the behaviors that got someone promoted, not the work that moved the product.

Every design career ladder I've read has the same structure. The early levels describe execution. The mid levels add ownership. The senior levels talk about influence. The staff levels talk about organization-level impact. It reads like a clean arc from doing the work to shaping how the work gets done.

What it doesn't tell you is how any of this gets measured. "Demonstrates strong systems thinking" is on a lot of ladders. Very few ladders explain what separates someone who demonstrates it from someone who doesn't.

The gap between the description and the evaluation is where most career ladder problems live.

What ladders actually measure

The uncomfortable truth is that career ladders, as practiced, mostly measure visibility and alignment with whoever controls promotions. That's not cynicism. It's the logical consequence of having abstract criteria evaluated by a small group of people with unequal information about the work.

A designer who works on a high-visibility product and presents frequently in the right rooms will get promoted faster than a designer doing equally good work on a low-visibility surface with fewer opportunities to be seen. Neither the criteria nor the evaluators are usually equipped to correct for this. The ladder says nothing about it.

This doesn't mean ladders are useless. They're useful for communicating expectations and giving people a shared vocabulary for career conversations. The problem comes when the ladder is treated as an accurate measurement system rather than a rough guide.

The scope inflation problem

One of the most reliable ways to advance on a design ladder is to expand your scope. Take on more projects, more cross-functional relationships, more "organization-level" work. The ladder rewards breadth of responsibility, so the incentive is to accumulate responsibility rather than to do any particular thing better.

The result is that your most senior designers are often the ones most spread across the organization, doing shallower work on more surfaces. They've optimized for the ladder rather than for craft. When you need someone to go deep on a hard design problem, they're not available, and the junior designers who haven't yet learned to protect their time are the ones doing the deep work.

Some amount of this is inevitable. Senior designers should operate at higher scope. The issue is when the ladder makes breadth a prerequisite for advancement rather than one possible shape of it. There are designers who should be going deeper at senior levels, not broader, and most ladders don't offer them a path for doing that.

The "influence" trap

The word that shows up most often in senior-to-staff level criteria is influence. "Influences product direction." "Shapes team culture." "Has organization-wide impact through their influence."

Influence is real. But it's also a description that's almost impossible to evaluate fairly. It favors people who are comfortable in meetings, who self-promote their contributions, who have strong relationships with senior stakeholders. Those are useful traits. They're not the same as being a good designer.

Two designers can have equivalent impact on product direction. One of them will be more visible about it than the other. On most ladders, visibility counts more than the underlying contribution.

What I actually look for

When I'm assessing someone's growth, I try to work backwards from decisions rather than behaviors. What decisions did this person influence that wouldn't have gone the same way without them? What did the work look like before they engaged, and what does it look like now?

The answer can't always be traced cleanly. But trying to trace it is more honest than asking whether they "demonstrated" a behavior on the rubric.

I also pay attention to whether people can articulate the reasoning behind their own work: what they built, why the alternatives wouldn't have worked, what they'd change if the constraints had been different. That kind of reasoning is what actually produces growth over time, and it shows up in conversation more reliably than it shows up in a performance review.

The ladder is a starting point for the conversation, not a conclusion. The designers who grow fastest are usually the ones who use the criteria as a prompt to think about their own gaps, rather than as a checklist to optimize against.

Greg Sargent
Greg SargentDirector of Design Systems, Spring Health

I write about design systems, accessibility, and the way AI is changing how we build software.

Published January 5, 2026

Be the first to rate this article.