Everything from

Silicon Valley Product Group (Marty Cagan)

2 resources from Silicon Valley Product Group (Marty Cagan) we point founders to, and the questions each answers.

📄 Article
✓ Link checked Free Intermediate

Why we picked it This companion piece warns about the opposite failure: cutting so hard that the thing is minimal but not actually viable or usable. It helps you find the floor, the point below which the product stops being worth using. Read it alongside your cut list to check you have not gone too far.

Viable Product vs. Minimal Product

From Silicon Valley Product Group (Marty Cagan) by Marty Cagan ~6 min read

  • Minimal is not enough on its own; the product still has to be usable and worth choosing.
  • Find the floor where cutting more would break the core value.
  • Viability, not just smallness, is the real target for v1.
Open svpg.com →
Answers How do I decide which features to cut from v1?
✍️ Essay
✓ Link checked Free Advanced

Why we picked it Cagan argues your job is to deliver outcomes, not to maintain a prioritized list of everyone's requests. That is the backbone of anchoring a no to the outcome you are chasing rather than to who shouted loudest. Read it to stop treating your roadmap as a request queue.

Product Roadmaps

From Silicon Valley Product Group (Marty Cagan) by Marty Cagan 10 min read

  • Commit to problems and outcomes, not a fixed list of features
  • A request spreadsheet quietly pushes in things users do not actually need
  • Frame the roadmap around the outcome so a no has a reason behind it
Open svpg.com →
Answers How do I say no to feature requests without losing customers? Every user interview gives me a different feature request. How do I turn messy feedback into a real prioritisation decision? How do I set a roadmap when half my revenue comes from one big customer who keeps asking for custom features? Should I share a public roadmap with my early users, or does that just create pressure and expectations I cannot meet?
eChai Partner Brands