Why are resource constraints central to implementation?
Because all implementation happens in finite systems. Time, staff, and attention are limited. Constraint is the baseline, not a special case.
What is the most common mistake teams make about resources?
Treating constraints as temporary or external. Teams assume things will ease after rollout, but constraints rarely resolve on their own.
Why do constrained systems resist new interventions?
Because new work displaces existing work. Implementation is zero-sum, with hidden opportunity costs. Resistance often reflects realism.
What is opportunity cost in implementation?
What must stop or slow to make space for new work. Opportunity costs are usually implicit and often ignored.
Why does adding just one more thing fail?
Because cumulative burden exceeds system capacity. Small additions compound into overload and failure.
What does resource realism mean?
Designing interventions to fit actual capacity rather than ideal capacity. Designs that require spare capacity rarely survive.
Why do pilots hide resource problems?
Because pilots are artificially supported with extra attention and flexibility. Pilot success often borrows future resources.
What resource is most underestimated in implementation?
Attention. Competing priorities and cognitive load make attention the scarcest resource.
Why is time pressure a safety issue?
Because it forces trade-offs under stress. Shortcuts increase error likelihood and risk.
What does designing for constraint involve?
Reducing steps, decisions, and dependencies through simplicity and strong defaults. Low-friction designs survive pressure.
Why is training a weak response to constraint?
Because it consumes time without reducing workload. Training adds burden, while design removes burden.
What is capacity illusion?
Assuming unused capacity exists because work is invisible. Silence is often mistaken for slack.
Why do constrained systems rely on workarounds?
Because formal processes are too slow or heavy. Workarounds signal misfit and migrate risk.
How should implementation teams respond to constraint signals?
By redesigning work rather than escalating pressure. Fewer steps and better timing solve more than urgency.
What leadership mistake worsens constraint?
Layering initiatives without retiring others. Priority inflation leads to exhaustion.
Why must trade-offs be made explicit?
Because implicit trade-offs fall to the frontline, creating moral injury and unsafe shortcuts. Explicit trade-offs protect staff.
What is the OHFE role under constraint?
Making invisible burden visible through workflow mapping and load articulation. HF translates experience into design decisions.
Why is fairness not sameness under constraint?
Because capacity varies across settings. Equal demands can be inequitable when staffing and infrastructure differ.
How do constraints affect sustainment?
They erode non-essential work first. Optional steps disappear and quality drifts. Only low-burden work persists.
Why does constraint amplify implementation failure modes?
Because tolerance for friction disappears. Weak designs are abandoned faster under pressure.
What is a minimum viable implementation?
The simplest version that still delivers value safely. Non-essential elements are removed first.
Why is early simplification safer than later trimming?
Because habits form quickly. Early defaults stick, while later removal is resisted.
How should evaluation adapt under constraint?
By measuring only what informs decisions. Low-burden, actionable metrics preserve capacity.
What does constraint-aware leadership look like?
Protecting capacity and making trade-offs explicit by saying no and removing work. Leadership creates space.
-
*MASTER 101101
-
*Intervention vs Implementation Mapping84
-
*Implementation Frameworks — What’s in the Box?75
-
Refresher102
-
CFIR56
-
1 What Implementation Science Is (and Is Not)30
-
2 Core Implementation Mental Models30
-
3 Implementation Outcomes (and Why They Matter)30
-
4 CFIR for Practitioners30
-
5 EPIS & Phase-Based Thinking30
-
6 Determinants vs Barriers vs Root Causes30
-
7 Implementation Strategies That Actually Work30
-
8 Engagement, Buy-In, and Trust30
-
9 Adaptation vs Fidelity30
-
10 Theory of Change & Logic Models for Practice30
-
11 Implementation Evaluation & Learning30
-
12 RE-AIM in Real Life30
-
13 Common Implementation Failure Modes30
-
14 Sustainment Is Not a Phase30
-
15 Digital Health Implementation30
-
16 Implementation × Human Factors30
-
17 Scaling, Spread, and National Rollouts30
-
18 Safety, Risk, and Escalation in Implementation30
-
19 Leadership for Implementation30
-
20 Implementation in High-Reliability Organisations (HROs)30
-
21 Implementation Under Resource Constraints30
-
22 Teaching & Coaching Implementation Science30
-
23 Implementation Playbooks & Checklists (Done Right)30
-
24 Diagnosing Stuck Implementations30
-
ERIC — Strategy Selection & Misuse (Practitioner Diagnostic Deck)21
-
Implementation Metrics — What Misleads, What Matters20
-
Executive Mini Deck25
