A new lead comes in through the website form. The CRM creates the contact. An automated email goes out. And then, for nine days, nothing happens.
Nobody ignored the lead on purpose. The sales team assumed marketing would nurture it. Marketing assumed sales would reach out. The automation did exactly what it was built to do, and stopped, because nobody had been asked to build what comes next. When someone finally noticed, the lead had gone elsewhere, and the post-mortem turned up an uncomfortable answer: nobody was responsible for that step.
Most process problems aren’t caused by bad tools or careless people. They’re caused by steps that nobody clearly owns. And there’s a simple way to find them.
What the “Who Owns This?” Test Is
The test is one question, asked about every step in a process: who is responsible for making sure this happens?
Not who usually does it. Not who could do it. Not who was told about it once. Who, by name or by role, is accountable for this step happening, happening correctly, and being fixed if it doesn’t?
It sounds almost too simple to be useful. But the answers are often surprising, because most businesses have never asked the question step by step. They’ve asked it about projects and about departments, but rarely about the small moments inside a workflow where things actually slip.
Why Gaps Form in the First Place
Gaps rarely appear because someone decides to leave a step unassigned. They appear because processes grow in pieces. A form gets added by one person, an automation gets built by another, a follow-up task gets created by a third. Each piece makes sense on its own, and each person assumes someone else is covering the space between them.
Handoffs are the most common place for this to happen. A step that’s clearly owned on one side of a handoff and clearly owned on the other can still leave the moment of transfer itself owned by no one. The lead is the marketing team’s until it’s the sales team’s, and in between, it belongs to nobody.
The Real Cost of Unowned Steps
Unowned steps fail quietly. Since nobody is responsible for them, nobody notices when they stop working, and nobody feels the need to check. A broken automation, an unanswered inquiry, or a report that stopped being sent can go unnoticed for weeks.
The cost isn’t only the individual failure. It’s the pattern. When a process has hidden gaps, the team learns to work around them with informal habits and personal reminders, which means the process only works when the right people happen to remember. That’s a fragile way to run anything, and it gets more fragile as the business grows or when someone changes roles.
Step 1: Pick One Process and Define Where It Starts and Ends
Don’t try to audit the whole business at once. Choose a single process that matters, such as new lead follow-up, client onboarding, invoicing, support requests, or content publishing, and define its boundaries. Where does it begin? What counts as finished?
A clear start and end keep the exercise manageable and make it much easier to spot what falls in between.
Step 2: List Every Step, Including the Small and Automated Ones
Write out each step in order, in plain language. Include the steps that happen automatically, the steps that happen in someone’s head, and the steps that only happen “if someone remembers.” These smaller, less visible steps are exactly where gaps tend to hide.
If your process includes automations, list those too: what triggers them, what they do, and what happens after they finish. An automation is a step like any other, and it needs an owner just as much as a human task does.
Step 3: Ask “Who Owns This?” About Each Step
Go down the list and ask the question about every step. Write the answer next to it, and be strict about what counts. “The team” is not an owner. “Whoever’s available” is not an owner. “Probably Sam” is not an owner until Sam has agreed to it.
A real owner is a specific person or role who knows they’re responsible, has the access and authority to act, and would be the one expected to notice if something went wrong.
Step 4: Sort the Results Into Four Patterns
Once the list is filled in, the gaps tend to fall into four recognizable types:
- No owner. Nobody is responsible. These are the most obvious gaps, and often the most costly.
- Too many owners. Two or three people each assume they’re responsible, or each assume the others are. This leads to duplicated effort at best, and everyone waiting for someone else at worst.
- A hidden owner. Someone is doing the work, but nobody else knows it, and it isn’t documented. The process works until that person is out or moves on.
- The wrong owner. The step belongs to someone who lacks the access, context, or authority to do it well, or to someone for whom it’s a distant priority.
Naming the type matters, because each calls for a different fix.
Step 5: Look Closely at the Handoffs
Pay special attention to every point where work moves from one person, team, or tool to another. For each handoff, ask who is responsible for the transfer itself. Who makes sure it happened? Who finds out if it didn’t?
Many of the most damaging gaps live in these seams. A lead that moves from marketing to sales, a signed contract that moves to onboarding, and a support ticket that moves to a specialist are all moments where work can quietly fall between two clearly owned stages.
Step 6: Ask What Happens When the Owner Is Out
An owner who exists on paper but can’t act when they’re away is only a partial answer. For each critical step, ask what happens if the owner is on vacation, sick, or no longer with the company. Is there a backup? Is the step documented well enough for someone else to pick it up?
You don’t need elaborate coverage for every task. But for the steps where a delay would affect customers or revenue, there should be a clear answer.
Step 7: Assign, Document, and Make It Visible
For every gap you found, make a deliberate decision: assign an owner, simplify a step to remove duplication, or retire a step that no longer needs to exist. Then write it down somewhere the team can see it, even if that’s just a simple shared document listing each step and its owner.
Visibility is part of ownership. A person who has been assigned a step but whose responsibility isn’t recorded anywhere is only one reorganization away from being a hidden owner again.
Step 8: Build in a Way to Notice When a Step Fails
Ownership isn’t only about doing the work. It’s about noticing when the work doesn’t happen. For each owned step, consider how the owner would find out if it stalled. For automated steps, that might be an alert or a regular check. For human steps, it might be a task queue or a weekly review.
An owner who has no way of knowing something went wrong is an owner in name only.
Step 9: Repeat the Test When Things Change
Ownership gaps reopen whenever the business changes: new hires, departures, new tools, new automations, restructured teams. Running the test on your most important processes once or twice a year, and any time something significant changes, keeps small gaps from becoming expensive ones.
A Quick Version You Can Run Today
If you only have fifteen minutes, take one process and answer these questions:
- What are the five most important steps, and who owns each one?
- Is there any step where you hesitated before answering?
- Where does work move from one person or tool to another, and who owns that moment?
- If the person who owns the most critical step were out for a week, what would happen?
- If the most important automation in this process stopped working tonight, who would notice, and how soon?
The hesitations are the gaps.
The Bigger Lesson: Clear Ownership Is What Makes a Process Reliable
It’s tempting to think reliable processes come from better software or tighter rules. Those help, but they rest on something simpler: people knowing what they’re responsible for. A well-built automation with no owner will eventually fail without anyone noticing. A modest process with clear ownership will usually catch and fix its own problems.
The goal isn’t to add bureaucracy. It’s to remove ambiguity, so that nothing important depends on someone happening to remember.
The Takeaway
Most process failures trace back to steps that nobody clearly owns. The “Who Owns This?” test asks one question about every step: who is responsible for making sure this happens? Run it on one process at a time, list every step including the automated ones, sort the gaps into no owner, too many owners, hidden owner, and wrong owner, look hard at the handoffs, and make sure each owner has backup coverage and a way to notice when something stalls.
Do this consistently, and the gaps stop being something you discover after a customer is lost, and become something you find on a quiet afternoon, with time to fix them.
At Kujenga, we build automated systems and map the workflows behind them, so every step in your process, from lead capture to follow-up, has a clear purpose and a clear owner.
If you suspect there are steps in your process that nobody is really responsible for, let’s walk through it together and find them.
