From senior to staff or principal designer: what actually changes

Most designers can describe what they need to do to get to senior. Good craft, solid process, the ability to run a project end-to-end, positive feedback from PMs and engineering partners.

Fewer designers can describe what they need to do to get from senior to staff or principal. The criteria are less obvious. The rubric is less written down. And the feedback loop is slower because you’re being evaluated over quarters, not sprints.

Here’s what I’ve observed across multiple teams and companies.

The shift from execution to influence

The clearest distinction between a senior designer and a staff or principal designer isn’t skill level. Both are highly capable designers. The distinction is in what they make happen beyond their own work.

A senior designer:

• Does high-quality work on the projects they’re assigned
• Collaborates effectively across functions
• Executes product direction well
• Explains their design decisions clearly

A staff or principal designer:

• Raises the quality of others’ work, not just their own
• Aligns the team around shared goals, not just collaborates with them
• Shapes product direction, not just executes it
• Influences business decisions, not just design decisions

The shift is from being good at your job to expanding the scope of what you affect.

This distinction matters for career progression because at the staff and principal level, your impact can no longer be measured by your individual output. You’re being evaluated on what happens in the organisation because you were there.

What staff-level scope looks like in practice

A senior designer typically owns a feature or a product area. Their work is well-defined. They receive direction and translate it into good design. Their success is measurable in the quality and outcomes of what they ship.

A staff designer owns something harder to define. They might hold the design direction for an entire product, work across multiple feature teams, or be responsible for raising the craft standard across the design organisation. Their success is measured partly in their own output and partly in the calibre of work the people around them produce.

This change in scope requires different skills. You can be an excellent senior designer without ever navigating complex organisational dynamics or building alignment across competing priorities. At staff level, that’s most of the job.

The three capabilities that matter most at staff level

1. Operating without clear direction

Senior designers generally work within direction that’s been established by a PM or design lead. Staff designers are expected to create direction in the absence of it.

This means spotting problems or opportunities that nobody has articulated yet. Developing a design vision for an area that doesn’t have one. Going to a stakeholder not to ask what you should be working on, but to tell them what you think the team should be prioritising: with evidence to back it up.

The ability to identify what matters when nobody has told you what matters is one of the clearest signals of staff-level readiness.

2. Influencing roadmaps and priorities

Senior designers advocate for their work. Staff designers advocate for work that hasn’t been scoped yet.

This is the difference between “here’s the design I’d like to ship” and “here’s what I think we should build and why.” The second requires a different level of business understanding, a stronger relationship with the PM, and a clearer view of what the company cares about and why.

The tool for this is the same regardless of level: connecting design decisions to metrics, and metrics to business outcomes. The difference is that at senior level you do this for work you’ve already designed. At staff level, you do it to argue for work that hasn’t started yet.

3. Elevating the work of others

This is the one most designers underinvest in.

It’s easier to do the work yourself than to make someone else’s work better. Elevating others requires patience, a clear articulation of what good looks like, and a willingness to invest in improvements that you won’t get credit for directly.

At principal level, this extends to shaping the design culture of the organisation: how decisions are made, what quality means on your team, what the norms are for sharing work and receiving feedback.

The skills that get you stuck at senior

There are patterns I see consistently in senior designers who plateau.

Over-investing in craft at the expense of influence. The work is excellent. The stakeholder relationships are thin. The ability to connect design decisions to business context is underdeveloped. This produces a designer who is trusted to execute but not consulted on direction.

Explaining decisions rather than influencing them. Senior designers present their work and answer questions. Staff designers walk into design reviews with a clear point of view about what the business should do and why, and they’ve often already built agreement with key stakeholders before the review.

Defining their role by their remit, not their impact. “That’s the PM’s job” or “I don’t have context on that” are common refrains. At staff level, the expectation is that you find out what you need to know and engage with the full problem, not just the design execution slice of it.

The AI era makes this more urgent

As AI makes design execution faster, the economic case for large teams of senior execution-focused designers weakens. The productivity per person goes up; the number of people needed to produce a given output goes down.

The part of the design role that AI doesn’t compress is judgment, alignment, and strategic input. Understanding what to build and why. Identifying the right problems. Aligning stakeholders around a direction. Communicating design decisions in terms of outcomes.

These are the skills that distinguish staff and principal designers: and the ones that will matter most as the industry changes.

What to work on if you’re ready to make the jump

If you’re at senior level and want to move toward staff or principal, there are a few concrete places to start.

Expand your business context. Learn how your company makes money. Understand the value streams your team’s work supports. Know which product areas are high-leverage and which are not. This is the foundation for influence.

Build stakeholder relationships before you need them. The designers who get to shape direction are the ones who’ve spent months building the relationships that make that possible. Stakeholders consult people they trust. Trust is built over time, not in design reviews.

Start advocating for work that hasn’t been scoped. Find a problem or opportunity your team isn’t working on that you think matters. Build the case for it. Take it to your PM. Even if it doesn’t get prioritised, you’ll start to develop the muscle for operating with more autonomy.

Invest in elevating others. Spend part of each week on someone else’s work. Give feedback. Pair on hard problems. Improve what’s in front of you without taking it over. Track the improvement over time.

The path from senior to staff is not a straight line of doing more of the same things better. It’s a change in what you’re trying to achieve. If you’re still spending most of your week in delivery work, start with breaking out of delivery mode.