Actor Perspective Interview¶
Procedure — instantiates Situational Attribution Check
An interview method for eliciting what the actor saw, knew, intended, misunderstood, feared, or could do.
Actor Perspective Interview sits the person whose behavior is being judged down and recovers the one thing an outside observer structurally cannot see: the inside view of the moment. Its whole job is to turn "what were they thinking?" from a rhetorical accusation into an actual answer — a first-person record of what the actor perceived, what information they had, what they were trying to do, what they misread, what they were afraid of, and which options they believed were open to them. Its defining move is that it is elicited testimony, not observer inference: the account comes from the actor's own mouth about their own experience, captured before the observer's trait story is allowed to overwrite it. That is exactly what separates it from a situation-reconstruction, which triangulates many sources into an objective picture of the setting — this interview stays inside one head on purpose.
Example¶
A junior engineer pushes a config change that takes down checkout for eleven minutes. The on-call thread has already settled on "reckless — didn't check." Before that hardens into a performance note, her lead runs an Actor Perspective Interview. Organized around what she saw, knew, intended, feared, and could do, it surfaces: the deploy dashboard showed the canary as green (it was caching a stale run); she believed the change was config-only and non-routable; she had been told an hour earlier that a waiting release was "blocking three teams," so she felt pressure to not stall; and she did not know a second, faster rollback path existed because it wasn't in the runbook she was handed. None of that excuses the outage on its own — but the record now shows a person acting on bad instruments under felt pressure, not someone who shrugged at risk. That is a different problem, and it points at a different fix.
How it works¶
- Interview against a hypothesis, not for excuses. The interviewer names the trait story out loud ("we're reading this as carelessness") and treats the interview as a test of it, not a hunt for mitigation.
- Walk the five faces of the inside view — saw / knew / intended / misunderstood / feared / could-do — separating recall of fact ("the dashboard was green") from justification ("so I thought it was safe").
- Anchor everything to the moment. Answers are timestamped to what was known then, not what is obvious now, so the account is not quietly rewritten by the outcome.
- Capture close to verbatim. The record preserves the actor's own words, because paraphrase is where the observer's story leaks back in.
Tuning parameters¶
- Rapport vs. challenge — a warmer stance gets fuller disclosure; a more probing one gets less self-flattery. Too warm collects a comfortable story; too cold collects a defended one.
- Timing — how soon after the event. Sooner preserves detail but catches people rattled; later is calmer but memory has already begun to tidy itself.
- Recording fidelity — verbatim transcript versus a summarized note; fidelity guards against paraphrase drift but costs time and can chill candor.
- Interviewer independence — the actor's own manager versus a neutral party; independence reduces the incentive to perform, at the cost of context the manager already holds.
- Scope — a single behavior versus a pattern across time; widening it finds themes but dilutes the sharp reconstruction of one moment.
When it helps, and when it misleads¶
Its strength is that it is the only mechanism that recovers the actor's private information — the misread instrument, the pressure nobody logged, the option that was never visible. Without it the review is guessing at the interior it most needs.
Its failure mode is that self-reports are motivated. People narrate their own conduct in situational terms[1] and reach for disposition when explaining others — the actor–observer asymmetry — so an unguarded interview can hand the actor the very excuse the archetype warns against. The classic misuse is treating the account as the verdict: taking "I thought it was safe" as proof it was blameless. The discipline that keeps it honest is to treat the record as testimony to be weighed against records and other accounts, not accepted on its own, and to keep the standard and the harm in view while the story is heard.
How it implements the components¶
actor_perspective_record— this is the mechanism's product: a structured, first-person account of what the actor knew, intended, feared, and believed was possible at the time.observed_behavior— it re-anchors the concrete act from the actor's telling, often correcting an observer's description (the "ignored the alert" was a stale alert never raised), so the behavior under review is what actually happened.
It records one person's inside view but does not rebuild the objective setting or weigh explanations against it — situational_factor_map and explanatory_weighting belong to its nearest twin, Context Reconstruction Interview, which triangulates many sources instead of eliciting a single account. It also does not test which constraints actually bit (constraint_context_review — Constraint and Incentive Checklist) or hold the standards-and-harm line (accountability_boundary — Policy Exception Review).
Related¶
- Instantiates: Situational Attribution Check — it supplies the actor's inside view, the perspective the rest of the check is missing.
- Sibling mechanisms: Context Reconstruction Interview · Behavior-Context Mapping Template · Constraint and Incentive Checklist · Empathy Mapping · Incident Timeline Review · Performance Context Review · Policy Exception Review · Just Culture Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: The mechanism is an interview method for eliciting what the actor saw, knew, intended, misunderstood, feared, or could do, so its operative form is communication, facilitation, or learning exposure.
Independent corroboration: The frozen evidence defines Actor Perspective Interview as 'An interview method for eliciting what the actor saw, knew, intended, misunderstood, feared, or could do', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Analysis, Modeling & Optimization — The interview interaction elicits the actor's perspective; analysis of that material is downstream.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Ethnography & Qualitative Methods
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Eliciting a first-person account of what an actor saw, knew, intended, feared, and believed possible through close, timestamped interviewing is a qualitative-research method.
Related originating lineages:
- Organizational & Management Science — Incident interviews and just-culture review supply a common professional implementation.
- Psychology — Attribution theory and avoidance of trait-based fundamental attribution error provide the diagnostic question.
Review resolution: The defining artifact is an open-ended interview that recovers the participant's own meanings, intentions, perceived options, and contextual constraints, making ethnography and qualitative methods primary. Psychology motivates the attribution-bias check and organizational incident learning supplies a major use, while the encyclopedia combines them.
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:
References¶
[1] Jones, E. E., & Nisbett, R. E. "The Actor and the Observer: Divergent Perceptions of the Causes of Behavior". In Attribution: Perceiving the Causes of Behavior, 79–94. General Learning Press (1972). Describes the actor–observer asymmetry: actors emphasize situational causes for their own conduct while observers emphasize dispositions. registry ↩