Small mistakes from those on “your side” unaware of the marching orders, which line up like James Reason’s slices of Swiss cheese, creating a path for disaster to walk straight through the holes.

Why Structure Isn’t Optional

A method isn’t a luxury; it’s a vaccine. And to achieve herd immunity, everyone needs to be vaccinated. The idea of the lone hero - the method certified PM - improvising a win belongs in cheap thrillers.

Standards don’t just tidy up paperwork in order to please your internal auditor — they make roles, checkpoints, and who-decides-what so clear that the organization moves like a marching band, not a garage jam session.

What This Training Actually Means

It isn't about polishing every specialist until they shine. It’s about making sure everyone shares the same proficiency in your chosen method, so that they all:

• work from the same playbook (documents, meetings, controls),

• know the checkpoints, the roles, and who gets the final say,

• And catch the usual small errors before they snowball into a real failure.

Real success comes from people knowledgeable enough on project execution to agree on the way forward.

The Tax You Pay When You Don’t

Neglecting to educate all on the methodology will make you pay dearly for:

• Signal loss with stakeholders;

• Ownership so muddled that decisions ooze rather than occur;

• Ad-hoc patchwork that saws through quality and schedule;

• And shadow systems that disperse “truth” across competing spreadsheets.

Read enough Issue Logs, and you’ll get sick of the same conclusion: thin training plus fuzzy procedure equals harm that was entirely avoidable.

What “Good” Looks Like

Educate before kickoff, not mid-flight. Teaching your method while the house is on fire is how manuals end up as evidence at the inquest.

Do it for everyone, not just the project manager. Making the PM the sole keeper of the sacred knowledge is both unfair and ineffectual.

Clarify role-specific responsibilities: who decides, when, on which inputs, and when to escalate. Not every type of decision is made democratically. The user representative on a board evaluates the implications of various technological options, but should not always have the final word. Especially not when it comes to signing off on "known bugs”. Read I Am Spartacus for more on that.

And for big projects with lots of handoffs, General Stanley McChrystal’s book Team of Teams makes a point worth borrowing: shared method comes first, speed follows — it’s a result, not a shortcut.

On Institutional Responsibility

Asking a PM to…

• lead a team that’s never been trained in the company’s own method,

• report to a Board that is not fluent in the methodology,

• inside a company that hasn’t mastered it either.

…isn’t a plan; it’s a mistake dressed up as one.

What follows won’t be “learning on the job.” It’ll be losing the same way twice, capped off with a tidy post-mortem listing the training that would have saved everyone the public embarrassment and tombstones reading “Agile in Name Only”. These tombstones have reportedly sold out.

Last Word

No generals were harmed writing this, but the rule is older than most military uniforms: agree on the rules of engagement, then run the mission. Getting everyone aligned isn’t a nice extra — it’s what makes the team stronger than the sum of its parts.

Skilled people, trained in the same method, are your best shot at getting out alive — especially when you’re dropped into the swamp of corporate politics and the quiet sabotage of people who exploit the process-knowledge gaps present in both the army brass and the cannon fodder.

The Wet Sponge

Every tribe has its talisman. In childhood it was mother’s kiss: a sacrament applied to a scraped knee with miraculous results. On the football pitch—soccer, if you must—the anointed object is the damp sponge. A man writhes as though auditioning for the Last Rites; a sponge is dabbed; Lazarus sprints.

Projects have their own sponge. It goes by “contingency” or “tolerance,” depending on which catechism you recite. And—here is the true enchantment—it is always ten percent. Not eight, not fifteen. Ten. The digits march like Roman soldiers: And. It. Is. Always. Ten. Percent.

Reality is not Fixed

This, in a sane world, would be the point at which someone asks whether the margin of error might have something to do with reality. With how well we know the domain. With the volatility of prices, the fragility of suppliers, the novelty of the technology, the competence (or absence) of the team, the brutality of the schedule. But no: bring forth the silver bullet that fits every caliber.

Is it a Perfect 10?

