The hidden cost of unclear ownership and approval

Ownership and approval are different things

It helps to separate two ideas that often get blurred.

Ownership means being responsible for moving a piece of work forward. The owner of a step does not have to do all of it personally, but they are the person who notices when it stalls and does something about it.

Approval means having the authority to say that a piece of work is acceptable and can move to the next stage. An approver might be inside the business, such as a senior designer reviewing a junior's work, or outside it, such as the client signing off a deliverable.

Problems appear when either is missing or shared so widely that nobody feels personally accountable. A step with three owners often has none. An approval that requires everyone's agreement often takes the longest to get.

Why shared responsibility tends to fail

Social psychologists have studied a related effect for decades. In a well-known 1968 experiment, John Darley and Bibb Latané found that people who believed they were the only witness to an emergency were far more likely, and quicker, to seek help than people who believed others were also present. They called this diffusion of responsibility: when responsibility appears to be shared, each individual feels less of it.

An office is not an emergency, and it would be a stretch to apply laboratory findings directly to a project team. But the pattern is familiar to anyone who has watched an unassigned task sit in a shared inbox. When a request is addressed to everyone, each person can reasonably assume someone else will handle it. Naming a single owner removes that ambiguity.

Making decision roles explicit

Management frameworks exist precisely to make these roles visible. The RACI model, common in project management, separates who is Responsible for doing the work, who is Accountable for it, who must be Consulted and who should be Informed. Bain and Company's RAPID framework, described by Paul Rogers and Marcia Blenko in a 2006 Harvard Business Review article titled Who Has the D?, focuses on decisions and insists that one person holds the final decision while others recommend, provide input, agree or perform.

You do not need to adopt either framework formally. Their shared lesson is enough: for every step and every decision, someone specific should hold it. Consultation is useful, but it should not be confused with authority.

Where the costs actually show up

The cost of unclear ownership is rarely a single dramatic failure. It is a steady accumulation of small waits.

Work waits between stages. A finished draft is not moving while it waits for review. If review responsibility is unclear, it waits longer.

People spend time coordinating instead of working. Every time someone asks who is handling this, they are doing coordination work that a clear assignment would have made unnecessary.

The founder becomes the bottleneck. In many small businesses the founder is the default approver for everything. That works with a handful of clients. With more, every project queues behind one calendar.

Clients wait too. Client approvals are often the slowest step in a project, especially when the business has not said clearly what it needs the client to approve, by when and what happens if they do not. Unclear client approval also leads to late feedback, which is the most expensive kind.

How to define ownership in practice

Start with your most common workflow, such as onboarding or a standard delivery cycle. List each stage in order. For each stage, write one name, not a team, as the owner. If you cannot choose one person, that is a sign the stage needs to be split into smaller steps.

Next, identify every approval point. For each, write who approves, what they are approving against and how long they normally have. Internal approvals should have a default turnaround. Client approvals should have an agreed window that is stated in writing at kickoff.

Then decide what does not need approval. Many approvals exist out of habit. If a project lead is trusted to manage a client, they can usually approve work that is within agreed scope and budget without escalation. Reserve senior or founder approval for changes in scope, price or risk.

Finally, make ownership visible where the work lives. When tasks and stages show their owner in the project view, people do not need to ask. When client-facing approvals happen through a defined channel such as a client portal rather than scattered email replies, it is clear what has been approved and when.

Designing client approvals well

Client approvals deserve special care because you cannot control the client's calendar. A few practices help.

Tell clients at the start of the engagement which approvals you will need, roughly when and how long you would like them to take. Ask who on their side is authorized to approve. A deliverable approved by the wrong person is not really approved.

When you request an approval, make it easy to give. State exactly what you are asking them to approve, what has changed since the last version and the date by which you need a response to keep the timeline.

Agree in advance what happens if an approval does not arrive. That might be that the timeline moves by the same number of days. Saying this kindly and early prevents awkward conversations later.

Ownership in a very small team

It is easy to assume that ownership only matters once a business has several employees. In practice, it matters as soon as two people touch the same client, including a founder and a part-time assistant, or a consultant and a subcontractor.

Small teams often rely on goodwill: whoever notices a problem fixes it. That works until both people are busy at once, which is exactly when problems are most likely. Writing down who owns each stage takes minutes and prevents the situation where each person assumes the other has replied to the client.

Ownership also matters when the owner is the only person in the business. A sole operator who writes down their own stages and approval points can see where work waits on them and where it waits on the client. That distinction becomes valuable the moment they hire help.

Keep ownership current

Ownership assignments go stale. People change roles, take leave or leave the business, and new services are added without anyone deciding who owns their stages. A brief review every quarter is usually enough. Look at each core workflow, confirm each stage still has a single named owner and check that the owner actually has the time and authority the role requires.

When someone leaves a role, reassign their stages explicitly on their last day rather than letting the work find a new owner on its own. Unassigned stages are where client requests go quiet.

Pay particular attention to stages that have quietly become shared again. They often show up in project reviews as the places where work waits longest.

A practical example

A professional services firm notices that its projects consistently finish two weeks late. On review, the work itself is not slow. The delays sit between stages: drafts waiting for partner review and deliverables waiting for client sign-off.

The firm makes three changes. Each stage gets a named owner. Partners agree to review within two business days and delegate approval of routine work to senior staff. Client approval windows are written into the kickoff summary along with the name of the client's approver. Within a quarter the waiting time between stages is the first thing the team checks in each project review, and it becomes visibly shorter.

In summary

Unclear ownership and approval cost time quietly, in the gaps between stages rather than in the work itself. Naming one owner per step, defining every approval point and delegating routine approvals removes a surprising amount of waiting.

If you want to see how this structure fits a specific type of business, the Professional Service Firms solution shows how one connected environment can support defined stages, owners and approvals.