Spending your attention on the trivial thing everyone understands. The reactor was approved in minutes.
The reactor costs ten million pounds and no one on the committee understands a word of it, so it is approved in two minutes, nemine contradicente. Then comes the bike shed — three hundred and fifty pounds, and a thing everyone can picture — and the opinions arrive like weather: what colour, what roof, one door or two. Then the fifteen-pound coffee budget, which everyone has both used and felt, consumes the rest of the afternoon. Press raise a point and add your own; it will land, like all the others, on the cheapest thing in the room. The amount of attention a matter receives is inversely proportional to how much it actually matters — and the bike shed, bless it, is something everyone has an opinion on.
In Parkinson's Law, C. Northcote Parkinson imagines a finance committee that waves through a multi-million-pound atomic reactor in minutes — no one understands it — then spends an hour on a clerk's bicycle shed, and longest of all on the price of coffee for meetings. Attention, he observes, flows to the cheapest item.
Triviality is an invitation. A bike shed is small enough that every person in the room feels qualified to have an opinion about its colour, so every person does. The reactor is so far beyond the committee that silence feels safer than a foolish question. Competence intimidates; simplicity democratizes.
On the FreeBSD mailing list, Kamp writes a now-famous email — “A bike shed (any colour will do)…” — to explain why a tiny proposal drew endless argument while large changes slid by unremarked. The post fixes the metaphor permanently in engineering culture, and the verb is born.
The phrase enters mailing-list and IRC vocabulary as shorthand: when a thread balloons over something trivial, someone invokes the bikeshed and, occasionally, it works. To accuse a discussion of bikeshedding is to point at the reactor everyone is ignoring.
Pull requests bikeshed on variable names, import order, and the exact wording of a log line, while a load-bearing design decision three files over receives a single LGTM. The bug is human, not technical: review attention pools where confidence is highest, not where risk is.
Logo shades, the office snack list, the name of the new channel, the emoji for deploys — these consume the meeting because everyone can contribute. The migration plan, which only two people understand, gets the last four minutes. Parkinson described your Tuesday standup in 1957.
Every naming thread, every brand-colour debate, every interminable argument about the trivial-but-visible is the same law at work. The word survives because the failure does: give a group a decision simple enough for all to judge, and they will, at length, judge it. The reactor, meanwhile, is fine. Probably.