Bikeshedding - Parkinson's Law of Triviality

In 1957, C. Northcote Parkinson wrote about a fictional committee tasked with approving a nuclear power plant. The committee spent almost no time on the reactor. It was too complex, too abstract, too far outside the members’ experience. But the bicycle shed for the plant’s staff? That they could discuss. Everyone had opinions about roofing materials and paint colors. The meeting ran long.

Parkinson called this the Law of Triviality. Today we call it bikeshedding.

Why It Happens

The standard explanation is that people avoid hard problems and gravitate toward familiar ones. That is true, but it misses the more precise mechanism.

Trivial topics grant universal permission to participate. The nuclear reactor requires domain knowledge. The bicycle shed requires none. When the reactor comes up, most people in the room stay quiet because they cannot say anything useful. When the shed comes up, everyone can contribute. Paint color, roof material, whether the door should face east or west. Nobody lacks an opinion. The room fills with voices.

The more precise mechanism is that trivial topics lower the barrier to entry for speaking. Hard topics require expertise before you can contribute. Easy topics require none. So when the shed comes up, participation broadens, discussion time expands, and the whole thing feels productive. The attention problem is real, but it runs on a participation engine.

Hard thinking stays hard even when everyone is in the room.

Software teams run into this constantly. An architectural decision that will shape the codebase for years gets thirty minutes of tentative discussion. The naming of a function, or the color of a button, gets an hour.

Only three people in the room can say anything meaningful about the architecture. Twelve can comment on a name. The time allocation follows the participation, and the participation follows the expertise barrier.

The Cost

Bikeshedding is not harmless. Every hour spent on the shed is an hour not spent on the reactor. Decisions that matter get deferred, delegated, or made carelessly in the last five minutes of a meeting that ran over.

There is also a subtler cost. When a team habitually avoids the hard problems, it trains itself to do so. The instinct to reach for something comfortable, something discussable, becomes a reflex. Hard thinking atrophies.

How to Recognize It

A few signs that bikeshedding has taken hold:

The simplest item generates the most notes. A decision that should take five minutes has run through three revisions. People who stayed quiet during the hard discussion are suddenly the most vocal. Discussion volume rises as the decision’s actual consequence falls. The meeting ends without resolving the original problem, but everyone leaves feeling like they contributed.

What to Do About It

If bikeshedding is a participation problem, the fixes should address participation directly.

Constrain who decides low-stakes questions. If one person has the expertise and accountability to make a call, the group does not need to be in the room for it.

For high-stakes decisions, shift the default from open discussion to written reasoning first. When people commit a position to writing before the meeting, they engage with the complexity instead of waiting for a comfortable moment to speak. It also makes visible who has actually thought through the problem.

Timebox the shed. If a name or a visual choice will not noticeably change the outcome, set a short limit and move on when the time is up. A hard stop removes the incentive to treat a minor decision as a participation opportunity.

And name it when it happens. Most people, when told directly that the group has drifted, will redirect.