Why ten? Nobody knows, and—more damning—nobody seems embarrassed not to know. Perhaps, in some ancestral spreadsheet, ten percent was a defensible hedge for one specific undertaking. Perhaps a standards committee embalmed it, and the embalming fluid spread across the corporate bloodstream. Or perhaps it diffused the way all superstitions do: because it was tidy, repeatable, and made the anxious feel insured against the weather.

Whatever the origin, the effect is the same. A risk unpriced is a risk unmanaged, and a risk priced by numerology is managed by nobody.

Contingency Reflects the Risk

The adult alternative is not mystical: quantify uncertainties, model ranges, revisit as information improves, and fund the consequences. Some projects deserve two percent; others, twenty and a prayer. Only a cult would insist they all merit the same tithe.

A “Safe” 10% is not Safe

But then, magic has its consolations. You don’t have to think; you don’t have to argue; you don’t have to tell the Steering Committee that the gods may be angry and that appeasement will cost more than a round number. You can intone “ten percent” and pass the peace.

As with all talismans, the power is in the believer, not the object. And as with all talismans, reality eventually intrudes.

The loudest calendar sets the plan, scope contorts to fit the week, and “quality” is whatever passes a demo. Entropy, as physics reminds us, isn’t a metaphor but a law, and no amount of TED-talk optimism grants an exemption.

When You Throw Away the Map

When you “go it alone,” the same failure modes arrive as reliably as Monday:

• Timelines slip because plans were fantasies, not baselines.

• Risks detonate because nobody is logging, owning, or escalating them.

• Signals garble, and stakeholders talk past each other.

• Quality sags, rework blooms.

• Roles blur, so accountability evaporates.

• “Flexibility” mutates into scope creep (the managerial euphemism for cowardice).

• Shadow practices appear, spreadsheets and back-channel reports, the only things that actually work.

Why Leaders Skip Structure (and Why That’s Folly)

Organizations rarely renounce methodology after sober inquiry. They do it from the narcotic of wishful thinking: the fantasy that brilliance will flourish best uncoached, unbounded, and unreviewed. One recalls Aristotle’s distinction between potentiality and actuality; the former never becomes the latter without form. Methodology is not a prison; it is the scaffolding that keeps the cathedral from collapsing while the artisans do their work.

The PM Paradox

Rip out the guardrails, and your most capable people begin to shoulder unpriced risk. The conscientious become human shock absorbers, until, inevitably, physics wins and the blast radius widens. Meanwhile, the unscrupulous, who treat ambiguity as their native element, flourish. Methodologies exist for the same reason mountain roads have barriers: to keep talent alive long enough to reach the summit.

If you need a reminder of where “winging it” leads, recall Chernobyl.

Any Methodology Helps (Even an Imperfect One)

Choose Scrum, a lean PM playbook, or a principled PMBOK-style setup; almost any coherent approach beats “vibes-based delivery.” Done sanely, structure:

• Stabilizes planning with baselines you can steer against.

• Forces risk management and real escalation paths.

• Clarifies roles and decision rights (no more séance-style meetings).

• Standardizes communication and status so truth can travel.

• Bakes in quality gates and acceptance criteria.

• Makes forecasts first-class citizens instead of an afterthought.

Set Expectations Like an Adult

To be clear, no methodology, however sanctified, guarantees success; what it guarantees is a higher average and survivable failures. Free-solo climbers train obsessively so that the “freedom” looks graceful rather than terminal. The ease is engineered.

Treat methodologies as an operating system, patched and updated, not as scripture to idolize or a papier-mâché effigy to beat with sticks at the quarterly offsite. The point is not ritual; it is reliability.

Bottom Line

If leadership cannot stomach even a lightweight methodology, take the hint about future projects: you’re being asked to cross a minefield with a blindfold and a pep talk. Put the rails back on, pick a methodology you will actually practice, and shorten the distance between plan and reality.

If you still crave “freedom,” try this kind: freedom from preventable failure.

How the Slogan Shrunk the Goal

The phrase began as shorthand for balanced delivery: right thing, right way, right cost, right time. Taken literally, it amputates what makes the effort worthwhile:

