Quality
and Parkinson’s Law: When Your Organization’s Quality Projects Expand to
Fill Whatever Time You Give Them — and the Deadline You Set Becomes the
Only Thing That Determines How Long Improvement Actually Takes

The Six-Month
Project That Took Six Months

In 1955, a British naval historian named Cyril Northcote Parkinson
published a short essay in The Economist that would become one
of the most quoted observations in management science. He had been
studying the British Admiralty and noticed something odd: the number of
administrators was growing even as the number of ships was shrinking.
The work wasn’t expanding because there was more of it. The work was
expanding because there were more people available to do it.

Parkinson distilled this into a law: “Work expands so as to
fill the time available for its completion.”

Sixty words. One sentence. And yet it explains something that every
quality professional has witnessed but rarely names: the eight-week
corrective action that takes exactly eight weeks. The six-month FMEA
update that finishes on the last day of month six. The year-long quality
transformation that somehow needs every single day of that year.

Not because the work required that much time. Because that much time
was available.

The
Laboratory Inside Your Corrective Action System

If you want to see Parkinson’s Law in action, don’t read Parkinson.
Open your corrective action database and sort by closure date.

Look at the actions that were assigned a 30-day deadline. Most of
them closed somewhere around day 28 or 29. Now look at the ones that
were given 90 days. They closed around day 85. The six-month actions?
They closed at month five, week three.

Same types of problems. Same organizations. Same people. Completely
different durations. And the only variable that predicted how long the
corrective action took was the deadline someone wrote on the form.

This isn’t laziness. This isn’t incompetence. This is a fundamental
property of how human beings manage complex work when the constraints
are soft and the finish line is arbitrary. When you give a team six
months, they will find a way to use six months. When you give them six
weeks, they will find a way to do it in six weeks. The work doesn’t
change. The behavior around the work changes.

Why Quality Work Is
Especially Vulnerable

Parkinson’s Law operates everywhere, but it has a particular affinity
for quality work. Here’s why.

Quality projects are often ill-defined. “Implement
SPC on Line 7” could mean anything from printing a control chart and
taping it to the machine to building a real-time statistical monitoring
system with automated out-of-control alerts. The ambiguity invites
expansion. If you have twelve weeks, “implement SPC” gradually grows to
include everything from operator training to dashboard design to a fully
automated data collection system. If you have three weeks, it shrinks to
the essential: plot the data, calculate the limits, and start
reacting.

Quality work has no natural stopping point. Unlike
production — where the shift ends when the parts are made — improvement
work can always be refined, extended, documented more thoroughly, or
validated more rigorously. There is always one more data point to
collect, one more stakeholder to consult, one more scenario to test.
This infinite horizon means the deadline isn’t just a constraint. It’s
the only constraint.

Quality teams are perfectionists by training. We
teach our people to care about details. We teach them to verify,
validate, and confirm. And then we’re surprised when they use every
available minute to verify, validate, and confirm one more time. The
same mindset that prevents defects also prevents efficiency.

Quality improvement lacks market feedback. When a
product development team ships late, customers complain. When a quality
improvement project finishes late, almost nobody notices — because the
“customer” is internal, the “product” is a process change, and the
“deadline” was a suggestion written on a project charter that nobody
outside the quality department ever read.

The Comfort of a Long
Deadline

There is a particular kind of organizational psychology at work here,
and understanding it is the first step toward managing it.

When a manager assigns a six-month deadline to a corrective action,
it feels responsible. It feels thorough. It communicates that the
organization takes the problem seriously. The manager gets credit for
being diligent. The quality team gets breathing room. Everyone feels
good.

But what actually happens during those six months?

Typically, the first two weeks involve genuine urgency. The problem
is fresh, the data is available, the energy is high. Then comes the
planning phase, which is legitimate but expandable. The team meets. They
define scope. They assign roles. They build a timeline. This takes a
week if the deadline is tight. It takes a month if the deadline is
generous.

Then comes the analysis phase — and this is where Parkinson’s Law
really flexes. With a tight deadline, the team identifies the most
likely root cause, verifies it, and moves on. With a generous deadline,
they investigate every possible cause, run additional tests, consult
external experts, and build elaborate Ishikawa diagrams that look
impressive in presentations but don’t change the conclusion.

The implementation phase follows the same pattern. With a tight
deadline, the team implements the minimum viable countermeasure and
monitors the results. With a generous deadline, they redesign the entire
process, update every related document, train every affected operator,
and build a comprehensive monitoring dashboard — all for a problem that
might have been solved with a single fixture modification.

The final weeks are almost always consumed by documentation, review
cycles, and the slow mechanics of closure. The corrective action report
gets written, reviewed, revised, reviewed again, and finally signed off.
The effectiveness check gets scheduled, conducted, documented, and
filed. Each step is legitimate. Each step could be done faster. But why
rush? The deadline is still weeks away.

The Cost of Padded Time

The financial cost of Parkinson’s Law in quality work is substantial
but hard to see, because it doesn’t show up as a line item on any
budget.

First, there is the cost of extended problem duration. Every day a
known defect continues, it generates real costs — scrap, rework,
warranty claims, customer complaints, audit findings. A corrective
action that takes six months instead of six weeks isn’t just slower.
It’s more expensive, because the problem keeps producing damage for five
additional months.

Second, there is the opportunity cost. The quality engineer who
spends six months on one corrective action could have addressed four
problems in the same period with tighter deadlines. The organization
doesn’t just lose time. It loses the improvements that time could have
produced.

