Quality
and the Law of Triviality: When Your Organization Spends More Time
Debating Label Fonts Than Fixing the Process That’s Producing Defects —
and the Trivial Discussions Everyone Engaged In Became the Critical
Problems Nobody Had Time to Address
The
Committee That Built a Nuclear Power Plant in Three Minutes
In 1957, the British cognitive scientist C. Northcote Parkinson
observed something deeply uncomfortable about how organizations make
decisions. He watched a finance committee approve a £10 million nuclear
power plant in two and a half minutes — then spend forty-five minutes
debating a £2,300 bicycle shed for the employees. The reason, Parkinson
explained, was simple: nobody on the committee understood nuclear
reactors, so they had nothing to say. But everyone understood bicycle
sheds. Everyone had an opinion. Everyone felt qualified.
Parkinson called it the Law of Triviality. The rest of the world
calls it bike-shedding. And if you’ve spent any time in quality
management, you’ve watched it happen in your own organization — probably
this week.
The steering committee spends ninety minutes arguing about the color
of the quality dashboard and eleven minutes reviewing the corrective
action plan for a critical customer complaint. The management review
meeting devolves into a heated debate about whether nonconformance
reports should use “defect” or “nonconformity” while the process that’s
generating both terms runs unchecked on the shop floor. The
cross-functional team spends three meetings perfecting the layout of a
form nobody will read and zero meetings discussing why the form’s data
shows a trend that’s about to produce a major failure.
This is not a joke. This is your quality system. And the cost of
bike-shedding is measured not in wasted meeting hours but in the
defects, failures, and customer losses that occurred while everyone was
busy arguing about the shed.
Why Your Brain
Prefers the Shed to the Reactor
Bike-shedding isn’t a character flaw. It’s a cognitive architecture.
Your brain — and everyone else’s — operates on a simple energy-saving
principle: engage with what you understand; avoid what you don’t.
When a quality engineer presents a statistical analysis of process
capability showing that Cpk has dropped from 1.67 to 0.89 on a critical
dimension, most people in the room will nod wisely and move on. They
don’t understand capability indices deeply enough to ask meaningful
questions. The silence isn’t respect. It’s self-preservation. Nobody
wants to expose their ignorance in front of colleagues.
But when someone suggests changing the format of the production
traveller — the routing sheet that accompanies every part through the
factory — suddenly everyone is an expert. The production manager wants
larger fonts. The quality manager wants a signature block added. The
logistics coordinator thinks the checkboxes should be rearranged. The
plant director wonders if it should be printed on yellow paper instead
of white.
Forty-five minutes later, you have a beautifully designed traveller
and a process that’s still producing parts outside specification.
The mechanism at work is deceptively simple: competence
creates confidence, and confidence creates contribution. People
contribute to discussions they feel competent to contribute to. The more
people understand a topic, the more opinions they’ll have, and the
longer the discussion will take. The converse is equally true and far
more dangerous: the less people understand a topic, the fewer opinions
they’ll voice, and the faster the decision will be made — regardless of
how important that decision is.
In quality management, this creates a systematic bias toward trivial
decisions and away from consequential ones. The decisions that determine
whether your product meets customer requirements — process design,
measurement system selection, tolerance allocation, supplier
qualification — receive less scrutiny than the decisions that determine
what color the Andon lights are.
The Anatomy of a Quality
Bike-Shed
Let me walk you through a real scenario. I’ve seen variations of this
play out in automotive, aerospace, medical device, and electronics
manufacturing. The names change. The dynamic doesn’t.
Monday, 9:00 AM — Management Review Meeting
The quality director presents the monthly scorecard. Buried on slide
fourteen is a data point that should stop the meeting cold: three
consecutive months of increasing customer returns on Product Line A,
with the defect rate trending from 0.3% to 0.8% to 1.4%. At this rate,
the company will breach its customer quality threshold within two
months, triggering a controlled shipping requirement that will cost
$180,000 per quarter.
The presentation of this data takes forty-five seconds. The plant
manager asks one question: “Is it the same defect mode?” The quality
director confirms it is. The plant manager nods. The meeting moves
on.
Monday, 9:47 AM — Same Meeting
The conversation shifts to the proposed redesign of the shop floor
quality boards. The lean manager presents three layout options. What
follows is a thirty-minute discussion involving every person in the
room. The production supervisor prefers Layout B because the metrics are
at eye level. The engineering manager thinks Layout A is cleaner. The HR
representative suggests adding an employee recognition section. The
plant director wonders if the boards should be digital. Two people argue
about whether the boards should show weekly or daily data.
At 10:17 AM, the meeting ends. The quality board layout has been
decided. The customer return trend has not been discussed again.
In forty-five seconds, the committee made a decision that affects
$180,000 and a customer relationship. In thirty minutes, they made a
decision that affects the visual aesthetics of a board that most
operators glance at once per shift.
This is bike-shedding. And it is quietly destroying the effectiveness
of your quality management system.
The Three Forms of
Quality Bike-Shedding
Bike-shedding in quality management doesn’t always look like a
committee arguing about a bicycle shed. It takes three distinct forms,
each with its own signature and its own cost.
Form 1: Cosmetic Over
Structural
The organization spends disproportionate time on visible, tangible,
surface-level quality elements while neglecting the structural
foundations that determine actual product quality.
What it looks like: Endless refinement of visual
management boards, quality policy statements, document formatting,
dashboard aesthetics, and workplace organization. The 5S audit scores
are impeccable. The quality manual is beautifully typeset. The SOPs have
perfect formatting. But the measurement systems haven’t been calibrated
in eighteen months, the FMEAs haven’t been updated since launch, and
nobody can explain why Cpk on three critical dimensions has been below
1.0 for the last quarter.
Why it happens: Cosmetic quality is visible.
Everyone can see it, understand it, and have an opinion about it.
Structural quality is invisible to anyone who isn’t actively working
with the data. You can walk into a factory and immediately assess the
visual management. You cannot walk into the same factory and immediately
assess whether the gauge R&R study was conducted correctly.
The cost: The organization looks world-class but
performs at a mediocre level. Auditors are impressed. Customers are
not.
Form 2: Administrative
Over Technical
The organization spends disproportionate time on quality system
administration — documentation, procedures, forms, approvals, reviews —
while neglecting the technical work that actually prevents defects.
What it looks like: The CAPA process has twelve
approval steps and takes an average of forty-five days to close. The
nonconformance report form has grown from one page to four pages over
three years, with each revision adding fields that nobody reads. The
management review agenda has forty-seven items, of which six involve
reviewing actual process performance data. The rest involve reviewing
the review process itself.
Meanwhile, the engineering team hasn’t conducted a design review in
two product launches. The supplier quality engineer is spending 70% of
their time on documentation and 30% on actual supplier development. The
process engineers are so busy maintaining the quality system that they
haven’t been on the production floor in weeks.
Why it happens: Administrative work is comfortable.
It has clear inputs, clear outputs, and clear deadlines. Technical work
is messy. It requires judgment, expertise, and the willingness to
confront uncertainty. Given the choice between reviewing a completed
form and investigating why a process is drifting, most people —
including most quality professionals — will choose the form.
The cost: The quality system becomes a bureaucracy
that consumes resources without producing quality improvement. The ISO
certificate remains on the wall. The defect rate remains on the
dashboard.
Form 3: Comfortable Over
Consequential
The organization spends disproportionate time on quality topics that
are comfortable to discuss while avoiding topics that are consequential
but politically or emotionally charged.
What it looks like: The team enthusiastically
discusses implementing a new SPC software system. It’s an exciting
project with clear deliverables, a generous budget, and no political
risk. Nobody will be upset by a new software tool.
At the same time, everyone knows that the real quality problem is
Operator Station 7, where the senior operator has been deviating from
the standard work for three years because “he knows better” and because
his brother-in-law is the production manager. The process audit data
shows it. The SPC charts show it. The customer complaints trace back to
it. But addressing it means having a difficult conversation with a
powerful person, and nobody is willing to have that conversation.
So the team discusses software instead.
Why it happens: Comfortable topics carry no personal
risk. Consequential topics often involve challenging authority, exposing
failures, demanding accountability, or making unpopular decisions. The
same people who will spend hours debating a software feature list will
fall silent when the conversation turns to why a senior leader’s
department has the worst audit findings in the plant.
The cost: The organization invests in solutions that
don’t address the actual problems. The new SPC software generates
beautiful charts that confirm what everyone already knows but isn’t
willing to act on. The defect rate doesn’t change. The investment is
written off as “improvement” in the annual quality report.
How to Recognize When
You’re Bike-Shedding
The insidious thing about bike-shedding is that it doesn’t feel like
wasted time. It feels like productive work. You’re in a meeting. People
are engaged. Decisions are being made. Action items are being assigned.
How can that be unproductive?
Here are five signals that your quality organization is
bike-shedding:
Signal 1: The discussion duration is inversely proportional
to the decision’s impact. If you spend more time choosing a
font than reviewing a failure mode, you’re bike-shedding. If the
corrective action approval takes longer than the root cause
investigation, you’re bike-shedding. If the document revision meeting is
longer than the process audit review, you’re bike-shedding.
Signal 2: Everyone in the room has an opinion. This
sounds like engagement. It’s actually a warning sign. If everyone feels
qualified to contribute, the topic is probably too simple for the room
you’ve assembled. Your senior leadership team should not be spending its
collective expertise on decisions that a competent individual
contributor could make in five minutes.
Signal 3: The same topics keep coming back. If
you’ve discussed the quality dashboard redesign in three consecutive
meetings, it’s either the most important decision your organization
faces — or it’s a bike-shed. Here’s a test: ask yourself what would
happen if you simply stopped discussing it and made an arbitrary
decision. If the answer is “nothing meaningful would change,” it’s a
bike-shed.
Signal 4: The room goes quiet when the important topics come
up. If the energy drops every time the conversation shifts from
administrative matters to technical performance data, your team is
telling you something. They’re comfortable with the admin and
uncomfortable with the analysis. That discomfort is where the real work
lives.
Signal 5: You leave meetings feeling productive but nothing
improves. This is the ultimate diagnostic. If your meetings are
full of discussion, decisions, and action items, but your quality
metrics aren’t improving, you’re almost certainly spending your time on
the wrong things. Activity is not impact. A meeting agenda that’s been
fully completed is not the same as a quality problem that’s been fully
solved.
The Anti-Bike-Shedding
Framework
Recognizing bike-shedding is necessary but not sufficient. You need a
systematic approach to prevent it from hijacking your quality management
system. Here’s a practical framework I’ve implemented across multiple
organizations.
Step 1: Decision Impact
Scoring
Before any quality meeting, score every agenda item on two
dimensions: impact (how much does this decision affect
product quality, customer satisfaction, or financial performance?) and
expertise required (how much specialized knowledge is
needed to make this decision well?).
Items with high impact and high expertise requirements should receive
the most time and the most senior attention. Items with low impact and
low expertise requirements should be delegated to the lowest competent
level and decided quickly. Items with high expertise requirements but
low impact should be delegated to specialists. Items with low expertise
requirements but high impact — these are your dangerous ones, because
everyone will want to weigh in — should be decided by a designated
decision-maker, not by committee.
This takes ten minutes before the meeting. It saves hours during the
meeting.
Step 2: The
Two-Minute Rule for Complex Topics
Here’s a counterintuitive approach: when a complex, technical quality
issue comes up in a meeting, give it two minutes. Not two hours. Two
minutes.
In those two minutes, the presenter states the problem, the data, and
the proposed response. Then the meeting makes one of three decisions:
(1) approve the proposed response, (2) request additional analysis with
a specific deadline, or (3) escalate to a specialized team.
What you do NOT do is open the floor for general discussion. The
production manager does not need to weigh in on the statistical validity
of a capability study. The HR director does not need to share their
thoughts on measurement system analysis. Complex technical decisions
should be made by people with the expertise to make them — and presented
to leadership for approval, not for debate.
This feels wrong. It feels like you’re rushing important decisions.
But you’re not. You’re protecting important decisions from being drowned
in uninformed commentary. The expertise has already been applied during
the analysis. The meeting is for alignment and approval, not for
rediscovering the analysis through group discussion.
Step 3: Protected Technical
Time
If your quality engineers are spending 70% of their time in meetings
and 30% doing actual quality engineering, you have a bike-shedding
problem at the organizational level. The people who should be preventing
defects are spending their time in discussions about how to prevent
defects.
Establish protected technical time — blocks during which quality
engineers, process engineers, and reliability engineers are not
available for meetings. During these blocks, they work on FMEAs, conduct
process studies, analyze SPC data, perform measurement system analyses,
and investigate root causes. The work that prevents defects is technical
work. It requires focus, expertise, and time. It cannot be done in
fifteen-minute increments between meetings.
Step 4: Agenda Inversion
Most quality meetings are organized from the trivial to the
consequential. Administrative items come first because they’re easy.
Technical items come last because they’re hard. By the time the
technical items come up, the room is tired, the time is short, and the
cognitive energy has been spent on things that didn’t matter.
Invert the agenda. Start with the most consequential, technically
demanding items. Give them the full attention of a fresh room. End with
the administrative items. You’ll find that the administrative items
either resolve themselves quickly (because the room has already
established a tone of decisive action) or turn out to be unnecessary
(because the real decisions have already addressed them).
Step 5: The Bike-Shedding
Audit
Once a quarter, conduct a bike-shedding audit. Review the last three
months of management review minutes, quality steering committee notes,
and corrective action review records. For each meeting, calculate the
ratio of time spent on high-impact decisions versus low-impact
decisions. If the ratio favors low-impact decisions, your quality
management system is not underperforming — it is being prevented from
performing by its own decision-making process.
Share the results with the leadership team. Make the invisible
visible. Bike-shedding thrives in darkness. When people see the data —
“we spent 78% of our quality meeting time on items with minimal quality
impact” — the behavior begins to change.
The
Deeper Truth: Bike-Shedding Is a Symptom, Not a Disease
All of the above is practical and effective. But it addresses the
symptom, not the root cause. The root cause of bike-shedding in quality
organizations is almost always a lack of quality literacy at the
leadership level.
When leaders don’t understand process capability, they can’t ask
meaningful questions about it. When they don’t understand measurement
system analysis, they can’t evaluate whether the data they’re seeing is
trustworthy. When they don’t understand the relationship between
variation and quality, they can’t distinguish between a process that’s
improving and a process that’s just having a good month.
So they focus on what they can understand: forms, formats,
dashboards, and administrative processes. They bike-shed not because
they don’t care about quality but because they don’t know how to engage
with quality at a technical level. The bike-shed is the only structure
in the room they feel qualified to discuss.
This means the ultimate solution to bike-shedding is quality
education. Not training on the quality management system — everyone
already knows how to fill out the forms. Education on the quality
management principles that the system was designed to serve. What is
variation? What does a control chart actually tell you? Why does
measurement error matter? What is the relationship between process
capability and customer satisfaction? How do you read an FMEA well
enough to know whether it’s protecting your customer or just satisfying
an audit requirement?
When leaders develop genuine quality literacy, the bike-shedding
naturally diminishes. Not because you’ve imposed rules against it but
because the leaders now have something more interesting to discuss. They
can engage with the reactor. They don’t need to argue about the
shed.
The Question That Changes
Everything
Next time you’re in a quality meeting and the discussion is running
long on a topic that feels productive but maybe isn’t, ask yourself one
question:
“If this decision were made wrong, would any customer ever
notice?”
If the answer is no, you’re bike-shedding. Move on. Your customer is
waiting for you to discuss something that matters.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has spent decades watching brilliant
teams waste their collective genius on discussions about font sizes
while their processes quietly drifted out of control — and he has
dedicated his career to helping organizations redirect their attention
from the trivial to the transformative.