• Scope: Did we deliver the thing we promised, not just something with the same label?

• Quality: Is it usable, reliable, and safe (or merely demo-able)?

When these vanish, organizations celebrate counterfeits: features kicked to “phase two,” quality shaved to meet a date, defects deferred like unsecured debt. (For a classic warning, read Brooks’s The Mythical Man-Month.)

Why Smart People Keep Falling for It

This narrow success frame persists because it produces flattering illusions:

1. False positives: Punctual mediocrity passes as victory.

2. Cosmetic control: Gantt charts behave even when risks go unmanaged.

3. Perverse incentives: Worship a metric; get rituals, not results.

Software teams learned this the hard way, which is why they track lead time, deployment frequency, change-failure rate, and mean time to restore; signals that outcomes, not optics, are improving.

What Competence Actually Requires

Real management solves a system of equations, not a single constraint. Judge performance across multiple dimensions and accept that trade-offs are inevitable:

1. Time & Cost (necessary, never sufficient).

2. Scope (completeness and intent, not scope creep by stealth).

3. Quality (defects, reliability, usability).

4. Benefits (adoption and activation now; revenue and cost-to-serve later).

5. Risk (which hazards we reduced, accepted, or created).

6. Stakeholders (expectations met, not just signatures collected).

The adult distinction is between disciplined trade-offs (explicit, justified, transparently governed) and undisciplined slippage (quiet cuts and quiet hopes).

A Better Instrument: Scorecard, Not Slogan

Replace the bumper sticker with a compact scorecard that makes trade-offs visible and auditable:

• Baseline vs. Actual Time/Cost: facts over boasts.

• Planned vs. Achieved Scope: no euphemisms.

• Quality Outcomes: escaped defects, uptime/SLOs, usability thresholds.

• Benefits Realization: leading (usage, activation) and lagging (unit economics).

• Risk Posture: open risks, mitigations, residual exposure.

• Stakeholder Signals: satisfaction deltas, not vanity NPS.

Evaluate the how (governance, risk management, change control) alongside the what (measurable outcomes). If this feels unfamiliar, start with Kaplan & Norton’s Harvard Business Review classic, The Balanced Scorecard - Measures That Drive Performance.

Conclusion: Retire the Small God

A project can miss its first date or budget and still be exemplary if it delivers the right scope at durable quality, realizes benefits, and manages risk openly. But a project that hits date and dollar while hollowing out everything else is not a success, it’s a liability with good manners. If “on time and on budget” is your whole liturgy, you’re grading chance and calling it leadership. Raise the standard; measure what matters.

Content over Competence

Seasoned project managers know the ritual. You’re vetted by an intermediary whose first sacramental question is, “Do you have experience with Unicorns?” Answer “No,” and the catechism concludes: “Too bad—client insists on deep Unicorn expertise.” Your history of delivering complex efforts in a controlled manner is waved away. Content is king; competence is court jester.

Product versus Process Knowledge

Consider the farce as it would look in any other arena. You’re hiring someone to organize a rock festival. The decisive criterion? Not whether they can plan logistics, wrangle suppliers, manage risk, and keep 50,000 humans watered, fed, and untrampled—but whether they can play lead guitar and recite Metallica’s back catalog. That they have already staged jazz, film, and food-truck festivals with aplomb counts for little. If they can’t shred, they can’t shepherd. Thus, expertise in the product masquerades as expertise in the process.

Appointing a project manager on content alone is selecting the right man for the wrong job—and then blaming him when he does the job he was selected for. You have, in effect, hired a fan to run security.

Kill Your Darlings

Two pathologies follow. First, conflict of interest. A project manager’s cardinal duty is adjudication: trading scope against time against money, and doing so without emotional attachment to any single feature. The domain obsessive—our rock purist—will be tempted to spend the medical tent on an extra band, because the music moves him more than the ambulance does. Affection is not governance.

Stay Afloat

