1.03 Stakeholder Interview Plan

1. Key Stakeholder Types

You’ll want a diverse mix so you capture business, technical, and user-facing perspectives:
	•	Product Management → Define vision, strategy, priorities
	•	Engineering / Tech Leads → Feasibility, limitations, integrations
	•	Design / UX → Usability, user needs, adoption blockers
	•	Marketing → Positioning, growth, acquisition
	•	Sales / Business Development → Customer objections, selling points
	•	Customer Support / Success → Real user issues, common pain points
	•	Operations / IT (if internal-facing app) → Process constraints, workflow integration
	•	End-users (internal champions / power users) → Direct perspective on needs

⸻

2. Interview Questions

A. Business Goals & Success
	1.	“What does success for this Task Manager App look like to you in the next 6–12 months?”
	2.	“How does this project align with your team’s broader goals or KPIs?”

B. Pain Points & Constraints
	3.	“What current challenges or inefficiencies are you hoping this app will solve?”
	4.	“Can you share examples where existing tools or processes have fallen short?”

C. User Assumptions
	5.	“What do you believe our users struggle with the most when managing tasks?”
	6.	“If you had to guess, what’s the one feature users would value the most—and why?”

D. Technical / Operational Limitations
	7.	“From a technical or process standpoint, what constraints should we be aware of (e.g., integrations, scalability, compliance)?”
	8.	“Are there any existing systems or workflows this app must fit into?”

E. Success Metrics & Prioritization
	9.	“Which metrics would you personally track to know this app is working?”
	10.	“If you had to choose, would you prioritize adoption, engagement, or efficiency gains—and why?”

⸻

3. Structure & Style Notes
	•	Keep questions open-ended → invite stories, not yes/no answers.
	•	Use “what / how” framing → avoids leading the stakeholder.
	•	Encourage examples and anecdotes → real-world context beats abstract opinions.
	•	End with a catch-all “Is there anything else you think we should know that I haven’t asked?”

⸻

4. Interview Guide Formatting

Here’s how you could structure your guide:

Section A: Warm-up
	•	Introduce purpose of interview (exploring goals, needs, and constraints).
	•	Ask: “What’s your role in relation to this project?”

Section B: Business & Goals
	•	Q1, Q2

Section C: Pain Points & Constraints
	•	Q3, Q4

Section D: User Assumptions
	•	Q5, Q6

Section E: Technical / Operational
	•	Q7, Q8

Section F