One owner per number. Accountability the scorecard enforces.

One name, never two

A single owner enforces accountability by default. In every instance where I've seen two people, or "the team," own a number, it broke down — and usually the breakdown was a symptom of something deeper, a performance problem or an unresolved organizational question hiding behind the shared label. One owner is simply the better and simpler approach to both reporting a metric and owning it.

That readout question is the tell. The moment a number is co-owned, the basic mechanics get awkward — and the awkwardness is a signal that the accountability underneath is mushy too. More than one owner undermines the entire discipline of clear ownership, which is the whole point of putting a name on the number in the first place. If you can't name one person, you don't have an owner; you have a hope.

The owner owns the outcome — not necessarily the work

Ownership at the leadership level means owning the outcome, not personally doing every piece of the work. The owner might also be the doer, especially early on, but that's incidental. What matters is that one leader is ultimately responsible for the number and for all the results of the team they lead. They can — and should — delegate the activities. What they can't delegate is the answer to "how is this number doing, and what are you doing about it?"

That distinction keeps single ownership from feeling unfair. You're not saying one person must execute everything that moves the metric. You're saying one person is accountable for the result, owns the readout, and answers for the plan. The work spreads across the team; the accountability concentrates in a name.

The readout is the enforcement

Here's the mechanism that makes all of this real rather than theoretical: the owner reports their own number, every week, in the leadership meeting, in front of their peers and their bosses. That single ritual does an enormous amount of quiet work. It forces the owner to keep the number actually updated. It forces them to understand what's driving it red, yellow, or green. And it forces them to walk in with a point of view on any issue and a plan to correct course.

Picture the alternative you're trying to avoid: walking into the meeting with stale numbers, getting asked why something's red, and having nothing. No one wants to be that person on a Tuesday morning, week after week. That mild, recurring social pressure — the simple fact that you will be asked, by name, in public — is the engine of the whole system. The beauty isn't the metric alone, or the owner alone. It's the metric, the single owner, and the weekly readout working together.

Assigning it: along lines of responsibility

Who owns what is usually straightforward: ownership follows the lines of responsibility on your org chart. The head of sales or GTM owns the sales and marketing metrics; engineering owns the engineering metrics; success owns retention. The only numbers that need more thought are the ones that span multiple areas — a cross-functional metric like Net New MRR, which depends on both new sales and the success team's expansion and churn, naturally belongs to a co-founder or a leader who sits above both.

One honest caveat from our own scorecard: for years ownership was concentrated in just a few leaders, each holding a big block of the board. That's workable, but it's largely a function of company size. As the team grows, ownership should distribute outward — more names, each holding fewer numbers — so accountability lives closer to where the work actually happens, rather than piling onto two or three people at the top.

When the owner points elsewhere

It doesn't happen often, but sometimes a number's owner has a legitimate case that the cause lives in someone else's territory. A botched product launch with weak QA spikes the bug count and then floods support with tickets — is that support's number to answer for? Or pipeline coverage drops and sales points, fairly, at lead volume and quality coming from marketing. These are real interdependencies, not just excuses.

There are two ways through, and you usually need both. The first is the cadence itself: discuss and solve it openly as a team, in the room, instead of letting it calcify into a standing grievance. The second is org design. If two functions are so interdependent that ownership genuinely blurs — sales and marketing being the classic pair — the fix is often structural: put them under one leader, so a single person is accountable for the joined-up outcome. A chronic ownership dispute is frequently an org-chart problem wearing a metrics costume.

The cadence is the proving ground

Everything in this series leans on this one rule. Every metric on the scorecard, and every rock, issue, and to-do that comes out of it, gets exactly one owner. That's not coincidence; it's the same principle applied at every altitude of the system.

And the weekly cadence is where that principle stops being a poster on the wall and gets proven, over and over. The one-metric-one-owner rule, enforced by a readout in front of the team every single week, is what converts "we value accountability" into a habit people actually live. The relationship runs in one direction and it's worth stating plainly: break the one-owner rule, and your accountability will break along exactly the same lines. Keep it, and the cadence does the enforcing for you.