An org chart says where people sit. It doesn't say who decides.

Two charts, two different questions

A reporting line answers where do I sit. It is about management: who runs your one-to-ones, who signs your leave, who you escalate to. It is genuinely useful and it is not what you're looking for when a release slips.

An accountability chart answers what do I own. Same team, same boxes, different thing written on them: for each piece of work your team is on the hook for, which role owns it and which single role decides it. Those two charts disagree far more often than anyone expects. Work migrates to whoever is good at it, and the reporting line stays where it was drawn.

Many hands is fine. Two deciders is not.

The instinct when something is going badly is to count how many people are involved and conclude there are too many. That is almost never the problem. Five people working on onboarding is five people working on onboarding.

What breaks a team is two people who each believe they decide it. Nothing feels wrong day to day — both are reasonable, both are senior, both defer a bit. Then something has to be settled quickly and the disagreement arrives all at once, with a deadline behind it.

Which is why the useful finding is never this has two owners. It is nobody has said who decides this. The first is a judgement about your people. The second is a sentence you can go and write today.

When the decider isn't on your team

Some of the work your team is measured on is decided somewhere else. Pricing sits with finance. The release date sits with platform. The brand rules sit with marketing. This is the single most common thing a leader discovers when they write the chart down, and it is constantly mistaken for a gap in the team.

It is not a gap, and hiring will not close it. What it needs is an agreed path: who you ask, roughly how long it takes, and what happens when the answer is no. Naming the department is what turns an unexplained delay into a conversation someone can actually have.

The same goes the other way. Every piece of work that crosses out of your team — a decision made elsewhere, or a handover to another department — is an obligation somebody has to honour. Count them once and you usually find more than you expected.

You don't need a framework for this

There are good ones. RACI, DACI, the accountability chart out of EOS, whatever your company already runs — if you have one, keep it, and skip this section. It will answer more than what follows.

If you don't have one, do not go and adopt one first. Naming decision roles is a company's own way of organising, and asking a team to learn a vocabulary before they can read their own chart is work that helps nobody. Two facts per piece of work get you most of the value:

• Who works on it. As many people as it really takes. This number is information, never a verdict.
• Which one role decides it. Exactly one. If you cannot name it, you have found something.

Note that both of those attach to a role, not to a person. Write “the platform lead decides the release date” rather than a name, and the sentence survives a promotion, a parental leave and a resignation. Write the name and you rewrite the chart every time someone moves.

How to actually write one

An hour, on your own, before you take it to anyone:

• List what your team is on the hook for. Standing things, not dated ones — “billing and payments”, not “billing live by November”. Eight to fifteen is normal.
• Against each one, name the role that decides it. Not the people involved — the one role that says yes.
• Mark the ones you couldn't answer. That list is the point of the exercise. It is usually short and it is usually the same things that keep coming back to you.
• Mark the ones where the answer was another department. That list is the second point of the exercise.
• Now show it to your team, one to one. What you are checking is whether they would have written the same thing. Where they wouldn't, you have found the disagreement early, which is the only time it is easy to settle.

Do this before you write a job description, not after. A role whose scope nobody wrote down is the one that takes two quarters to work out after the person starts — and that is unfair to them before it is expensive for you.

Where Ygora fits

Ygora stress tests what you have been asked to deliver. You say what it is and by when, then answer plain questions about what exists and who owns it — including the ones on this page. Does every deliverable have one role that decides it. Is it written down which decisions you wait on from other teams, and which they wait on from you. Is anyone outside your team deciding something you are measured on.

What comes back is what it takes, in three lists: what is yours to do, what needs somebody else, and what is outside your reach and worth saying out loud at the start of the period. From the answers it drafts the team charter — the page that says who decides what, so you are not holding it in your head. No scores, no benchmarks. Nobody sees any of it until you decide to show them.

Questions we get about this