13 Common Implementation Failure Modes

Question 1

What is an implementation failure mode?

Answer 1

A recurring pattern that causes implementation to stall, degrade, or collapse. These failures are predictable and repeat across projects. Failure modes are warnings, not surprises.

Question 2

Why do implementation failures repeat across projects?

Answer 2

Because teams repeat the same assumptions and shortcuts, often driven by overconfidence and time pressure. Different projects, same mistakes.

Question 3

What is the training-as-solution failure mode?

Answer 3

Defaulting to education when the real problem is system design. If people know what to do but cannot act, training failed before it started.

Question 4

What is the pilot illusion failure mode?

Answer 4

Mistaking pilot success for scale readiness. Pilots operate under protected conditions with extra attention and hide fragility.

Question 5

What is the early adopter trap?

Answer 5

Designing around enthusiasts instead of average users. Champions compensate for system weaknesses, but systems do not.

Question 6

What is the compliance framing failure mode?

Answer 6

Interpreting non-use as defiance rather than misfit. Compliance framing moralises behaviour and suppresses learning.

Question 7

What is the communication escalation failure mode?

Answer 7

Responding to low uptake with more emails and reminders. Awareness does not equal action, and noise increases without impact.

Question 8

What is the invisible workload failure mode?

Answer 8

Adding work without removing anything. Burden accumulates and hidden costs erode goodwill.

Question 9

What is the design-by-policy failure mode?

Answer 9

Using rules and mandates to compensate for poor design. Policy without usability creates shadow work and workarounds.

Question 10

What is the late engagement failure mode?

Answer 10

Engaging stakeholders only after key decisions are made. This appears performative and erodes trust.

Question 11

What is the no owner failure mode?

Answer 11

Responsibility is diffused across committees, leaving no clear accountability or sustainment ownership.

Question 12

What is the handover cliff failure mode?

Answer 12

Collapse after project teams withdraw. Knowledge is lost and support disappears, making handover a high-risk moment.

Question 13

What is the one-size-fits-all failure mode?

Answer 13

Ignoring meaningful local differences. Context is overlooked and workarounds increase.

Question 14

What is the over-customisation failure mode?

Answer 14

Allowing unlimited local variation. Core elements erode and coherence is lost.

Question 15

What is the metrics obsession failure mode?

Answer 15

Optimising numbers instead of practice. Gaming and superficial compliance replace real improvement.

Question 16

What is the outcome fixation failure mode?

Answer 16

Focusing on distal outcomes while ignoring implementation quality. Lagging indicators lead to misattribution.

Question 17

What is the premature scale failure mode?

Answer 17

Expanding before the intervention is stable. Scaling too early multiplies defects and unfinished learning.

Question 18

What is the strategy inertia failure mode?

Answer 18

Persisting with the same strategies despite poor results, such as repeated training or reminders. Persistence without learning is stagnation.

Question 19

What is the context blindness failure mode?

Answer 19

Assuming conditions are similar across settings. Staffing and workflow differences explain variation, not attitude.

Question 20

What is the blame shift failure mode?

Answer 20

Attributing failure to individuals under pressure. Blame damages morale and stops learning while hiding design flaws.

Question 21

What is the success story bias failure mode?

Answer 21

Highlighting wins while suppressing problems. This creates unrealistic expectations and erodes trust.

Question 22

What is the implementation by enthusiasm failure mode?

Answer 22

Relying on goodwill instead of systems. Enthusiasm-driven success is fragile and leads to burnout.

Question 23

What is the evaluation after the fact failure mode?

Answer 23

Collecting data only once things go wrong. Late, defensive evaluation cannot prevent failure.

Question 24

What is the assumption blindness failure mode?

Answer 24

Treating assumptions about behaviour or capacity as facts. Unexamined assumptions become hidden risks.

Question 25

What is the ownership drift failure mode?

Answer 25

Responsibility slowly migrates away from the system. Project teams linger while line ownership remains unclear.

Question 26

What is the over-policing failure mode?

Answer 26

Responding to friction with enforcement. This produces surface compliance and hidden resistance.

Question 27

What is the no exit plan failure mode?

Answer 27

Launching without planning how support will end. Dependency is created and sustainment becomes impossible.

Question 28

What failure mode appears most often at scale?

Answer 28

Loss of fit combined with fidelity drift. Variation increases while oversight decreases, exposing design weakness.

Question 29

Why is naming failure modes useful?

Answer 29

Because it depersonalises problems and accelerates correction by creating shared language and faster diagnosis.

Question 30

In one line, why study implementation failure modes?

Answer 30

Because most implementation failures are predictable, and therefore preventable.