Know who decides before the choice becomes urgent.
A charter is one team’s editable account of its purpose, work, measures, authority, roles, and guidelines. Its decision rights answer four practical questions: who decides, who must be consulted, who needs to hear the result, and who carries it out.
Write those answers before the next urgent choice. People can move faster because they know where authority lives, and the people with useful knowledge still have a clear way to shape the decision.
You have 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 is not collaboration. It is 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, irreversible customer harm, or choice beyond a named limit can still move upward for a clear reason.
Write the rule once. Keep each decision that follows it.
The decision right describes a recurring class of choice. A decision record captures one real choice made under that right. You need both: the right tells a new colleague what they may decide next, while the records show how authority worked in practice. Particulars preserves both the constitution and the case law.
Right
Pricing exceptions above 15% are decided by the Commercial lead after consulting Finance and the account owner.
Record
On July 14, the Commercial lead approved an 18% exception for the Orion renewal after that consultation.
Route
The right tells everyone where to bring the next pricing exception and whose knowledge belongs in the choice.
History
The records show who decided, how long the choice took, and whether the same exception keeps escalating.
Give every recurring choice a route people can follow.
Name the choice and its limit
Suppose an account owner asks for an 18% discount. “Commercial strategy” gives the team a territory, but it gives the account owner no route. “Pricing exceptions above 15%” names a choice everyone can recognize when it arrives.
Give that choice to a role, such as Commercial lead, so the authority survives a leave or a handoff. Then write the limit. The role may approve the exception after consulting Finance and the account owner; a discount beyond 25% may move to a different right.
Clear limits make local authority easier to trust. The Commercial lead can move inside the range, and everyone can see where that authority ends.
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. The right can also say when those views are due, so silence loses its power to hold the choice forever.
Consultation changes the quality of the decision. The deciding role still owns the choice and its consequences. If Finance sees a contractual problem that belongs under another right, it can point to that boundary instead of quietly turning advice into a veto.
Other teams may only need the result before their work changes. Put that result in the decision record. Information should not require attendance.
Name who moves after the decision
The Orion choice only matters when someone updates the offer, tells the customer, and adjusts the forecast. Name the role that carries out the choice and the point when execution can begin.
Execution often includes smaller choices of its own. The account owner may decide how to explain the discount while the Commercial lead remains accountable for the exception itself. Writing that handoff prevents a recorded decision from sitting still.
The final record can stay short: the issue, the governing right, the people consulted, the choice, the reason, and the execution state. The team reads the authority once and uses it again for the next case.
A recurring right and the decisions made under it
Raise the issue, select the right that governs it, gather the required consultation, and record the choice with its reason and evidence. The result stays readable instead of disappearing into chat and calendar memory.
The feed shows how long choices take, which ones escalate, and whether the named role made the decision. People still make the choice; Particulars keeps the route and the result visible.
Find decisions stuck waiting for unnecessary approval.
Once rights and decisions live together, you can see where the route keeps breaking down. A recurring choice may have no written right. A consulted team may have become an approval gate. A decision may be complete while nobody owns the follow-through.
Particulars shows the stated right beside the evidence from each decision. You can inspect the pattern and decide whether to clarify the language, move the authority, shorten consultation, or leave a healthy exception alone.
The history also helps the next person who fills the role. They can see how the right worked in several real cases without turning one unusual choice into a permanent rule.
- Compare stated deciders with the people who actually decide.
- Distinguish healthy escalation from authority that routinely escapes.
- Notice a correct decision that arrived too late for the teams it changed.
“Healthy escalation has a clear reason and remains the exception, rather than becoming the normal path to authority.”
— The Particulars thesis