Know who decides before the choice becomes urgent.

01The approval reflex

You’ve been in the meeting where nobody knows who can decide.

A familiar question comes up. Several teams care about the answer, but nobody can point to the person or role that owns the choice. The invitation list grows. A manager joins because the choice feels important. An adjacent team joins in case its work changes. An executive joins because everyone wants cover.

The meeting ends with alignment. The practical choice stays fuzzy until somebody senior repeats the consensus. This isn’t collaboration. It’s an authority-discovery ritual. Soon local choices rise by habit, consultation feels like approval, and people attend meetings just to learn what happened.

A written decision right gives the next case a route. Ordinary choices stay with the team closest to the work. A contractual risk, an irreversible customer harm, or a choice beyond a named limit can still move upward, for a clear reason.

02The distinction

Write the rule once. Keep each decision that follows it.

A decision right describes a recurring kind of choice. A decision record captures one real choice made under it. The right tells a new colleague what they may decide next. The records show how authority worked in practice. You need both: the constitution and the case law.

03Three principles

Give every recurring choice a route people can follow.

1. 1

   Name the choice and its limit.

   An account owner asks for an 18% discount. “Commercial strategy” gives the team a territory but gives the account owner no route. “Pricing exceptions above 15%” names a choice everyone recognizes when it arrives. Give it to a role, like Commercial lead, so the authority survives a leave or a handoff. Then write the limit: beyond 25%, a different right applies. Clear limits make local authority easier to trust.

2. 2

   Give advice a deadline.

   For the Orion exception, Finance checks margin and the account owner explains the customer risk. The Commercial lead has to ask for both views, and the right can say when they’re due, so silence loses its power to hold the choice forever. The deciding role still owns the choice. If Finance sees a contractual problem, it points to that boundary instead of quietly turning advice into a veto.

3. 3

   Name who moves after the decision.

   The choice only matters when someone updates the offer, tells the customer and adjusts the forecast. Name the role that carries it out and when execution can begin. The final record can stay short: the issue, the governing right, who was consulted, the choice, the reason, and where execution stands.

04In Particulars

A recurring right, and the decisions made under it.

Raise the issue, pick the right that governs it, gather the consultation it requires, and record the choice with its reason. People still make the call. Particulars keeps the route and the result where everyone can read them.

Illustrative team. The right describes the route; the record shows whether the choice followed it.

05What becomes possible

Find the decisions stuck waiting for approval nobody needs to give.

Once rights and decisions live together, you can see where the route keeps breaking down. A recurring choice has no written right. A consulted team has quietly become an approval gate. A decision is made, and nobody owns the follow-through. Then decide what to do: clarify the language, move the authority, shorten the consultation, or leave a healthy exception alone.

• Compare who the charter says decides with who actually does.
• Tell healthy escalation from authority that routinely escapes.
• Catch the right decision that arrived too late for the teams it changed.

“Healthy escalation has a clear reason, and stays the exception rather than the normal path to authority.”

The Particulars thesis