Loading book details
Loading book details
Inspired cover

Inspired

Marty Cagan•2008

  1. Chappy's Book Notes•332 books

Inspired

Marty Cagan•2008

Length
8h 46m•~368 pages
Read
Sep 9th - 18th '23
ManagementInformation TechnologyProductivity
•

The summary and key takeaways below are auto-generated. I ran an AI pass based strictly on my handwritten notes for this book. I haven't done my own pass over them yet.

I read a book once and take handwritten notes as I go, then leave them alone. Weeks or months later I come back and write the key points and summary from those notes.

The delay is on purpose. Having to rebuild a book out of my own notes does far more for my recall than a second read-through would.

This one has only gotten as far as the AI pass. I'll come back and redo the takeaways and summary myself soon!

Summary

Great products come from empowered product teams solving problems, not feature factories shipping roadmaps. The right process: continuous discovery and delivery — tackle risks upfront with prototypes, design collaboratively, and validate with reference customers before building. Products must deliver on four dimensions: value, usability, feasibility, and business viability. Fall in love with the problem, not the solution. Think in outcomes, not output — OKRs should define what, not how.

Key Takeaways

  • Team = PM + designer + 2-12 engineers; high empowerment and accountability, flat structure
  • PM is like CEO but not boss — deep knowledge of customer, data, business, and market
  • Designers own wholistic UX and partner with everyone; engineers are partners, not mercenaries
  • You can't know value or cost in advance — business cases are theater; prototype and test instead
  • Types: feasibility prototype, live data prototype, wizard of oz, demand tests (landing pages)
  • Customer interviews to understand needs; pay attention to misbehavior to find real trends
  • Vision: 2-10 year objective; start with why, think big, don't fear disrupting yourself
  • Strategy: focus on one market/persona at a time; align with business and GTM strategy
  • Evangelize continuously — it's a leap of faith that needs constant reinforcement
  • Business objectives, not feature output; 1-3 OKRs refreshed 1-4 times per year
  • Define what, not how — give teams the problem and let them find the solution
  • Market prioritization by TAM, distribution channels, and time to market
  • 6 reference customers (all similar profile) = product-market fit
  • Reference customer = evangelist you can go deep with; demand validation through concierge tests
  • Work backwards from customer letter (Amazon-style) to frame risks and identify opportunities

Notes

1: Lessons from top tech companies

  • Ideas → product roadmap
  • Business case:
    • How much money, value created
    • How much money, time will it cost
  • ↑ shouldn’t do: can’t know
    • Can’t know in advance (AB testing)
    • Miss many of the benefits of agile
  • User stories → design → engineering → QA
  • Beyond lean and agile:
    • Risks tackled upfront, not at end
    • Products designed collaboratively
    • Solving problems, not just features
  • Key concepts:
    • Wholistic product
    • Continuous discovery, delivery
    • Prototypes: quick experiments
    • Product delivery: production quality
    • PMF:
    • Product vision: 2-10 year objective

2: The right people

  • Product teams
    • PM, designer, 2-12 engineers
    • High empowerment, accountability
    • Flat org structure
    • Scope: determine split strategy
    • Relationships, context, expertise
  • Product manager
    • Deep knowledge of:
      • The customer
      • The data
      • Your business: stakeholders
      • Your market, industry
    • Access to domain experts
    • Like CEO, but not boss of anyone
    • Know: CS, accounting / finance
  • Product designers
    • Product discovery
    • Wholistic UX design
    • Prototyping, user testing
    • Interaction, visual design
    • Partners with everyone
  • The engineers
  • Product marketing manager
    • Based on customer, not per-team
    • Market positioning
  • Supporting roles:
    • User researchers (qualitative)
    • Data analysts (quantitative)
    • Test automation engineers
  • Roles of leadership:
    • Lead PM: wholistic view of product
    • Lead of product design: UX
    • Lead of tech org: system / infra
  • Head of product:
    • Teacher, strategy, product culture
  • Head of technology:
  • Project / program / delivery manager
  • Find balance: central systems ↔︎ autonomy

3: The right product

  • Aspects of a product:
    • Value, usability, feasibility, business viability, time to money (iterations)
  • Outcome, not feature roadmaps
  • Product vision + strategy: lead + manage
  • Market prioritization:
    • Sizing: TAM
    • Distribution: GTM, sales channels
    • TTM: time to market
  • Principles of product vision:
    • Start with the why
    • Fall in love with problem, not solution
    • Think big, inspire
    • Don’t be afraid to disrupt yourself
    • Determine, embrace meaningful trends
    • Aim for future, not present
    • Stubborn on vision, flexible on details
    • Realize it’s a leap of faith
    • Evangelize continuously, relentlessly
  • Principles of product strategy:
    • Focus on 1 market / persona at a time
    • Aligned with business strategy
    • Aligned with sales, GTM strategy
    • Obsess: customers, not competitors
    • Communicate strategy across org
  • OKR: objective and key results
    • What, not how; objective
  • OKR technique:
    • Business objectives, not output
    • 1-3 OKRs, 1-4 times per year

4: The right process

  • Transformation techniques: new objective
    • Framing, risk identification: customer letter, opportunity assessment
  • Opportunity assessment:
    • Objective, key results
    • Customer problem
    • Target market
  • Customer letter: work backwards
    • Focus on user impact
  • Startup canvas: identify biggest risks
  • Reference customer: evangelist
    • Relationship: ppl you can go deep with
    • Demand validation ↓
    • 6 RCs (all similar) = PMF
  • Customer interviews: understand needs
  • Concierge test: understand how they use
  • Pay attention to misbehavior: find trends
  • Feasibility prototype: before committing
  • Use → live data prototype
  • Wizard of oz prototype
  • Concrete prototype user study advice
  • Demand tests: secret door, landing page
  • Discovery, optimization A/B testing

5: The right culture

  • Customer centric culture
  • Compelling product vision
  • Focused product strategy
  • Strong PMs
  • Corporate courage
  • Time to innovate