Product Strategy Means Saying No
If you’re building a product, you have to be great at saying No. Not ‘maybe’ or ‘later’. The only word is No. Building a great product isn’t about creating tonnes of tactically useful features which are tangentially related. It’s about delivering a cohesive product with well defined parameters. As Apple’s latest advert points out, there are literally tens of thousands of permutations of your product based on every addition, both minor and major. So many reasons to say yes When your product gets traction, you’ll find yourself inundated with good ideas for features. But The Data Looks Good “We’ve tried this feature with a small group and engagement is off the charts.” But It’ll Only Take A Few Minutes The main problem with this argument is that the scope of work should never be a reason to include a feature in a product. Lots of bad ideas can be built quickly. But this customer is about to quit This is feature blackmail. But we can just make it optional This leads to death by preferences.
Related: UX Strategy
• Elements de réflexion
• Product management
• Product Manager Readings