Manish Chiniwalar's StationManish Chiniwalar's Station

The Bicycle Shed Paradox

Mar 27, 2026 · 7:08 · 1 article

0:00

Listen in your favorite app

Hosts

MMei-ling
NNut

Source Articles

Law of triviality

grokipedia.com

Transcript

Mei-ling: You have a committee, right? They need to approve two things. Like, a huge nuclear reactor, probably cost them, oh, ten million dollars. Big, complicated, important stuff, lah.

Nut: Ten million? Serious business!

Mei-ling: Yes, very serious. And then, second, maybe a little bicycle shed. Small money, just like… fifty dollars. Everyone knows what a bike shed is, right?

Mei-ling: Guess which one they spent two hours arguing about?

Nut: Hmm, the nuclear reactor? No wait, that's too obvious... It's the bicycle shed, isn't it? Oh, I know this story! I just love it, it's so true.

Mei-ling: You got it! Precisely. They spent, oh, like, two hours on the bicycle shed. And then on the nuclear reactor? Maybe thirty minutes. Can you imagine that? How is that even possible?

Nut: Ah, okay. So this is what they call the 'Law of Triviality,' no? Or, like, 'bike-shedding.'

Mei-ling: Bike-shedding. Yes.

Nut: It comes from this British guy, C. Northcote Parkinson. He wrote about it in the fifties.

Mei-ling: Parkinson's Law, yes, I've heard that name before, but I didn't connect it to this story.

Nut: Oh, it's all connected, Mei-ling! The basic idea, ah, how do I put this... it's about, like, the time people spend discussing something, it's... it's like, the opposite of the money involved.

Mei-ling: The opposite? So... less money, more time?

Nut: Exactly! So, if it's big money, really complex stuff? They approve it fast. But small money, simple decisions? Oh, endless, endless debate.

Mei-ling: But why? Like, wouldn't you want to spend more time on the ten-million-dollar nuclear reactor? The consequences are, you know, a little bit more significant than a bike shed.

Nut: That's what you'd think, right? But the article, ah, it says it's actually about competence.

Mei-ling: Competence?

Nut: Yeah. Like, nobody on the committee, they're not nuclear physicists, probably. So they can't really argue about the reactor, you know? They just have to trust the experts.

Nut: But a bike shed? Everyone knows what a bike shed is. Everyone has an opinion on what color it should be, or what material for the roof. It makes them feel like they're contributing, like they're smart.

Mei-ling: Ah, so it's not that they actually want to waste time... it's more like they feel this pressure, you know, to contribute, to add value. And the bike shed, it's just the easiest thing for them to talk about.

Nut: Exactly, Mei-ling! It's not people being stupid or anything. It's really a failure of the process.

Mei-ling: The meeting design.

Nut: Yes! The way we set up our meetings. We put everything on the same agenda, right? Big, complex things, just next to small, simple things.

Nut: It just happened to me last week, actually. We were on a call for Manish Chiniwalar's Station, reviewing the new analytics dashboard. The data pipeline architecture? The really complex stuff connecting all the different sources? We greenlit that in five minutes, because nobody really understood it.

Mei-ling: Oh, no, I think I know where this is going.

Nut: Oh, yes!

Nut: We spent... like, forty-five minutes! Just arguing over, should the daily listeners graph be a line chart or a bar chart? My designer, she was about to quit, Mei-ling. Really, she was about to quit!

Mei-ling: Forty-five minutes?

Nut: Yes!

Mei-ling: For a line or a bar?

Nut: Forty-five minutes! Because everyone could see it, right? Everyone could understand. They could feel their opinion... it mattered. It's... it's a trap!

Mei-ling: Okay, I see what you mean about the process design then. If the meeting agenda treats a nuclear reactor and a bike shed as equal items, then you invite everyone to weigh in on the one they understand.

Nut: Yeah, so it's like, you can't just tell people to shut up about the bike shed, no? The real solution... it's to rethink who is in the meeting. And what they are deciding. And how those things are presented.

Mei-ling: Hmm. But is it always a bad thing, though, this bike-shedding? I mean, it just sounds like a pure waste of time, doesn't it?

Nut: Mmm, I thought so too.

Mei-ling: We should just have better meeting discipline, right? Focus on the important things, not the trivial ones.

Nut: See, that's what I thought at first. Like, 'Oh, these people are just inefficient.' But then I started thinking, maybe sometimes arguing over the bike shed isn't just about the bike shed.

Mei-ling: What do you mean?

Nut: Maybe it's a proxy. Like, arguing about the color of the bike shed, or whether it has a little roof, is actually a way for people to talk about deeper issues. Like company culture, or how much management values employee comfort, or even just letting off steam about other things they can't control.

Mei-ling: So you think arguing about fifty dollars for a bike shed can really be a discussion about company values? That seems like a very inefficient way to have that conversation.

Nut: It is inefficient, sure. But, ah, how do I put this... maybe it's the only way sometimes, you know? It's like... a messy, democratic way for people to feel heard.

Nut: Even if it's about something so small. If you just shut down all bike-shedding, maybe you're also shutting down the only outlet for people to express deeper frustrations.

Mei-ling: I don't know... I still think it's mostly just a waste of productive time, Nut. A company's time is money.

Nut: True.

Mei-ling: Those, ah, couple hours on the bike shed? That's not fifty dollars. That's many, many thousands of dollars in salaries for all those people. If people want to discuss company culture, there are better ways, right? Town halls, surveys, one-on-ones.

Nut: But do people feel safe to say what they really feel in a town hall? Maybe the bike shed is safe because it is trivial. It's a low-stakes way to push back. It's like, a symptom of something else, not the problem itself. If you just fix the symptom, the deeper problem is still there, just... hidden.

Mei-ling: Hmm. I need to think about that more. I always just saw it as a sign of poor meeting facilitation.

Mei-ling: So, the next time you're in a meeting and everyone's arguing about some tiny, trivial detail, is it your job to call it out and get things back on track? Or are you witnessing some important, maybe inefficient, conversation about what people actually care about?

Nut: I don't know, Mei-ling. It's a tough one. Should you just... shut it down, or let it breathe?

Mei-ling: Exactly. It's not so simple.

Nut: Definitely not.

Mei-ling: And I'm Mei-ling. You've been listening to Manish Chiniwalar's Station.

Turn your reading list into a daily podcast

Create your own station