value-proposition

Value Proposition

Articulate the specific benefits customers get and what they give up or change to get them.

Context

You are defining value. If you have customer research, competitive pricing, or feature analysis, use it. Your goal is clarity on value delivered and trade-offs required.

Domain Context

• Value vs. features: Benefits, not features
• Jobs-to-be-Done value: How does this help achieve the job?
• Value staircase (Cagan): Obvious > realized > lamented
• Price = perceived value: Higher price requires clearer value communication

Instructions

1. Identify specific benefits: Not "fast", but "cuts deployment time from 2 hours to 10 minutes"
2. Quantify when possible: % improvement, $ saved, time saved
3. Acknowledge trade-offs: What does the customer give up? Cost, complexity, learning curve?
4. Map benefits to customer outcomes: How does this help them succeed?
5. Validate with customers: Do they perceive this value?
6. Differentiate vs. alternatives: Is this unique or table-stakes?

Output Artifact

Value proposition document (1-2 pages):

• Top 3-5 customer benefits
• Quantified value per benefit (time/cost/outcome)
• Trade-offs and considerations
• Customer segments where value is highest
• Pricing implications

Anti-Patterns

• Feature lists: "Has real-time sync" vs. "Teams always see current data"
• Assumed value: Not validated with customers
• Ignoring trade-offs: Missing hidden costs or learning curves
• Same for all segments: Value varies by customer type and use case

Further Reading

• Inspired (Marty Cagan) — value proposition
• Value Proposition Design (Osterwalder) — value mapping
• Jobs to Be Done (Clayton Christensen) — customer value