Most design leaders know the feeling. A deadline is close, a roadmap is backed up, and the fastest path forward is to pull your most experienced designers onto whatever needs to ship. They handle it. The work gets done. And somewhere in the process, the things only they can do: the high-judgment work, the strategic thinking, the cross-functional influence. These get quietly pushed to the side.
It happens in most product design teams. It's rarely acknowledged as the structural problem it actually is.
A 2025 survey of design leaders found that 70% said their most skilled designers were regularly working below their level. Not occasionally. Regularly. That's not a workload problem. That's a team composition problem, and it has a predictable set of downstream consequences.
What Working Below Level Actually Costs
When senior designers spend significant time on execution that a less experienced designer could handle, a few things happen simultaneously.
The senior designer's highest-value contributions go unmade. The strategic work, the mentorship, the design decisions that require real depth: these get deferred or dropped. Over time, this shapes how senior designers experience their roles. The ones who have options start to weigh them.
The team's output capacity doesn't actually increase. Senior designers executing at a junior level doesn't free up capacity. It consumes it differently. The work gets done, but the team's ceiling stays exactly where it was.
The gap widens quietly. The distance between what the team could be doing and what it is doing grows without ever showing up on a sprint board or a headcount report.
Why This Keeps Happening
The structural reason is straightforward: most design teams are top-heavy by necessity, not by design.
When early-career designers join a team without real development support around them, they require more management, more oversight, and more correction than the team has bandwidth to provide. The natural response is to lean on senior designers to fill the gap: reviewing the work, catching the errors, absorbing the friction. What starts as a temporary patch becomes the operating model.
The underlying assumption is that this is just how it works with junior designers. That the overhead is inherent. That the only way to avoid it is to hire senior.
"That assumption is worth questioning."
The Variable Most Teams Aren't Controlling For
The overhead associated with early-career designers isn't a fixed cost. It's a function of how much structured support they have outside of the team.
When an early-career designer has genuine development infrastructure around them: structured guidance, consistent feedback, experienced oversight that doesn't fall on the team lead. The tax on senior designers drops significantly. The early-career designer ramps faster, produces more independently, and stops being a drain on the people the team needs for its hardest work.
The result is a team that's actually structured the way it's supposed to be. Senior designers doing senior work. Early-career designers developing the judgment to do more over time. And a design function that isn't quietly consuming its own capacity to stay afloat.
A Different Way to Think About Team Structure
The question worth asking before the next hiring decision isn't just "do we need a senior or junior designer." It's "what would have to be true for our team to actually function the way we want it to."
For most teams, the answer involves having reliable development support for early-career designers that doesn't depend on senior bandwidth to work.
FirstRoot is built specifically for that gap. The program provides early-career product designers with structured development support that runs alongside their existing role, so design leaders get the early-career hires they need without the overhead that's made those hires feel like a trade-off.
If your senior designers are regularly doing work that shouldn't require their level, it's worth asking why, and whether the answer is really about who you're hiring, or about what's in place to support them.
If this is a dynamic you're navigating on your team, it's a conversation worth having. Visit FirstRoot or reach out directly. This is exactly the kind of problem FirstRoot is built to solve.