Sarah is your best manager. She runs the operations team like a Swiss watch. When clients have problems, they ask for Sarah. When executives need something done right, they go to Sarah. When new initiatives launch, Sarah makes them work. Her team is high-performing, loyal, and efficient. She knows every process, every system, every relationship that makes operations function.
Your organization doesn't just depend on Sarah. It runs on Sarah.
And that's not a sign of organizational strength. It's a catastrophic risk hiding in plain sight.
The "manager who holds everything together" exists in almost every organization. They're celebrated, promoted, and rewarded for being indispensable. What nobody discusses: indispensability is a single point of failure, and you've built critical organizational capability around a person instead of building it into the organization.
When Sarah gets sick, takes a new job, burns out, or gets hit by the proverbial bus, you're going to discover that she wasn't just holding things together—she was the only thing preventing everything from falling apart.
Why "Holding Everything Together" Feels Like Success
Let's first acknowledge why organizations celebrate these managers instead of recognizing them as risks:
They Deliver Relentlessly
The manager who holds everything together produces results. Projects complete on time. Problems get solved. Teams perform. Stakeholders are satisfied.
From a quarterly results perspective, they're your star performers. Every metric looks great.
They Create Stability in Chaos
When the organization is undergoing change, dealing with crises, or navigating uncertainty, these managers create pockets of stability. Their teams aren't panicking. Their operations keep running. They absorb organizational chaos and output calm efficiency.
This feels invaluable—and it is, in the short term.
They Enable Leadership to Focus Elsewhere
Executives love these managers because they don't require attention. "Sarah has it handled" becomes the default assumption. Leadership can focus on strategy, growth, and other priorities because they trust Sarah to manage operations without oversight.
This delegation feels like efficient leadership. It's actually abdication.
They Mask Organizational Dysfunction
Broken processes, unclear strategies, under-resourced teams, poor systems—the "holder-together" manager compensates for all of it. They fill gaps, work around problems, and make dysfunction invisible to leadership.
This feels like problem-solving. It's actually preventing the organization from confronting and fixing systemic issues.
The Recognition Trap
Organizations reward these managers with:
- Promotions (more responsibility, more things to hold together)
- Compensation increases (you can't afford to lose them)
- Public praise (setting the standard others should meet)
- Additional scope (because if anyone can handle it, they can)
Every reward increases their indispensability—and the organization's dependence on them.
The Hidden Risks Nobody Talks About
While leadership is celebrating Sarah's indispensability, several dangerous dynamics are compounding:
Risk 1: Knowledge Concentration
Sarah knows how everything works. Not just formally documented processes, but:
- The workarounds that make broken systems function
- The relationships that grease organizational wheels
- The unwritten rules about how decisions really get made
- The historical context for why things are done certain ways
- The tribal knowledge about what's been tried and failed
The danger: This knowledge exists in Sarah's head, not in organizational systems. When Sarah leaves, it leaves.
Real example:
A manufacturing company's operations manager—their "Sarah"—took a medical leave unexpectedly. Within two weeks:
- Production scheduling broke down (nobody else knew the complex logic she used)
- Supplier relationships deteriorated (she was the only one who knew key contacts and relationship history)
- Quality issues emerged (her informal quality checks weren't documented)
- Cross-functional coordination failed (she was the glue connecting departments)
It took them six months and $3M in operational disruptions to reconstruct what she'd been doing. Much of her tribal knowledge was permanently lost.
Risk 2: Organizational Learned Helplessness
When one person "holds everything together," everyone else learns they don't have to.
The pattern:
Problem emerges → "Let Sarah handle it" Decision needed → "Ask Sarah what we should do"
Process broken → "Sarah will work around it" Stakeholder unhappy → "Sarah will smooth it over"
The consequence: The organization's problem-solving muscles atrophy. Teams become dependent, passive, and incapable of functioning without the central figure.
What happens when Sarah leaves:
Suddenly, problems that Sarah routinely solved become crises. Teams that operated smoothly under her leadership are paralyzed. The organization discovers it hasn't actually built capability—it outsourced it to one person.
Risk 3: Burnout Inevitability
Nobody can hold everything together indefinitely. The weight eventually becomes unsustainable.
The burnout trajectory:
Year 1-2: Sarah thrives. She's energized by being needed, capable of handling the load, and getting recognition.
Year 3-4: Cracks appear. The load is growing. Sarah is working longer hours, stressed more often, but still performing.
Year 5-6: Sarah is exhausted. She's going through the motions. The quality of her work is declining. She's dreaming about quitting but feels trapped (who else could do this?).
Year 7+: Sarah either burns out catastrophically (health crisis, breakdown, sudden resignation) or becomes a shell of herself (physically present, mentally checked out).
The organizational blindness:
Because Sarah keeps delivering, leadership doesn't see the burnout coming. They're tracking results (which remain solid through force of will), not sustainability (which is collapsing).
When burnout hits, it's sudden and shocking—and the organization is completely unprepared.
Risk 4: Innovation and Improvement Stagnation
When one person holds everything together, they become invested in maintaining the system they've mastered.
The dynamic:
Sarah knows how everything works. She's built expertise in current processes. Changing those processes would:
- Undermine her hard-won knowledge
- Create short-term disruption she'd have to manage
- Risk making things worse
- Potentially make her less indispensable
The result: Sarah—often unconsciously—becomes a barrier to change. Improvement ideas get dismissed as impractical. New approaches are resisted. The status quo ossifies.
Meanwhile, competitors are innovating and the organization is locked into ways of working that were optimal years ago but are suboptimal now.
Risk 5: Succession Impossibility
How do you develop Sarah's replacement when:
- Nobody else has exposure to the breadth of what she does
- She's too busy to mentor or document
- Her knowledge is too complex and contextual to easily transfer
- Potential successors leave because there's no path forward (Sarah has the role locked)
The succession trap:
Organizations keep Sarah in place because they can't replace her. They can't replace her because they've kept her in place without building succession. The longer this continues, the more impossible replacement becomes.
Risk 6: Organizational Fragility Disguised as Strength
From the outside, Sarah's team looks like the strongest, most reliable part of the organization. "If only every manager were like Sarah!"
In reality, it's the most fragile. It's entirely dependent on one person remaining healthy, engaged, and employed.
The stress test:
Resilient systems handle disruption without breaking. Sarah's operation looks resilient—until Sarah is disrupted. Then it collapses because the strength was personal, not organizational.
The Warning Signs You're Dependent (Not Just Well-Led)
How do you distinguish between "excellent manager with high-performing team" and "organizational dependency disguised as management excellence"?
Warning Sign 1: The "Only Sarah" Phenomenon
Listen for phrases like:
- "Only Sarah knows how to..."
- "We need to wait for Sarah to..."
- "Sarah is the only one who can..."
- "Let me check with Sarah because..."
If multiple people across the organization routinely say these things, you don't have an excellent manager—you have a dependency.
Warning Sign 2: The Indispensability Test
Ask: "If Sarah won the lottery tomorrow and resigned effective immediately, how long would it take to get her operation back to current performance levels?"
If the answer is:
- 2-4 weeks: You have good documentation and distributed capability
- 2-3 months: You have some dependency but manageable risk
- 6+ months: You have dangerous concentration risk
- "We'd be completely screwed": You have a single point of failure
Warning Sign 3: The Vacation/Sick Day Pattern
What happens when Sarah is out?
- Does work continue smoothly? (Good—capability is distributed)
- Does work slow but continue? (Acceptable—some dependency but not total)
- Does work stop until she returns? (Dangerous—she's a bottleneck)
- Does she work while on vacation/sick? (Critical—she can't actually disconnect)
If Sarah hasn't taken a real vacation (fully disconnected, no working) in over a year, you have a problem.
Warning Sign 4: The Successor Question
Ask Sarah: "If you were promoted tomorrow, who would take over your role?"
If she:
- Names someone and that person is largely ready: Good succession planning
- Names someone but acknowledges they'd need significant development: Normal
- Can't name anyone or says "nobody could do this job": Red flag—knowledge isn't transferable
Warning Sign 5: The Expansion Pattern
Is Sarah's scope continuously expanding?
- New responsibilities keep getting added to her plate
- When problems emerge elsewhere, they get moved to Sarah
- Her team grows but her individual load doesn't shrink
Continuous expansion signals the organization is solving problems by giving them to Sarah rather than building capability elsewhere.
What to Do: Building Organizational Capability Instead of Personal Dependency
If you've identified that you have a "Sarah"—a manager holding everything together in ways that create risk—here's how to transition from personal dependency to organizational capability:
Step 1: Acknowledge the Risk (Not the Blame)
Sarah isn't the problem. She's doing exactly what was asked of her—being excellent, solving problems, delivering results.
The problem is organizational design that concentrated too much capability in one person.
The conversation:
Not: "Sarah, you're a single point of failure and that's a problem."
But: "Sarah, you've built something remarkable here. We need to ensure this capability is sustainable and doesn't entirely depend on you—both for the organization's resilience and your wellbeing."
Step 2: Knowledge Transfer and Documentation
The brutal truth: Sarah is too busy to document. Documentation has to become part of her job, with time protected.
What this means:
- Reduce Sarah's operational load 20-30% to create time for knowledge transfer
- Assign someone to shadow Sarah and document processes, decisions, relationships
- Create structured knowledge capture (process documentation, decision frameworks, relationship maps)
- Record Sarah explaining complex processes/decisions
This feels inefficient short-term (Sarah is less productive). It's critical long-term (her knowledge becomes organizational knowledge).
Step 3: Distribute Responsibilities
Sarah shouldn't just offload tasks—she should redistribute authority and decision-making.
The approach:
Identify Sarah's major responsibilities and systematically transfer ownership:
- Assign clear DRIs (directly responsible individuals) for each area
- Give them decision authority, not just execution responsibility
- Provide them time with Sarah to learn context and nuance
- Support their early decisions even when different from what Sarah would do
The discomfort:
This requires Sarah to let go of control and accept that things might be done differently (and maybe initially not as well). It requires leadership to accept short-term performance dips for long-term resilience.
Step 4: Build Successor Capability
Identify potential successors and actively develop them:
- Exposure to Sarah's full scope (not just pieces)
- Stretch assignments with Sarah's support
- Relationship-building with her key stakeholders
- Explicit development plan toward readiness
Timeline: 12-24 months of focused development to build genuine successor readiness.
Step 5: Fix the Systems Sarah Was Compensating For
Sarah is likely working around broken processes, unclear strategies, and resource gaps. Stop asking her to compensate and fix the underlying issues:
- Broken systems she's been working around? Fix them.
- Unclear strategies she's been interpreting? Clarify them.
- Resource gaps she's been filling personally? Address them.
- Process failures she's been preventing? Redesign the processes.
Step 6: Create Structural Resilience
Build organizational design that doesn't depend on any single person:
- Cross-training so critical knowledge exists in multiple people
- Documented processes for complex workflows
- Distributed decision-making authority
- Succession plans for all critical roles
- Regular rotation of responsibilities to prevent concentration
The Hardest Part: Sarah Might Resist
Sarah has built her identity, value, and security around being indispensable. Efforts to make her dispensable can feel threatening.
The resistance patterns:
"Nobody else can do this as well as I do" (true initially, but prevents development) "It's faster if I just do it myself" (true short-term, dangerous long-term) "I'm too busy to train someone" (creates the very dependency that keeps her too busy) "My team needs me" (they do, partly because she's trained them to)
The compassionate response:
"I know this feels like we're saying you're not valuable. That's not it. You're so valuable that we need to ensure this capability survives and thrives beyond any single person—including you. And frankly, we need to ensure you're not carrying unsustainable weight."
The Bottom Line: Indispensability Is a Bug, Not a Feature
Organizations celebrate the manager who holds everything together because they deliver results and create stability.
But indispensability is organizational fragility disguised as individual excellence.
When critical capability exists in one person rather than the organization:
- Knowledge is concentrated and at risk
- Teams become dependent and passive
- Burnout becomes inevitable
- Innovation stagnates
- Succession becomes impossible
- One departure creates organizational crisis
The manager who holds everything together is a warning signal, not a success story.
Build organizational capability instead. It's harder, slower, and less heroic. It's also sustainable, resilient, and actually scalable.
Sarah is excellent. The organization depending entirely on Sarah is not.
Fix it before you find out what happens when she's gone.
