The Hidden Cost of “Just Ask the Ops Lead”

The message usually looks harmless.

“Quick question — how do refunds get approved for annual plans?”

Then another one ten minutes later. “Which deck do we send to enterprise prospects?” Then a thread in a private channel about an exception nobody wrote down because everybody assumed somebody else had.

Most teams have a person like this. The ops lead. The senior engineer. The CS manager who has survived three tool migrations and a reorg. They know where the real process lives, which is often not in the docs folder. It lives in memory. In judgment calls. In old Slack messages. In a sense of how things are done around here.

For a while, this can feel efficient. It is faster to ask that person than to hunt through Notion. Faster to ping Amir than to read the SOP that may or may not be current. Faster, in the moment.

That speed is expensive.

What the team keeps paying for

The obvious cost is interruption. The person with all the answers loses whole chunks of the day to context switching. A “quick question” is rarely quick for the person answering it. It means stopping, remembering the exception, checking whether anything changed last quarter, and replying carefully enough that the answer doesn’t create two more questions.

But the larger cost sits elsewhere.

New hires learn that the fastest path to getting unstuck is not understanding the system. It’s knowing who to ask. So onboarding turns into a social map instead of a learning process. The new hire who keeps Slacking the same three people is not the problem. They are responding rationally to the environment.

Then mistakes start repeating in familiar shapes. Someone sends the wrong template. A handoff misses one required field. A customer gets an answer that was true six months ago. None of these errors are dramatic on their own. They just keep happening. Small delays, small corrections, small bits of rework. Enough of them together and the team starts feeling slower than it should.

This is why tribal knowledge is such an annoying problem. It rarely arrives as a crisis. It shows up as drag.

And because the drag is distributed, teams get used to it. A little waiting here. A little guessing there. A senior person carrying too much of the system in their head. Everyone adapts, which makes the problem harder to see.

The expert is doing two jobs

The hidden role of the “just ask them” person is not only doing their own work. They are also acting as a live interface to the company.

They translate messy reality into next steps. They remember why a rule exists. They know which part of the official process matters and which part everybody quietly ignores. Often, they are good at this, which is part of the trap. Competent people can absorb an impressive amount of operational chaos before anyone notices there is too much of it.

From the outside, this can even look like leadership. People trust them. Things keep moving. Questions get answered.

From their side, it often feels different. Their real work gets squeezed into the gaps between pings. They become the safety net for unclear systems, outdated docs, and half-finished onboarding. If they take a day off, things wobble. If they leave, everyone suddenly discovers how much they were holding together.

That is not resilience. It is dependency with a friendly face.

Documentation fails when it tries to be complete

Most teams know they should document more. The problem is that “document more” sounds like a side project for a calm quarter that never arrives.

So nothing happens until the pain gets sharp enough. Someone quits. A new manager joins and asks how a process works. An audit appears. Then the team swings too far in the other direction and tries to capture everything at once.

That usually produces a graveyard: long SOPs, heroic notion pages, and training materials nobody reads because they were written to be comprehensive rather than usable.

The first useful step is smaller than that.

Not “document the whole process.” Document the moments that reliably cause interruption.

If the ops lead gets the same question four times a month, that is a training asset waiting to happen. If every onboarding cohort gets stuck on the same handoff, that is not a people problem. It is undocumented knowledge. If managers have to explain the same exception every quarter, the exception is part of the process now.

This is where lighter-weight course formats and internal learning tools can help, including platforms like Capya, but the method matters more than the tool. Start with the repeat questions. Turn them into something another person can actually absorb: a short walkthrough, a scenario, a simple decision tree, a recorded explanation with context.

Not a wiki page called “Refund Process Final v3.”

Something a tired person can use on a Tuesday morning.

What that person actually knows

The mistake teams make is trying to extract facts when the valuable thing is often judgment.

The ops lead rarely knows only the steps. They know where people hesitate. They know the weird edge cases. They know that one field in the CRM matters more than the other five. They know that if a request comes from finance on the last day of the month, the normal rule may not apply.

That kind of knowledge is harder to capture, but it is also what makes training useful.

A decent internal learning resource does not just say what to do. It shows how someone experienced thinks. Why this exception exists. What a good handoff looks like. Which mistake is common enough to check for every time.

That is why transcripts, call recordings, process walkthroughs, and annotated examples are often more valuable than polished documentation. They contain the shape of real work. The texture. The part a formal SOP tends to sand down until nobody can recognize it.

Teams do not need to document every corner of the business before they can benefit from this. They need to reduce the number of times the same knowledge has to be manually reissued by the same exhausted person.

Once that starts happening, something else changes too. Onboarding gets less dependent on who is available. Managers spend less time rescuing routine tasks. The expert gets to be an expert again, instead of a human search bar.

That is the real cost of “just ask the ops lead.” It is not only the interruptions or even the slowdown. It is the quiet decision to keep knowledge scarce because sharing it feels harder than repeating it.

For a while, that decision can look practical.

Then the team grows, and practicality starts answering Slack all day.