The hour that vanished into a logo color
Think back to a meeting that overran and ask yourself what actually ate the clock. Often it wasn't the hard thing on the agenda. It was the easy thing. The team nodded through a quarter-million-dollar vendor contract in four minutes, then spent forty-five arguing about the wording of an out-of-office message, the shade of a button, or whether the team lunch should be Thursday or Friday.
This isn't a failure of discipline, and it isn't because your colleagues are unserious. It's a documented pattern with a name, an origin, and a mechanism you can interrupt once you can see it.
What the law of triviality actually says
In 1957, the British naval historian C. Northcote Parkinson described what he called the law of triviality: the time an organization spends on any item tends to be inversely proportional to its importance. His illustration has outlived him. He imagined a finance committee with three items: approving a multimillion-pound nuclear reactor, building a bicycle shed for the staff, and the annual budget for refreshments at committee meetings.
The reactor passes almost without comment. It's too large, too technical, too far outside what any single member can confidently evaluate. The bike shed gets a real debate — everyone has built or seen a shed, so everyone has a view on the roofing material and whether aluminum would be cheaper. And the coffee budget, the most trivial item of all, consumes the most time of the lot, because every person in the room is a fully qualified expert on coffee.
Decades later, software engineer Poul-Henning Kamp gave the pattern its enduring nickname while watching a mailing list erupt over a tiny code detail while sweeping architectural changes sailed through unexamined. He called it bikeshedding, and the word stuck because everyone recognized the shed.
Why the small stuff pulls so hard
The instinct is to blame the people. The more useful move is to notice the structure, because bikeshedding is produced by a few ordinary features of how groups think.
The first is the barrier to entry. To say something credible about the reactor, you need expertise most people in the room don't have, so they stay quiet. To say something credible about the bike shed, you need to have once thought about a shed. The trivial topic is the one where the largest number of people feel entitled to an opinion, so it generates the most opinions. Volume of discussion tracks accessibility, not importance.
The second is the pull to contribute. Sitting silent in a meeting feels like not pulling your weight, especially when others are visibly engaged. Psychologists describe a broad human drive toward effort justification — we want our presence to mean something. A trivial-but-accessible item is the easiest place to discharge that drive. You can be seen adding value without the risk of being wrong about something hard.
The third is discomfort with ambiguity. Big decisions are often genuinely murky; the data is incomplete and the right answer is uncertain. That ambiguity is unpleasant, and groups unconsciously drift toward problems that offer the relief of a clean, reachable conclusion. Choosing the shed's paint color produces a tidy sense of resolution that the reactor never will. The meeting feels productive precisely because it solved the thing that was easiest to solve.
Put these together and bikeshedding stops looking like a quirk. It's the predictable result of a room full of people who want to participate, gravitating toward the items where participation is cheapest and resolution feels best.
The cost isn't just time
It's tempting to write this off as harmless — so the meeting ran long, who cares. But the law of triviality has a second edge. The minutes spent on the coffee budget are minutes not spent on the reactor, and the reactor is the decision that actually moves the organization.
When a group exhausts its attention on accessible problems, the consequential ones get waved through under-examined, not because everyone agrees but because no one has the energy or the standing to open them up. The big risks pass in silence. Then, months later, the project that failed turns out to have been the one nobody questioned in the room — because questioning it was hard, and the shed was right there.
There's a reputational cost too. People learn what a meeting rewards. If the discussions that get airtime and visible engagement are the trivial ones, the room quietly trains itself to bring trivial things, and the hard questions migrate to hallways and side channels where they get less scrutiny, not more.
How to interrupt it
You don't fix bikeshedding by telling people to focus. You fix it by changing the conditions that produce it.
Name the pattern out loud. The single most effective intervention is simply saying, "I think we're bikeshedding this." The term is doing real work — it gives everyone a shared, blameless label for the drift, so redirecting feels like a recognized move rather than a rebuke. Groups that know the word self-correct faster.
Match time to stakes deliberately. Before the discussion, decide roughly how much of the meeting each item deserves based on its importance, and say it. "This one's a five-minute decision; the budget is our main event today." Stating the ratio up front fights the instinct to let accessibility set the agenda.
Pre-decide the trivial things, or push them down. Many bike-shed items don't need a meeting at all. Give someone the authority to just pick the paint color and move on. A good rule: if a decision is cheap to reverse, it should not be made by committee. Reserve collective time for decisions that are expensive to undo.
Protect the hard item first. Put the consequential decision at the top, while attention is fresh, rather than letting it land last when energy is spent. The reactor should never be the thing you rush through in the final two minutes because the shed ran long.
Make the silence on big items suspicious. When a major decision passes with no friction, treat that as a signal, not a success. Ask directly: "This went quiet fast — is that because we agree, or because it's hard to push on?" Naming the under-discussion is how you surface the questions that accessibility crowded out.
What to take from the shed
The deeper lesson of the law of triviality is that the feeling of a productive meeting is an unreliable guide to whether it was one. Resolution feels good. Consensus on something concrete feels good. But those feelings cluster around the easy items, which is exactly why the easy items expand to fill the room. A meeting can leave everyone satisfied and have decided nothing that mattered.
The defense is to stop trusting the texture of the conversation and start watching where the time actually went. Importance and attention should rise together. When they pull apart — when the most airtime went to the least consequential thing — that gap is the bike shed, and it's worth catching while you still can.
That's the habit behind MeetingMortem: it gives a meeting a short, honest post-mortem, so you can see where the minutes really went and whether they tracked the stakes. When the record shows an hour on the coffee budget and four minutes on the contract, the pattern stops hiding in the feeling that you were busy. If you want your team to spend its scarcest resource on the decisions that deserve it, you can start at https://meetingmortem.lumenlabs.works — and bring back what you learn to the next room.