Going from Senior to Staff Designer isn't about doing the best work anymore.

Photo by PNW Production: https://www.pexels.com/photo/women-hiking-in-a-forest-7624850/

You’ve been a Senior Designer for a few years. Maybe Lead for one or two. Staff or Principal is the next rung, and nobody can quite tell you what the job actually is.

Some recruiters call it “player-coach.” Job descriptions say “set direction.” LinkedIn posts romanticize “mentorship-while-shipping.” None of it tells you what you’ll be doing Tuesday morning when you get there, or how to start practicing now to be ready.

I’m not a Staff or Principal designer. I’m the person who rewrites portfolios for them (seven in the past year), and I’ve cross-referenced what I’m seeing against Artiom Dashinsky’s Path to Staff Designer. So this is an adjacent experience, plus the homework.

Here’s what the jump looks like.

The term “Player-Coach” has been showing up in many design career conversations recently. Andy Budd, who founded Clearleft and now coaches design leaders for a living, wrote the piece on this that gets passed around the most.

If you’ve been looking at Staff/Principal Designer job listings, you’ve probably seen the term as well.

The pitch is simple: you’ll still design, but you’ll lead. You’ll ship, but you’ll mentor.

It sounds great. It’s also two different jobs pretending to be one, and conflating them is what costs people years.

One version is management: a design manager with 1–3 reports who still ships their own work. Budd says most people fail at this within 18 months.

The Leadership Research Institute calls the failure mode the “player-player trap”: managers who default to taking the work themselves, where coaching and feedback “happen after hours or via email.”

The other version is IC: a senior designer expected to set direction without managing anyone. That’s the path most seniors are on once they pass lead, and it’s the one this piece is about.

It has a name. It’s not player-coach. Its direction.

Direction comes from the creative world. Art direction, sound direction, creative direction. Same job everywhere it shows up: set the priorities, the principles, and the bar, then make sure the work everyone produces ladders up.

For a Staff or Principal, that looks like:

• Turning business outcomes into design priorities your team can run with

• Setting the quality bar by making it legible enough that other designers can hit it

• Owning consistency, identity, and how the design system gets used

• Critiquing in a way that teaches, not just corrects

Notice what’s missing: screens as the main thing.

Most Staff and Principals still ship work. Some ship a lot, especially at smaller companies. But it’s no longer how they create their primary value, and that’s where I see seniors getting tripped up.

The thing that got you to senior was usually being the person who could ship work that solved problems. Whenever someone handed you a gnarly problem, they trusted that you’d figure out the design.

That’s not a bad instinct. It’s the instinct that earned you the role. But it’s also the instinct that quietly stalls a lot of strong seniors at the next door. “I’ll just tackle it” gets in the way of the actual job.

Dashinsky describes the Principal-level shipping competency this way: “Motivates, unblocks, and coaches others to ship fast. Able to identify blind spots across teams in estimating or delegating work and builds processes to resolve that. Delegates work often.”

Personally shipping the hardest screen on the team isn’t in there.

The seniors who don’t make the trade tend to be the strongest individual designers on the team, which is what makes it hard. The thing that’s been working for you is exactly the thing you’re being asked to outgrow.

So if you’re senior right now and reading this, the audition starts before the title does. The question isn’t whether I’m shipping the best work on the team. You probably are.

The question is closer to: can I make the work around me better, even when I’m not the one doing it?

The moment you stop being the one moving pixels, you have to figure out how to communicate what you’d do if you were.

You become the person you used to roll your eyes at. The PM who slacks, “Can you make this pop?” and disappears. The exec who says “this doesn’t feel premium enough” and offers nothing else. The senior who reviews your work for ten minutes and lands on “I dunno, something’s off.”

Now you’re one of them.

When you’re setting direction, you’re giving feedback on work you didn’t do. You can see the better version. You just haven’t done the work of translating it into something a designer can act on.

That gap between what you can see and what you can say is the actual next-level skill.

It’s also the thing seniors can start practicing now, on the designers below them, before any title shows up. Every time you give feedback to a junior or mid-level designer, you’re either building this muscle or you’re not. And honestly, most of us skip the rep.

