Ask a leadership team who should own process in their company and you'll get a long, awkward pause. Then someone offers "operations, probably?" and everyone nods, relieved the question is over. It isn't over. That pause is the whole problem, and it's costing you more than you think.
The ghost in the org chart
If you run on EOS®, you've got an Accountability Chart, and every important function has a name next to it. Sales has an owner. Finance has an owner. Marketing, operations, delivery, all spoken for. Now find the box that says "make sure the way we do the work actually gets captured, taught, and followed." You can't. There isn't one.
That's the ghost in the org chart. The single most valuable long-term asset your company has, the knowledge of how the work gets done, belongs to nobody. It's everybody's job, which means it's no one's job, which means it doesn't happen. Everyone's too busy doing the work to capture how the work gets done. So it stays locked in people's heads and walks out the door when they do.
Why it isn't HR, and isn't ops
The reflex is to hand it to a department that already exists. HR runs onboarding, so give it to HR. But HR onboards people into the company. They can't capture the specific expertise of how your best estimator estimates or how your top rep closes. They don't do the work, and they can't document what they don't do.
Operations is the other reflex, and it's closer, but it fails for a different reason. Your ops leader is buried in today. Their entire job is keeping the current work moving: this week, this shipment, this fire. Capturing and transferring knowledge is important but never urgent, so it loses every single time to whatever's burning. Ask someone to own process on top of a full-time operational job and you've guaranteed it stays at the bottom of the list forever.
Why a consultant can't own it either
So companies reach for the outside fix and hire a consultant. Smart people, often genuinely helpful. But a consultant has a fatal flaw as the owner of your process: they leave. They come in, document a batch of procedures, hand you a polished binder, and drive off. The binder is a snapshot of a moving thing.
You didn't build a business. You built a job that employs other people. And a job that only runs when you're in the room isn't an asset. It's a trap with a payroll.
Six months later the process has changed, the binder's stale, and the person who understood it is gone. Knowledge transfer isn't a project with an end date. It's an ongoing function. You can't outsource an ongoing function to someone who, by definition, won't be there next quarter.
Who should own process: a dedicated owner of knowledge transfer
Here's the answer the pause was avoiding. Someone in your company needs to own process the way someone owns sales: as their actual, named job, not a side quest. Call it what it is, the person responsible for getting knowledge out of your experts' heads and into the hands of everyone who needs it. In our world we call that role the Playbook Builder, and it's the missing seat on almost every org chart I see.
It doesn't have to be a new hire on day one. It can be a sharp person who already gets your business, given protected time to do this and only this. The non-negotiable is that it's owned, named, and given real hours. An unowned responsibility is just a wish. Give it a name, put it on the chart, and protect the hours. That single act separates the companies that capture their knowledge from the ones that keep losing it.
What this role actually does
The job isn't "write documents." It's running a loop that never really ends.
- Find where the business is leaking knowledge, the roles where one person is a single point of failure.
- Capture how the best people do the work, ideally as short video, not a wall of text.
- Get it in front of the team where and when they need it, then check whether they used it and whether the number moved.
That loop, capturing and reinforcing how the work gets done over and over, is the whole job. W. Edwards Deming found that about 80 percent of the time, when something goes wrong, the root cause is a broken process, not a bad person. Someone has to own the processes for that to ever get better.
When a company actually gives this role to someone, the results show up fast. Russ Davis Wholesale, a $150M food distributor with 2,000 employees, put real ownership behind capturing how the work gets done and built roughly 150 playbooks. Turnover dropped from 115 percent to 40 percent in a single quarter. That doesn't come from a binder nobody owns. It comes from a named person running the loop, week after week.
Name the role, or keep paying for the ghost
The company that names this role pulls away from the one that leaves it a ghost. If your process work keeps stalling, it's almost never a discipline problem. It's an ownership problem. The cost of the ghost never shows up as a line item, which is exactly why it's so easy to ignore, and so expensive to keep ignoring. See how we think about getting Process off the ground, give your owner the tools to run the loop, and if you've got the right person in mind, look at certifying them to own it so the knowledge stays in-house for good.
Jon LoDuca
founder
PlaybookBuilder
