Your Best Employees Are Doing Two Jobs Right Now

Lean does not always mean efficient.

In many organizations, running lean began as a sensible short-term move. Hiring slowed. Teams adapted. Strong performers absorbed the gaps because the work still needed to get done.

Then the temporary adjustment quietly became permanent structure.

The employee who absorbed a departing colleague's work never fully gave it back. The leader covering two functions is still covering two functions. The person everyone relies on keeps saying, "I've got it" — while effectively doing two jobs at once.

And because the work continues to get done, leadership often assumes the structure underneath it is healthy.

For a while, that looked like resilience.

In many organizations, it was actually dependence.

Why leaders often can't see it

The reason this goes undetected isn't inattention. It's that high performers are exceptionally good at making things look fine.

They compensate before they complain. They protect client relationships, cover institutional knowledge gaps, support struggling teammates, and keep projects moving — often without escalating anything. Harvard Business Review notes that managers consistently assign extra work to their most dependable people, precisely because those people handle it without visible strain. The output continues. The calendar stays full. The status updates read green.

The signal that something is wrong is the absence of a signal. And that's exactly what makes this hard to catch before it becomes expensive.

What to actually look for

The signals rarely show up in performance reviews or engagement surveys. They show up in the design of the team — in patterns that developed quietly and never got examined.

A few worth looking at honestly:

One person the organization quietly depends on.

Is there one person whose departure would create an immediate client or operational crisis? Not necessarily because they're uniquelytalented — but because responsibilities and relationships quietly consolidated around them over time, without anyone making that a deliberate choice.

Roles whose scope expanded but was never revisited.

If a job description was written 18 months ago and the person in that seat is doing materially more than it describes, that gap has been absorbed rather than addressed. The role grew. The structure didn't.

Institutional knowledge that lives in one person's head.

Processes that were never documented. Relationships that were never properly transitioned. Context that exists only in someone's inbox or memory — and walks out the door with them if they leave.

The person who is always available.

Never pushes back on scope. Always picks up the extra ask. Responsive at any hour. That pattern deserves attention — not as a performance observation, but as a capacity and retention risk.

Work that stalls when one person is unavailable.

Projects that pause, decisions that slow down, or client issues that suddenly bottleneck whenever a specific employee is out for a few days. That's not a scheduling problem. It's a structural one.

None of these signals mean something is broken. They mean something worth examining developed quietly, and the right time to look is before it becomes a departure.

What it's actually costing

Most leaders who ran lean over the past few years did so as a form of financial discipline. The logic was sound: don't add headcount until you're certain you need it, manage costs carefully, protect the business.

What rarely makes it onto the spreadsheet is the other side of that equation.

The visible costs are familiar — recruitment fees, time-to-hire, onboarding ramp, productivity gaps during transition. Those are real. But they're almost always smaller than the costs that accumulate while the decision is being deferred.

Retention risk compounds quietly.

The most capable person on your team is watching how their situation evolves. If they're absorbing work without corresponding recognition, trajectory, or relief — and they're good enough to have options — the risk of losing them isn't hypothetical. When they leave, they take institutional knowledge, client relationships, and context that took years to build. And replacing them is harder and slower than it would have been a few years ago —particularly when the role itself has quietly expanded beyond what one person was originally hired to do.

The people closest to that situation are watching too.

They draw their own conclusions about how the organization values and protects talent. Retention risk rarely stays contained to one departure.

For PE-backed and founder-led companies, this surfaces in the numbers before anyone connects the cause. A deal that didn't close on the right terms. A client relationship that didn't get the attention it needed. An operational gap that created friction at exactly the wrong moment. The cost of a delayed hiring decision rarely shows up as a line item — it shows up as erosion, six to twelve months after the decision was made. It's the same dynamic behind why delayed hiring decisions often become far more expensive later — something we explored previously in Time Kills All Deals — And Hires.

The math on running lean looks clean on a spreadsheet. It gets harder to defend when you account for what it costs to rebuild what quietly eroded while you were waiting.

The succession gap nobody's talking about

The person you didn't backfill twelve months ago is often the person you now have no replacement for. The delay meant no one was developing in that direction, no internal successor was being prepared, and the role itself quietly expanded beyond what a lateral hire could step into without a significant ramp.

Delayed hiring doesn't just create a vacancy. In fast-moving organizations, it creates a succession gap — at exactly the moment you can least afford one.

This is the part that's hardest to see from inside a lean structure. Everything looks functional right up until it doesn't. And by the time the gap is visible, the cost of closing it has already compounded. We touched on this directly in Stop Filling Seats. Start Building Teams — the difference between a hire that fills a gap and a hire that actually strengthens the structure underneath it.

The question worth asking now

None of this is an argument against running lean. Lean teams can be high-performing teams, and financial discipline in uncertain conditions is often exactly the right call.

The question is whether the current structure is lean by design — or lean by default, held together by a small number of people carrying more than the organization fully accounts for.

Those aren't the same thing. And in a lot of organizations right now, the honest answer is the second one.

The leaders who navigate this well tend to do one thing consistently: they ask the hard question before circumstances force it. Who on this team is genuinely irreplaceable right now? What actually happens if they leave? Is what we're running today sustainable — or are we operating on borrowed time?

Those questions don't always require an immediate hiring decision. But they do require an honest look at what's actually holding the organization together — and whether the structure underneath the output is as strong as the output suggests.

That's usually where the real conversation starts.

Because by the time the strain becomes visible, the people carrying it are often already looking for a way out.

That's a conversation we regularly help leadership teams navigate.