Action Barrier Walkthrough¶
Diagnostic protocol — instantiates Knowing-Doing Bridge Design
Walks the actual moment of action step by step to find exactly where knowing stops turning into doing, and names the kind of barrier that stops it.
An Action Barrier Walkthrough is the upstream diagnostic that every bridge depends on: before you install a cue, a job aid, or an owner, you walk the real episode where the action is supposed to happen and find the exact point where a person who knows the right move fails to make it. Its defining move is that it studies the doing channel, not the knowing channel. It assumes the knowledge is already there — and checks that assumption — then treats the failure as a property of the moment: the trigger, the timing, the tools at hand, the competing default. The output is not a fix but a located, labeled fault: "the action fails here, and the reason is of this type." That labeled fault is what lets the right bridge be chosen instead of the reflexive one (another reminder).
Example¶
A municipal water utility keeps telling field crews to log near-misses — a valve that almost failed, a trench wall that nearly slid. Every crew can recite the policy; the near-miss log stays nearly empty. A safety lead runs an Action Barrier Walkthrough by riding along for a shift instead of re-reading the policy. She first confirms the crews genuinely know what a near-miss is and agree it should be logged (it isn't a knowledge or a buy-in problem — they describe examples fluently). Then she maps the actual episode: the near-miss happens at 10 a.m. in a muddy trench, gloves on, the logging app lives on a tablet locked in the truck cab 40 feet away, and the shift's real pressure is to keep digging. The decoupling point is sharp — the intention to log survives right up until the moment the crew would have to stop, climb out, and hunt for the tablet. She classifies the barrier: not ignorance, not defiance, but friction plus a missing point-of-action trigger, compounded by a competing production default. That one labeled sentence is the whole value — it tells the team to fix the capture path, not to run another toolbox talk.
How it works¶
- Verify knowledge and intention first. Ask the actor to explain what should be done, when it applies, and what success looks like — and whether they actually endorse it under real conditions. If either is missing, stop: this is a learning or a motivation problem, not a bridge problem, and the walkthrough routes it elsewhere.
- Map the live episode. Reconstruct the real moment as a sequence: trigger, timing, location, device, role, emotional and cognitive load, the tools within reach, and the default behavior that happens if nobody acts. Observe it if you can; reconstruct it from the actor if you can't.
- Locate the decoupling point. Trace the episode until intention and execution come apart — the specific step where a willing, knowledgeable person still doesn't act.
- Classify the barrier. Name its type: trigger absence, activation energy, friction, missing affordance, capacity gap, ambiguity, social risk, accountability gap, feedback delay, competing incentive, habit, or environment mismatch. The type is what selects the bridge.
Tuning parameters¶
- Observation depth — ride-along and direct observation versus a reconstructed interview. Direct observation catches frictions the actor has normalized; interviews are cheaper and scale.
- Episode granularity — how finely the moment is sliced. Finer slicing pinpoints the decoupling step but risks drowning in detail.
- Knowledge/intention rigor — a quick check versus a structured probe. Skimp here and you may "bridge" a gap that is really disagreement in disguise.
- Barrier taxonomy resolution — a coarse label (friction) versus a specific one (glove-incompatible touchscreen 40 feet away). Specific labels pick better bridges; coarse ones are faster to produce.
- Number of episodes sampled — one representative case or several. More cases separate a personal quirk from a structural barrier.
When it helps, and when it misleads¶
Its strength is that it refuses the default remedy — repeating the message — and forces attention onto the moment where behavior is actually produced. It is what keeps a team from installing a beautiful bridge over the wrong river. Naming the barrier type is the payload: the same empty log can come from friction, from social risk, or from a missing cue, and each needs a different fix.
Its central failure mode is diagnosing from the armchair. A walkthrough done by imagining the episode rather than observing it tends to recover the analyst's own theory of the problem; the frictions that matter most are precisely the ones insiders have stopped noticing. The classic misuse is skipping the knowledge-and-intention check and labeling a disagreement as a "gap," which sends the team building action bridges for people who never intended to cross — a case the archetype's own anti-signatures warn against.[n1] The guarding discipline is to observe the real moment, and to treat a confidently-stated barrier the actor can't corroborate as an untested hypothesis, not a finding.
How it implements the components¶
Action Barrier Walkthrough fills the diagnostic side of the archetype — it produces the map, never the bridge:
knowledge_and_intention_evidence— its first gate: it confirms the actor can explain the action and endorses it, so a true knowing-doing gap is separated from ignorance or dissent.action_episode_map— it reconstructs the live moment as a sequence of trigger, timing, tools, load, and default path.decoupling_point_diagnosis— it traces that sequence to the exact step where intention stops becoming execution.barrier_type_classifier— it labels that step with a barrier type, which is what selects the matching bridge.
It installs nothing: the fixes it points to — reducing friction_and_affordance_adjustment (that's Activation-Energy Reduction Pass), adding an action_context_trigger (that's Point-of-Action Prompt), or closing the loop with an action_feedback_loop (that's Follow-Through Checkback) — belong to other siblings that consume this diagnosis.
Related¶
- Instantiates: Knowing-Doing Bridge Design — it supplies the located, labeled barrier that tells every other mechanism which bridge to build.
- Sibling mechanisms: Activation-Energy Reduction Pass · Default Path Redesign · Feedforward Action Rehearsal · Follow-Through Checkback · Named Action Owner Protocol · Point-of-Action Prompt · Social Permission Script · Tiny First-Step Design · Implementation Intention Script
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: The mechanism walks the actual moment of action step by step to find exactly where knowing stops turning into doing, and names the kind of barrier that stops it, so its operative form is offline analysis, modeling, or optimization.
Independent corroboration: The frozen evidence defines Action Barrier Walkthrough as 'Walks the actual moment of action step by step to find exactly where knowing stops turning into doing, and names the kind of barrier that stops it', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Protocol, Workflow & Routine — The stepwise walkthrough is used diagnostically to locate the barrier, so analysis is primary and sequence is supporting.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Separating knowledge and intention from environmental friction, triggers, habits, and competing defaults is grounded in behavioral and motivational psychology.
Related originating lineages:
- Ethnography & Qualitative Methods — Ride-alongs and observation of normalized workarounds reveal barriers actors may not report.
- Human-Computer Interaction — Task analysis, affordances, point-of-action friction, and user-journey diagnostics supply the stepwise walkthrough.
- Organizational & Management Science — Workflow, ownership, incentives, and production defaults contribute common organizational barrier classes.
Review resolution: The mechanism first separates capability and intention from opportunity, motivation, tools, defaults, and environmental barriers, which is a behavioral-psychology diagnosis. Ethnographic observation, HCI task walkthroughs, and organizational workflow analysis materially shape how that diagnosis is conducted in context.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The walkthrough is deliberately fix-free. Keeping diagnosis separate from remedy is what stops a team from reaching for its favorite tool (usually another reminder) before it knows what kind of barrier it faces — and it lets the same diagnosis feed whichever bridge the barrier type actually calls for.
[n1] The knowing-doing gap — Jeffrey Pfeffer and Robert Sutton's term for the recurring organizational pattern in which people and firms know what to do yet fail to act on it. Their point that the gap is a property of systems and situations, not of missing knowledge, is exactly why this mechanism studies the moment of action rather than repeating the message. ↩