Skip to content

ilandahan/AID / skills/pre-prd-research

pre-prd-research

Verified

Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.

references/interview-guide.md

View on GitHub
# Stakeholder Interview Guide

Comprehensive guide for conducting effective stakeholder interviews during the research phase.

## Interview Types

### Discovery Interview
**Purpose**: Understand the problem space deeply
**Duration**: 60-90 minutes
**When to use**: Beginning of research phase

### Validation Interview
**Purpose**: Confirm hypotheses and assumptions
**Duration**: 30-45 minutes
**When to use**: Mid-to-late research phase

### Expert Interview
**Purpose**: Gain domain-specific insights
**Duration**: 45-60 minutes
**When to use**: When specialized knowledge is needed

---

## Interview Preparation Checklist

### Before Scheduling
- [ ] Identify stakeholder role and relevance
- [ ] Research their background (LinkedIn, company role)
- [ ] Define what you need to learn from them specifically
- [ ] Prepare 5-7 core questions
- [ ] Prepare 3-5 follow-up questions per topic

### Day Before
- [ ] Send reminder with agenda
- [ ] Test recording equipment (if recording)
- [ ] Prepare note-taking template
- [ ] Review previous interviews for context

### Day Of
- [ ] Arrive/log in 5 minutes early
- [ ] Have water ready
- [ ] Have backup questions prepared
- [ ] Clear your schedule for processing time after

---

## Question Bank by Topic

### Understanding Current State

```markdown
**Workflow Questions**
- "Walk me through a typical day when you [relevant activity]"
- "What's the first thing you do when [trigger event] happens?"
- "Who else is involved in this process?"
- "What tools do you currently use for this?"

**Pain Point Questions**
- "What's the most frustrating part of [process]?"
- "If you could change one thing about [current solution], what would it be?"
- "Tell me about the last time [problem] happened"
- "What workarounds have you developed?"

**Impact Questions**
- "How much time do you spend on [task] per week?"
- "What happens when [problem] occurs?"
- "Who else is affected when this goes wrong?"
- "What's the cost of not solving this?"
```

### Understanding Needs & Goals

```markdown
**Outcome Questions**
- "What does success look like for you?"
- "If this was solved perfectly, what would change?"
- "What would you do with the time/money saved?"

**Priority Questions**
- "Of all the problems we discussed, which is most critical?"
- "What keeps you up at night about this?"
- "If you could only fix one thing, what would it be?"

**Constraint Questions**
- "What limitations do you work within?"
- "What's been tried before?"
- "What would prevent you from adopting a new solution?"
```

### Understanding Context

```markdown
**Historical Questions**
- "How long has this been a problem?"
- "How has this evolved over time?"
- "What solutions have you tried before?"

**Environmental Questions**
- "What external factors affect this?"
- "Are there regulatory/compliance considerations?"
- "What's changing in your industry that affects this?"

**Stakeholder Questions**
- "Who else should I talk to about this?"
- "Who would need to approve a new solution?"
- "Who would be most affected by changes?"
```

---

## Interview Flow Template

### Opening (5 minutes)
```
"Thank you for taking the time to speak with me today. I'm [name]
and I'm researching [topic area] to understand [goal].

This conversation is about learning from your experience -
there are no right or wrong answers. I'm here to understand, not to sell.

Do you mind if I take notes? [If recording: May I record for accuracy?]

Before we start, do you have any questions for me?"
```

### Warm-up (5 minutes)
```
"To start, could you tell me a bit about your role and
how long you've been doing this?"

"What does a typical day look like for you?"
```

### Core Exploration (40-50 minutes)
Use questions from the Question Bank, following the interviewee's lead.

**Key techniques:**
- **Mirror**: Repeat the last 3 words they said as a question
- **Label**: "It sounds like that was frustrating..."
- **Silence**: Wait 3-5 seconds after they finish
- **Dig deeper**: "Tell me more about that..."

### Future State (10 minutes)
```
"If you could wave a magic wand and have the perfect solution,
what would it do?"

"What would make you say 'this is exactly what I needed'?"

"What would success look like a year from now?"
```

### Closing (5 minutes)
```
"What question should I have asked but didn't?"

"Who else would you recommend I speak with?"

"Is there anything else you'd like to add?"

"Thank you so much for your time. This has been incredibly valuable.
May I follow up if I have additional questions?"
```

