The Art of Saying “NO”
Chandra Kalle
28510

The hard thing as a PM is where to draw the line of something being needed or not. In idealistic world we all want to build just features that are used by most of the users. But is that most 90%? 51%? What if a core feature is needed by just 10 or 25%?

The same goes for the kill line. Do you remove something if it’s used by less than 50% of users? Or is it 10% or 1%?

Values and priorities are nice, but even with those well listed the questions above stay.

Intercom might talk about saying no, but it has grown from a simple single-feature product to an OS where most people use just a small part of it. Preach or practice?