Core Idea
When an exception request seems reasonable, that is evidence the policy needs updating — not that this person deserves special treatment. Default to working the policy, not granting the exception.
Work the policy, not the exception is Will Larson’s principle that engineering managers should respond to exception requests by improving the underlying policy rather than granting individual workarounds.
Why Exceptions Are Harmful
- Precedent and scaling: Every exception is an implicit commitment to grant it to anyone in similar circumstances. With 100 engineers, informal negotiation collapses.
- Manager-as-bottleneck: Exception-granting concentrates decision power in the manager; people learn to advocate with the manager rather than follow the system.
- Systematic unfairness: Only those who ask — or ask well — receive exceptions. Quieter team members and newer joiners systematically receive less.
- Exception debt: Accumulated exceptions form an invisible parallel policy — inconsistent, informal, and resentment-generating. See Exception-Debt.
- Cognitive load: Each exception requires re-litigating context and tracking precedent — costs that compound with team size.
When Exceptions Are Appropriate
- Genuine emergencies that no policy could anticipate — unique, one-time circumstances
- Discovery mechanism: grant the exception AND immediately update the policy
- Explicit one-time events — name them as non-repeating when granting, and track them
Four-Step Response Framework
- Ask: Is this request exposing a gap in the policy?
- If yes: Fix the policy first, then apply the updated policy to this person
- If no: Grant explicitly as a named, one-time exception
- Track: If you grant the same exception twice, that’s a policy gap — update the policy
Procedural Justice Angle
Research on procedural justice (Thibaut & Walker, 1975; Tyler, 1990) shows that consistent rule application is perceived as fair — even when the outcome is unfavorable — because the process signals respect and impartiality. Policy consistency is not just operationally efficient — it is perceived as more just.
Connection to Systems Thinking
The principle applies Deming’s distinction between common cause variation (systemic issues requiring policy change) and special cause variation (unique circumstances justifying individual response). See Systems-Thinking-Stocks-Flows-Feedback.
Related Concepts
- Larson-2019-An-Elegant-Puzzle
- Systems-Thinking-Stocks-Flows-Feedback
- Exception-Debt
- Six-Degrees-of-Managerial-Control
Sources
-
Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9. Chapters 3.3 and 4.1.
-
Thibaut, John W. and Walker, Laurens (1975). Procedural Justice: A Psychological Analysis. Lawrence Erlbaum Associates. ISBN: 0-470-85803-6.
- Foundational research: perceived fairness depends on process consistency; uniform rule application perceived as legitimate
-
Tyler, Tom R. (1990). Why People Obey the Law. Yale University Press. ISBN: 978-0-300-04820-7.
- Procedural fairness drives voluntary compliance more than favorable outcomes
-
Deming, W. Edwards (1986). Out of the Crisis. MIT Press. ISBN: 978-0-262-54115-7.
- Distinguishes common cause variation from special cause variation
-
Kahneman, Daniel, Rosenfield, Andrew M., Gandhi, Linnea, and Blaser, Tom (2016). “Noise: How to Overcome the High, Hidden Cost of Inconsistent Decision Making.” Harvard Business Review, October 2016.
- Discretionary exception-granting produces high variance outcomes
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.