Overflow Work Isn't Beneath a Good Designer

A few months ago an agency reached out with a straightforward ask: their senior designer was out for six weeks, they had two client projects mid-flight, and they needed someone who could pick up the work without the client ever noticing a handoff had happened.

No pitch deck. No "let's explore how we might partner." Just: here's the Figma file, here's the deadline, can you do this.

I said yes immediately.

The ego problem

I've noticed a strange thing happens when designers hear "overflow work." They hear it as a demotion. As if picking up someone else's project mid-stream, working inside someone else's system, and staying invisible to the end client is somehow beneath the work of "real" design.

It isn't. It's a different skill.

A different kind of discipline

Overflow work asks you to do something most designers never practice: subordinate your ego to someone else's process. You're not setting the direction. You're not pitching your point of view in the kickoff call. You're matching an existing voice, hitting a deadline that was set before you arrived, and making an agency look good to their own client.

Harder than it looks

That's harder than it sounds. It's also, frankly, a better test of craft than most greenfield briefs. Anyone can design well when they control every decision from day one. Fewer people can step into someone else's half-finished system, understand its internal logic fast, and extend it without a seam showing.

What agencies are actually hiring for

The agencies that use me this way aren't hiring a lesser version of a designer. They're hiring the part of the job that's actually hard to find: someone reliable enough to hand off a live client relationship to, without babysitting.

If your bench is stretched this quarter

If you're an agency carrying more scope than your bench can absorb this quarter, that's the gap I sit in. No new logo on the work, no direct client contact unless you want it, just capacity that shows up on time.