3 Implementation Outcomes (and Why They Matter)

Question 1

What are implementation outcomes?

Answer 1

• Measures of how well an intervention is adopted, used, and sustained
• Distinct from clinical outcomes
• Focus on use, not effect

They tell you whether something is actually happening.

Question 2

Why separate implementation outcomes from clinical outcomes?

Answer 2

• Clinical effects depend on successful implementation
• No use → no effect
• Poor use → misleading results

Bad outcomes may reflect poor implementation, not a bad intervention.

Question 3

What question do implementation outcomes answer?

Answer 3

“Is this being used as intended, by the right people, over time?”
* Who uses it
* How often
* How well

They diagnose delivery, not efficacy.

Question 4

What is adoption?

Answer 4

• The initial decision or action to start using an intervention
• Often binary at first
• Happens early

Logins, first use, sign-ups are adoption signals.

Question 5

Why is adoption a weak success signal on its own?

Answer 5

• Starting use does not guarantee continued or correct use
• Novelty effects
• Compliance without commitment

High adoption with low follow-through is common.

Question 6

What is fidelity?

Answer 6

• The degree to which an intervention is used as intended
• Focuses on core components
• Not rigid uniformity

Fidelity drops when workarounds increase.

Question 7

Why can perfect fidelity be undesirable?

Answer 7

• Rigid use can break fit with local context
• Intelligent adaptation matters
• Core ≠ everything

Good fidelity protects purpose, not form.

Question 8

What is acceptability?

Answer 8

• How acceptable the intervention feels to users and stakeholders
• Perceived burden
• Perceived legitimacy

Low acceptability predicts quiet erosion.

Question 9

Why does acceptability matter even if use is mandatory?

Answer 9

• Poor acceptability drives minimal, superficial, or workaround use
• Compliance ≠ engagement
• Workarounds hide resistance

Mandates don’t eliminate sentiment.

Question 10

What is feasibility?

Answer 10

• The extent to which an intervention can be carried out in real conditions
• Time
• Resources
• Workflow fit

If it only works on good days, it’s not feasible.

Question 11

How is feasibility different from acceptability?

Answer 11

• Feasibility is about can we do this; acceptability is about do we want to
• Both independently matter

Something can be liked but impossible—or doable but resented.

Question 12

What is appropriateness?

Answer 12

• The perceived fit or relevance of an intervention for a given problem
• Problem–solution alignment
• Role alignment

“Why are we doing this?” signals low appropriateness.

Question 13

Why does appropriateness affect adoption?

Answer 13

• People disengage from solutions they see as misapplied
• Wrong tool for the job
• Poor targeting

Low appropriateness looks like apathy.

Question 14

What is penetration?

Answer 14

• The extent to which an intervention reaches all eligible users or settings
• Depth, not just presence
• Completeness matters

One clinic using it well ≠ penetration.

Question 15

How is penetration different from adoption?

Answer 15

• Adoption is who starts; penetration is how fully it spreads
• Adoption can be patchy
• Penetration reflects system reach

Penetration exposes equity gaps.

Question 16

What is sustainability (sustainment)?

Answer 16

• The extent to which an intervention continues over time
• Beyond project funding
• Beyond champions

If it collapses after handover, it wasn’t sustained.

Question 17

Why is sustainment often misjudged?

Answer 17

• Teams confuse short-term continuation with long-term routinisation
• Early months are deceptive
• Decay is delayed

Check use after staff turnover.

Question 18

What outcome best reflects normalisation?

Answer 18

• Sustained, routine use without active support
• No reminders
• No escalation

Silence can indicate success.

Question 19

Why do implementation outcomes change over time?

Answer 19

• Different outcomes matter at different stages
• Adoption early
• Fidelity and acceptability mid-phase
• Sustainment late

Using the wrong outcome at the wrong time misleads.

Question 20

What’s the danger of measuring too many outcomes?

Answer 20

• Diffuses attention and slows learning
• Measurement burden
• Analysis paralysis

Choose outcomes that guide action.

Question 21

Why are implementation outcomes action-oriented?

Answer 21

• They point directly to design or strategy changes
• Low adoption → engagement issue
• Low fidelity → design or training issue

Each outcome suggests a different fix.

Question 22

What does high adoption + low fidelity suggest?

Answer 22

• The intervention is attractive but hard to use correctly
• Design mismatch
• Cognitive or workflow strain

Simplify before scaling.

Question 23

What does high fidelity + low penetration suggest?

Answer 23

• The intervention works where used but hasn’t spread
• Access barriers
• Uneven leadership support

This is a spread problem, not a design problem.

Question 24

Why are clinical outcomes poor indicators early on?

Answer 24

• They lag behind implementation success
• Too distal
• Too confounded

Early clinical results mislead teams.

Question 25

What does "right outcome for the phase" mean?

Answer 25

* Matching outcomes to where the implementation is * Early: adoption, acceptability * Mid: fidelity, feasibility * Late: sustainment ## Footnote Phase mismatch leads to wrong conclusions.

Question 26

Why do **dashboards** often mislead implementation teams?

Answer 26

* They mix outcomes without interpretation * No causal story * No phase awareness ## Footnote Numbers need framing to guide action.

Question 27

What is the role of **qualitative data** in implementation outcomes?

Answer 27

* To explain why the numbers look the way they do * Reveals mechanisms * Surfaces hidden costs ## Footnote Quant tells what; qual tells why.

Question 28

Why should **implementation outcomes** be revisited repeatedly?

Answer 28

* Systems adapt and conditions change * Drift occurs * Context shifts ## Footnote Yesterday’s success can be today’s failure.

Question 29

What’s the biggest mistake teams make with **implementation outcomes**?

Answer 29

* Treating them as evaluation endpoints instead of learning tools * Outcomes should trigger adjustment * Not just reporting ## Footnote If nothing changes, measurement was wasted.

Question 30

In one line, why do **implementation outcomes** matter?

Answer 30

They tell you whether an intervention is becoming real, reliable, and routine.