Engineering Failure Into the Plan: A Different Way to Think About Business Risk

Most business strategies are built around what people hope will happen. A market will grow. A rollout will go smoothly. A new system will get adopted because, well, it is better than what came before it. Hope is not a strategy, but it has a habit of sneaking into strategic plans dressed up as confidence.
Engineers build differently. Before anything is allowed to fly, an aeronautical engineer maps every single thing that could go wrong with a system and designs against it deliberately, rather than hoping none of it happens. This discipline has a name: failure mode analysis. It is not a metaphor borrowed for a business article. It is a specific, repeatable method that translates into business planning far more directly than most leaders realise.

What Failure Mode Analysis Actually Is

Where It Comes From

Failure mode analysis, often shortened to FMEA, is a structured risk methodology that originated in aerospace and defence engineering, where the cost of an undetected failure is measured in lives, not just budgets. It is a deliberately proactive exercise. Rather than waiting for something to break and then working out why, engineers map out every plausible way a system could fail before it is ever built, tested, or flown.

Structured failure analysis helps organisations move beyond generic risk categories and focus on specific, actionable vulnerabilities.

The Core Logic

For every component, process, or decision point, the exercise asks three specific questions:

How could this fail?

How serious would the consequences be if it did?

Would we notice in time to act, or would the failure go undetected until the damage was done?

Each potential failure is assessed against these three factors: severity, likelihood, and detectability. The failures that score highest across all three, severe, likely, and hard to spot early, get the attention. Everything else gets noted and monitored, not over-engineered. This is the same logic we apply in Business & Strategy Consulting engagements, stress-testing a plan before it's executed, not after it fails.

Why Most Business Strategies Skip This Step

The typical strategic process runs in one direction: define the goal, build the plan to reach it, present the plan with confidence. Risk usually gets a single slide near the end, with broad categories such as "market risk" or "execution risk" that sound thorough but say very little. Nobody has actually named the specific way the plan could fail, rated how serious that would be, or worked out how they would even know it was happening.
The result is a familiar pattern. An organisation invests significant time and money, runs into a problem six months in, and describes it as unexpected. In hindsight, it rarely is. Most strategic failures were entirely visible in advance to anyone who deliberately looked for them. The problem was never a lack of intelligence in the room. It was that nobody was tasked with finding the failure before it found them.

Three Failure Modes That Show Up Again and Again in Business Transformation

Effective transformation programmes begin by identifying what could derail success before committing resources to implementation.

Across enough digital transformation work, the same patterns recur with striking consistency:

The technology performs exactly as designed, but the people who are meant to use it daily were never genuinely brought into the change, so adoption never really happens.

The process being digitised was never properly documented in the first place, so the new system simply automates an inconsistency that was previously invisible.

The executive sponsor who opened doors and unblocked decisions in month one is no longer actively involved by month four, and the project quietly loses its authority to make hard calls.

None of these is unusual or unpredictable. They are some of the most common, well-understood failure modes in organisational change, and every one of them can be named and planned for before the project starts.

Why This Discipline Matters Even More in High-Stakes Environments

In aviation, where this thinking originates, the standard goes further still. Regulators expect multiple, independent layers of protection so that a single error in judgment cannot, on its own, cascade into a catastrophic outcome. That same principle, often called defence in depth, applies just as usefully to a large capital project, a regulated industry rollout, or a government contract, anywhere the cost of an undetected failure is genuinely high. The stakes differ. The discipline of deliberately looking for failure, rather than discovering it by accident, does not.

Building Failure Mode Thinking Into Your Own Planning

This does not require an engineering degree to apply. It requires a habit.

Name the specific failure, not the vague category. "Adoption risk" tells you nothing useful. "Branch staff revert to the old spreadsheet because the new system takes three extra clicks", tells you exactly what to fix.
Score it, rather than simply feeling uneasy about it. A rough rating of severity, likelihood, and detectability is enough to separate failures worth designing around from those worth simply monitoring.
Build the response into the plan itself, with an owner and a checkpoint, rather than parking it in an appendix nobody reopens.

Closing Thought

The goal is not to predict every failure with perfect accuracy. Even the most rigorous engineering process cannot do that. The goal is to build the habit of looking for failure on purpose, before it happens, rather than explaining it afterwards. That single shift, from hoping a plan works to deliberately stress-testing where it might not, is one of the more transferable habits engineering has to offer business.

Frequently Asked Questions

What is Failure Mode Analysis (FMEA)?
It is a structured risk methodology, originally developed in aerospace and defence engineering, that identifies every plausible way a system or process could fail before it is built or implemented, then rates each failure by severity, likelihood, and ease of detection.
How is this different from a standard business risk register?
Most risk registers list broad, generic categories such as "market risk" or "execution risk." Failure mode thinking requires naming the specific failure mechanism, rating it honestly, and integrating the mitigation directly into the implementation plan rather than storing it separately.
Can this be applied outside engineering and aviation?
Yes. The underlying logic, specific failure naming, honest rating, and built-in mitigation apply to any planning exercise where getting it wrong has real consequences, including digital transformation, market entry, and large capital projects.
How do you decide which failure modes actually matter?
Focus on the failures that combine high severity, high likelihood, and low detectability. A severe but easy-to-spot failure is far less dangerous than a moderately severe one that remains nearly invisible until it has already caused damage.