Article · 7 min read

On Killing It by Killing Features

Daria Marmer · HubSpot Product Blog Free Intermediate

A product team's honest account of the ongoing cost every shipped feature adds to engineering, design, support, and the next decision you make. It reframes a dead feature as a tax on all future work, which is the exact point of our short answer. Good for convincing yourself, or a co-founder, that removal is progress.

  • Every feature carries permanent maintenance and support cost
  • A rarely used feature can eat a large share of your team's time
  • Removing the right things speeds up everything you do next

The question it answers

  1. When is it right to stop iterating on a feature and just kill it?

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. Video · ~13 min How to Plan an MVP Michael Seibel (YC)
  3. A punchy, contrarian classic on building a lean, sane, profitable company from the founders of Basecamp. It's the antidote to... 37signals Book · ~288 pages Rework Jason Fried & David Heinemeier Hansson
  4. Des Traynor makes the case that "no" is the product strategy, and that adding a feature for one loud customer quietly costs... Intercom (Des Traynor) Article · ~8 min read Product Strategy Means Saying No Des Traynor
  5. Doshi names the IKEA effect, how you overvalue what you built simply because you built it, which is the quiet engine behind... Shreyas Doshi (Substack) Essay · 12 min read The Product Builder's True Journey Shreyas Doshi
  6. Zerodha built its products in-house rather than leaning on outside vendors, and Kamath explains how staying close to the build... Inc42 Article · 12 min read Zerodha's Nithin Kamath On The Art Of Building World Class Products Nithin Kamath
eChai Partner Brands The partnership →