Law of Triviality
Introduction#
In 1957, Cyril Northcote Parkinson observed that committees spend more time debating bike shed colors than nuclear reactor budgets. This counterintuitive phenomenon explains why software teams argue for hours about code formatting while rushing through architecture decisions.
The Law of Triviality reveals that discussion time inversely correlates with decision importance. The more trivial the topic, the longer the debate.
The Law Stated#
“The time spent on any item of the agenda will be in inverse proportion to the sum [of money] involved.”
Parkinson’s example: a committee reviewing a £10 million nuclear reactor (2.5 minutes), a £350 bike shed (45 minutes), and £21 of coffee supplies (1 hour 15 minutes). The pattern is clear, complexity and stakes reduce discussion time.
Why This Happens#
Three factors drive bike shedding:
The nuclear reactor was too complex to evaluate meaningfully, so people deferred to expertise. The bike shed was accessible, everyone could visualize it and felt qualified to contribute. The coffee supplies had such low stakes that endless refinement seemed harmless.
Simple topics invite participation because they appear understandable and safe to debate.
Bike Shedding in Software Teams#
Code reviews focus on variable names and formatting while algorithmic logic gets minimal attention. Sprint planning debates story points endlessly while glossing over technical risks. Teams spend hours configuring linters but make hasty database choices.
The pattern is consistent: trivial decisions consume disproportionate time and energy while consequential architecture decisions get rushed through meetings.
The Real Cost#
Bike shedding creates opportunity costs. Time debating indentation is time not spent on architecture reviews. Decision fatigue from trivial debates reduces the quality of important choices.
Teams feel productive after long formatting discussions while making no progress on significant challenges. Meanwhile, critical decisions get deferred until they become urgent, forcing hasty choices under pressure.
Fighting Back#
Allocate meeting time by decision importance, not discussion volume. Time-box trivial topics regardless of how much debate they generate. Use automation for formatting and linting to remove these topics entirely.
When everyone has strong opinions about colors but stays silent during architecture discussions, you’re bike shedding. Make the pattern visible and redirect attention to consequential choices.
Connection to Other Laws#
Like Brooks’ Law, the Law of Triviality reveals counterintuitive group dynamics. Both show that more discussion time doesn’t necessarily improve outcomes.
Time spent bike shedding increases work-in-progress for important decisions, extending their cycle time while creating false productivity signals, a direct violation of Little’s Law.
Conclusion#
Groups naturally allocate discussion time inversely to decision importance. Recognizing this pattern is the first step toward better attention allocation.
The solution isn’t eliminating trivial discussions entirely—some details matter for team cohesion. Instead, consciously allocate decision-making energy based on consequence rather than comfort.
The next time everyone has passionate opinions about indentation but stays silent during architecture discussions, remember Parkinson’s bike shed. The real work happens when teams push through the discomfort of complex topics rather than seeking the false productivity of trivial debates.