What does owning a process actually mean?
It does not mean doing the work. It means four specific things. You decide what the standard shape of the job is. You approve any change to that shape. You watch one or two numbers that tell you whether it is still working. And you are the person asked when it breaks.
Put like that, most firms discover something uncomfortable. They can name who does every step of a process. They cannot name who decides how the steps fit together. For work that sits inside one team, the team leader usually fills that gap by default. For work that crosses teams, there is no default, and the gap stays open for years.
Why do cross-department processes end up with no owner?
Take taking on a new client. A fee earner agrees the work. An administrator opens the file and sets up the folder. Someone runs identity and conflict checks. Finance sets the billing arrangement and the rate. Marketing adds the name to a list. A partner signs the engagement letter.
Every one of those steps has an owner. The path between them has none. And the delay almost never lives in the steps. It lives in the hand-offs: the form that sits in an inbox, the check that waits on a document nobody chased, the engagement letter drafted from a template that finance changed six months ago and nobody told the fee earners. The hand-off belongs to nobody, so nobody fixes it.
The structural reason is simple. An organisation chart runs vertically and work runs horizontally. Accountability follows the chart. The work crosses it. Client onboarding is the clearest example, but the same pattern shows up in billing, in bid production, in complaints handling and in anything where a document travels between a fee earner, an administrator and a reviewer.
How can you tell a process has no owner?
The signs are consistent across firms:
- Nobody can produce a current description of how the job is done. There is a document, but it was written for an accreditation and nobody has opened it since.
- Three people describe the process three different ways and all three are right about their own version. That is the pattern behind twelve ways of doing one job.
- The last person who changed anything has left the firm.
- When something goes wrong, each department can explain why it was the other department's part.
- Ask "who decides?" and you get a pause, then a name, then a qualification about how it depends.
None of these feels like a crisis. That is the point. An ownerless process does not fail loudly. It thickens.
Why does the absence of an owner cost money so quietly?
Because steps only ever get added. Something goes wrong once, so a check is introduced. A client complains, so a second approval is inserted. A new regulation lands, so a form appears. Each addition is sensible on the day it is made.
Removing a step is different. Removal requires someone to judge that the risk it guards against is no longer worth the time, and to carry that judgement if it turns out to be wrong. Nobody takes that on without authority. So the ratchet turns one way and the process gets heavier every year, which is why templates and forms accumulate the way they do. Templates rot for the same reason: no one is responsible for the whole of them.
The cost shows up in places nobody attributes to process design. Bills raised late. Work in progress sitting unbilled because a step stalled and no one was watching the path, which is the mechanics behind billing delay. Fee earners doing administrative chasing at their charge-out rate. You can put a figure on that with the unbillable hours calculator, though most firms have never looked.
Isn't the managing partner the owner by default?
No. The managing partner is accountable for the firm, which is not the same as being accountable for how new matters get opened. Spreading accountability over everything is how it ends up attached to nothing.
A rebuild that has a sponsor but no owner works beautifully for a quarter and then drifts back, which is exactly the pattern described in what good looks like after go-live.
Who should the owner be?
Four tests, in order of usefulness.
- They feel the pain. If the process breaks, their week gets worse. Appointing someone who is insulated from the consequences produces a name on a page and nothing else.
- They are close to the work. Close enough to know which exceptions are real and which are habit. That is frequently an operations manager or a senior administrator rather than a partner.
- They have authority to change the template. Granted explicitly, in front of other people. Ownership without decision rights is just chasing.
- They are likely to still be here next year. Continuity matters more than rank.
Seniority appears only in the third test, and then only as something the partnership grants. This is a different appointment from choosing who leads AI in a firm. That role is about change. This one is about custody.
Why can't you rebuild a process nobody owns?
Because a rebuild is a sequence of decisions, and decisions need a decider. Which of the existing versions becomes the standard. Which exceptions get designed in and which get handled by hand. What the output should contain. Who approves it before it reaches a client.
Without an owner, one of two things happens. The project stalls while everyone consults everyone, and the thirty days turn into six months of workshops. Or the build follows whoever was loudest in the room, and the people who were not in the room carry on as before. Either way the firm has paid for something it does not use.
With an owner, the questions get answered in the week they are asked. That is most of why some rebuilds land and others do not. Before any of it, documenting how the process actually runs today is the owner's first real task, and the first honest test of whether they have the authority they were given.
What should a managing partner do this month?
List the processes that cross a departmental boundary. In most firms of this size there are fewer than ten that matter: taking on clients, raising bills, producing proposals, reporting to clients, handling complaints, closing files.
Put one name against each. Not a committee, not a department, one person. Tell them what they can change without asking. Agree one number each will watch and a date each quarter when they report it. That is the whole of it: one page, no software, no programme.
Then pick the one that hurts most and fix it properly. The process priority scorer will rank them against each other, and the audit will tell you where the hours are actually going before you choose.