Pattern/Aphorism/No. 0554
Law of Triviality (Bikeshedding)
The law of triviality, or bikeshedding, is a tendency for groups to spend more time on minor, familiar issues than on major decisions. C. Northcote Parkinson described it in 1957 as a satirical rule of thumb, reflecting how ease of participation can draw attention away from importance.
Also called Bikeshedding · Parkinson's Law of Triviality · Bike-Shed Effect
- Evidence
- Useful, modest evidence
- Read
- 6 min
- Links
- 7 connections
01You've seen this when…
- at work
A launch meeting leaves the payment system’s failure handling unexamined. Six people then debate whether the confirmation button should be green or blue.
- in life
Your siblings are planning help for a parent after surgery. Everyone weighs in on meal containers; nobody settles who covers the first night.
- out in the world
At a town meeting, a dense drainage proposal passes with few questions. The discussion heats up over the style of benches to install beside it.
02The idea
Sometimes a meeting’s longest discussion centers on the decision that the most people understand, while a more important decision gets less time.
C. Northcote Parkinson illustrated this with an imaginary committee approving a nuclear reactor and a bicycle shed. The reactor requires specialized knowledge. Most members have little to say. A bicycle shed is familiar: everyone can picture one, compare materials, and offer an opinion. The smaller item attracts the bigger discussion.
That’s the law of triviality, commonly called bikeshedding. The problem isn’t discussing details. It’s allocating attention by ease of participation rather than by consequence. A group can leave an expensive uncertainty untouched while thoroughly settling a cheap preference.
Unlike Parkinson’s law, which concerns work expanding to fill available time, this pattern concerns where the time goes. It is an aphoristic rule of thumb. The relationship between importance and discussion time varies, and a quiet approval can reflect careful review.
03Why it happens
Several forces can make the easy topic crowd out the consequential one:
- Familiarity lowers the entry cost. You don’t need engineering training to discuss paint. With a complicated proposal, you may need an hour of reading before you can ask a useful question. Under bounded rationality, attention naturally favors what is manageable.
- Small opinions feel safer. Challenging a technical assumption risks exposing what you don’t know. Expressing a preference about a label feels less dangerous. Evaluation apprehension can reinforce that imbalance.
- Participation is visible. A minor suggestion gives someone a contribution they can point to. Quietly checking a difficult assumption may be more valuable but less noticeable.
- Shared ground sustains conversation. Everyone understands the small issue, so each comment invites another. Research on shared information bias shows that groups favor information members already have in common. That is evidence for a related tendency. Its connection to bikeshedding is indirect.
These are plausible, overlapping explanations. Parkinson’s story doesn’t establish which one drives a particular meeting.
04A worked example
Consider an illustrative clinic committee preparing to install a backup generator. Its agenda includes which circuits the generator will serve, how the switch to backup power will be tested, and the appearance of maintenance labels.
The electrical proposal is technical. Members assume somebody else has checked it. The labels are easy to picture, so the committee spends most of its remaining time comparing fonts and colors.
What it looks like Careful review. The meeting ends with a clear decision after many people contribute and several options get considered.
What’s actually going on The committee has resolved a visible preference while leaving consequential questions unanswered. Who confirms that essential equipment stays powered? Who witnesses the test? Which assumptions still need independent review? The labels have value. The group’s attention is out of proportion to the unresolved stakes.
What would have helped Separate the decisions before the meeting. Assign a qualified reviewer to the electrical plan, require a short account of unresolved risks, and give routine label choices to the maintenance lead. The whole committee need not become electrical experts, but it must know who has checked the critical parts.
05How to spot it
06What to do about it
- Allocate time before discussion begins. Rank agenda items by consequences, uncertainty, and reversibility. An Eisenhower matrix can help distinguish importance from whatever is demanding attention now.
- Make the difficult item discussable. Ask its owner for a plain-language explanation of the decision, the alternatives, and what remains unknown. Give people enough preparation to contribute beyond preferences.
- Name the reviewer instead of trusting the room. Record who has the relevant expertise, what they checked, and where their review stops. Silence should not count as sign-off.
- Delegate bounded choices. Let one person choose low-stakes details within agreed constraints. Not every decision benefits from universal consent.
- Put a price on another round. Ask what another ten minutes could change and what those minutes displace. That exposes the opportunity cost of continuing.
- Redirect without belittling. Acknowledge the detail, assign an owner, and return to the unresolved decision. Calling someone’s concern trivial can suppress useful information along with noise.
For recurring meetings, compare planned time with actual time. The pattern is easier to correct when you can see which topics repeatedly consume the agenda.
07When it isn’t bikeshedding
A small-looking detail can carry large consequences. Button wording can affect consent. Label colors can affect safety. A meal container can matter if the person recovering from surgery cannot open it. Judge importance by a topic’s effects, whatever its name suggests.
A major decision may also deserve little meeting time because qualified people have already reviewed it. Check whether scrutiny happened elsewhere, regardless of how many committee members spoke.
In groupthink, pressure for agreement suppresses dissent. Bikeshedding can involve lively disagreement. Shared information bias concerns common versus privately held information; bikeshedding concerns disproportionate attention to accessible, minor matters.
The label is most useful when it prompts a check of priorities. It is least useful when a powerful person uses it to dismiss inconvenient details.
08Roots
In 1957, historian C. Northcote Parkinson put an imaginary finance committee around a table. Its agenda put refreshments in the same meeting as a nuclear reactor and a shelter for employees’ bicycles. The reactor was formidable. The bicycle shed invited opinions about roofing materials. Refreshments offered still more familiar ground.
The scene appeared in Parkinson’s Law, his satirical book about administration. It was a comic construction built around an invented committee meeting. By making the biggest expenditure the hardest thing to discuss, Parkinson exposed a recognizable weakness in committee life: the ease of having an opinion can determine how much attention an item receives.
The bicycle shed later became the shorthand. In a widely circulated 1999 message to the FreeBSD developer community, Poul-Henning Kamp retold Parkinson’s example to explain why small technical proposals could provoke sprawling arguments. Software communities adopted bikeshedding. The term spread into product teams and became part of the language used in workplace meetings and online discussion. The shed survived because it gave an abstract allocation problem a picture almost anyone could recognize.
09How solid is this?
This memorable rule of thumb originated in satire. An inverse relationship between importance and discussion time remains unproven. Research supports related tendencies, such as favoring shared information. That evidence bears on the law of triviality indirectly.
10Connections
- Often confused withShared Information Bias
- Countered by Eisenhower Matrix
- See also Opportunity Cost, Parkinson’s Law, Bounded Rationality, Groupthink, Evaluation Apprehension
11Origin and sources
C. Northcote Parkinson described the law of triviality in Parkinson’s Law (1957), using an imaginary committee’s nuclear-reactor and bicycle-shed decisions. Poul-Henning Kamp helped popularize bikeshedding in software communities in 1999.
- [1]Parkinson, C. N. (1957). Parkinson's Law, and Other Studies in Administration. Houghton Mifflin.
- [2]Kamp, P.-H. (1999, October 2). A bike shed (any colour will do) on greener grass... Message to the freebsd-hackers mailing list.
- [3]Stasser, G., & Titus, W. (1985). Pooling of unshared information in group decision making: Biased information sampling during discussion. Journal of Personality and Social Psychology, 48(6), 1467–1478.
Suggest an edit· Updated 2026-10-02