Who Owns a Process: Minimal Accountability for a Small Business

In a small business every step usually has somebody who performs it - but the process as a whole usually has nobody. That explains the familiar phenomenon: everyone did their part and the outcome still did not happen. The fix is not hierarchy but one name against the process.

The difference between the two

Row two is the critical one: when something falls between two steps, the step owners do not see it as their responsibility - rightly so. The person who sees it is the process owner, and when there is none, nobody does.

The four questions that define ownership

Per process, not per task:

1. Who is accountable for the outcome? - one name.
2. Who performs each step? - names, by step.
3. Who decides in a disagreement? - usually the same person as question 1.
4. Who needs to know it happened? - as short as possible.

That is all it takes. In a business of up to ten people, such a table for five main processes is written in an hour and covers most of what falls through.

What happens when the answer is "the owner"

In small businesses that is the common answer to question 1 across every process, and it is fine up to a point - but it is also what makes them the bottleneck. The expansion is in finding the bottleneck in your process.

The practical way out is not handing over every process at once but one: choose a complete process, give it to one person with authority, and do not interfere for a month. What decides it is not the announcement but the restraint - an owner who keeps approving every step has in fact handed over nothing.

What a process owner needs

• Authority to decide within defined limits, not just responsibility.
• Access to information - visibility across every step.
• Time in their calendar, not "on top of everything else".
• One metric measuring the outcome, not the effort.
• A stated mandate - the team knows they decide.

The first is the most commonly withheld: responsibility given without authority, leaving the accountable person chasing approvals. That is worse than appointing nobody, because they carry accountability for an outcome they cannot influence. Defining the authority itself is covered in approval limits and controls.

What it looks like in practice

Take an "order to dispatch" process. Step owners: whoever takes orders, whoever picks, whoever hands to the courier. Process owner: one person accountable for an order received on Sunday going out on Monday.

What changes with a process owner: when something is stuck, somebody decides what to do; when something falls twice, somebody asks why; and when something needs changing, somebody is authorised. Without an owner, each of those situations ends in a group conversation with no decision.

Note that the process owner is not necessarily whoever performs the most work. In this case it may well be whoever takes the orders - they see when it arrived, they are who the customer will ask, and they will know first when something did not go out. Proximity to the outcome matters more than share of the work.

How ownership changes what you measure

Once a process has an owner, it can finally be measured end to end rather than by steps. The difference is large: step-level measurement shows every step meeting its target while the overall outcome is late - which is exactly what happens when the waiting between steps is measured by nobody.

The metric a process owner needs is a single one, and it is always about the outcome: how long from end to end, or what share of cases met the target. Once it exists the conversation changes - instead of establishing who is to blame for a delay, you can ask where the time is going. The full method for locating that is in finding the bottleneck in your process.

What not to do

• Do not appoint a committee. Two accountable people are zero accountable people.
• Do not allocate by hierarchy but by who genuinely sees the process.
• Do not add complex tables with four levels of responsibility.
• Do not appoint without delegating - responsibility with no authority is a trap.

The first surprises people: in small businesses it is common to appoint two "for cover", and that is exactly what produces the state where each assumes the other handled it.

How do you know a process has no owner?

By four signs that are easy to spot. A recurring question - "who is supposed to handle this?" asked more than once a week about the same kind of case. Fixes without learning - the same fault recurs and nobody changes anything, because changing it is nobody's responsibility. Decisions that stall - every small change needs a meeting. And contradictory reporting - two people give different answers to where something stands.

The second is the most serious, because it means the process never improves. A step owner fixes the case in front of them; only a process owner asks why it happened again.

What happens when you appoint an owner for the first time

Three things, all predictable. First, they discover the process differs from what everyone assumed - which is good, because it is the start of a real map. Second, they hit the limits of their authority in the first week, usually around spending or a customer. And third, part of the team keeps going to the owner out of habit.

All three resolve the same way: redirect. When the owner answers "ask whoever is accountable" three times, the message lands - faster than any announcement. It is also worth giving the process owner a first month with no expectation of measurable improvement; what they do in it is mostly understand what actually happens.

Sources

• How to improve business efficiency
• Israel Tax Authority - information for businesses