# Product Manager / Project Manager - Brain Seed

## Core Knowledge
- RICE scoring: Reach × Impact × Confidence / Effort — use for backlog prioritization
- Sprint velocity: rolling 3-sprint average, don't commit more than 85% capacity
- User story format: "As a [persona], I want [action] so that [outcome]"
- Definition of Done: code reviewed, tested, documented, deployed to staging, PO accepted
- Burndown chart: if above ideal line for 3+ days, investigate blockers immediately

## Frameworks
- Jobs-to-be-Done: focus on the job the user is hiring the product to do
- Opportunity Solution Tree: map desired outcome → opportunities → solutions → experiments
- MoSCoW: Must-have, Should-have, Could-have, Won't-have for scope negotiation
- Kano Model: Basic (must), Performance (more=better), Excitement (delighters)
- RACI matrix: Responsible, Accountable, Consulted, Informed for role clarity

## Meeting Patterns
- Sprint Planning: timebox 2hr for 2-week sprint, pull from prioritized backlog
- Daily Standup: 15min max, blockers go to parking lot for offline resolution
- Retro format: What went well / What didn't / Action items (max 3, assigned with DRI)
- Stakeholder review: demo working software, not slides

## Risk Management
- Traffic light system: Green (on track), Yellow (at risk), Red (blocked/delayed)
- Pre-mortem: "Imagine this project failed — what went wrong?" to surface hidden risks
- Dependency mapping: identify cross-team dependencies in planning, not during execution
- Buffer: add 20% buffer for unknowns, 40% for novel technology

## Metrics That Matter
- Activation rate: % of signups who reach "aha moment"
- Retention: D1, D7, D30 cohort retention curves
- NPS: >50 is excellent, <0 needs immediate attention
- Time-to-value: how quickly new users get value from the product
- Feature adoption: % of MAU using a feature within 30 days of launch