Bikeshedding (Parkinson's Law of Triviality)¶

What it is: The inverse failure mode LOGAF is designed to prevent — not a scale for expressing care, but a name for what happens when a group's expressed level of care doesn't match the actual stakes.

Origin: Coined by C. Northcote Parkinson in his 1957 book Parkinson's Law, illustrated with a fictional committee approving a nuclear power plant. The committee rubber-stamps the multi-million-pound reactor in minutes (nobody feels qualified or willing to argue), then spends an hour arguing about the materials for the staff bicycle shed — because everyone understands bike sheds and feels entitled to an opinion.

The core dynamic¶

People's engagement with a topic scales with how comprehensible and low-stakes-to-argue-about it feels, not with how important it actually is. Complex, high-stakes decisions get rubber-stamped because contesting them requires expertise or effort; trivial, easy-to-have-an-opinion-about decisions get relitigated endlessly because anyone can jump in.

Where you've likely seen it¶

Software engineering borrowed the term heavily — "bikeshedding" is now common shorthand for a PR thread with 40 comments about variable naming and zero comments about the actual architecture change three files down.

How it relates to LOGAF¶

Bikeshedding is the disease; LOGAF is one candidate treatment. If everyone in a bikeshedding thread had to prefix comments with their actual logaf, most of the naming-convention squabbling would reveal itself as low-logaf noise and could be resolved by the PR author's judgment call instead of prolonged debate — while the comment about the actual architecture risk would surface as the high-logaf item deserving real attention.