Explore / Build the product

Starting Up

Build the product

Ship an MVP, work with builders, and iterate toward something people use.

What founders use for build the product, ranked by how many answers lean on it.

  1. A practical checklist drawn from many product leaders on the exact question of when a feature has earned its removal. It gives... Lenny's Newsletter Article · 10 min read When to sunset a feature Lenny Rachitsky
  2. A product team's honest account of the ongoing cost every shipped feature adds to engineering, design, support, and the next... HubSpot Product Blog Article · 7 min read On Killing It by Killing Features Daria Marmer
  3. This treats unshipping as a craft with real upside, not just cleanup, and shows how to use usage data to decide what goes. It... Mixpanel Article · 9 min read The art of removing features and products Neil Rahilly
  4. Written for solo and small-team founders, this makes the case that saying no and removing features is a survival advantage when... The Bootstrapped Founder Essay · 10 min read The Power of Omission: Killing Features for Fun and Profit Arvid Kahl
  5. The step-by-step operational side of your question: once you have decided to kill a feature, how do you actually retire it... Product Teacher Article · 9 min read How to Deprecate a Feature Clement Kao
  6. This gives you the simple two-axis map (how many people use a feature, and how often) that turns a gut feeling into a picture... Intercom Article · 6 min read Prioritising Features: Who'll Use It and How Often (the Feature Audit) Des Traynor
  7. A short, practical answer on how to actually decline feature requests and keep the product lean, including their line that you... Signal v. Noise Article · 5 min read Ask 37signals: How do you say no? Jason Fried
  8. Video · 10 min Build product. Talk to users. Michael Seibel
  9. A practical playbook for the part founders fear most: removing a feature while keeping the few users who relied on it on your... airfocus Article · 9 min read How to kill product features without losing customers Andrei Tiburca
  10. A practical piece on the exact failure mode where each big customer gets their own custom feature and the product fragments... The Startup (Kit Merker) Essay · 8 min read How to Avoid the Per-Customer Feature Trap Kit Merker
  11. A grounded take on the real risk sitting under your question: when one customer is half your revenue, losing them can halve the... SaaStr (Jason Lemkin) Article · 7 min read Customer Concentration is Definitely a Risk. But It's Probably OK. Jason Lemkin
  12. The practical companion piece: what to actually show and say when your largest account asks where their features sit on the... Aha! Article · 6 min read A Big Customer Wants to See Your Roadmap. Now What? Brian de Haaff
  13. Shows the healthy version of working closely with big customers: a deliberate design partner program where a handful of... First Round Review Article · 15 min read The Hard Way Pays Off: Inside Sierra's Design Partner Strategy First Round Review
  14. Practical scripts for turning down or deferring a request without blowing up the relationship, which is the skill you need when... Lenny's Newsletter (Lenny Rachitsky) Article · 10 min read On Saying No Lenny Rachitsky
  15. Deals with the specific pressure of a request that arrives wrapped in a deal, where sales and a big customer both want a yes... Saeed Khan (On Product Management) Article · 9 min read How to Deal with B2B Sales-Driven Feature Requests Saeed Khan
  16. Video · 50 min watch Building for the Enterprise Aaron Levie
  17. Goldfein ran engineering at Facebook and VMware and lays out how release process should change as a team grows from one person... First Round Review Article · 20 min read The Right Way to Ship Software Jocelyn Goldfein
  18. Holman was an early GitHub engineer and this is the single most complete plain English essay on what a healthy deploy looks... zachholman.com Essay · 30 min read How to Deploy Software Zach Holman
  19. Video · 35 min How GitHub Uses GitHub to Build GitHub Zach Holman
  20. Orosz maps the full spectrum from YOLO shipping (change it in prod and watch) to heavy multi stage verification, and explains... The Pragmatic Engineer Article · 25 min read Shipping to Production Gergely Orosz
  21. Majors argues that instead of piling on pre deploy gates, you invest in fast deploys, good observability, and quick rollback so... Honeycomb Blog Article · 12 min read I Test in Production Charity Majors
  22. Flags let you merge and deploy unfinished or risky work while keeping it switched off, so you avoid long lived branches and can... martinfowler.com Article · 30 min read Feature Toggles (aka Feature Flags) Pete Hodgson
  23. Once a second person is committing, the first real risk is two branches drifting apart, and this essay explains the one habit... martinfowler.com Article · 30 min read Continuous Integration Martin Fowler
  24. A focused reference on the simplest branching model that works for small teams: short lived branches off one trunk, merged... trunkbaseddevelopment.com Article · Reference site Trunk Based Development Paul Hammant

Show the next 24

The questions93 answers