The Bike Shed Argument Is Telling You Something


a pink bicycle parked in front of a building

On 2 October 1999, a Danish programmer named Poul-Henning Kamp sent an email to the developers of the FreeBSD operating system under the subject line “A bike shed (any colour will do) on greener grass…” The thread that set him off was about whether a tiny command called sleep should accept fractional seconds. The change would have broken nothing. It had been argued over for days anyway. Kamp called it “the most blatant example of a bike shed discussion we have had ever in FreeBSD”, and the label stuck. Twenty-seven years later, “bikeshedding” is how engineers, and more and more managers, describe a group pouring its energy into the smallest decision in front of it.

Kamp borrowed the idea from C. Northcote Parkinson, the British historian who satirized bureaucracy in The Economist in 1955 and later expanded those essays into a book. In Parkinson’s version, a committee approves an atomic reactor almost without discussion and then argues at length over a bicycle shed for the staff. Kamp’s explanation of why is still the best one. A power plant is “so vast, so expensive and so complicated that people cannot grasp it,” so they “fall back on the assumption that somebody else checked all the details before it got this far.” A bike shed is different: “Anyone can build one of those over a weekend.”

Most management writing stops there and draws the obvious lesson: keep your meetings off the trivia. I think that lesson is half right and mostly unhelpful. After 25 years of running meetings in operations, my view is that the bike shed argument is rarely the real problem. It’s a symptom, and the manager usually built the conditions for it.

The agenda decides what gets argued about

Start with the mechanics. Steven Rogelberg, who has spent most of his career studying meetings, summarizes the research bluntly: “the items early in the agenda received a disproportionate amount of time and attention, regardless of their importance.” On the same page he estimates that about half of agendas are simply recycled from one meeting to the next.

Put those two findings together and you get a picture most of us know. The recycled standing items sit at the top: status updates, housekeeping, the facilities question that has come back three weeks running. The decision that actually matters sits at item six, with fifteen minutes left on the clock and half the room thinking about their next call. Nobody chose to spend forty minutes on the shed. The agenda chose for them.

Boards aren’t immune. In a Board Intelligence survey run with Cambridge Judge Business School, respondents reported spending 32% of meeting time on strategy, against 41% on performance and 26% on governance, and 44% wanted more time for strategy. It’s a small sample (50 board members, most of them company secretaries), so I wouldn’t hang a policy on the exact numbers. The direction will still be familiar to anyone who has sat through a quarterly review: the backward-looking, easy-to-discuss material expands, and the hard forward-looking question gets whatever time is left.

Why people pile onto the small stuff

Kamp’s email has a line that most summaries skip. No matter how reasonable a proposal is, “somebody will seize the chance to show that he is doing his job, that he is paying attention, that he is here.” In Denmark, he wrote, they call it “setting your fingerprint.”

That isn’t vanity, or not only vanity. It’s a person looking for somewhere to contribute. When the big item arrives as a forty-slide deck that was finished before the meeting started, the honest options are to nod or to pick a fight you can’t win. The small item is the only door left open, so people walk through it.

I watched this happen more than once in capital planning at a large telecom. A multi-year network refresh, worth more than most of the people in the room would earn in a career, would go through review with a handful of clarifying questions. The same group would then spend half an hour on how the on-call rotation should be displayed in the shared calendar. For years I read that as a discipline problem. Eventually I noticed that the refresh had been shaped for months by a small architecture group, and by the time it reached the room, the only real choice anyone had was yes. The calendar was the one item on the agenda where everyone’s opinion still counted.

There’s research behind that instinct. W. Chan Kim and Renée Mauborgne’s work on fair process, published in Harvard Business Review, found that people will commit to a decision they disagree with if they believe the process that produced it was fair. Their three conditions are engagement (being asked for input and allowed to challenge ideas), explanation (understanding why the final call was made) and clarity about what’s expected afterward. Take engagement away from the decisions that matter and people will find somewhere else to be engaged. Very often, it’s the shed.

Shutting it down makes it worse

The standard fix is to cut it off: “let’s take that offline,” a parking lot on the whiteboard, a facilitator with a timer. Those tools have their place. Used as the main defence, though, they teach your team that speaking up gets managed. That’s the last lesson you want people carrying into the next high-stakes decision, where the fact that changes the answer is often sitting with the quietest person in the room.

The standard fix also misjudges which decisions are trivial. The calendar layout was trivial to the capital committee. It was not trivial to the technicians who had to live with that rotation every night. Something that feels like a bike shed to the person running the meeting can be the most consequential item on the agenda for the people sitting in it. Before you cut a discussion short, ask who it’s small for.

Kamp’s own closing line deserves more attention than it gets: “I wish we could let people build a bike shed every so often, and I don’t really care what colour they paint it.” He wasn’t asking for less participation. He was asking for the shed to be handed over, so the group could stop fighting about it.

What I do instead

None of this needs a new framework. It needs four habits.

Put the expensive decision first. Rogelberg’s advice is to reach the most important items within about five minutes of the start. If the reactor is item one, it gets the room’s best attention. If it’s item six, the shed wins by default. (Parkinson’s better-known law, that work expands to fill the time available, applies here too: an hour-long meeting with one real decision will find fifty minutes of something else to discuss.)

Bring people into the big decision before it’s finished. If the first time your team sees a major proposal is the meeting where it gets approved, you’ve removed their only chance to shape it. Circulate the draft early, ask specific people to attack specific parts, and say plainly what’s still open. Input that arrives before the deck is final is the only kind that changes anything.

Delegate the shed outright. Most bike sheds are cheap, reversible decisions. Give them to one person, or to the people most affected, with a deadline and a budget. Then accept whatever colour they choose. The fastest way to end a bike shed debate is to make it somebody’s call.

Read where the energy goes. When a meeting spends twenty minutes on something small, treat that as information. Either the item matters more to the team than it looks from your chair, or the team has no voice on the bigger items. Both are worth knowing, and moving on to the next agenda item fixes neither.

The next time your team burns half an hour on the colour of something, resist the urge to call it a waste of time. Ask what the conversation is telling you. Then look at what you put at the top of the agenda, and what you decided before anyone else got a say.

Ty Sutherland

Ty Sutherland is an operations and technology leader with 20+ years of experience. He is Director of IT Operations at SaskTel, founder of Ops Harmony (fractional COO and EOS Integrator), and former COO at WTFast. He writes Management Skills Daily to share practical management frameworks that work in the real world.

Recent Posts