What is CFIR for, in one line?
A structured way to diagnose why implementation succeeds or fails in real settings.
Key points:
* Diagnostic, not prescriptive
* Explains variation
In practice: Use CFIR to ask better questions, not to label problems.
What mistake do practitioners most often make with CFIR?
Treating it as a checklist instead of a thinking tool.
Key points:
* Over-coding
* Under-interpreting
In practice: If CFIR feels bureaucratic, it’s being misused.
How many CFIR domains are there?
Five.
Key points:
* Intervention characteristics
* Outer setting
* Inner setting
* Characteristics of individuals
* Process
In practice: Domains help you scan the system systematically.
What is CFIR not good at?
Choosing solutions or predicting success.
Key points:
* CFIR diagnoses
* Strategies come later
In practice: CFIR tells you what’s wrong, not what to do.
What does the “intervention characteristics” domain capture?
How the intervention itself affects uptake.
Key points:
* Complexity
* Adaptability
* Relative advantage
In practice: If use feels hard, start here.
Why is complexity such a powerful CFIR construct?
Because complexity multiplies failure points.
Key points:
* More steps
* More coordination
In practice: Complex interventions fail silently.
What does “relative advantage” mean in CFIR terms?
Whether users see the intervention as better than current practice.
Key points:
* Better for whom matters
* Benefits must outweigh costs
In practice: If advantage isn’t obvious, adoption stalls.
What does adaptability refer to?
How much the intervention can be modified without losing its core purpose.
Key points:
* Core vs periphery
* Intelligent adaptation
In practice: Rigid designs break at scale.
What does the “outer setting” domain focus on?
External pressures and influences on implementation.
Key points:
* Policy
* Regulation
* Patient expectations
In practice: Outer setting shapes urgency and legitimacy.
Why is patient need part of the outer setting?
Because perceived patient benefit motivates adoption.
Key points:
* Real or imagined needs
* Equity considerations
In practice: If staff don’t see patient value, effort drops.
What does the “inner setting” domain capture?
The organisation’s readiness and climate for change.
Key points:
* Culture
* Resources
* Leadership engagement
In practice: Inner setting determines execution capacity.
Why is “readiness for implementation” so critical?
Because motivation without capacity leads to failure.
Key points:
* Time
* Staffing
* Infrastructure
In practice: Enthusiasm can’t compensate for overload.
What does “implementation climate” mean?
How much the organisation expects, supports, and rewards the change.
Key points:
* Priority signals
* Competing initiatives
In practice: Climate is read from actions, not speeches.
What belongs in the “characteristics of individuals” domain?
How individuals perceive and engage with the intervention.
Key points:
* Beliefs
* Self-efficacy
* Identity
In practice: This is about perception, not personality.
Why is individual knowledge rarely the main determinant?
Because most clinicians already know what to do.
Key points:
* Knowledge ≠ opportunity
* Systems constrain action
In practice: If people know but can’t act, look elsewhere.
What does the “process” domain focus on?
How implementation is planned, executed, and reflected upon.
Key points:
* Planning
* Engaging
* Reflecting
In practice: Good ideas fail with poor process.
Why does stakeholder engagement sit in the process domain?
Because engagement is an active implementation activity.
Key points:
* Who is involved
* When they’re involved
In practice: Late engagement looks like resistance.
What is the danger of over-emphasising the “individuals” domain?
It shifts blame onto people instead of systems.
Key points:
* Moralising non-use
* Missing structural constraints
In practice: If the fix is always “train harder,” something’s wrong.
How should CFIR domains be used together?
As interacting contributors, not isolated causes.
Key points:
* Domains influence each other
* No single root cause
In practice: Implementation failures are multi-domain problems.
What does CFIR help you explain?
Why uptake varies across sites, teams, or time.
Key points:
* Same intervention
* Different outcomes
In practice: Variation is diagnostic data.
When is CFIR most useful in a project?
Before and during implementation, not after failure.
Key points:
* Guides anticipation
* Supports course correction
In practice: CFIR is most powerful when used early.
Why is CFIR poor at prioritisation on its own?
Because it surfaces many issues without ranking them.
Key points:
* Everything looks important
* Trade-offs are required
In practice: Diagnosis must be paired with judgement.
What’s a practical way to apply CFIR in meetings?
Use domains as prompts, not reporting categories.
Key points:
* “What inner-setting issues do we see?”
* “What about the intervention itself?”
In practice: CFIR structures discussion, not slides.
Why is CFIR compatible with human factors thinking?
Both focus on system constraints and real work.
Key points:
* Non-blaming
* Context-sensitive
In practice: CFIR + HF prevents user blaming.