Third, there is the cost of organizational attention. A quality
problem that lingers for months becomes background noise. It stops
generating urgency. People stop talking about it in the morning meeting.
The customer who filed the complaint stops waiting for a response and
starts looking for a new supplier. The momentum that could have driven
real improvement dissipates into the comfortable fog of “we’re working
on it.”

Fourth — and this is the one nobody talks about — there is the cost
of over-engineering. When teams have too much time, they don’t just work
slower. They work bigger. The simple corrective action becomes a
systemic redesign. The single countermeasure becomes a comprehensive
action plan with twelve deliverables. And each of those deliverables
introduces new risks, new failure modes, and new opportunities for
things to go wrong. The cure becomes more dangerous than the
disease.

The
Counterintuitive Solution: Shorter Deadlines

The answer to Parkinson’s Law in quality work is not to work harder
or to monitor more closely. The answer is to give people less time.

This feels reckless. Quality professionals are trained to be
thorough, and thoroughness takes time. Cutting deadlines feels like
cutting corners. It feels like the kind of shortcut that produces the
very defects we’re trying to prevent.

But consider the evidence. When organizations implement rapid
problem-solving methodologies — Toyota’s Practical Problem Solving,
six-week Kaizen events, or 8D with strict timeboxing — the quality of
the solutions doesn’t degrade. In many cases, it improves.

This is because shorter deadlines force prioritization. When you have
two weeks to solve a problem, you can’t afford to investigate every
possible root cause. You have to identify the most likely one quickly,
verify it efficiently, and implement a countermeasure. You focus on what
matters and discard what doesn’t. The constraint doesn’t reduce quality.
It sharpens it.

Shorter deadlines also force collaboration. When time is abundant, a
quality engineer can work in isolation for weeks — analyzing, planning,
documenting — before engaging the production team. When time is short,
the engineer has to go to the gemba immediately, talk to operators
directly, and build solutions with the people who will implement them.
The constraint produces better teamwork.

And shorter deadlines produce faster feedback. A countermeasure
implemented in two weeks generates real production data within a month.
If it works, you know quickly and can replicate it. If it doesn’t work,
you know quickly and can adjust. A countermeasure implemented over six
months generates feedback so slowly that by the time you discover it’s
not working, the organization has already moved on to the next
crisis.

The Art of
the Aggressive but Achievable Deadline

Not all deadlines should be short. Some quality problems genuinely
require months of work — a supplier quality transformation, a multi-site
FMEA program, or a management system redesign. Parkinson’s Law doesn’t
argue that all work can be done quickly. It argues that work will expand
to fill available time, and that the deadline you set shapes the
efficiency of the work more than the complexity of the problem does.

The practical approach is to set deadlines based on the minimum time
required, not the maximum time available. This means:

Break large projects into small deliverables.
Instead of a single six-month corrective action, define six one-month
milestones. Each milestone has a specific output, a clear owner, and a
firm deadline. The overall timeline stays the same, but the work is now
structured to prevent expansion.

Distinguish between critical-path work and nice-to-have
work. Critical-path work is the minimum set of actions required
to eliminate the root cause and verify effectiveness. Everything else —
expanded documentation, additional training, broader scope, aesthetic
improvements to the corrective action report — is optional and should be
treated as such. Complete the critical path first. Add refinements only
if time remains.

Use timeboxing for analysis phases. The analysis
phase of any quality investigation is the most vulnerable to Parkinson’s
Law. It’s open-ended by nature: there’s always more data to analyze and
more theories to test. Timeboxing — “we will spend exactly three days on
root cause analysis and then move to verification” — forces the team to
make decisions with the information they have rather than waiting for
perfect certainty.

Review progress at the midpoint, not the endpoint. A
six-month project that’s reviewed only at month six will take six
months. A six-month project that’s reviewed at month one, month three,
and month six will still take six months — but the quality of the work
will be higher, because the midpoint reviews create accountability that
the distant deadline alone cannot provide.

The Cultural Dimension

Ultimately, Parkinson’s Law in quality work is not a time management
problem. It’s a cultural problem. It thrives in organizations where:

• Deadlines are treated as suggestions rather than commitments
• Thoroughness is always valued over speed, regardless of context
• The penalty for finishing early and missing something is greater
  than the penalty for finishing late
• Quality projects are measured by effort rather than results
• Nobody asks whether the additional time actually produced additional
  value

The organizations that resist Parkinson’s Law most effectively are
the ones that have built a culture of urgency without panic. They don’t
rush. They don’t cut corners. But they also don’t inflate. They have a
clear sense of what “done” looks like, and they stop when they get there
— not when the deadline arrives.

This is a leadership decision more than a process decision. It
requires managers who are willing to say, “This corrective action should
take three weeks, not three months, and I’m setting the deadline at
three weeks.” It requires quality professionals who are willing to push
back on scope creep and deliver the minimum effective solution rather
than the maximum possible one. And it requires organizations that
measure the speed of improvement as carefully as they measure the speed
of production.

The Parkinson Test

Here’s a simple diagnostic. Open your quality project portfolio and
ask one question: If you cut every deadline in half, how many
projects would actually fail?

If the honest answer is “very few,” then Parkinson’s Law is running
your quality system. The deadlines aren’t protecting you. They’re
slowing you down. And every day that a known quality problem continues —
not because it can’t be solved, but because the calendar says there’s
still time left — is a day your organization is paying for comfort it
cannot afford.

Parkinson saw it in the Admiralty. You can see it in your corrective
action database. The work will expand to fill the time. The only
question is whether you’re setting the time — or whether the time is
setting you.

---

Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries.