Article

Product vs Feature Teams

Marty Cagan · Silicon Valley Product Group (SVPG) Free Intermediate

Cagan draws the line between teams measured by output (features shipped) and teams measured by outcomes (problems solved). If you keep defaulting to the exciting build, this explains the mindset shift that stops it. It reinforces judging bugs, promises, and new work by the result they produce rather than how exciting they feel to build.

  • Measure the team by outcomes solved, not features shipped
  • A roadmap of features handed down breeds the wrong incentives
  • Being empowered to solve the problem beats being told what to build

The question it answers

  1. What is a sane way to prioritise between fixing bugs, paying customer promises, and building the exciting new thing?

Read with it

  1. The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past... momtestbook.com Book · ~130 pages The Mom Test Rob Fitzpatrick
  2. The essay that put 'product-market fit' into the startup vocabulary. Read it for the gut-level description of what PMF feels... pmarchive.com Essay · ~15 min read The Only Thing That Matters Marc Andreessen
  3. The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few... paulgraham.com Essay · ~15 min read Do Things That Don't Scale Paul Graham
  4. Video · ~13 min How to Plan an MVP Michael Seibel (YC)
  5. The original, primary source where the RICE framework was introduced, cite this, not the SEO reposts. The clearest way to... Intercom Blog Article · ~12 min read RICE: Simple Prioritization for Product Managers Sean McBride
  6. Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary... Basecamp / 37signals Book · free online book Shape Up: Stop Running in Circles and Ship Work that Matters Ryan Singer
eChai Partner Brands The partnership →