Skip to content
Home » The Decision Rules Every Leader Should Write Down

The Decision Rules Every Leader Should Write Down

Leader writing decision rules on a whiteboard during a team meeting

Leadership decision rules are short, written statements that define who decides, which criteria matter, when to escalate, and when to stop. Writing them down prevents recurring choices from consuming fresh attention every time and gives your team a consistent basis for action.

You made one call on Monday, then handled a similar request differently on Friday. Now your team is comparing answers, asking for exceptions, and wondering which version applies. Written rules help you reduce that confusion, protect decision quality under pressure, and delegate routine choices without losing control.

Why Do Unwritten Decision Rules Cost So Much?

Unwritten rules force you and your team to reopen decisions that should already be settled. The cost appears in repeated meetings, inconsistent answers, delayed work, and unnecessary escalation.

A McKinsey & Company survey of 1,259 participants found that only 20 percent said their organizations excelled at decision-making. Sixty-one percent said most of the time devoted to decisions was used ineffectively. The same research found that decision speed and quality don’t always conflict. Organizations with sound decision practices can move quickly without accepting weaker choices.

Decision fatigue also changes how you respond as the day progresses. A request that receives careful analysis in the morning may receive a rushed answer later, even when the facts are similar. Written leadership decision rules reduce the amount of interpretation required for routine calls. You preserve your attention for decisions involving unfamiliar risks, major commitments, or competing priorities.

Unwritten rules also create political behavior. Team members learn whom to ask, when to ask, and how to reframe a request after receiving an unfavorable answer. A written rule shifts the discussion from personal influence to agreed criteria. That improves leadership consistency and makes exceptions easier to identify.

What Is a Decision Rule and What Is It Not?

A decision rule is a clear instruction that connects a recurring situation with a defined action. It isn’t a detailed procedure, a vague value statement, or a substitute for judgment.

A value may say, “Protect customer trust.” A usable rule goes further: “Escalate any decision that could create a lasting customer commitment the team cannot reverse.” The first statement describes an aim; the second guides action. Your strongest rules translate priorities into observable thresholds, ownership boundaries, or trade-offs.

Decision rules also differ from standard operating procedures. A procedure explains how to complete a known task, often through a sequence of steps. A rule tells someone how to choose when several actions are available. Procedures create repeatability in execution, and rules create consistency in judgment.

Good rules leave room for exceptions, but they don’t hide behind vague language. “Use good judgment” isn’t a usable rule because it provides no shared test. “Escalate when the downside exceeds your approved budget or affects another department” gives the decision owner a boundary. Specific wording lets your team act without waiting for permission on every routine matter.

Which Leadership Decision Rules Should You Write Down?

Write rules for recurring decisions involving ownership, reversibility, spending, escalation, evidence, trade-offs, and stopping conditions. Start with choices that repeatedly consume leadership attention or produce inconsistent answers.

  • Ownership rules: State who can decide and who provides input.
  • Reversibility rules: Allow faster action when a choice is inexpensive and easy to undo.
  • Threshold rules: Define the money, time, risk, or customer impact that requires approval.
  • Escalation rules: Identify the conditions that move a decision to a higher level.
  • Evidence rules: Set the minimum information needed before a decision proceeds.
  • Trade-off rules: Explain which priority wins when goals conflict.
  • Stopping rules: Establish kill criteria for ending work that no longer meets its purpose.

Your delegation rules should give decision authority to the closest qualified person who can see the relevant facts. That person needs a defined operating boundary, not unlimited freedom. A rule could authorize a manager to approve reversible purchases below a set amount without a meeting. Larger commitments, hard-to-reverse choices, or decisions affecting several teams can require added review.

Your escalation rules should describe triggers rather than personalities. Avoid rules that depend on whether someone feels uncomfortable or believes a matter looks important. Use observable conditions: the decision exceeds an approved limit, creates an external commitment, affects another team’s resources, or carries a downside the owner cannot absorb. These thresholds reduce unnecessary escalation without blocking legitimate concerns.

Stopping rules deserve special attention because teams often find it easier to start work than end it. Define what evidence would cause you to pause, change, or cancel an initiative before enthusiasm and sunk costs take over. A stopping rule can refer to missed milestones, unavailable resources, failed assumptions, or benefits that no longer justify the cost. Setting kill criteria early makes later review more disciplined.

How Do You Turn a Repeated Decision Into a Written Rule?

Start by identifying a choice that has appeared at least twice, then capture the conditions, criteria, owner, action, and exception path. Write the rule in language a new team member could apply without a private explanation.

Review recent meetings, approval requests, chat threads, and escalations. Look for questions that begin with “Can we,” “Who approves,” “When should we,” or “What happens if.” Choose one repeated issue and describe the facts that should change the answer. Remove details tied to a single event so the rule applies to the next similar decision.

A practical rule can follow a simple structure: “When these conditions exist, this person decides using these criteria. Escalate only when these limits are crossed.” Add the reason behind the rule in one sentence. The reason helps people handle cases that don’t fit perfectly and reduces mechanical compliance.

