Bikeshedding

What is bikeshedding?

Bikeshedding means spending disproportionate time on a minor, easily understood issue while a more consequential issue receives little attention. It is also called the Law of Triviality or Parkinson’s Law of Triviality.

The image comes from C. Northcote Parkinson’s committee discussing a nuclear reactor and a bicycle shed. The reactor is complicated; few people can confidently debate it. Everyone can have an opinion about the shed. The smaller decision consumes the discussion.

Examples of bikeshedding

• Business meetings: a team debates office paint while leaving a consequential budget decision unresolved.
• Software development: a group argues over naming conventions while a major design problem receives little scrutiny.
• Policy discussions: an easily understood detail crowds out a harder question about how the policy will work.

These are illustrations. Paint, names, and policy details are not inherently trivial; the issue is how much attention they deserve relative to the decision’s stakes.

Bikeshedding in software discussions

Poul-Henning Kamp’s 1999 message, linked from the FreeBSD FAQ, documents the metaphor’s use in software discussions. It is an informal management observation, not a law all groups follow.

How to recognize it

Ask what is being left undecided and what a wrong decision would cost. A topic that feels minor to you may matter to someone else. Establish the stakes before dismissing the discussion as bikeshedding.