Decision-making glossary
Team rulebook
A team rulebook is the set of rules a team is working by today, each with an owner, the date it was decided, the reason and the rule it replaced. Unlike a handbook, every rule is a recorded decision, so anyone can see who decided it and when, and an old rule is replaced, not left in place.
Most teams already have rules: who approves overtime, what a refund limit is, how a customer is told about a delay. They live in a handbook, in old email threads and in people’s heads, and they change without the handbook changing. The usual symptom is a question nobody can answer quickly: what is the rule, and who decided it?
A rulebook treats each rule as a decision with a record behind it. The record gives the rule’s wording, its owner, the date, where it was recorded and what it replaced. Rules are grouped by area, such as safety, quoting or hiring, and an area can have one owner who decides when no rule exists yet.
A rulebook is not a policy library or a procedure manual. It holds the rules, not the long explanations of how to follow them, so the two work together: the handbook explains, the rulebook says what is currently in force. The common failures are rules with no owner, rules nobody has checked in years, and two rules that contradict each other.
In Decize: Decize’s Rulebook page lists the decisions in force today by area, and anyone can ask what the rule is in the app, by email or in Slack. You can also import rules from a handbook. See how →
Free template: Team rulebook template
Sources: Google re:Work, “Understand team effectiveness” (structure and clarity)