Innovation Team Reference

Parkinson's Laws
A Practical Guide

Four principles from C. Northcote Parkinson's 1957 work that explain why teams spend their energy on the wrong things — and what to do about it.

Cyril Northcote Parkinson was a British naval historian who, in 1955, published a satirical essay in The Economist based on his observations of the British Civil Service. Despite its humour, the essay exposed real organisational dysfunctions — and the principles he described have held up across nearly seven decades of management research. He expanded the essay into a 1958 book, Parkinson's Law: The Pursuit of Progress, which went on to become an international bestseller. There are four interconnected laws worth knowing.

The Four Laws
Law 01
Parkinson's Law
"Work expands so as to fill the time available for its completion."
Give a team two weeks for a one-day task, and it will take two weeks. The extra time doesn't produce better output — it fills with unnecessary revisions, scope creep, delayed starts, and a false sense that complexity must match the available calendar. Parkinson illustrated this with a woman whose only task for the day was to send a postcard. Finding the card, locating her glasses, composing the message, deciding whether to take an umbrella to the postbox — the task expanded to consume her entire day.
The evidence

Parkinson studied the British Admiralty and found that administrative staff increased while the number of ships in the fleet decreased. The Colonial Office had its greatest number of employees at the point when it was folded into the Foreign Office — because there were no more colonies left to administer.

Law 02
The Law of Triviality
"The time spent on any item of the agenda will be in inverse proportion to the sum involved."
Also known as bikeshedding. The less expertise required to have an opinion, the more opinions you'll get, and the longer the discussion runs. Parkinson imagined a committee reviewing plans for a nuclear power plant. The reactor design — a $10 million decision requiring specialist knowledge — was approved in minutes. The $350 bike shed provoked 45 minutes of debate. A $21 coffee budget for meetings threatened to consume the entire session.
Why it happens

People don't want to appear uninformed, so they avoid weighing in on complex topics where they might be wrong. But on familiar, low-stakes topics — everyone feels qualified. The risk of being wrong is near zero, and the desire to demonstrate value is high. The result: attention flows to the trivial, and the consequential goes unchallenged.

Law 03
The Coefficient of Inefficiency
Committees become ineffective as they grow. The optimal range is 5–8 members.
Parkinson devoted an entire chapter to what he called comitology — the study of how committees are born, grow, and eventually become useless. He traced British government cabinets across centuries and found a consistent pattern: as a governing body grows beyond ~20 members, real power migrates to a smaller inner group. The formal body becomes ceremonial. The cycle then repeats.
The pattern

The Council of the Crown grew from a small body to 50+ members and lost its power. It was replaced by the Lords of the King's Council (~10 members), which itself grew and was replaced by a Cabinet of five. By the 1950s, the Cabinet had inflated to 20+, and real decisions had already migrated to an inner kitchen cabinet. The empirical ceiling for functional decision-making: somewhere between 19.9 and 22.4 members, beyond which a committee is manifestly ineffective.

Law 04
Administrative Bloat
The number of people in an organisation grows regardless of whether the work grows.
This is the organisational version of Law 01. Parkinson identified two driving forces: first, managers want to multiply subordinates, not rivals — so they hire assistants rather than peers. Second, officials create work for each other — every new layer of management generates coordination overhead that the layer below must service. The result is a self-perpetuating cycle of growth that has no relationship to output.
Parkinson's formula

He calculated that the British Civil Service grew at 5–7% per year regardless of workload. When Gorbachev heard about Parkinson's work in 1986, he reportedly said: "Parkinson's Law works everywhere." The book became a bestseller in the Soviet Union — a bureaucracy that understood the diagnosis intimately.

Where You'll See This in Innovation Work
Bikeshedding
The demo day slide debate
The team spends 30 minutes arguing over slide layouts, colours, and font choices for a stakeholder presentation — while the actual narrative and success metrics get five minutes of discussion. The slides are easy to have opinions on. The strategy is hard.
Parkinson's Law
The delivery cycle fills its container
A project that could be validated in three weeks expands to fill the full delivery cycle. The extra time doesn't produce more insight — it produces more polish, more edge cases explored prematurely, and more status meetings about progress.
Coefficient of Inefficiency
The steering committee grows
What started as a five-person review group now has 15 members. Decisions that used to take one session now require pre-meetings, alignment sessions, and follow-ups. The real calls get made in a hallway conversation between two people anyway.
Bikeshedding
Naming the project
Everyone has strong feelings about what to call the initiative. Nobody has strong feelings about the measurement methodology that will determine whether it succeeds or fails. The name is visible and low-risk. The methodology is invisible and high-stakes.
Administrative Bloat
Process layers accumulate
Each new initiative adds a reporting template, a check-in cadence, a sign-off step. None are ever removed. Over time, the overhead of running the innovation process consumes more energy than the innovation itself.
Parkinson's Law
The "thorough" research phase
Given four weeks of discovery, the team fills four weeks — reading broadly, mapping exhaustively, building decks. Given one week, they'd focus on the three questions that actually matter and get to the same decision point.
What to Do About It
1
Name it in real time
The single most powerful countermeasure is shared vocabulary. Once a team knows the term "bikeshedding," anyone can call it out mid-meeting without it feeling like an accusation. It becomes a neutral observation: "I think we're bikeshedding" is much easier to say than "you're all wasting time on something that doesn't matter."
2
Timebox the trivial, protect the complex
Invert the default allocation. Give low-stakes decisions a hard two-minute cap. Reserve the bulk of meeting time for the one or two items that are genuinely hard. If an agenda item is easy enough for everyone to have an opinion, it's easy enough for one person to decide.
3
Assign single owners to small decisions
Bikeshedding only happens in groups. If one person owns the bike shed — the slide template, the project name, the meeting room — nobody else debates it. Reserve group decision-making for things that actually require multiple perspectives.
4
Shrink the container
Work fills the time you give it. Shorten the deadline and the work compresses to fit. A four-week discovery phase becomes a one-week sprint. A 60-minute review becomes a 25-minute standup. The constraint forces focus on what actually matters and eliminates the filler.
5
Keep decision groups at 5–8
If a meeting has more than eight people, it's a broadcast, not a decision forum. Decide who the actual decision-makers are and keep the group tight. Everyone else gets informed of the outcome. More voices doesn't mean better decisions — it means slower ones.
6
Run the subtraction audit
Periodically ask: what processes, meetings, reports, or approvals exist that no longer serve the work? Administrative bloat is invisible because each layer feels small. The accumulation is what kills you. Remove one thing before adding anything new.

The Parkinson Inversion Test

Before your next meeting, project kickoff, or planning session, run four quick checks:

Time: If we had half the time, would we still reach the same decision? If yes — we have too much time.
Triviality: Is the energy in the room proportional to the stakes of the topic? If not — we're bikeshedding.
Headcount: Does every person in this room need to be here for a decision to happen? If not — shrink the group.
Process: Would this process exist if we were starting from scratch today? If not — it's bloat.
Based on C. Northcote Parkinson's Parkinson's Law: The Pursuit of Progress (1958). Concepts are paraphrased summaries of Parkinson's original observations, applied to innovation team contexts.