What is the core overlap between implementation science and human factors?
Both explain behaviour as a product of system design. Context shapes action and constraints matter. If behaviour looks irrational, the system is not yet understood.
How does human factors redefine non-compliance?
As rational adaptation to constraints. Deviation reflects local rationality and trade-offs under pressure, not defiance.
Why do good ideas fail in real work settings?
Because work-as-imagined differs from work-as-done. Simplified assumptions and hidden variability undermine implementation.
What does work-as-done mean?
How tasks are actually performed under real conditions, including interruptions and resource constraints. Work-as-done is the design target.
Why is work-as-imagined dangerous in implementation?
Because it hides complexity and cognitive load by assuming linear processes and ideal conditions. Many plans describe work-as-imagined only.
What is local rationality?
The principle that people act reasonably given their goals, knowledge, and constraints. Understanding decisions requires understanding context.
How does cognitive load affect implementation?
High cognitive load reduces reliability and adherence due to memory limits and attention competition. Design should reduce thinking at the point of action.
Why are checklists not a universal solution?
Because they can add cognitive load and disrupt workflow. Overuse creates fatigue and poor timing reduces value.
What is a sharp end perspective?
The viewpoint of people doing the work in real time, under time pressure and risk exposure. Implementation must be designed from the sharp end.
Why does the blunt end matter for implementation?
Because upstream policies and decisions shape sharp-end constraints, including staffing, scheduling, and incentives.
How does human factors change the meaning of training?
Training should support systems, not compensate for them. If training is essential, the design is fragile.
What is a forcing function?
A design feature that prevents incorrect action. Forcing functions are hard to bypass and deliver high reliability.
Why are reminders weak human factors strategies?
Because they rely on memory and attention, leading to alert fatigue and easy dismissal. Reminders signal missed design opportunities.
What does human factors mean by error?
Error is a symptom of system conditions, not personal failure. Errors are predictable and contextual.
Why do workarounds matter in implementation?
Because they reveal how systems really function. Workarounds indicate hidden labour and design mismatch.
What is functional resonance?
The concept that small variations can combine to produce large effects through non-linear interactions. Failures rarely have single causes.
Why is standardisation risky without human factors insight?
Because it may eliminate necessary flexibility. Rigid standards push variability underground.
How does human factors inform adaptation decisions?
By identifying cognitive, physical, and organisational constraints that drive behaviour. Adapt where pressure is highest.
Why do human factors and CFIR complement each other?
CFIR maps where determinants sit, while human factors explains how they operate. Together they deepen diagnosis.
What human factors lens improves sustainment?
Designing habits rather than heroics. Defaults and routines enable low-effort reliability.
Why is fatigue a critical implementation determinant?
Because fatigued systems degrade silently, with slower detection and more shortcuts. Fatigue undermines good design.
What does human factors say about safety culture in implementation?
Culture emerges from systems, signals, and consequences, not slogans. Design choices shape culture.
Why is blame incompatible with human factors-informed implementation?
Because blame suppresses reporting and learning. Fear distorts behaviour and silence increases risk.
How does human factors change evaluation questions?
From Did they comply to What made this hard? The focus shifts to mechanisms and design.