Second, loss of altitude. The subject-matter manager cannot help plunging into the weeds, second-guessing the very specialists they hired. They meddle because they know, and because knowing feels like managing. Meanwhile, the real work—forecasting cost, policing risk, sequencing dependencies, choreographing change—goes malnourished.

Look Ahead, not Down

These are the managers who brief the Steering Committee with breathless technical minutiae about a change request, yet cannot produce an up-to-date cost forecast, a living risk profile, or the mitigations that make unpleasant surprises merely expensive rather than fatal.

Put differently: they’re backstage tuning guitars and arguing over the set list while no one is erecting the ticket booths, stocking the concessions, or ensuring that the toilets, those unglamorous guarantors of civilization, actually function. The music may be sublime; the festival will still fail.

Respect and Value the Trade

The remedy is drearily adult. Hire project managers for the things they do: impose structure, price risk, arbitrate trade-offs, and keep promises. Let experts be experts, accountable for outputs within their craft. The project lead's demand is not devotion to a domain, but fidelity to delivery. If you must worship something, worship the schedule and the balance sheet; they, unlike taste, can be audited.

Otherwise, by all means keep privileging virtuosity over vigilance. Just don’t feign astonishment when the solos soar and the crowd stampedes.

Far out!

Yes, literally.

Here Comes the Bride

Permit, for once, a domestic parable. You are the father of the bride: dazed by the prospect of your princess leaving the citadel, and newly acquainted with the medieval custom that her joy will be financed by your treasury. The dress was chosen at thirteen, the napkin colors at fifteen; the bill is due now. You hire a wedding planner—your project manager—who compiles requirements, drafts a plan, and totals the cost.

Mr Murphy is Also Invited

Do you then sleep the untroubled sleep of the credulous, persuaded that a fairytale admits no plot twists? Or do you, like any sentient mammal, ask what might go wrong? Rain, for example—the wet kind, not the confetti. Power failure, a vanishing band, an inconvenient illness, a venue that “regrets to inform you” at the eleventh hour. If you have even a trace of paternal instinct—and a memory of how reality behaves—you treat these not as hallucinations but as probabilities with price tags.

Assess and Act

So you act. You watch the forecast and line up tents. You rent a generator—not to run Versailles, perhaps, but enough to keep the champagne cold and the music audible. You fit the band’s contract with a penalty clause and stock a list of disc jockeys as fallback. You arrange for first aid. As for the nightmare of the venue canceling: it is low-likelihood, high-impact. You can insure against it with a punitive clause, line up a backup site, or—consciously, deliberately—accept the risk and its consequences. Note the verb: accept, not ignore.

Issues Arise but Solutions are in Place

On the day, something does, of course, go wrong. A shower passes; the tents shrug it off. The band appears; Uncle Peter does not, quite—he is revived by the medics after too many toasts to the happy couple. The generator hums pointlessly, and you are glad it does: paying for a needless precaution is cheaper than mourning the absence of music and melted ice. The event is beautiful. The album will inflict ninety minutes of “how delightful” on future visitors. Your wallet is thinner; your daughter is incandescent. You count that a bargain.

Risks are not Optional

Now observe how differently projects are treated. Project managers are told to identify risks, to update the log, to demonstrate vigilance. But when they propose the adult sequel—mitigation with a price, contingency with cash—our sacerdotal Steering Committee recoils. Risks, you see, are “virtual.” Their probability hovers near zero in the metaphysics of the spreadsheet. Money attached to them is “optional,” “non-productive,” a tax on optimism. Why approve now what you might never need? Why buy tents when the sun is still shining on the slide deck?

A Real “Shocker”

And then, inevitably, the sky darkens. A major issue arrives, punctual as gravity, and the most scandalized faces in the room are the very ones that vetoed the umbrella. The risk, documented from day one, never registered as real because it was never budgeted as real. In that sense alone, the surprise is genuine: they are startled by their own refusal to believe in weather.

Live Happily Ever After

Memorize this, if you can’t bear to tattoo it: a risk not priced is a risk not managed. Either mitigate and fund, or accept and own. But do not sanctify pretense—do not confuse a log entry with a parachute.