When critique stays at “I like” and “I don’t like,” the design ends up reflecting the preferences of whoever argues the loudest. The team grinds through cosmetic changes that get reversed in the next review. The senior who can’t articulate the call is often the one creating the churn, even when they’re the strongest designer in the room.

Underneath better feedback, you need a position. A stable sense of what good looks like for this product, this moment, this team.

That position is what people call “taste”.

Taste’s been having a moment for a couple of years. The argument’s straightforward (from the Nielsen Norman Group): when AI lowers the cost of execution, technical skill stops being where designer value lives. Selection and discernment do.

But there’s a version of this that turns taste into something mystical. A gift, a vibe, an aesthetic instinct you either have or you don’t. That version lets people off the hook for the actual work.

Phil Morton said it best: “Good taste isn’t magic. It’s pattern recognition developed through years of experience.”

Here’s the useful piece of news. It’s not that you don’t have taste. If you’ve been doing this for ten years, you have taste. The Staff and Principals I work with don’t describe themselves as having more of it than the seniors on their team.

They describe themselves as having gotten a little better at getting it out of their head.

Direction is the what. Taste is the why. Once you’re at this level, the why has to leave your head. It has to become something others can use in their work, their reviews, and their decisions when you’re not in the room.

If it stays internal, you’re back to “make it pop” in a fancier outfit.

The real skill, the one nobody trains you for, isn’t developing taste. It’s externalizing it. And the seniors who start practicing this a year or two before they need it tend to be the ones who don’t get stuck.

None of these are clever. They’re just the work most of us skip.

1. Stop saying “I like” and “I don’t like.” Replace them with “I think this is effective because…” and “I think this could be more effective by…” Fill in the rest with actual design vocabulary: hierarchy, contrast, rhythm, density, voice. The grammar forces the thinking. You’ll catch yourself reaching for “I like” and realize you don’t actually know why.

2. Write your taste down as principles, not preferences. A preference is “I like generous whitespace.” A principle is “When the page has more than three priorities, we resolve them with whitespace before we resolve them with type weight.” The first can’t be argued with. The second can be applied by someone who isn’t you. Three to seven of these, written down and shared, is what direction actually looks like.

3. Build a reference library. 20 to 30 examples that exemplify the bar you’re setting. Next to each one, write a sentence or two about what you’re actually pointing at. The way the empty state uses one strong illustration instead of three weak ones. When you tell a designer “make this feel more confident,” send them three references with the sentences attached. Vague becomes specific.

4. Pre-state your criteria before you review. Before you open the Figma file, write down what good looks like for this specific brief. It forces you to commit to a position before the work biases you. And when you share the criteria with the designer up front, the review stops being a black box. Most “the senior is impossible to please” complaints disappear once the senior writes the brief down.

5. Use the five whys on your own gut reactions. The feeling that something’s off is the alarm bell, not the feedback.

It feels cluttered. Why? Too many priorities competing. Why? Hierarchy is collapsed, three things use the same weight.

So the feedback is: “the H2, the CTA, and the alert are all weighted the same. We need to drop two of them.” That’s actionable. It feels cluttered isn’t.

6. Connect the aesthetic call to a user or business outcome. “This feels too playful” is a taste. “This feels too playful for the moment a user is entering their bank credentials, and we’ll lose conversion at the trust step” is the direction.

Same instinct, same eye. But now the designer doesn’t have to choose between your aesthetic preference and their understanding of the user. Do this consistently and what would [you] say about this? becomes a useful question for your team to ask when you’re not in the room.

Your job at the next level is to make your call legible enough that the designer next to you can act on it tomorrow. The career move from senior to Staff or Principal isn’t about getting better at design. You’re already good at design.

It’s about making the good you already have leave your head.

The designers you work with don’t need you to be a better player. They need a coach who can actually coach. Which means saying out loud, in words they can use, what you’d do if you were them.

The title catches up later.

Working on positioning yourself for a Staff or Principal jump? Book a free 30-minute fit call to talk through where you are and what’s next.

I rewrite portfolios for Senior, Lead, Staff, and Principal designers. I write about what I see in the Data and Design Newsletter, and help designers tell the story of why their work matters: to land jobs, get buy-in, and reach the next level.