How do you build something people actually want and will use time and time again? Sharing lessons we've learned in the six-plus years building Intercom, in this series you'll learn how to evaluate your current product, how to decide which features to build in a haystack of those you shouldn't, best practices for getting those features used, and much more.
Chapter 9: Get comfortable killing a feature
Feature creep comes at a high cost, which is why you must get comfortable killing a feature.
Chapter 8: How to increase user engagement
There is no consistent quantifiable definition of engagement across different products, but if you make user engagement a priority there are loads of quick wins to be had.
Chapter 7: Why do new features flop?
New features are just code that’s gathering virtual dust, unless they're being used by your customers. To keep your next launch from flopping, ask yourself these 5 key questions before you ship.
Chapter 6: How to fight physics envy
We’d all love it if the ROI for a feature was always perfectly proportional to the time we spent on it. That's not the case – but in software it can be an advantage. Plus, a 5-step process for rolling out new features.
Chapter 5: Which new features should you actually build?
What things should you actually add to your product roadmap? We've got an acid test of 10 'Yes or No' questions, and any feature must score straight yes's if it's going to get built.
Chapter 4: Making things people want
The problems people encounter in their lives rarely change from generation to generation, but the products they hire to solve these problems change all the time. Why a strong understanding of the outcome customers want, and how they currently get it, is essential to succeed in product management.