If only every risk were addressed as if it menaced a daughter’s wedding, we might have fewer heroic postmortems and more quietly competent successes. Alas, the corporate preference remains for fantasy over foresight, for vows without provisions. And reality, unforgiving as any jilted bride, keeps the receipts.

This is not resistance to change. It is resistance to a Trojan Horse.

Whose Tool Is It, Really?

If project managers did not ask for it, then they were never its intended beneficiaries.

Follow the pipelines of data, and the victors quickly reveal themselves: Finance, Compliance, Audit, Controlling. These are the true clients. For them, the new system is a godsend; no more clunky macros, no more bloated spreadsheets. Their reports are clean, their dashboards luminous, their enthusiasm unmistakable.

But this is not empowerment for project managers. It is conscription. They are reduced to data clerks, feeding the machine for someone else’s benefit.

Newton’s Revenge

Newton’s third law applies: every action has an equal and opposite reaction. The work did not vanish; it merely shifted.

Where once project managers orchestrated delivery, now they spend their days curating data in a system with all the charm of an administrative console and all the humility of a Panopticon. Michel Foucault, writing on the disciplinary society, noted that surveillance was never neutral; it was a technique of control. The enterprise PM tool is no different: a digital tower from which others can gaze, while the project managers labor visibly below.

The time and focus that ought to be spent planning the future is instead squandered on maintaining the past.

Call it “digital transformation” if you must. They call it clerical servitude.

Consequences in the Wild

What follows is entirely predictable, and faintly comic:

Shadow systems. Project managers retreat to Excel and Word. The official tool becomes a Hollywood façade of a Western town, while the real plan lives elsewhere.

Past vs. future bias. Finance adores Actuals, and so the tool obsesses over them. But project management is about Forecasts. A tool that underweights them is like a ship with an anchor but no rudder: technically afloat, but going nowhere useful.

The illusion of control. Executives gaze at their dashboards, mistaking visibility for mastery. Meanwhile, project managers mutter, “If only you knew…”

The Harder Truth

Enterprise PM tools can, in theory, help project managers. But only when chosen by them, and designed with their priorities in mind. Otherwise, the price is measured in squandered hours, fractured focus, and the slow suffocation of delivery.

So before congratulating yourself, ask the only questions that matter:

Does the tool strengthen planning and forecasting, or merely prettify past data?

Does it empower delivery, or only comfort others (e.g., Finance)?

The Last Word

Let’s be brutally honest about the machine you’ve wheeled into the room. It is not a chisel in the craftsperson’s hand; it is a watchtower on the shop floor. It is visibility weaponized, a comfort blanket for other departments that force project managers into unpaid clerical service.

Tools that serve delivery earn affection. Tools that serve the hierarchy demand obedience. Choose which you want and stop pretending you can have both.

It Usually Starts Well

A conscientious project manager, the sort who still believes numbers mean something, will dutifully inventory features, tasks, effort, time, and cost. She will even do the unfashionable thing: risk analysis. That tiresome discipline asks what might go wrong, how likely it is to do so, how hard it will bite when it does, and what mitigations cost.

From this arithmetic of contingency, two bookends emerge.

• Best Case: nothing untoward happens; all risk remains theoretical, pristinely inert.

• Worst Case: the entire rogues’ gallery of risks strolls onstage, plus a few latecomers you were too innocent to imagine.

These scenarios are not prophecies but illuminations. They map the enterprise's tolerances, the width of the financial corridor through which success must pass.

How Bad Can it Be?

Enter the Steering Committee, that secular priesthood of the confident shrug.

Present the Worst Case and watch the ritual commence. A senior eminence rolls his eyes—the gesture is contagious—and announces, with the authority of revealed truth: “Well, that’s the Worst Case. We’ll never be that unlucky.”

The room exhales. The apocalypse is dismissed. Worst Case is ceremonially erased, not by reasoned rebuttal but by etiquette.

In a narrow sense, our eye-roller is correct. Worst Case is vanishingly unlikely. Team USA returning from the Olympics without a single medal is technically possible, in the same way that heat death is: conceivable, not expected.