---

## Active Listening Techniques

### The TEDW Framework
- **T**ell me more about...
- **E**xplain what you mean by...
- **D**escribe a time when...
- **W**alk me through...

### Mirroring
Repeat the last 1-3 words as a question:
> Interviewee: "...and that's when everything fell apart"
> You: "Fell apart?"

### Labeling Emotions
Name the emotion you're sensing:
> "It sounds like that was really frustrating"
> "It seems like that made you feel uncertain"

### Strategic Silence
After they answer, wait 3-5 seconds before responding. They often fill the silence with deeper insights.

### Summarizing
Periodically summarize what you've heard:
> "So if I understand correctly, the main issues are X, Y, and Z?"

---

## Note-Taking Template

```markdown
## Interview: [Name] - [Role]
**Date**: [Date]
**Duration**: [Time]
**Traceability ID Prefix**: [PROJECT]-A-INT-XXX

### Background
- Role:
- Experience:
- Context:

### Key Insights
1. [Insight] - ID: [PROJECT]-A-INT-001
2. [Insight] - ID: [PROJECT]-A-INT-002
3. [Insight] - ID: [PROJECT]-A-INT-003

### Pain Points Identified
| Pain Point | Severity (1-10) | Frequency | Quote |
|------------|-----------------|-----------|-------|
| | | | |

### Current Solutions/Workarounds
-

### Desired Future State
-

### Notable Quotes
> "[Quote]" - regarding [topic]

### Follow-up Questions
-

### Recommended Next Interviews
- [Name/Role]: because [reason]

### Surprises / Unexpected Findings
-

### My Hypotheses Challenged
-
```

---

## Common Interview Mistakes

| Mistake | Why It's Bad | How to Fix |
|---------|--------------|------------|
| Leading questions | Biases responses | Use open-ended questions |
| Talking too much | Miss insights | 80/20 rule (they talk 80%) |
| Not following up | Surface-level data | Always ask "tell me more" |
| Taking sides | Creates bias | Stay neutral, curious |
| Jumping to solutions | Premature closure | Focus on problems first |
| Not recording | Lost data | Always take notes, record if possible |
| Scheduling back-to-back | No processing time | Leave 30 min gaps |

---

## Post-Interview Processing

### Immediately After (15 min)
1. Complete any unfinished notes
2. Write down immediate impressions
3. Note any follow-up questions
4. Rate insight quality (1-5)

### Within 24 Hours
1. Assign traceability IDs to all insights
2. Update traceability matrix
3. Identify patterns with previous interviews
4. Draft summary paragraph

### Interview Synthesis Template

```markdown
## Interview Synthesis: [Name]

### Top 3 Insights
1. **[PROJECT]-A-INT-XXX**: [Insight]
2. **[PROJECT]-A-INT-XXX**: [Insight]
3. **[PROJECT]-A-INT-XXX**: [Insight]

### Confirmation of Previous Findings
- Confirms: [Previous ID] - [Finding]

### New Information
- [New finding not seen before]

### Contradictions
- Contradicts: [Previous ID] - [How]

### Impact on Hypothesis
- [How this changes our understanding]

### Next Steps
- [ ] Follow up on [topic]
- [ ] Interview [recommended person]
- [ ] Investigate [new area]
```

---

## Remote Interview Tips

### Technical Setup
- Use reliable video platform (Zoom, Teams, Meet)
- Have backup phone number ready
- Test audio/video before
- Use headphones to reduce echo
- Have good lighting on your face

### Building Rapport Remotely
- Turn camera on (encourage them to as well)
- Look at camera, not screen, when they speak
- Use their name occasionally
- Acknowledge their environment if appropriate
- Be more expressive than in person

### Managing Technical Issues
- "I think we had a brief connection issue, could you repeat that?"
- Have chat backup ready
- Send follow-up email if call drops

---

## Interview Metrics

Track these across your interview program:

| Metric | Target | Actual |
|--------|--------|--------|
| Total interviews | 8-12 | |
| Stakeholder types covered | 3+ | |
| Average insights per interview | 5+ | |
| New vs. confirming insights | 40/60 | |
| Follow-up interview requests | 2+ per interview | |
| Interview-to-insight ratio | 1:5 minimum | |
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall