There’s always one.

The person who just gets it done.
They know the systems, the workarounds, the context.
They catch the mistakes before anyone else sees them.

Your ops feel smooth because of them.
Until they go on leave.
Or resign.
Or get promoted.

And suddenly… things stall.

Hero-ops looks like performance.

But it’s actually a liability.

If one person holds all the operational context,
You don’t have a workflow, you have a dependency.

That’s not scale.
It’s risk management waiting to fail.

In smaller firms, the risk is even sharper

This problem is especially dangerous in lean teams.
The thinking goes: “That’s just part of their job, we don’t need to document it.”

But here’s the truth:
Smaller teams don’t have buffers.
If one person disappears, there’s no redundancy.
No second operator. No offboarding playbook.
Just a mess everyone’s too busy to fix properly.

And when the firm is growing?
That undocumented knowledge becomes a bottleneck…or worse, a single point of failure right when you’re trying to scale.

What breaks when they’re not around?

Deadlines get missed.
Reporting slows down.
Backlogs pile up.
Client outputs get rushed or skipped.

Because all the critical knowledge (the nuance, the logic, the “how we actually do it”) lives in one person’s head.

Not in your system.

What smart firms are doing differently:

1. Map your dependency risks
Ask: “If this person stepped away for two weeks, what would break?”
Audit core workflows — CRM, reporting, research, investor comms.
Anywhere a single name owns the outcome = exposure.

2. Turn repeatable tasks into documented workflows
If it happens more than twice, it gets a process.
Use Loom, Notion, Scribe or even just a checklist in a shared doc.
Good enough beats perfect. Every time.

3. Embed capability teams to absorb execution
Instead of waiting until someone’s overwhelmed or burned out, embed global specialists to take over repeatable ops, research, and admin.
That’s how you scale without stretching internal teams to breaking point.

4. Design for handover, not heroics
Build with the assumption that people will be unavailable.
That means shared logins, access to templates, process tags in CRM, and clarity on “who steps in if…”

5. Stress-test now, not after someone quits
Yes it’s a pain. Yes, it will keep slipping down your never-ending to do list but you NEED to force the handover.
Can someone else pick up this task with what’s already documented?
If not, you’ve got more work to do.

The takeaway

Your best people should create leverage, not fragility.

If your operations stop when someone’s away,it’s not their fault.

It’s your design.

This isn’t a big company problem.
It’s a growing company problem.
And the ones who solve it early scale faster, cleaner, and with less chaos.

Build ops that survive holidays, promotions (even exits).
No heroics needed.