Parkinson's Law of Triviality
"The time a committee spends on an item is inversely proportional to the money involved."
"The time a committee spends on an item is inversely proportional to the money involved."
The law of triviality holds that an organisation, especially a committee, devotes attention to an issue in inverse proportion to its actual importance or cost. Groups give disproportionate weight to trivial, easily grasped matters while under-scrutinising the important, complex, or expensive ones. In software culture the same pattern is called bikeshedding, from Parkinson's image of a committee waving through a nuclear reactor but bickering endlessly over a bicycle shed. A bike-shed discussion is one that consumes energy out of all proportion to its stakes.
Rated Heuristic: a dependable rule of thumb, not a proven theorem. The other 224.
The driving force is comprehensibility and the sense of competence it confers. A vast, technical, expensive item, a nuclear reactor, is beyond most committee members, so rather than engage they defer, assuming someone else checked the details. A trivial item, a bicycle shed or the coffee budget, is within everyone's grasp, so everyone feels qualified to weigh in and does. Because contributing an opinion is how members demonstrate diligence and belonging, the easy items lower the barrier to participation and attract a flood of it, while the consequential ones pass in near silence.
The software world's name for the same law, from Kamp's 1999 email: the urge to argue about the colour of the bike shed (the thing anyone can build over a weekend), rather than the reactor no one dares question.
The close relative: in any dispute the intensity of feeling is inversely proportional to the value of the issues at stake, which is why the trivial agenda item generates the most heat.
It explains how agendas get distorted so that low-stakes, high-comprehension items crowd out the high-stakes, high-complexity ones, degrading consequential decisions. Boards and committees can appear to exercise vigorous oversight of trivia while effectively rubber-stamping the choices that carry the real risk, precisely because those are hard to scrutinise. In engineering teams, naming the pattern as bikeshedding is itself a defence, letting maintainers recognise and shut down debate that has grown out of proportion to what is at stake.
It is an illustrative heuristic, not a measured relationship: Parkinson wrote as a satirist, and the committee scene and its figures are a fictional illustration rather than data, so the 'inverse proportion' phrasing is rhetorical. Nor is disproportionate attention always irrational; small recurring costs, precedent-setting items, and morale can genuinely warrant discussion, and quick approval of a large item may reflect legitimate prior vetting rather than negligence. The effect is strongest where members lack expertise on the big item and feel accountable to be seen participating, and weaker where real expertise or clear ownership exists.
It is not the same as Parkinson's Law proper, that work expands to fill the time available; the two are distinct ideas from the same book. Bikeshedding is not old slang but a term traceable to Kamp's 1999 email, decades after Parkinson. The reactor, shed, and coffee figures are Parkinson's invented example, not a report of a real meeting. And the claim is about disproportionate attention, not that small matters are worthless.
Real as a rule of thumb, not as a theorem. Parkinson's Law of Triviality is rated Heuristic here: dependable enough to plan with, and with no proof behind it.
Rated from three sources. 225 of the 1,116 entries carry this rating. How the scale works.
The best-known laws are the least likely to rest on measurement; the full verdict on Parkinson's Law of Triviality.
Stated by C. Northcote Parkinson in his 1957 book Parkinson's Law, or The Pursuit of Progress, in the essay 'High Finance, or the Point of Vanishing Interest': a different essay from, and not to be confused with, his main law that work expands to fill the time available. The software term 'bikeshedding' comes from Poul-Henning Kamp's 1999 FreeBSD email.
10 languages, as recorded on Wikidata. These are names the idea already goes by, not translations we made. The whole index by language.
Everything above traces to archive.org, phk.freebsd.dk and en.wikipedia.org, three sources in all, two of them the original publications rather than accounts of them. Nothing is written from memory, and the method is written down. Spot an error or a better source? Suggest a fix.