Product Strategy
Design's Role in Strategy
At senior levels, designers don't just execute strategy—they help define it. Strategic designers understand business models, competitive dynamics, and market trends, using design thinking to shape company direction.
Strategic vs Tactical Design
| Tactical | Strategic |
|---|---|
| Improve checkout flow | Define e-commerce vision for next 3 years |
| Design new feature | Identify new market opportunities |
| Optimize existing product | Decide which products to build |
| Quarterly roadmap | Multi-year product vision |
Product Vision
Components of Product Vision
- Target User: Who are we serving?
- User Need: What problem are we solving?
- Product Approach: How are we solving it?
- Differentiation: Why us vs competitors?
- Success Metrics: How do we measure success?
Example: Slack's Vision
2013 Vision Statement: "Make work life simpler, more pleasant, and more productive"
Target User: Knowledge workers in teams
User Need: Email is overwhelming, context gets lost, hard to find information
Product Approach: Organized channels, searchable history, integrations
Differentiation: Delightful UX, not enterprise software feel
Success Metric: Messages sent per team (engagement)
Result: Clear vision guided all product decisions, $27B acquisition
Creating Compelling Vision
- Aspirational: Inspiring future state
- Concrete: Specific enough to guide decisions
- User-Centered: Focused on user value, not features
- Differentiated: Unique point of view
- Achievable: Ambitious but realistic
Market Analysis
Competitive Analysis Framework
- Direct Competitors: Same solution, same market
- Indirect Competitors: Different solution, same need
- Potential Competitors: Could enter market
- Substitutes: Alternative ways users solve problem
Example: Figma's Competitive Strategy
2016 Market: Sketch dominated design tools
Sketch Strengths: Native Mac app, fast, plugin ecosystem
Sketch Weaknesses: Mac-only, no collaboration, file-based
Figma's Differentiation:
- Web-based: Works on any platform
- Real-time Collaboration: Multiple designers in same file
- Version Control: Built-in, not file chaos
- Developer Handoff: Inspect mode, code export
Result: Went from 0 to industry standard in 5 years, $20B acquisition by Adobe
SWOT Analysis
- Strengths: What do we do better than anyone?
- Weaknesses: Where do we fall short?
- Opportunities: Market trends we can capitalize on
- Threats: External risks to our business
Product-Market Fit
Signs of Product-Market Fit
- Organic growth through word-of-mouth
- High retention (users keep coming back)
- Users would be "very disappointed" if product disappeared
- Press and investors seeking you out
- Struggling to keep up with demand
Example: Superhuman's Path to PMF
Approach: Measured PMF before scaling
Survey Question: "How would you feel if you could no longer use Superhuman?"
- Very disappointed
- Somewhat disappointed
- Not disappointed
PMF Benchmark: 40%+ say "very disappointed"
Initial Result: 22% (not PMF yet)
Action: Interviewed users, identified gaps, improved product
6 Months Later: 58% (strong PMF)
Then: Scaled marketing and sales
Lesson: Don't scale before achieving PMF
Roadmap Planning
Roadmap Horizons
- Now (0-3 months): Committed features, in development
- Next (3-6 months): Validated ideas, high confidence
- Later (6-12 months): Exploration, lower confidence
- Future (12+ months): Vision, themes, not specific features
Example: Spotify's Bet Framework
Portfolio Approach: Balance different types of bets
- Core (70%): Improve existing features, incremental gains
- Adjacent (20%): Expand to related areas
- Transformational (10%): Moonshots, high risk/reward
Example Bets:
- Core: Improve recommendation algorithm
- Adjacent: Podcasts (adjacent to music)
- Transformational: Spotify Car Thing (hardware)
Result: Balanced innovation with stability
Prioritization Frameworks
- RICE: Reach × Impact × Confidence / Effort
- Value vs Effort: 2×2 matrix, prioritize high value/low effort
- Kano Model: Basic, performance, delighters
- MoSCoW: Must have, Should have, Could have, Won't have
Business Models
Common Business Models
- Subscription: Netflix, Spotify (recurring revenue)
- Freemium: Dropbox, Slack (free tier + paid upgrades)
- Marketplace: Airbnb, Uber (take rate on transactions)
- Advertising: Facebook, Google (attention economy)
- E-commerce: Amazon (sell products)
- Enterprise: Salesforce (B2B sales)
Example: Dropbox's Freemium Strategy
Free Tier: 2GB storage
Purpose: Viral growth, network effects
Conversion Triggers:
- Run out of space
- Need advanced features (file recovery, sharing controls)
- Team collaboration
Design Implications:
- Make free tier valuable enough to spread
- Create natural upgrade moments
- Don't annoy free users with constant upsells
Result: 700M users, 46% convert to paid over time
Unit Economics
- CAC (Customer Acquisition Cost): Cost to acquire one customer
- LTV (Lifetime Value): Revenue from one customer over lifetime
- Healthy Ratio: LTV should be 3x CAC
Example: If CAC is $100, LTV should be $300+ for sustainable business
Platform Strategy
Example: Shopify's Platform Evolution
Phase 1 (2006): E-commerce store builder
Phase 2 (2009): App store—third-party developers extend functionality
Phase 3 (2013): Payments, shipping, fulfillment—full commerce platform
Phase 4 (2020): Shop app—consumer-facing, aggregates all Shopify stores
Strategy: Each phase built on previous, created network effects
Result: $200B market cap, powers millions of businesses
Network Effects
What: Product becomes more valuable as more people use it
Types:
- Direct: More users = more value (phone network)
- Indirect: More users = more complementary products (iOS apps)
- Two-Sided: More buyers attract sellers and vice versa (eBay)
Example: Facebook—more friends join → more valuable → more people join
Go-to-Market Strategy
Distribution Channels
- Viral: Users invite others (Dropbox referrals)
- Content: SEO, blog, educational content (HubSpot)
- Paid: Ads, SEM (most startups)
- Sales: Enterprise sales team (Salesforce)
- Partnerships: Integrate with existing platforms (Zapier)
- Community: Build engaged community (Notion)
Example: Zoom's Product-Led Growth
Strategy: Free product so good it sells itself
Tactics:
- Free Tier: 40-minute meetings, unlimited 1:1s
- No Download for Guests: Join from browser
- Superior Quality: Better video/audio than competitors
- Viral Loop: Every meeting is a demo to participants
- Bottom-Up: Individual users adopt, then buy for team
Result: Grew from 10M to 300M users in 3 months (COVID), minimal marketing spend
Strategic Frameworks
Jobs to Be Done (JTBD)
Concept: People don't buy products, they hire them to do a job
Example: "I need to make a milkshake" → actual job: "I need something to keep me occupied during my boring commute"
Implication: Competitors aren't other milkshakes, but bananas, bagels, podcasts
Example: Intercom's JTBD Analysis
Product: Customer messaging platform
Jobs Customers Hire It For:
- "Help me onboard new users"
- "Help me support customers efficiently"
- "Help me engage inactive users"
- "Help me announce new features"
Product Strategy: Built separate products for each job (Messages, Support, Product Tours)
Result: Clearer positioning, better product-market fit per segment
Blue Ocean Strategy
Red Ocean: Compete in existing market (bloody competition)
Blue Ocean: Create new market space (uncontested)
Example: Cirque du Soleil—not competing with other circuses, created new category (artistic circus for adults)
Strategic Design Sprints
Example: Google Ventures Design Sprint
Purpose: Answer critical business questions through design and testing
5-Day Process:
- Monday: Map the problem, choose target
- Tuesday: Sketch competing solutions
- Wednesday: Decide on best solution
- Thursday: Build realistic prototype
- Friday: Test with real users
Use Cases:
- Validate new product idea before building
- Solve major product challenge
- Explore new market opportunity
Result: Validate or invalidate strategy in 1 week vs months
Measuring Strategic Success
OKRs (Objectives and Key Results)
Objective: Qualitative goal (what you want to achieve)
Key Results: Quantitative metrics (how you measure success)
Example:
- Objective: Become the leading design tool for teams
- KR1: Increase team accounts from 10K to 50K
- KR2: Achieve 90% weekly active usage for team accounts
- KR3: NPS score of 50+ among team users
Example: LinkedIn's North Star Metric Evolution
Early Days: Total members (vanity metric)
Problem: Many inactive accounts, not driving value
New North Star: Monthly active users (MAU)
Problem: Didn't capture depth of engagement
Current North Star: Weekly active users creating economic opportunity
Why: Aligns with mission (connect professionals), measures real value
Result: Strategy focused on helping people get jobs, make connections that matter
Strategic Communication
Strategy Artifacts
- Vision Document: 3-5 year product vision
- Strategy Deck: Market analysis, competitive positioning
- Roadmap: Visual timeline of initiatives
- Principles: Decision-making framework
- Case Studies: Examples of strategy in action
Presenting Strategy to Executives
- Start with Why: Business problem and opportunity
- Show the Data: Market research, user insights, metrics
- Competitive Context: Where we stand vs others
- Clear Recommendation: Specific path forward
- Expected Impact: Revenue, growth, retention projections
- Resource Ask: What you need to execute
📅 Evolution of Product Strategy
Pre-2000: Business-Driven Strategy
Example: Microsoft Windows strategy
- Strategy set by business/sales teams
- Design had no strategic input
- Focus on features and market share
- Long-term planning (3-5 year roadmaps)
- Competitive analysis drove decisions
Pre-2023: Design-Informed Strategy
Example: Airbnb, Uber product strategy
- Design participates in strategy
- User research informs roadmap
- Design thinking workshops
- OKRs and quarterly planning
- Data + design insights combined
2023+: Design-Led Strategy
Example: Apple, Figma, Linear
- Design drives company strategy
- AI-powered market analysis
- Continuous strategy iteration
- Design vision shapes business model
- CDOs in board meetings
Fun Fact
Steve Jobs' famous "1000 songs in your pocket" iPod strategy came from design thinking, not market research! In 2001, MP3 players existed but were clunky. Instead of asking users what they wanted, Jobs envisioned the experience: carrying your entire music library everywhere. The strategy wasn't "build a better MP3 player"—it was "revolutionize how people experience music." This design-led vision created a $150B+ business (iPod + iTunes + iPhone music)!
⚠️ When Theory Meets Reality: The Contradiction
Theory Says: Product strategy should be based on market research and competitive analysis
Reality: Dyson ignored market research and spent 15 years perfecting a product nobody asked for.
Example: Dyson's Bagless Vacuum Strategy
- Market research said people wanted cheaper vacuums
- James Dyson believed in superior design instead
- Spent 15 years and made 5,127 prototypes
- Launched at 2x the price of competitors
- Result: $6B company, market leader in premium vacuums
Lesson: Sometimes vision beats data. Market research tells you what exists, not what's possible. Great strategy often means ignoring conventional wisdom and betting on a better future. But you need conviction and patience.
📚 Resources & Further Reading
Books
- Osterwalder, Alexander, and Yves Pigneur. Business Model Generation. Wiley, 2010.
- Cagan, Marty. Inspired: How to Create Tech Products Customers Love. 2nd ed., Wiley, 2017.
- Ries, Eric. The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business, 2011.
- Thiel, Peter. Zero to One: Notes on Startups, or How to Build the Future. Crown Business, 2014.
Articles & Papers
- Harvard Business Review. "What Is Strategy?" by Michael Porter. https://hbr.org/1996/11/what-is-strategy
- Gibson Biddle. "Product Strategy Framework." https://gibsonbiddle.medium.com/
Frameworks
- Jobs-to-be-Done Framework
- Blue Ocean Strategy
- Lean Canvas