Prd V05 Risk Discovery Interview

Risk Discovery Interview

Position in workflow: v0.4 Screen Flow Definition → v0.5 Risk Discovery Interview → v0.5 Technical Stack Selection

This is an interactive interview skill. The AI asks questions, the user reflects and decides. The goal is to surface risks so the user can mitigate or accept them—not to kill ideas.

Design Principles

1. Interview, not inquisition — Facilitate discovery, don't interrogate
2. Inform, not kill — Surface risks so user can mitigate, not abandon
3. User owns decisions — AI facilitates, user assigns severity and response
4. Actionable outputs — Every risk has a mitigation path or explicit "accept"

Risk Categories

Discovery Categories (Interview Prompts)

Scoring Categories (README Scorecard)

Each RISK- entry maps to one of 3 scoring categories for the README Risk Scorecard:

Interview Flow

Phase 1: Context Review

Before asking questions, AI reviews:

• CFD- evidence from v0.1-v0.2
• FEA- features and their priorities
• UJ- journeys and their complexity
• BR- business rules and constraints

Phase 2: Guided Questions

Ask questions from each category, adapting based on product context:

Market Risks:

• "What happens if [competitor] launches something similar in 60 days?"
• "What market assumption are you least confident about?"
• "What would cause users to choose a competitor instead?"

Technical Risks:

• "Which feature has the most technical uncertainty?"
• "What technology choice are you least confident about?"
• "Is there anything you've never built before?"

Adoption Risks:

• "What's the biggest friction point in [UJ-001 onboarding journey]?"
• "What behavior change are you asking users to make?"
• "What would cause a user to churn in the first week?"

Resource Risks:

• "If you had only 2 developers, what would you cut?"
• "What skill does the team lack?"
• "What's your runway for validation?"

Dependency Risks:

• "What external API or service could break your product?"
• "What partner relationship is critical?"
• "What regulatory requirement could block launch?"

Timing Risks:

• "Is there a hard deadline? What happens if you miss it?"
• "Is there a market window closing?"
• "What seasonal factor affects launch timing?"

Phase 3: Risk Documentation

For each identified risk, create RISK- entry with user input on severity and response.

Phase 4: Priority & Review

• Force-rank risks by Impact × Likelihood
• Identify top 3-5 that require active mitigation
• Document "accept" decisions explicitly

Interview Techniques

RISK- Output Template

RISK-XXX: [Risk Title]
Scoring Category: [Market | User | Technical]
Discovery Category: [Market | Technical | Adoption | Resource | Dependency | Timing]
Description: [What could go wrong]
Trigger: [What would cause this to happen]
Impact: [High | Medium | Low] — User assessed
Likelihood: [High | Medium | Low] — User assessed
Raw Score: [Impact × Likelihood, 1-9]
Status: [open | mitigating | mitigated | resolved | accepted]
Effective Score: [Raw Score × Status Weight]

Early Signal: [How we'd know this is happening]
Response: [Mitigate | Accept | Avoid | Transfer]
Mitigation: [Specific action if Response = Mitigate]
Owner: [Who is responsible for monitoring]

Linked IDs: [FEA-XXX, UJ-XXX, BR-XXX affected]
Review Date: [When to reassess this risk]
Added: [PRD stage when discovered, e.g., v0.5]

Status weights: open=1.0, accepted=1.0, mitigating=0.5, mitigated=0.25, resolved=0.0

Example RISK- entry:

RISK-001: Primary API Dependency (Stripe) Outage
Scoring Category: Technical
Discovery Category: Dependency
Description: Stripe API outage would block all payment processing
Trigger: Stripe infrastructure failure or rate limiting
Impact: High (3) — All revenue blocked during outage
Likelihood: Low (1) — Stripe has 99.99% uptime SLA
Raw Score: 3
Status: mitigating
Effective Score: 1.5

Early Signal: Stripe status page, payment failure rate spike
Response: Mitigate
Mitigation:
  - Implement graceful degradation (queue payments for retry)
  - Add status page monitoring alert
  - Document manual billing fallback process
Owner: Tech Lead

Linked IDs: FEA-020 (payments), UJ-005 (checkout), BR-030 (pricing)
Review Date: Before launch, quarterly thereafter
Added: v0.5

Risk Response Types

Severity Matrix

Anti-Patterns to Avoid

Phase 5: Score & Scorecard

After documenting all risks:

1. Assign scoring categories: Map each RISK- to Market, User, or Technical
2. Calculate scores: Raw Score = Impact × Likelihood; Effective = Raw × Status Weight (all start as open)
3. Sum by category: Add effective scores within each scoring category
4. Determine risk level: Total score → Low (0-12), Moderate (13-25), Elevated (26-40), High (41+)
5. Update README scorecard: Fill in the Risk Scorecard table in README.md

Quality Gates

Before proceeding to Technical Stack Selection:

• All 6 risk categories explored
• Maximum 10-15 RISK- entries (focused, not exhaustive)
• Force-ranked by priority (Impact × Likelihood)
• Top 5 risks have specific mitigation plans
• "Accept" decisions are explicit, not accidental
• Every RISK- has an owner
• Every RISK- has a scoring category (Market/User/Technical)
• README Risk Scorecard updated with baseline scores

Continuous Risk Management

v0.5 establishes the baseline risk register, but risk discovery does not end here. New RISK- entries can be added at any stage:

Protocol when adding risks after v0.5:

1. Use the same RISK- template (assign next available number)
2. Set Added: v0.X to record which stage surfaced it
3. Recalculate category and total scores
4. Update README Risk Scorecard

Protocol when risk status changes:

1. Update the RISK- entry status in PRD.md
2. Recalculate effective score (Raw × new Status Weight)
3. Update README Risk Scorecard totals

Downstream Connections

RISK- entries feed into:

Detailed References

• Interview question bank: See references/question-bank.md
• RISK- entry template: See assets/risk.md
• Example risk register: See references/examples.md