Test the draft against several past decisions. Ask whether the rule would have produced a sensible answer, whether two people would interpret it similarly, and whether someone could misuse the wording. Tighten unclear thresholds and define unfamiliar terms. Publish the rule once it works for normal cases, then treat unusual cases as learning material rather than reasons to abandon it.

How Should You Share Decision Rules With Your Team?

Store decision rules in one searchable location, assign an owner to every rule, and connect each rule to the work it governs. A rule hidden in meeting notes or scattered messages won’t improve decision velocity.

Organize the rules by decision area rather than by the date they were created. Useful categories include spending, hiring, customer commitments, project priorities, quality control, and escalation. Keep each entry short enough to scan during real work. Add the rule’s purpose, decision owner, approval threshold, exception route, and review trigger.

Introduce new rules through actual decisions. Show your team which recurring problem the rule resolves, where authority now sits, and when escalation remains appropriate. Ask several team members to apply the wording to a recent case. Different answers reveal ambiguity that needs correction.

Your own behavior determines whether the rules remain credible. Don’t override a delegated decision simply because you would have chosen differently. Intervene when the rule was misapplied, the facts were wrong, or the permitted boundary was crossed. If you reverse a sound decision made within the rule, you teach your team that authority still rests with your personal preference.

When Should You Update a Decision Rule?

Update a rule when its assumptions change, repeated exceptions appear, or the rule produces an outcome that conflicts with its stated purpose. Revision shows disciplined learning when you explain what changed and why.

Don’t rewrite a rule after every disappointing result. A sensible decision can still produce a poor outcome, and a weak decision can benefit from luck. Review whether the owner followed the stated criteria and used the information available at the time. Change the rule when the reasoning no longer holds, not simply because one result hurt.

Track exceptions because they reveal where a rule needs attention. One unusual case may justify a documented departure. Several similar exceptions suggest that the threshold, category, or ownership boundary is wrong. Updating the written rule is better than maintaining an unofficial version that only experienced employees understand.

Give every rule an owner and a review trigger. The trigger could be a process change, a new operating limit, repeated escalation, or a set number of exceptions. Record revisions in a short decision log so your team can see what changed. This prevents old copies and remembered versions from competing with the current rule.

How Does a Decision Journal Improve Your Rules?

A decision journal records what you knew, expected, and chose before the outcome was visible. Reviewing that record helps you identify recurring errors and refine your leadership decision rules with evidence rather than memory.

Farnam Street describes a decision journal as a form of quality control for thinking. A useful entry includes the problem, available options, governing variables, expected outcomes, confidence level, and reasons for rejecting alternatives. It can also capture your physical and mental state, especially when stress or fatigue could affect judgment. The goal is to preserve your original reasoning before memory reshapes it.

Decision rules and decision journals serve different purposes. The rule guides a repeated choice, and the journal records the reasoning behind a consequential choice. When several journal entries reveal the same decision pattern, you may have found a rule worth documenting. When outcomes repeatedly challenge an existing rule, the journal gives you material for review.

Keep journaling proportional to the stakes. Routine, reversible decisions rarely need a long entry. Hard-to-reverse commitments deserve a clearer record of assumptions, alternatives, decision criteria, and stopping conditions. A short review after the outcome can separate process quality from luck and help you improve future rules.

What Mistakes Make Decision Rules Backfire?

Decision rules fail when they’re vague, excessive, outdated, easy to game, or disconnected from real authority. The fix is to keep the rule set small, testable, visible, and open to documented exceptions.

Too many rules recreate the delay you wanted to remove. If employees must search through pages of instructions before making a minor call, the system has become another approval layer. Prioritize decisions that recur, consume attention, or create meaningful exposure. Leave rare, low-impact choices to ordinary judgment.

False precision creates another problem. A threshold can make a rule easier to apply, but an arbitrary number may encourage people to structure requests just below it. Pair thresholds with a purpose statement and an exception path. Review patterns across related decisions so repeated workarounds become visible.

Rules also fail when leaders ignore them without explanation. An undocumented exception signals that the rule is optional, personal, or politically applied. If you depart from a rule, record the reason and decide whether the exception exposes a drafting problem. Consistent use matters more than polished wording.

What Are Examples of Decision Rules for Leaders?

  • If reversal costs less than $1,000, decide without a meeting.
  • If an issue appears twice, write a rule.
  • If options score within 10%, choose the lower-risk option.
  • If a decision takes over one week, set a checkpoint.

Make Every Repeated Decision Pay You Back

You don’t need a rule for every choice. Write rules for decisions that recur, drain attention, create inconsistent answers, or slow work through avoidable escalation. Define ownership, criteria, thresholds, stopping conditions, and exceptions in plain language, then review what happens when people use them. Pair your rules with a decision journal when the stakes justify a written record. The best leadership decision rules turn yesterday’s judgment into tomorrow’s operating clarity, so your team can move without asking you to make the same call again.


References