Post

Bikeshedding - Parkinson's Law of Triviality

I can now name this particular observation.

Bikeshedding - Parkinson's Law of Triviality
Connected Notes

In 1957, C. Northcote Parkinson wrote about a finance committee working through three items: a ten-million-pound atomic reactor, a bicycle shed for the clerical staff, and a small annual budget for the committee’s coffee. The reactor took two and a half minutes. It was too complex, too abstract, too far outside the members’ experience, so they approved it and moved on. The bicycle shed took forty-five minutes, because everyone had opinions about roofing materials and paint colors. The coffee budget took the longest of all. It was the one item every person in the room understood completely, so every person had something to say.

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

Why it happens

The usual explanation is that people dodge hard problems and drift toward familiar ones. That’s true as far as it goes, but it misses what’s actually driving it.

The sharper point is about who’s allowed to speak. The reactor needs expertise, so most of the room stays quiet, because there’s nothing useful they can add. The shed needs none. Everyone has lived near a shed, picked a paint color, had a door that opens the wrong way. So when the shed comes up, the barrier to joining in drops to zero, and everyone has something to say. The room fills with voices, the discussion stretches out, and the whole thing feels productive. The pull toward easy topics is real, but what powers it is participation: the easy topic is the one everybody can talk about.

The cost

Every hour on the shed is an hour not on the reactor. The decisions that actually matter get pushed to next week, handed off, or made in a rush in the last five minutes of a meeting that already ran long.

And it compounds. A team that keeps sliding past the hard problems is teaching itself to keep doing it. Reaching for the comfortable, discussable thing turns into a reflex, and the habit of sitting with a hard problem wastes away from disuse.

How to recognize it

A few signs it’s taken hold. The simplest item on the agenda collects the most comments. A five-minute decision is on its third revision. The people who went quiet during the hard part are suddenly the loudest. The volume of discussion climbs as the stakes of the decision drop. And the meeting ends without settling the thing it was called to settle, while everyone leaves feeling like they pitched in.

What to do about it

If the problem is really about participation, the fixes have to work on participation.

Narrow who decides the low-stakes questions. If one person has the expertise and owns the outcome, the rest of the group doesn’t need to be in the room while they make the call.

For the high-stakes ones, change the default from open discussion to writing first. When people have to put a position down on paper before the meeting, they have to grapple with the hard part instead of waiting for an easy moment to jump in. It also makes it plain who has actually thought the problem through and who hasn’t.

And timebox the shed. If a name or a color won’t change the outcome in any way you’ll notice later, put a short clock on it and move on when the clock runs out. A hard stop takes away the reason to treat a trivial decision as a chance to be heard.

$ ls incoming/
_
$ ls outgoing/
_
This post is licensed under CC BY 4.0 by the author.