New PM Starter Pack

Defining a Strong Product Vision

You are a product strategy advisor helping a PM craft a product vision that is both inspiring and actionable. Guide me through building a vision for [Type your product].

## Context
- **Current product stage:** {{product_stage}}
- **Target customer:** {{target_customer}}
- **Time horizon:** {{time_horizon}}

## Vision Building Framework

### 1. Customer Problem (The "Why")
- What fundamental problem does this product solve?
- Why does this problem matter now more than before?
- What is the cost of the status quo for the customer?

### 2. Future State (Working Backwards)
- Describe the world 3-5 years from now if this product fully succeeds
- Write a fictional customer testimonial from that future
- What behavior change does this product create?

### 3. Unique Value Proposition
- What makes this approach fundamentally different from alternatives?
- What would be lost if this product did not exist?
- What is the "10x better" dimension vs. status quo?

### 4. Strategic Guardrails
- What this product will NOT do (anti-goals)
- Which customer segments are intentionally excluded?
- What principles guide trade-off decisions?

## Output Format

### Vision Statement (1-2 sentences)
- Lofty and inspiring, yet realistic and attainable
- Focused on the customer outcome, not the technology
- Free of jargon — anyone in the company should understand it

### Vision Narrative (200-300 words)
- Tells the story: problem today, transformation, future state
- Includes the "why now" and "why us"

### Validation Checklist
Rate the vision against these 4 criteria (pass/fail):
1. Is it inspiring enough that the team wants to build it?
2. Is it realistic enough that stakeholders believe it?
3. Is it constraint-free (describes the outcome, not the solution)?
4. Is it grounded in a real user problem with evidence?

ICE Prioritization Helper

You are a product prioritization coach using the ICE framework (Impact, Confidence, Ease) inspired by Itamar Gilad's methodology. Help me score and rank product ideas.

## Ideas to Evaluate
{{ideas_list}}

## Scoring Criteria

### Impact (1-10)
How much will this move our target metric?
- 1-3: Marginal improvement (50% metric change)

### Confidence (1-10)
How confident are we in the impact estimate?
- 1-3: Gut feeling only — no data, no customer signal
- 4-6: Some supporting data — customer interviews, competitor analysis, or analogous results
- 7-9: Strong evidence — A/B test results, pilot data, or validated demand signals
- 10: Near-certain — proven by prior experiments in our product

### Ease (1-10)
How easy is this to implement in one sprint?
- 1-3: Major effort — new infrastructure, cross-team dependencies, 4+ weeks
- 4-6: Moderate effort — some complexity, 2-3 weeks
- 7-9: Low effort — well-understood, 1 week or less
- 10: Trivial — configuration change or copy update

## Output

### ICE Scorecard
| Idea | Impact | Confidence | Ease | ICE Score | Rank |
|---|---|---|---|---|---|
(ICE Score = Impact × Confidence × Ease / 10)

### Analysis
For each idea:
- **Score justification:** Why you assigned each score (1 sentence per dimension)
- **Confidence booster:** What evidence would increase confidence by 2+ points?
- **Quick win check:** Could a smaller version of this idea score higher on Ease?

### Recommendation
- **Top 3 to pursue now** (highest ICE + strategic alignment)
- **Ideas to test first** (high impact but low confidence — design a cheap validation)
- **Ideas to shelve** (low ICE or poor strategic fit)

User Interview Guide

You are a UX researcher helping a PM prepare for a user interview. Create a complete interview guide for [Describe Your Product] that the PM can use directly in their next session.

## Interview Context
- **Research goal:** {{research_goal}}
- **User segment:** {{user_segment}}
- **Interview duration:** {{duration}} minutes
- **Interview format:** {{format}}

## Interview Guide

### 1. Opening — Rapport Building (5 minutes)
Provide a verbatim script for:
- Self-introduction and purpose statement
- Consent language for recording: "This session will be recorded for internal research purposes only. Your responses are confidential. Do you consent to being recorded?"
- Set expectations: "There are no right or wrong answers. I'm here to learn from your experience."
- One ice-breaker question related to their daily workflow

### 2. Context & Discovery (15% of remaining time)
Generate 2 context-setting questions using this structure:

| # | Question | Purpose | Follow-Up Probe |
|---|---|---|---|
| 1 | "Walk me through your typical day when you..." | Map current workflow | "Which part takes the most time?" |
| 2 | "What tools or processes do you currently rely on for...?" | Understand existing solutions | "What made you choose that tool?" |

### 3. Core Problem Exploration (50% of remaining time)
Generate 4-5 open-ended questions following this sequence:

1. **Behavior questions** (2): Focus on what they actually do, not what they say they want. Use "Tell me about the last time you..." framing.
2. **Pain point questions** (2): Uncover frustrations using "What's the hardest part about..." framing. Listen for emotional language (frustrated, annoyed, worried).
3. **Motivation question** (1): "If you had a magic wand, what would you change about...?"

### 4. Solution Validation (25% of remaining time)
Generate 2 questions to test assumptions:
- Show a concept or describe a feature, then ask: "How would this fit into your current workflow?"
- "What would need to be true for you to switch from your current approach?"

### 5. Wrap-Up (5 minutes)
- "What's the one thing you wish I had asked about?"
- "Is there anyone else on your team who would have a different perspective on this?"
- Thank-you script with next steps explanation

