Who owns what: assigning responsibility so work actually moves

The gap between "the team handles it" and a name

Ask who is responsible for onboarding a new client and you will often hear a team name: sales, operations, the delivery side. Ask who specifically, and the answer becomes vaguer. That vagueness is expensive. When a task belongs to a group, it belongs to nobody, and it moves only when someone notices it is stuck.

Ownership is not a formality. It is the mechanism that turns intention into finished work. A business can improve more from naming responsibilities clearly than from most process initiatives, and it costs an afternoon rather than a budget.

Three things people confuse

When work goes wrong, the post mortem often reveals that responsibility, authority, and accountability were split between different people without anyone deciding that.

Responsibility is doing the work. Many people can be responsible for parts of a deliverable.

Accountability is answering for the result. One person, always. If a deliverable has two accountable people, it has none, because neither will escalate when it slips.

Authority is the power to decide. If the accountable person cannot make the decisions the work needs, they are accountable for a result they do not control. This is the most common structural fault in growing companies, and it produces exactly the behaviour you would expect: people stop committing to dates and start hedging.

A useful rule: for any important deliverable, one name is accountable, that person has the authority they need to reach the outcome, and everyone else knows who it is.

Start at the level of deliverables

The classic temptation is to map every task to a person. This produces a matrix that is out of date within a week and is never consulted.

Work at the level of deliverables instead: things with a beginning and an end that someone can look at and judge. For a client project that might be the signed scope, the completed design, the trained team, the live process. For an operations team it might be the monthly report, the supplier review, the staffing plan. Keep the list to somewhere between ten and thirty items for a team, and revisit it when the work changes shape.

For each deliverable, record:

• One accountable person. Not a department, not a pair.
• Who does the work, if it is different, and whether anyone else must be consulted before sign-off.
• What "done" means, in a line. Not a full specification, just the test someone would use to accept it.
• The decisions that belong to this deliverable, and who makes them.

That fourth column is what makes the list useful rather than ceremonial. Most friction happens around decisions, not tasks.

The matrix is optional; the conversation is not

There are several well-known ways to present this: a responsibility matrix, a simple table, a page per team, a set of role cards. The format matters far less than the fact that the conversation happened and that the outcome is written where people can find it.

If you use a matrix, keep it readable. Deliverables as rows, roles as columns, and the smallest set of symbols that still carries meaning: who is accountable, who does the work, who must be consulted. Resist the temptation to add four more codes that nobody remembers.

If you have never done this exercise, run it as a working session with the people who do the work. Ask, for each deliverable, "who would we call if this were stuck at five o'clock on a Friday?" The answer is usually obvious in the room and surprising on paper, which is exactly the point of writing it down.

Define decision rights explicitly

Ownership of work without ownership of decisions is a trap. For each area of the business, write down the handful of decisions that recur and who makes them:

• Who can commit to a delivery date that a client will rely on?
• Who approves spending above a stated threshold?
• Who decides a process change that affects another team?
• Who resolves a disagreement between two functions?
• Who can say no to a new request when capacity is full?

Keep it to a page. Include the escalation route: if the decision-maker is unavailable or the decision is genuinely contested, who decides? A named escalation path prevents the slow drift of unresolved questions into group chats.

One caveat that matters in practice: decision rights should be pushed down as far as competence allows. Every decision that must travel upwards adds delay and removes the local judgement that makes teams fast. Reserve escalation for genuine trade-offs between functions or levels of spend, not for routine calls.

Handle the awkward seams

Most ownership problems sit at boundaries: between sales and delivery, between two teams sharing a system, between a client's process and yours. These seams deserve specific attention because the default outcome is a gap or a duplication.

For each seam, name:

• The point at which the work changes hands.
• What must be true before it can cross: what is handed over, in what form, accepted by whom.
• Who is accountable on each side.

A handover that is defined in a sentence ("delivery accepts the signed scope and completed intake form") prevents weeks of reconstruction later. Where the same step is being done twice by two teams, one of them is redundant, and the fix is usually to name a single owner for the shared step.

Expect resistance, and be precise about why it is happening

Some resistance is reasonable. People worry that a name next to a deliverable is a target painted on their back. The answer is to separate accountability from blame: accountability is about clarity in advance, not punishment afterwards. Naming an owner is what allows someone to escalate early without feeling they are admitting failure.

Some resistance comes from overlap: two people genuinely believe they own the same thing. That is a decision for their manager to make, and it is better made in a room than discovered during a deadline.

Some resistance comes from authority that was never granted. If a person is accountable for a result but cannot get the resources or decisions required, the fix is structural, not motivational.

Keep it current

An ownership map decays quietly. People leave, roles split, new services appear. Two lightweight habits keep it honest: review it whenever a role changes, and once a quarter, ask the team whether the list still matches how work actually flows. Adjustments are usually small and take minutes.

A short test

Pick any important piece of work happening this week. Can you name the one person accountable for it, the decisions they are entitled to make, and what "done" means? Can they?

If two people answer those questions differently, you have found the cheapest available improvement in your business.