Two People Accountable Means Nobody Is

Every matrix I've been handed with two accountable names in the same row was a peace treaty. Somebody senior wouldn't back down, somebody else wouldn't either, and putting both names in the cell let everyone leave the room without a fight. That fight didn't go away. It got scheduled for later, at the worst possible moment, with a deadline attached.

I understand why it happens. You're facilitating, the room is tense, and the security architect and the cloud lead both have a defensible claim on the same deliverable. Writing both names looks like diplomacy. It feels inclusive. It is also, quietly, you refusing to do your job, which in that moment is to decide who carries the thing and tell the other person why.

Shared accountability sounds noble in a values deck. On a live project it behaves exactly like unowned work. When a call needs making, each of the two named people does the reasonable thing, which is to check with the other one first. Neither wants to be the person who overrode a peer. So the decision sits in the space between them, and the space between two senior people is the slowest medium known to delivery.

The tell is easy to spot once you know it. Ask who decides if the two of them disagree. If the answer is "they'd work it out", you don't have two owners. You have a queue.

A 15-person cloud team at an energy supplier rolling out a new API gateway. The row on the matrix read "gateway policy configuration", and it carried two names: the cloud lead who was building the thing, and the security architect who owned the standards it had to meet. Both excellent. Both reasonable people. Both, in the words of the delivery manager, "jointly accountable".

Week 5, a question comes up that nobody planned for. The default rate limit will throttle a partner integration that does bulk overnight meter data pulls. Somebody has to decide whether the partner gets an exemption or the partner changes their batch behaviour. It's a ten minute decision for one person with authority.

It took nine days.

The cloud lead raised it with the security architect, who was on leave until Wednesday. On Wednesday she asked for the traffic profile, which took two days because the person who had it was doing something else. Then she said she was comfortable with an exemption if the cloud lead was comfortable with the audit trail, which the cloud lead read as "not my call", so he put it on the agenda for the following week's design forum. The design forum ran out of time. The partner escalated through their account manager, which meant it reached a director, which meant the two of them then spent an afternoon writing a note explaining why it had taken nine days.

Nothing in that story is incompetence. Every individual step is what a sensible person does. That's the point. Joint accountability produces slow, defensible, entirely reasonable behaviour, and slow is what kills you.

The other cost is less visible. For those nine days, the delivery manager's status report said the gateway workstream was green, because nobody was blocked in a way they could name. Two people waiting politely for each other doesn't look like a blocker. It looks like progress until the week it doesn't.

This is a conversation, and it's a short one. Do it privately, before the workshop, never in front of an audience. Something close to this:

"You're both on this row. I'm going to put one name in it, because when this gets contested at 6pm on a Thursday I need one person who can say yes without a meeting. I'd like it to be you. Here's what I want to protect for you: any policy that changes the standard needs your sign-off, and you can stop a release on that basis. But the day to day calls are hers."

That's the shape. One name accountable, and the other person gets something specific and real in exchange: a veto on a named dimension, a consultation that has to happen before a defined class of decision, an escalation route straight to the sponsor. Consulted is not a demotion when it comes with teeth. It's a demotion when it's a word you used to avoid a conversation.

Two things make this land. First, name what the other person actually cares about, out loud, before they have to defend it. Most ownership arguments aren't really about ownership. They're about someone being worried that a thing they're responsible for will get quietly traded away by somebody who doesn't feel the consequences. Address that and the argument usually evaporates.

Second, be willing to be wrong in public. Say that if the split turns out to be the wrong way round, you'll change it at the next review and you'll say why. People will accept a decision they disagree with far more easily than they'll accept a decision that can never be revisited.

And if you genuinely cannot choose, because the two claims are equally strong and you don't have the standing to pick, that's not a reason to write both names. That's a reason to escalate. Take it to whoever those two people both report into, with your recommendation already written, and ask them to confirm it. Five minutes of someone else's time now, or nine days of yours later.

Go through your matrix and find every row with more than one accountable name. Not responsible, that can be shared all day. Accountable.

For each one, before Friday, write this sentence and send it to both people:

"On [deliverable], [name] decides. [Other name] signs off on [specific dimension] and can hold a release on that basis. If either of you thinks that's the wrong way round, tell me by Wednesday and I'll change it."

Then put it in the matrix, with the date. If you're not willing to send that sentence, you've learned something useful: the reason there are two names in that cell is that you haven't decided yet, and the project is waiting on you.