Stakeholder Diagnostic Interview Script

Stakeholder Diagnostic Interview Script

This script helps you run short, focused diagnostic interviews that capture actionable evidence (not just anecdotes). Use it to discover where decisions break down, what knowledge is at risk, who owns recurring problems, and what measurable impacts those problems cause. Each question includes probes and fields you should record during or immediately after the interview.

Before you begin

• Timebox: aim for 30–45 minutes. Tell interviewees why you're there and how their input will be used.
• Consent: confirm it's okay to take notes and (if relevant) record for accuracy. Offer anonymity if that encourages candor.
• Materials: interview guide, recording device (optional), a blank recording template (below) or a digital form.
• Outcome: explain you'll capture concrete examples, estimate impact, and identify suggested next steps and owners.

Interview structure

1. Opening (2–4 min): purpose, confidentiality, and a high-level question about their role/context.
2. Core questions (20–30 min): role-appropriate prompts with evidence probes.
3. Closing (3–5 min): summarize top points, confirm suggested owners and next steps, ask for any final examples or documents.

How to record answers

For each meaningful statement, capture:

• Quote: a short verbatim phrase that captures the gist.
• Evidence: specific examples, documents, frequency, dates, system names, screenshots.
• Impact estimate: operational effect (time lost, defects, safety, revenue, customer impact). Use a simple scale: 1 (low)–5 (high).
• Confidence: how certain the interviewee is (low/medium/high).
• Suggested follow-up / owner: who should take the next step and what (investigate, pilot fix, escalate).

Core questions (use with all roles)

1. Describe a recent time when work didn't go as you expected. What happened?
• Probes: When was this? Who was involved? How often does this happen?
• Record: Quote, evidence, frequency, immediate impact.
2. What decisions do you make every day that are hard or uncertain?
• Probes: What information do you lack? What happens when the decision is delayed or wrong?
• Record: Example decision, missing inputs, downstream effects.
3. Where do handoffs between teams or roles break down?
• Probes: Systems used, unclear ownership, timing issues, error types.
• Record: Specific handoff, consequences, suggested owner.
4. What knowledge lives only in people’s heads and is at risk if they leave or are unavailable?
• Probes: Who depends on that person? Are there documents or checklists?
5. If you could change one process or tool today, what would it be and why?
• Probes: Expected benefits, estimated effort, quick wins vs. long-term fix.

Role-specific prompts

Operators / Frontline workers

• Walk me through your typical shift or task. Where do you most often pause, wait, or rework?
• Probes: system lags, missing parts, unclear instructions, safety concerns.
• Are there workarounds you use? How consistent are they across shifts?

Managers / Supervisors

• What recurring problems consume your time each week?
• Probes: meeting topics, escalations, staffing gaps, training issues.
• How do you measure whether a fix worked?

Leaders / Executives

• Which outcomes matter most to you and where are we falling short?
• Probes: strategic KPIs, customer feedback, regulatory exposure, cost drivers.
• Where are resources misaligned with priorities?

Cross-functional partners (quality, maintenance, IT, suppliers)

• How do you currently receive issues from other teams? What information is missing?
• Where do recurrent defects or failures originate, from your perspective?

Recording template (copy into notes or a simple form)

Quick prioritization method

After the interview, rate each captured problem by:

• Impact (1–5): How large the operational/customer/regulatory/cost effect is.
• Frequency (1–5): How often it occurs.
• Calculate a simple score: Impact x Frequency. Higher scores suggest earlier attention.
• Also note Confidence—if low, flag for rapid verification rather than immediate investment.

Closing the interview

• Summarize the top 1–2 issues you heard and the suggested next steps.
• Confirm any documents or data the interviewee can share and a point of contact for follow-up.
• Thank them and explain how you will use their input (e.g., prioritized remediation plan, quick wins, pilot).

Interviewer tips

• Ask for concrete examples and dates—avoid hypotheticals unless you explicitly label them.
• Listen for names, systems, and frequencies; these are the signals that turn anecdotes into evidence.
• When someone says "always" or "never," probe for exceptions and quantify frequency.
• Keep the interview conversational; use silence strategically to encourage more detail.

Suggested next steps after a batch of interviews

1. Aggregate problems by theme, owner, and score (Impact x Frequency).
2. Identify 1–3 quick verification steps for low-confidence, high-impact items.
3. Assign owners for short experiments or pilots, set measurable acceptance criteria, and schedule a follow-up check-in.
4. Create a short summary of findings with recommended actions and circulate to relevant stakeholders.

Use this script as a living template—adapt wording, scales, and recording fields to match your domain and the kinds of evidence you can access. If you plan to run many interviews, consider turning the recording template into an Interactive form so responses are standardized and storable.