agentic-team-templates 0.8.2 → 0.9.0

package/templates/product-manager/CLAUDE.md

@@ -0,0 +1,593 @@
+# Product Management Development Guide
+
+Principal-level guidelines for building products that deliver measurable business outcomes through customer-centric discovery, strategic prioritization, and cross-functional execution.
+
+---
+
+## Overview
+
+This guide applies to:
+
+- Product strategy and roadmapping
+- Customer discovery and user research
+- Feature prioritization and backlog management
+- PRDs and requirements documentation
+- OKRs, KPIs, and product analytics
+- Stakeholder communication and alignment
+- Go-to-market coordination
+
+### Key Principles
+
+1. **Outcomes Over Outputs** - Measure success by business impact, not features shipped
+2. **Continuous Discovery** - Talk to customers weekly; never stop learning
+3. **Data-Informed Decisions** - Use evidence, not opinions, to prioritize
+4. **Cross-Functional Leadership** - Unite engineering, design, and business around shared goals
+5. **Strategic Clarity** - Every feature traces back to company objectives
+
+### Core Frameworks
+
+| Framework | Purpose |
+|-----------|---------|
+| OKRs | Align team efforts with business outcomes |
+| RICE | Prioritize features objectively |
+| Opportunity Solution Trees | Map discovery to outcomes |
+| Jobs-to-be-Done | Understand customer motivations |
+| User Story Mapping | Visualize the user journey |
+| Kano Model | Categorize feature impact |
+
+---
+
+## Product Strategy
+
+### Vision to Execution Hierarchy
+
+```
+Company Vision
+    ↓
+Product Vision (3-5 year horizon)
+    ↓
+Product Strategy (1-2 year horizon)
+    ↓
+Product Roadmap (quarterly themes)
+    ↓
+OKRs (quarterly outcomes)
+    ↓
+Initiatives & Epics (deliverables)
+    ↓
+User Stories (implementation)
+```
+
+### Strategy Document Template
+
+```markdown
+# Product Strategy: [Product Name]
+
+## Vision
+[One sentence describing the ideal future state]
+
+## Mission
+[How this product uniquely serves customers]
+
+## Target Customer
+- Primary persona: [Name, role, key characteristics]
+- Secondary persona: [Name, role, key characteristics]
+- Anti-persona: [Who this product is NOT for]
+
+## Value Proposition
+For [target customer] who [has this need],
+[Product] is a [category] that [key benefit].
+Unlike [competitors], we [key differentiator].
+
+## Strategic Pillars (3-5)
+1. [Pillar 1]: [Brief description]
+2. [Pillar 2]: [Brief description]
+3. [Pillar 3]: [Brief description]
+
+## Success Metrics
+| Metric | Current | Target | Timeline |
+|--------|---------|--------|----------|
+| [North Star] | X | Y | Q4 2025 |
+| [Retention] | X% | Y% | Q2 2025 |
+| [Revenue] | $X | $Y | FY 2025 |
+
+## Competitive Landscape
+| Competitor | Strength | Weakness | Our Advantage |
+|------------|----------|----------|---------------|
+| [Name] | [X] | [Y] | [Z] |
+
+## Key Risks & Mitigations
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| [Risk 1] | High | High | [Action] |
+```
+
+---
+
+## OKRs (Objectives and Key Results)
+
+### Structure
+
+```
+Objective: [Qualitative, inspiring, time-bound]
+├── KR1: [Quantitative metric] - Current: X → Target: Y
+├── KR2: [Quantitative metric] - Current: X → Target: Y
+└── KR3: [Quantitative metric] - Current: X → Target: Y
+```
+
+### Best Practices
+
+- **3-5 Objectives per quarter** - Focus enables execution
+- **2-4 Key Results per Objective** - Measurable, not tasks
+- **70% achievement is success** - Stretch goals drive innovation
+- **Outcomes, not outputs** - "Reduce churn to 5%" not "Launch retention feature"
+- **Weekly check-ins** - Track progress, identify blockers
+
+### OKR Examples
+
+**Good OKR:**
+```
+Objective: Become the go-to solution for enterprise customers
+
+KR1: Increase enterprise NPS from 32 to 50
+KR2: Reduce enterprise onboarding time from 14 days to 5 days
+KR3: Grow enterprise ARR from $2M to $4M
+```
+
+**Bad OKR:**
+```
+Objective: Launch enterprise features
+
+KR1: Ship SSO integration
+KR2: Build admin dashboard
+KR3: Create 10 case studies
+```
+(These are outputs, not outcomes)
+
+### OKR Alignment
+
+```
+Company OKR
+├── Product OKR (contributes to company OKR)
+│   ├── Engineering OKR (contributes to product OKR)
+│   ├── Design OKR (contributes to product OKR)
+│   └── Marketing OKR (contributes to product OKR)
+```
+
+---
+
+## Product Discovery
+
+### Continuous Discovery Habits
+
+```
+Weekly Rhythm:
+├── Monday: Review customer feedback, plan interviews
+├── Tuesday-Thursday: Customer interviews (minimum 1/week)
+├── Friday: Synthesize learnings, update opportunity tree
+```
+
+### Opportunity Solution Tree
+
+```
+                    [Desired Outcome]
+                          │
+            ┌─────────────┼─────────────┐
+            ▼             ▼             ▼
+      [Opportunity]  [Opportunity]  [Opportunity]
+            │             │             │
+       ┌────┼────┐   ┌────┼────┐   ┌────┼────┐
+       ▼    ▼    ▼   ▼    ▼    ▼   ▼    ▼    ▼
+     [Sol] [Sol] [Sol][Sol][Sol][Sol][Sol][Sol][Sol]
+       │
+   [Assumption Tests]
+```
+
+### Customer Interview Framework
+
+```markdown
+## Interview Guide: [Topic]
+
+### Opening (2 min)
+- Thank participant
+- Explain purpose (learning, not selling)
+- Get consent for recording
+
+### Context (5 min)
+- Tell me about your role
+- Walk me through a typical day
+- What tools do you use for [problem area]?
+
+### Problem Exploration (15 min)
+- Tell me about the last time you [problem behavior]
+- What happened? What did you do?
+- What was frustrating about that?
+- How did you work around it?
+- How often does this happen?
+
+### Impact (5 min)
+- What does this problem cost you? (time, money, frustration)
+- If this were solved, what would change?
+
+### Closing (3 min)
+- Is there anything else I should have asked?
+- Can we follow up if we have more questions?
+```
+
+### Discovery Outputs
+
+| Artifact | Purpose | Update Frequency |
+|----------|---------|------------------|
+| Opportunity Solution Tree | Visualize discovery progress | Weekly |
+| Customer Interview Repository | Store learnings | Per interview |
+| Assumption Tracker | Validate/invalidate beliefs | Weekly |
+| Competitive Intelligence | Track market changes | Monthly |
+| User Persona | Profile target customers | Quarterly |
+
+---
+
+## Prioritization
+
+### RICE Scoring Framework
+
+```
+RICE Score = (Reach × Impact × Confidence) / Effort
+```
+
+| Factor | Description | Scale |
+|--------|-------------|-------|
+| **Reach** | Users affected per quarter | Actual number |
+| **Impact** | Effect on each user | 0.25 (minimal) to 3 (massive) |
+| **Confidence** | Certainty in estimates | 50% (low) to 100% (high) |
+| **Effort** | Person-months required | Actual estimate |
+
+### RICE Scoring Template
+
+| Feature | Reach | Impact | Confidence | Effort | RICE Score |
+|---------|-------|--------|------------|--------|------------|
+| Feature A | 10,000 | 2 | 80% | 2 | 8,000 |
+| Feature B | 50,000 | 1 | 60% | 4 | 7,500 |
+| Feature C | 5,000 | 3 | 90% | 1 | 13,500 |
+
+**Priority: C → A → B**
+
+### Impact Scale Guidelines
+
+| Score | Label | Criteria |
+|-------|-------|----------|
+| 3 | Massive | Would users churn without this? |
+| 2 | High | Significant improvement to key workflow |
+| 1 | Medium | Notable but not critical improvement |
+| 0.5 | Low | Nice-to-have, minor improvement |
+| 0.25 | Minimal | Barely noticeable |
+
+### When to Override RICE
+
+- **Technical debt** - May not score high but enables future velocity
+- **Security/compliance** - Non-negotiable regardless of score
+- **Strategic bets** - Intentional investments in uncertain areas
+- **Quick wins** - Very low effort with moderate impact
+
+---
+
+## Requirements Documentation
+
+### PRD Template
+
+```markdown
+# PRD: [Feature Name]
+
+## Overview
+**Author:** [Name]
+**Last Updated:** [Date]
+**Status:** [Draft | In Review | Approved | In Development | Shipped]
+
+## Problem Statement
+[2-3 sentences describing the customer problem]
+
+### Evidence
+- [Data point 1]
+- [Customer quote 1]
+- [Research finding 1]
+
+## Goals & Success Metrics
+
+| Metric | Baseline | Target | Measurement |
+|--------|----------|--------|-------------|
+| Primary | X | Y | [How measured] |
+| Secondary | X | Y | [How measured] |
+
+## User Stories
+
+### [Persona 1]
+As a [role], I want to [action] so that [benefit].
+
+**Acceptance Criteria:**
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Scope
+
+### In Scope
+- [Feature 1]
+- [Feature 2]
+
+### Out of Scope
+- [Explicitly excluded 1]
+- [Future consideration 1]
+
+## Design
+[Link to designs or embed key screens]
+
+## Technical Considerations
+[Notes from engineering on approach, risks, dependencies]
+
+## Dependencies
+| Dependency | Owner | Status | Risk |
+|------------|-------|--------|------|
+| [API] | [Team] | [Status] | [Risk] |
+
+## Timeline
+| Milestone | Target Date | Status |
+|-----------|-------------|--------|
+| Design Complete | [Date] | [Status] |
+| Dev Complete | [Date] | [Status] |
+| QA Complete | [Date] | [Status] |
+| Launch | [Date] | [Status] |
+
+## Risks & Mitigations
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| [Risk] | [H/M/L] | [H/M/L] | [Action] |
+
+## Open Questions
+- [ ] [Question 1]
+- [ ] [Question 2]
+
+## Appendix
+- [Research documents]
+- [Competitive analysis]
+- [Historical context]
+```
+
+### User Story Format
+
+```
+As a [persona],
+I want to [action],
+So that [outcome/benefit].
+
+Acceptance Criteria:
+Given [context],
+When [action],
+Then [expected result].
+```
+
+### Story Sizing
+
+| Size | Points | Description |
+|------|--------|-------------|
+| XS | 1 | < 1 day, well-understood |
+| S | 2 | 1-2 days, minimal unknowns |
+| M | 3 | 3-5 days, some complexity |
+| L | 5 | 1-2 weeks, needs breakdown |
+| XL | 8+ | Too large, must be split |
+
+---
+
+## Stakeholder Communication
+
+### Communication Cadence
+
+| Audience | Format | Frequency | Content |
+|----------|--------|-----------|---------|
+| Executives | Review | Monthly | Strategy, OKRs, risks |
+| Cross-functional leads | Sync | Weekly | Priorities, dependencies |
+| Engineering team | Standup | Daily | Sprint progress |
+| Sales/CS | Update | Bi-weekly | Roadmap, releases |
+| Customers | Newsletter | Monthly | What's new, what's next |
+
+### Roadmap Presentation by Audience
+
+**For Executives:**
+- Focus on business outcomes, not features
+- Show alignment to company OKRs
+- Highlight risks and resource needs
+- Use themes, not detailed timelines
+
+**For Engineering:**
+- Provide context and rationale
+- Share user research insights
+- Discuss technical constraints openly
+- Be specific about acceptance criteria
+
+**For Sales/Customer Success:**
+- Highlight competitive differentiators
+- Provide realistic timelines
+- Include talk tracks for customers
+- Share what's NOT on the roadmap
+
+**For Customers:**
+- Focus on value they'll receive
+- Use their language, not internal jargon
+- Be conservative with dates
+- Explain the "why" behind decisions
+
+### Saying No Gracefully
+
+```markdown
+## Framework for Declining Requests
+
+1. **Acknowledge**: "I understand why [feature] is important to you."
+
+2. **Explain**: "Here's what we're prioritizing and why: [context]"
+
+3. **Offer Alternative**: 
+   - "Here's what we can do in the meantime..."
+   - "This is on our radar for [timeframe]..."
+   - "Have you tried [workaround]?"
+
+4. **Stay Open**: "Let's revisit this in [timeframe] or if [conditions change]."
+```
+
+---
+
+## Product Analytics
+
+### Metrics Framework
+
+```
+North Star Metric
+├── Input Metrics (leading indicators)
+│   ├── Activation rate
+│   ├── Feature adoption
+│   └── Engagement frequency
+└── Output Metrics (lagging indicators)
+    ├── Retention
+    ├── Revenue
+    └── NPS
+```
+
+### Key Metrics by Stage
+
+| Stage | Metric | Formula |
+|-------|--------|---------|
+| Acquisition | Sign-up rate | Sign-ups / Visitors |
+| Activation | Activation rate | Activated / Sign-ups |
+| Engagement | DAU/MAU | Daily active / Monthly active |
+| Retention | D7/D30 retention | Users returning on day 7/30 |
+| Revenue | ARPU | Revenue / Users |
+| Referral | Viral coefficient | Invites × Conversion rate |
+
+### Instrumentation Standards
+
+```javascript
+// Event naming convention: object_action
+analytics.track('feature_used', {
+  feature_name: 'search',
+  user_id: '123',
+  session_id: 'abc',
+  timestamp: '2025-01-28T12:00:00Z',
+  properties: {
+    query: 'product roadmap',
+    results_count: 15,
+    time_to_first_result_ms: 234
+  }
+});
+```
+
+### Dashboard Structure
+
+```
+Executive Dashboard
+├── North Star Metric (trend)
+├── Key OKR Progress
+├── Revenue Metrics
+└── Risk Indicators
+
+Product Dashboard
+├── Funnel Conversion
+├── Feature Adoption
+├── User Segmentation
+└── Experiment Results
+
+Operational Dashboard
+├── Error Rates
+├── Performance Metrics
+├── Support Ticket Trends
+└── Infrastructure Health
+```
+
+---
+
+## Definition of Done
+
+### Feature Launch Checklist
+
+- [ ] **Discovery Complete**
+  - [ ] Problem validated with customer interviews
+  - [ ] Opportunity scored and prioritized
+  - [ ] Assumptions tested
+
+- [ ] **Requirements Complete**
+  - [ ] PRD approved by stakeholders
+  - [ ] User stories written with acceptance criteria
+  - [ ] Edge cases documented
+
+- [ ] **Design Complete**
+  - [ ] UX research conducted
+  - [ ] Designs reviewed and approved
+  - [ ] Accessibility requirements met
+
+- [ ] **Development Complete**
+  - [ ] Code reviewed and merged
+  - [ ] Unit and integration tests passing
+  - [ ] Performance benchmarks met
+
+- [ ] **Quality Complete**
+  - [ ] QA test cases executed
+  - [ ] No P0/P1 bugs open
+  - [ ] Regression testing passed
+
+- [ ] **Launch Prepared**
+  - [ ] Analytics instrumented
+  - [ ] Feature flags configured
+  - [ ] Rollback plan documented
+  - [ ] Support team trained
+  - [ ] Release notes written
+
+- [ ] **Post-Launch Planned**
+  - [ ] Success metrics defined
+  - [ ] Monitoring dashboards ready
+  - [ ] Review meeting scheduled
+
+---
+
+## Common Pitfalls
+
+### 1. Building What Stakeholders Ask For
+
+❌ **Wrong**: Stakeholder says "build feature X" → build feature X
+
+✅ **Right**: Stakeholder says "build feature X" → understand the underlying problem → explore solutions → build the best solution
+
+### 2. Prioritizing by Loudest Voice
+
+❌ **Wrong**: Sales escalates → feature jumps to top of backlog
+
+✅ **Right**: All requests go through RICE scoring → data-driven prioritization
+
+### 3. Shipping Without Measuring
+
+❌ **Wrong**: Launch feature → move to next feature
+
+✅ **Right**: Launch feature → measure impact → iterate or deprecate based on data
+
+### 4. Writing PRDs in Isolation
+
+❌ **Wrong**: PM writes PRD → hands off to engineering
+
+✅ **Right**: PM collaborates with engineering and design from day one → PRD is a shared artifact
+
+### 5. Confusing Activity with Progress
+
+❌ **Wrong**: "We shipped 12 features this quarter!"
+
+✅ **Right**: "Our activation rate improved from 15% to 28% this quarter"
+
+### 6. Ignoring Technical Debt
+
+❌ **Wrong**: "We'll address tech debt later" (never happens)
+
+✅ **Right**: Allocate 20% of capacity to tech debt every sprint
+
+---
+
+## Resources
+
+- [Continuous Discovery Habits - Teresa Torres](https://www.producttalk.org/)
+- [Inspired - Marty Cagan](https://www.svpg.com/inspired-how-to-create-products-customers-love/)
+- [Measure What Matters - John Doerr](https://www.whatmatters.com/)
+- [The Mom Test - Rob Fitzpatrick](https://www.momtestbook.com/)
+- [Escaping the Build Trap - Melissa Perri](https://melissaperri.com/book)
+- [Shape Up - Basecamp](https://basecamp.com/shapeup)