Tool

Stakeholder Interview Scripts, Notes & Analysis (Interactive)

A ready-to-run, guided interview form with differentiated question sets for executives, domain experts, frontline staff, and customers plus structured note capture, an outcome-framing section, and a quick scoring rubric. Submissions are saved for later affinity mapping and use-case hypothesis generation.

Interactive Tool

Stakeholder Interview — Script, Notes & Analysis

Use this guided interview to capture reliable, comparable input across stakeholders. The form includes role-specific prompts, structured fields to record pains and measurable outcomes, a short scoring rubric to judge interview usefulness for downstream use-case discovery, and fields that seed AI-assisted synthesis or affinity mapping. Save each interview to build an evidence-backed set of use-case hypotheses.

Enter date and time (e.g. 2026-08-12 10:00).
Who conducted the interview.
Name or identifier (use initials if confidentiality required).
Stakeholder's role or title in the organization.
Choose the best-fit category — helps compare responses across similar roles.
Use the stakeholder's words; capture concrete activities, frequency, and context.
Ask them to walk through a common task or shift. Note tools, handoffs, documents, and systems used.
Capture specific problems, how often they happen, and concrete examples. Avoid vague 'would be nice' language.
Estimate frequency. If not applicable, enter 0.
1 = minor nuisance, 5 = critical / business-stopping
1.0 10.0
Ask for existing KPIs or measurable outcomes (time saved, error rate, revenue, NPS, compliance events, etc.).
Note who performs the workaround, its cost or time, and failure modes.
What systems, spreadsheets, documents, or data sources are used or missing?
When this problem happens, who decides what to do and what information do they need?
This exposes upside beyond mere pain reduction — new capabilities, services, or ways of working.
(Use one or more probes based on stakeholder type: executives — outcomes and strategy; domain experts — constraints and priorities; frontline — steps and exceptions; customers — experience and unmet needs).
Capture memorable phrases or exact wording that reveal need or value language.
Convert the core pain into a single clear problem statement that AI/product work might address.
People, teams, customers, systems — provide counts or estimates when possible.
Provide current numbers for any important metrics mentioned.
What improvement would be convincing? Be specific (e.g., reduce time from 3 days to 1 day).
If unclear, leave blank. Helps estimate ROI.
1 = low priority, 5 = top priority
1.0 10.0
1 = unlikely / high effort, 5 = easy / data available
1.0 10.0
Quick labels to support later affinity mapping and filtering.
1 = vague, 5 = very specific
1.0 10.0
Yes if the stakeholder provided concrete metrics or clear success criteria.
Quick disposition to guide next steps.
Reviewer can suggest an affinity label for later grouping (e.g., 'invoice automation').
E.g., request data sample, schedule technical deep-dive, validate metric, build prototype.
Who should take the next step?
Optional target date (YYYY-MM-DD).
Summarize why this interview is valuable and what hypothesis it suggests (2–4 sentences).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.