Do You Feel Lucky, Punk?

But unless you’ve sold your soul to symmetry, the same applies to the other pole.

The Best Case—Team USA sweeping every medal in every event—is not merely unlikely; it is a parody of probability.

And yet, when Best Case is presented, the room does not roll its eyes. It leans forward. It sharpens its pencil, not to discard the fantasy but to improve upon it—shaving the number further, as if audacity alone could cow arithmetic.

At this point, one is tempted to inquire, with what diplomacy one can muster: which part of “Best Case” eludes comprehension? Do you intend to win more medals than exist?

Bookends are Usually the Same

Here, please, commit a maxim to memory (tattoo it if you must): the Best Case is as unlikely as the Worst Case. A point made over 20 years ago in Scott Burken’s The Art of Project Management.

This is not cynicism; it is statistics. But in the higher altitudes of governance, where oxygen is scarce and bonuses plentiful, only one figure survives the meeting: the prettiest one.

The Knock-On Effect

This number migrates instantly into next year’s P&L, is embalmed in the budget, and—by a miracle of transubstantiation—becomes the denominator of someone’s year-end compensation.

Thus, the project is launched under a banner of immaculate conjecture. The committee has wagered not merely that Team USA will win every medal, but that it will invent a few more to collect along the way.

But then Reality Joins the Party

When the inevitable friction arrives—risks materializing, mitigations costing—no one is surprised, only offended. Reality has failed to respect the slide deck.

So What to Do Next Time Around

The cure, alas, is not more bravado but more adulthood: treat the Best Case as an outlier, the Worst Case as a caution, and plan for the tractable middle where risk is priced, change is governed, and success is earned rather than fantasized. Anything else is not management. It is daydreaming with spreadsheets.

The Mix-Up

Time and again, when one asks the perfectly straightforward question—May I see your project plan?—what arrives, with the air of a conjurer unveiling Excalibur, is an .mpp file. If we had a coin for each time this happened, we would not be millionaires; we would merely dine better, which in our experience is a far more reliable measure of human progress.

The MPP Monster

Yes, an MS Project schedule can be impressive in its way. A hinge-point here, a dependency there, resources assigned with the precision of a Swiss watchmaker. Some go so far as to break down phases into sub-phases, activities into sub-activities, until the thing resembles a never-ending pattern of managerial anxiety. It is, at its best, a delicate piece of lacework. And, like lacework, largely ornamental—particularly to the majority who cannot even open the MPP file, condemned as they are to squint at a pixelated screenshot in a slide deck and pretend comprehension.

But no matter how grand the fresco or how fine the brushwork, it remains what it is: a schedule. It is still not a plan. Repeat after me, with staccato emphasis for those in the back: it. is. not. a. plan.

Plan vs Schedule

If we were to plan a bank robbery—and I do not recommend it, though the metaphor is serviceable—we might indeed decide who digs the tunnel, who cuts the alarm, which drill bites best through the safe, and how much time we have before the getaway car must depart. This is choreography. It may even be good choreography. But it is not strategy. It is not governance. It is not control.

It’s All About Control

The Project Management Body of Knowledge, not a volume to inflame the senses but occasionally sound on first principles, defines a project plan as “a formal, approved document used to guide both project execution and project control.” Please linger a moment on those last two words. A plan is not merely a roster of tasks and a calendar with delusions. The activities will change; the dates will slip; the people you are relying on will, being human, err. The plan is the system by which you intend to remain in charge of reality when reality declines to obey your spreadsheet.

Defining Control

Where is your governance model? How will you manage risk when it ceases to be hypothetical? What is your change control when change becomes the only constant? Where are the issue pathways, the escalation ladders, the communications regime that tells the right truth to the right people at the right time? Who decides, and what do they decide, and by what criteria, when the elegant latticework of your schedule meets the indifferent brutality of events?

Think Ahead

