Barrier Interview Protocol¶
Qualitative diagnostic method — instantiates Change Resistance Diagnosis and Support
A structured set of interviews that elicits why people expect a change to fail or harm them, then sorts those reasons into the barrier types the response must match.
A Barrier Interview Protocol is the diagnostic conversation that goes underneath resistance to find its causes, before anyone chooses a response. Its defining move is that it treats the affected person as the expert witness on their own reality: rather than measuring behavior from outside or persuading from above, it asks people to say — in their own terms — why they expect the change to fail, harm them, overload them, or clash with how the work actually gets done. The protocol's output is not a number and not a decision; it is a mapped and classified account of the resistance: who resists, over what, and of what kind — capability, trust, workload, incentive, technical fit, identity, or a genuine design flaw. That classification is what lets everything downstream match the support to the barrier instead of reaching for the default of "more communication."
Example¶
A hospital is rolling out a new sepsis-screening protocol that nurses are quietly skipping. Login data (a dashboard's territory) shows the skips but not the reason. The Barrier Interview Protocol sends a trained interviewer to sit with fourteen bedside nurses across three shifts, working from a fixed set of open prompts — "walk me through the last time you decided not to run the screen," "what would have to be true for this to feel safe?" The accounts don't converge on stubbornness. Night-shift nurses describe the screen adding six minutes per patient they don't have during admissions surges — a workload barrier. A cluster of senior nurses distrust the alert because it fired constantly during the pilot and cried wolf — a trust and technical-fit barrier. Two newer nurses simply aren't sure how to act on a positive result — a capability barrier. The interviewer records each as a distinct source, tagged by type. What leaves the room is a resistance map that says, precisely, that one problem needs staffing relief, one needs alert-tuning and evidence, and one needs training — three different responses that a single "re-education" push would have gotten wrong.
How it works¶
What distinguishes the protocol from a casual chat or an opinion survey is structure aimed at causes:
- Non-leading, reason-seeking prompts. Questions ask people to reconstruct concrete recent episodes and the reasoning behind them, not to rate agreement, because the goal is the why beneath the behavior.
- Sampling for the edges. Interviewees are chosen to include the roles, sites, and shifts where resistance clusters and the quiet non-adopters, not just the vocal or the convenient.
- Barrier typing during synthesis. Each stated reason is coded against a fixed taxonomy of barrier types, so the raw accounts become a classified map rather than a pile of quotes.
- Interviewing to saturation. New interviews continue until they stop surfacing new barrier types — the point of theoretical saturation[n1] — so the map is reasonably complete before response design begins.
Tuning parameters¶
- Structure vs. openness — a tightly scripted schedule versus a loose guide. Tight scripts compare cleanly across interviewees; open ones surface the barrier nobody anticipated.
- Sample composition — who is interviewed and how the edges are weighted. Skewing toward quiet non-adopters and high-resistance sites finds real barriers but costs access and trust to reach.
- Interviewer independence — an outsider versus the change owner asking. Outsiders hear franker answers; insiders understand the work but chill candor about the change itself.
- Depth vs. breadth — a few long interviews versus many short ones. Depth reaches identity and trust barriers; breadth maps how widely each barrier is shared.
- Taxonomy granularity — coarse barrier classes versus fine ones. Finer typing matches support more precisely but risks false confidence in ambiguous cases.
When it helps, and when it misleads¶
Its strength is that it recovers the information inside resistance — the rational, protective, locally-informed reasons that a compliance frame discards — and hands it back as a typed map that a matched response can act on. It is often the single step that prevents a change team from misdiagnosing a trust or workload problem as a training problem.
Its failure mode is that interviews capture stated reasons, which are not always the operative ones: people rationalize, tell the interviewer what seems safe, or name the acceptable barrier ("I need training") over the real one ("I don't trust this leadership"). A tidy set of coded barriers can lend false confidence to an account that is polite fiction. Its classic misuse is the readiness-theater interview — concerns are collected, coded into a slide, and then no support, design, or decision changes, which teaches people that talking is pointless and poisons the next round. The discipline that guards against both is to triangulate stated reasons against observed behavior before trusting them, and to close the loop visibly by showing interviewees what their input changed.
How it implements the components¶
resistance_source_map— the protocol's primary output is exactly this map: which people, teams, and workflow points resist, and in what form, grounded in first-person accounts.barrier_classification— its synthesis step codes each source into a causal type (capability, trust, workload, incentive, technical fit, identity, design flaw), which is the classification the matched response depends on.
It does not measure adoption over time or count reversion — adoption_monitoring and relapse_and_workaround_signal are the standing job of Adoption Dashboard. The interview elicits the anticipated *reasons through conversation; the dashboard counts the symptoms through instrumentation. Nor does the protocol build any response: it names the barrier, it does not clear it.*
Related¶
- Instantiates: Change Resistance Diagnosis and Support — the protocol is the archetype's diagnostic front end, the step that earns the right to choose a matched response.
- Sibling mechanisms: Adoption Dashboard · Incentive Realignment · Migration Assistance · Pilot Rollout · Training and Practice Program · Trust-Building Communication · Participatory Design Session · Transition Support Plan · Change Readiness Assessment
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: A structured set of interviews that elicits why people expect a change to fail or harm them, then sorts those reasons into the barrier types the response must match, making its operative form a designed exchange or learning exposure that changes understanding or capability.
Independent corroboration: The frozen evidence defines Barrier Interview Protocol as 'A structured set of interviews that elicits why people expect a change to fail or harm them, then sorts those reasons into the barrier types the response must match', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Ethnography & Qualitative Methods
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Structured qualitative interviews elicit participants' situated reasons and organize them into interpretable themes.
Related originating lineages:
- Organizational & Management Science — Change management supplies the intervention-oriented barrier categories.
- Psychology — Behavioral assessment contributes expectations of harm, capability, and avoidance.
Review resolution: Structured interviewing and saturation keep qualitative methods primary, while psychology and change management shape the causal barrier taxonomy and intervention routing. The named combined protocol is therefore a cross-disciplinary Encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Theoretical saturation — the point in qualitative research (from Glaser and Strauss's grounded-theory method) at which additional interviews stop yielding new categories. Interviewing to saturation is the standard guard against declaring a barrier map "complete" after too few conversations. ↩