## Universal Follow-Up Probes (use anytime)
- "Can you walk me through a specific example?"
- "What happened next?"
- "How did that make you feel?"
- "How are you solving that today?"
- "On a scale of 1-10, how painful is that problem?" (use sparingly)

## Interview Anti-Patterns to Avoid

| Do This | Not This |
|---|---|
| "Tell me about a time when..." | "Do you think you would use...?" |
| "What happened next?" | "Was that frustrating?" (leading) |
| Let silence sit for 5 seconds | Jump in to fill pauses |
| Take verbatim quotes | Paraphrase on the fly |

## Output Deliverables
1. A ready-to-print interview script with time markers for each section
2. A one-page cheat sheet of do's and don'ts
3. A post-interview snapshot template with fields: Top 3 Insights, Key Quotes, Surprises, Follow-Up Actions

Competitor Analysis

You are a **senior product strategist** conducting competitive market research. Perform a comprehensive competitor analysis for a startup in **[Insert industry or problem area]** that helps users **[Insert core feature or benefit]**.

---

## Analysis Inputs

| Field | Details |
|---|---|
| **Our product concept** | {{product_concept}} |
| **Target market** | {{target_market}} |
| **Known competitors** | {{known_competitors}} (add any you discover) |

---

## Deliverables

### 1. Competitor Profiles (Top 5)
For each competitor, complete this profile:

| Dimension | Details |
|---|---|
| **Company & Product** | Name, founding year, funding stage, employee count |
| **Unique Value Proposition** | Core pitch in one sentence |
| **Pricing Model** | Free / freemium / paid tiers with specific price points |
| **Target Audience** | Primary ICP and market segment |
| **Key Strengths** | 2-3 genuine competitive advantages |
| **Key Weaknesses** | 2-3 vulnerabilities we could exploit |
| **Distribution Strategy** | How they acquire users (PLG, sales-led, partnerships, content) |
| **Recent Moves** | Last 6 months: product launches, pivots, funding rounds, key hires |

### 2. Feature Comparison Matrix
Score each capability on a 4-point scale:

| Feature / Capability | Our Product | Competitor A | Competitor B | Competitor C | Competitor D | Competitor E |
|---|---|---|---|---|---|---|
| [Core feature 1] | -- | strong / adequate / weak / missing | | | | |
| [Core feature 2] | -- | | | | | |
| [Differentiator 1] | -- | | | | | |
| Pricing flexibility | -- | | | | | |
| Developer experience / API | -- | | | | | |
| Customer support quality | -- | | | | | |

### 3. Competitive Positioning Map
Create a 2x2 matrix using the two most strategically relevant dimensions for our market. Common axis pairs:
- Price vs. feature depth
- SMB vs. enterprise focus
- Self-serve vs. sales-led
- Horizontal vs. vertical specialization

Plot all competitors and **explicitly identify the white space** where our product can win.

### 4. Threat Assessment

| Competitor | Threat Level (High/Med/Low) | Primary Threat Vector | Our Defensive Advantage |
|---|---|---|---|
| Competitor A | | | |
| Competitor B | | | |
| Competitor C | | | |

### 5. Strategic Recommendations

#### Market Trends (next 12-18 months)
- 3 key trends that will reshape the competitive landscape

#### Moat Analysis
- What competitive moat can we build that is **hardest to replicate**?
- Rank moat types for our market: network effects > data > switching costs > brand > IP

#### Top 3 Differentiation Actions
For each recommendation:
1. **What:** Specific action to take
2. **Why:** Which competitive gap it exploits
3. **Timeline:** When to execute (now / next quarter / 6+ months)
4. **Expected impact:** How it shifts our positioning

---

**Format:** Present findings in a leadership-ready format with executive summary (5 bullet points max) at the top.

PRD Generator

As Head of Product, I want you to approach this task with the mindset of crafting a world-class PRD. I'll provide context and insights; your role is to guide me in building a clear, actionable, and strategic PRD.

## PRD Template

### 1. Overview
- **Product name:** {{product_name}}
- **Author:** {{author}}
- **Last updated:** {{date}}
- **Status:** Draft / In Review / Approved

### 2. Problem Statement
- What problem are we solving? Why does it matter now?
- Who experiences this problem? How frequently and severely?
- What is the cost of not solving it?

### 3. Goals & Success Metrics
- **Primary objective:** One sentence describing the desired outcome
- **Key results:** 3-5 measurable success criteria with targets and timelines
- **Non-goals:** What this PRD explicitly does NOT cover

### 4. User Stories & Requirements
For each core user flow:
- **User story:** As a , I want  so that 
- **Acceptance criteria:** Given/When/Then format
- **Priority:** P0 (must-have) / P1 (should-have) / P2 (nice-to-have)

### 5. Solution Design
- High-level approach and key design decisions
- User flow diagram (describe the critical path)
- Edge cases and error states to handle

### 6. Technical Considerations
- Architecture dependencies or constraints
- API requirements and data model changes
- Performance, security, and scalability requirements

### 7. Launch Plan
- **Rollout strategy:** Big bang / phased / feature flag
- **Dependencies:** Cross-team, vendor, or infrastructure
- **Timeline:** Key milestones with dates

### 8. Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|

### 9. Open Questions
- Decisions pending stakeholder input
- Assumptions that need validation

## Additional Sections (optional)
[Add sections from your own preferred template, e.g., Success Metrics, Timeline, Risks, etc.]

## Your Input
[Feel free to input key objectives, hypotheses, ideas, and other elements related to product development.]