24 Diagnosing Stuck Implementations

Question 1

What does it mean for an implementation to be stuck?

Answer 1

Progress stalls despite effort, attention, or pressure. Repeated fixes fail and frustration increases. More effort produces less movement.

Question 2

What is the first diagnostic question to ask?

Answer 2

Where exactly is progress breaking down: adoption, use, quality, or sustainment? Vague problems block diagnosis.

Question 3

Why is low buy-in a weak diagnosis?

Answer 3

Because it explains nothing about mechanisms. It is blame-laden and non-actionable. Attitudes must be translated into constraints.

Question 4

What does high adoption but poor fidelity suggest?

Answer 4

The intervention is attractive but hard to do correctly. Design complexity or workflow misfit is likely. Redesign before retraining.

Question 5

What does good fidelity but low spread suggest?

Answer 5

Local success without system readiness. This reflects access barriers or uneven leadership. It is a spread problem, not a quality problem.

Question 6

What does early enthusiasm followed by drop-off indicate?

Answer 6

Novelty without routinisation. Champion dependence and hidden burden suggest sustainment was never designed.

Question 7

Why do reminders often worsen stuck implementations?

Answer 7

They increase pressure without removing friction. Alert fatigue and resistance grow. More noise rarely fixes design problems.

Question 8

What does rising workaround behaviour signal?

Answer 8

Mismatch between formal process and real work. Time pressure and cognitive load drive adaptation. Workarounds are diagnostic data.

Question 9

What does silence from the frontline usually mean?

Answer 9

Disengagement or overload, not success. Learned helplessness or quiet abandonment are common. No feedback is a red flag.

Question 10

What does repeated retraining indicate?

Answer 10

Misdiagnosed design or workflow problems. Knowledge was not the issue; conditions were. Training is often a symptom, not a cure.

Question 11

What does it works in one site usually mean?

Answer 11

Conditions there are unusually supportive, such as extra capacity or informal fixes. Single-site success is not proof.

Question 12

What does staff saying we don’t have time usually reflect?

Answer 12

Real trade-offs under pressure. Opportunity costs and competing priorities are present. Time complaints are system signals.

Question 13

What diagnostic signal suggests leadership misalignment?

Answer 13

Conflicting priorities and mixed messages. Work is important but optional, with no protected time. Leadership signals shape reality.

Question 14

What does heavy policing or enforcement indicate?

Answer 14

Loss of trust and poor fit. Surface compliance hides resistance. Enforcement replaces design when learning stops.

Question 15

What does success in reports but not in practice suggest?

Answer 15

Metric gaming or superficial compliance. Checkbox behaviour and fear-driven reporting hide system problems.

Question 16

What does we just need more time usually mean?

Answer 16

Underlying design flaws or ownership gaps remain unresolved. Time does not fix misfit.

Question 17

What diagnostic pattern suggests unclear ownership?

Answer 17

Tasks fall between roles or teams. Everyone is involved but no one is responsible. Ambiguity predicts decay.

Question 18

What does increasing escalation without resolution indicate?

Answer 18

Broken feedback loops. Escalation to nowhere produces frustration. Unanswered signals shut down reporting.

Question 19

What does strong pushback late in rollout suggest?

Answer 19

Late discovery of hidden burden. Early politeness gives way to resistance once tolerance is exhausted.

Question 20

Why is culture a weak explanation for stuck work?

Answer 20

Because culture reflects system conditions. Design drives norms more than attitudes. Fix systems before blaming culture.

Question 21

What diagnostic question clarifies next steps fastest?

Answer 21

What would make this easier to do correctly? This shifts focus to design leverage and practical change.

Question 22

What does OHFE add to stuck implementations?

Answer 22

Translation of lived experience into redesignable constraints. Cognitive load and workflow friction become visible.

Question 23

Why do stuck implementations feel personal?

Answer 23

Because pressure is displaced onto individuals. Moral distress and burnout reflect system failure.

Question 24

What is the danger of trying harder narratives?

Answer 24

They hide structural problems. Short-term compliance leads to long-term failure. Effort cannot compensate for misdesign.

Question 25

What does progress after simplification indicate?

Answer 25

That burden was the limiting factor. Fewer steps and clearer decisions unlock use. Simplification is diagnostic and corrective.

Question 26

Why should diagnosis precede strategy changes?

Answer 26

Because wrong fixes deepen frustration. Strategy churn erodes credibility. Better diagnosis saves time.

Question 27

What does repeated redesign without improvement suggest?

Answer 27

The wrong problem definition. Surface tinkering misses real constraints. Step back before iterating again.

Question 28

What is a healthy response to a stuck implementation?

Answer 28

Slowing down to understand before acting. Curiosity and reframing prevent misdiagnosis. Speed worsens stuckness.

Question 29

What signals readiness to restart progress?

Answer 29

Shared understanding of what is blocking use. Aligned diagnosis reduces blame and restores momentum.

Question 30

In one line, what unsticks implementations?

Answer 30

Accurate diagnosis of system constraints followed by targeted redesign.