7 Implementation Strategies That Actually Work

Question 1

What is an implementation strategy?

Answer 1

A deliberate action designed to address specific determinants of implementation.

Purposeful, not generic; linked to diagnosis. Strategies respond to why something isn’t working.

Question 2

What is the most common strategy mistake teams make?

Answer 2

Choosing strategies before diagnosing determinants.

Jumping to training; copying past solutions. Strategy without diagnosis is guesswork.

Question 3

Why doesn’t more communication usually work?

Answer 3

Because most problems aren’t awareness problems.

People already know; constraints remain. If people agree but don’t act, communication won’t help.

Question 4

When does training actually work as a strategy?

Answer 4

When the main determinant is lack of skill or unfamiliarity.

New tasks; rare tasks. Training works when opportunity already exists.

Question 5

When does training fail?

Answer 5

When the system makes correct behaviour hard.

Time pressure; workflow mismatch. Training can’t overcome bad design.

Question 6

What kind of determinant calls for redesign?

Answer 6

Workflow, cognitive load, or coordination problems.

Too many steps; poor timing. Design fixes design problems.

Question 7

What is a structural implementation strategy?

Answer 7

A change to the environment that shapes behaviour automatically.

Defaults; physical layout; system rules. Structural strategies reduce reliance on motivation.

Question 8

Why are structural strategies often more powerful?

Answer 8

Because they don’t depend on memory or goodwill.

Persistent effect; low effort. Good structures make the right action the easy one.

Question 9

When are reminders an appropriate strategy?

Answer 9

When the task is important but easy to forget.

Infrequent tasks; clear action needed. Reminders fail when the task itself is burdensome.

Question 10

Why do reminders often stop working over time?

Answer 10

Because they add cognitive noise.

Alert fatigue; normalisation of ignoring. Ignored reminders signal deeper issues.

Question 11

What determinant suggests engagement strategies?

Answer 11

Low legitimacy, trust, or perceived relevance.

“Why are we doing this?”; “Who decided?” Engagement builds meaning, not capability.

Question 12

What is the goal of stakeholder engagement?

Answer 12

Shared understanding and ownership.

Not consensus on everything; not endless consultation. Engagement should change decisions.

Question 13

When do incentives make sense as a strategy?

Answer 13

When effort is high and priorities are ambiguous.

Short-term focus; clear behaviours. Incentives signal what matters now.

Question 14

Why do incentives sometimes backfire?

Answer 14

Because they distort behaviour and crowd out judgement.

Gaming; narrow optimisation. Incentives should be used sparingly.

Question 15

What determinant calls for role clarification?

Answer 15

Ambiguity about who is responsible for what.

Tasks fall through gaps; everyone assumes someone else. Unclear roles look like resistance.

Question 16

Why is ownership a powerful strategy lever?

Answer 16

Because ownership drives sustainment.

Someone absorbs cost; someone maintains standards. No owner = slow decay.

Question 17

What strategy helps when adoption is patchy across sites?

Answer 17

Targeted support rather than blanket rollout.

Site-specific barriers; context differences. Uniform strategies rarely fit uneven systems.

Question 18

When should you adapt the intervention itself?

Answer 18

When the design is the main source of friction.

Repeated workarounds; declining fidelity. Adaptation beats enforcement.

Question 19

What strategy addresses cognitive load?

Answer 19

Simplification and offloading.

Fewer steps; better sequencing. Reduce thinking, not effort.

Question 20

Why is sequencing a strategy?

Answer 20

Because timing affects feasibility.

Do less upfront; add complexity later. Early overload kills adoption.

Question 21

What strategy supports sustainment best?

Answer 21

Embedding the intervention into routine systems.

Job descriptions; performance expectations. Routines outlast enthusiasm.

Question 22

Why is policy a weak standalone strategy?

Answer 22

Because rules don’t create capacity.

Compliance pressure; no enablement. Policy without design creates shadow work.

Question 23

When is enforcement appropriate?

Answer 23

When the behaviour is critical and feasible.

Safety-critical tasks; clear expectations. Enforcement without feasibility breeds resentment.

Question 24

What strategy addresses loss of momentum over time?

Answer 24

Routinisation, not re-motivation.

Defaults; institutional memory. Don’t re-sell what should be normal.

Question 25

Why should strategies **change over phases**?

Answer 25

Because dominant problems evolve. ## Footnote Early: fit and buy-in; later: efficiency and durability. Static strategies signal stagnation.

Question 26

What does a **strategy mismatch** look like?

Answer 26

High effort with little improvement. ## Footnote More training, same problems; more reminders, same behaviour. Mismatch wastes goodwill.

Question 27

Why do **multi-strategy bundles** work better?

Answer 27

Because multiple determinants usually interact. ## Footnote Design + engagement; structure + feedback. One lever is rarely enough.

Question 28

What’s the risk of **copying strategies** from other projects?

Answer 28

Different contexts have different determinants. ## Footnote Superficial similarity; deep differences. Borrow logic, not tactics.

Question 29

How do you know a **strategy is working**?

Answer 29

When the targeted determinant weakens. ## Footnote Less friction; fewer workarounds. Watch behaviour, not enthusiasm.

Question 30

In one line, what makes an **implementation strategy effective**?

Answer 30

It directly reduces the constraints that prevent people from doing the right thing. ## Footnote Effective strategies address specific barriers to implementation.