System Mapping Interviews¶
Elicitation method — instantiates Boundary Critique Audit
Elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map.
System Mapping Interviews is the elicitation method that reconstructs the real system around a boundary by talking to the people who live on both sides of it. Its defining feature is that its product is primary testimony assembled into a map: it gathers what insiders, outsiders, maintainers, affected communities, and adjacent-system operators know but no document records, attributes each account to its source, and lays the accounts out as a dependency map that shows what the official boundary omits. It is upstream of judgment — it does not size the effects it finds or rule on who is to blame. It supplies the raw, traceable evidence, and its whole value is recovering the tacit dependency that the center of a system cannot see but its periphery lives with daily.
Example¶
A plant has a recurring seal-failure defect, and every incident report closes it the same way: operator error. Rather than accept that boundary, a process engineer runs a round of system mapping interviews across the vantage points the reports never reach. Floor operators describe a pneumatic torque tool that drifts out of calibration by the end of a shift. Maintenance techs reveal a months-long calibration backlog no dashboard shows. Night-shift crews report running two lines while short-staffed. The gasket supplier's rep mentions a quiet lot change three weeks before the failures began.
Each account is recorded with its source attached — who said it, from what vantage — so the finding can be traced back rather than asserted. Assembled, the accounts form a dependency map: the "operator error" boundary excludes calibration cadence, staffing levels, and a supplier change, and the defect is plainly system-shaped. The interviews neither price the scrap cost nor assign fault; they surface the omitted dependencies and hand a mapped, attributed body of evidence to whatever weighs it next.
How it works¶
- Sample vantage points deliberately. Choose interviewees to span insiders, outsiders, maintainers, affected communities, and adjacent operators — the periphery holds the dependencies the center cannot see.
- Elicit what documents omit. Use open prompts that invite the tacit, the worked-around, and the informally-known, rather than confirming the official account.
- Record with attribution. Attach each account to its source and vantage, so the resulting evidence is traceable back to specific testimony.
- Assemble into a dependency map. Lay the accounts out as cross-boundary relations, flagging the dependencies that cross the line the official frame drew.
Tuning parameters¶
- Vantage spread — insiders only versus the full periphery. Reaching outsiders and maintainers finds the hidden dependency; staying inside re-confirms the official story.
- Interview structure — tightly structured versus open-ended. Open elicitation surfaces the unanticipated dependency; structure makes accounts comparable but can steer them.
- Attribution vs. anonymity — how much each account is tied to a named source. Attribution strengthens traceability; anonymity loosens the tongues of people who face risk for speaking.
- Saturation — how many interviews are run before no new dependencies appear. Stopping early misses the periphery; running long past saturation wastes access.
- Map granularity — how finely the dependency map is drawn. Fine granularity captures subtle couplings but risks reifying a single account as system fact.
When it helps, and when it misleads¶
Its strength is recovering the tacit, undocumented dependency that no record holds — the calibration backlog, the workaround, the quiet supplier change — because the people at the edges of a system see what its official frame cannot. It operationalizes the "new view" of human error, which treats an operator's mistake not as a cause but as a symptom of deeper conditions in the system around them.[1]
Its failure mode is that interviews inherit the biases of whom you ask and what people recall: a periphery sampled narrowly yields a narrow map, and a vivid recent account can outweigh a chronic invisible one. The classic misuse is the interview round staged to confirm a predetermined boundary — questions aimed to elicit the answer the sponsor already wants. The guarding discipline is to sample adversarially, deliberately seeking vantages likely to disconfirm the official story, and to keep testimony marked as testimony — evidence-graded, attributed — rather than promoted to measured fact.
How it implements the components¶
evidence_trace— it records each account with its source and vantage, so every mapped dependency can be traced back to specific testimony.whole_system_impact_map— it assembles the elicited accounts into a dependency map of the cross-boundary relations the official frame omits.
System Mapping Interviews elicit and map the raw evidence; they do not size the external effects with an externality_mapping or run the materiality_test that separates the significant from the trivial — that measurement is Impact Assessment. The interviews supply the testimony; the assessment weighs it.
Related¶
- Instantiates: Boundary Critique Audit — this is the elicitation strand that supplies the audit's primary, traceable evidence.
- Sibling mechanisms: Ethical Review · Impact Assessment · Inclusion/Exclusion Register Review · Model Scope Review · Policy Scope Audit · Stakeholder Exclusion Audit · Whole-System Impact Map
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: System Mapping Interviews operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map.
Independent corroboration: The frozen evidence defines System Mapping Interviews as 'Elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Representation, Specification & Plan — System Mapping Interviews includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Ethnography & Qualitative Methods
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: System mapping interviews derives most directly from qualitative research's interview, observation, and situated-inquiry tradition; its defining operation is to elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map.
Related originating lineages:
- Sociology & Anthropology — Sociology and anthropology's institutions, culture, and social-relation tradition provides a formative adjacent lineage for the same system mapping interviews operation.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map.
Review resolution: Both blind reviewers independently select ethnography_qualitative_methods as the primary historical origin for the concrete operation—Elicits the real system around a boundary from the people inside and outside it, turning testimony official documents omit into a traceable dependency map. The queued differences concern reported ambiguity, alternate origin disagreement, origin mode disagreement, domain reach disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=medium is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Attribution caveat: Participatory system mapping spans qualitative inquiry, systems practice, and sociology.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
System Mapping Interviews is the elicitation that populates a map; the standalone Whole-System Impact Map is the artifact. They are easy to conflate because the interviews produce a mapped output, but the division of labor is real: the interviews recover and attribute the raw dependency evidence, while a dedicated impact-map artifact is where cross-boundary consequences are laid out and netted for a decision. Treat the interview map as a working draft of evidence, not the finished consequence artifact.
References¶
[1] Dekker, S. The Field Guide to Understanding Human Error, rev. ed. Ashgate (2006). Dekker's new view treats operator error as a symptom of deeper conditions in the surrounding system rather than as the cause. The source does not say that this mechanism operationalizes that view. registry ↩