Return, if you like, to our bank job. What do we do when the headcount is higher than expected? Do we triage the vulnerable or let the old teller die because he is inconvenient to the plan? Who assumes command when the appointed lead goes down under the flab-to-firearm zeal of an overeager security guard? What is the line we shall speak to the authorities when captured, and who is authorized to speak it? If you cannot answer these questions, you are not planning. You are daydreaming.

When a Plan Comes Together

This, incidentally, is why the beloved television series—La Casa de Papel (a.k.a. Money Heist) for the binge-watching classes—captured imaginations. The Professor is not impressive because he can tell time and assign tasks. He is impressive because he imagines failure states, inventorying the unknowns with morbid tenderness, and installs mechanisms of response: contingencies, countermeasures, doctrine. In other words, he has a plan. He has anticipated the moment when the plan fails—and planned for that too.

What is a Plan

A real project plan is the architecture of foresight. It lays out who decides and how, what risks justify preemption and which tolerate delay, what changes are admissible and what triggers a reset, and who needs to know what and when. It is the constitution of the enterprise, not the parade schedule.

Start Planning

By all means, keep your schedules. They are useful, as timetables are useful. But do not confuse the railway clock with the locomotive, let alone the track. If you wish to be something more than the victim of your own chart, build the apparatus of control: governance, risk, change, issue, and communication management. Then, and only then, may your glittering grid of dates aspire to be part of a plan rather than a calendar with pretensions.

One is tempted to admire its simplicity. Who wouldn’t want immaculate software, untainted by bugs, glitches, or the occasional crash? But only the very naïve (or the very pompous) believe it’s possible. In truth, the dream of flawless code is a myth sustained by managerial vanity and technical illiteracy, not by science or practice.

The Misconception

Enter the fabled “I Am Spartacus” moment. The scene is always the same: the final days before release, nerves taut, deadlines looming. A middle manager, swollen with borrowed conviction, thunders:

“I will not sign off until there are zero defects!”

How stirring. How cinematic. And how utterly stupid.

This isn’t moral courage; it’s theatre. What it reveals is not a principled stand, but a fundamental misunderstanding of software itself, akin to demanding an author publish only when every possible typo, misprint, and future misinterpretation has been eradicated.

The Reality of Testing

Fred Brooks spelled it out in The Mythical Man-Month: past a certain point, every bug fixed risks hatching new ones. Complexity is not tamed by human willpower; it multiplies under it.

Even Steve Jobs, a man not known for his tolerance of imperfection, acknowledged as much at Apple’s 1997 WWDC. If Jobs could admit to the inevitability of software flaws, what business does a cubicle Caesar have in insisting otherwise?

Look Around You

Do you own a smart phone? Then you own a monument to this truth. Apple, Samsung, Microsoft, these empires release products crawling with known bugs. And yet, people buy them by the billion. Why? Because the software works well enough for its purpose, and the defects are patched later.

Imagine if Bill Gates had once said: “We shall not release Windows until it is flawless.” You would still be waiting for Windows 95, and your office would still be filled with typewriters.

The Poison of “Zero Defects”

The most pernicious quality of this delusion is not its absurdity but its toxicity. Once the “zero defects” gauntlet is thrown, it becomes politically impossible to withdraw it. The loudmouth who made the pronouncement must either stand by it (at great cost of time, money, and morale) or suffer the humiliation of backpedaling.

And so projects stall, tempers flare, and credibility is squandered. Like any cult, the demand for purity ends in ruin.

A Rational Alternative

There is, mercifully, a grown-up approach:

• Define exit criteria before the hysteria begins.

• Recognize real constraints; time, money, risk.

• Reject absolutism and aim instead for fitness to purpose.

As the Google Testing blog often illustrates, intelligent testing is about managing risk, not eradicating imperfection.

The Takeaway Is This

What sustains the zero-defect myth is not logic but vanity. Humans crave the fantasy of control, the mirage of perfection. They would rather posture than confront reality.

If you must deal with such a zealot, I recommend relocating the debate to a bar. There, lubricated by whiskey, even the most deluded manager might concede that “bug-free” is a phrase best left to insecticide commercials. And if not? Then drink alone, by all accounts, that’s when the magic starts.