Professional preference is something else entirely. It often feels like whatever decision you make, it would be wrong for one reason or another. Why? Because everyone on the team cares a lot about what the Product Manager is doing with their precious product. This is what feeds them every day and ensures their prosperous future.
In product management, there's a certain pressure from clever guys who write books and everybody else who read them, that a product team should:
- A/B test everything
- Be bug-free
- Build fast
- Provide a quick and smooth user experience
- Encourage a user to generate rich content
- Keep a user as much time as possible in the product
- Provide value asap
- Retain a user to the product every day
- Make only data-driven decisions
- Monetize value aggressively
- Implement freemium
Every point of the list is valid, no doubt. It's logical and proven to work. But it often contradicts other points. And unlike daily life, if you don't meet some of these points you feel like you are doing a bad job.
The truth is that no one knows what is right and what is wrong, but doing things that are logical, recommended, and tested makes you feel safe, which justifies our desire to comply with the above list. Unlike our personal lives, wrong steps in product development can have much more important consequences: we can lose money, customers, reputation, team trust, etc. We are afraid of making a mistake and afraid of being blamed if we fail (even if our manager is amazing and will never blame us).
But trying to use all the best practices and expert advice is unhealthy because it leads to conflicts that you cannot resolve. It is right to create an awesome product and it's right to make decisions based on data, but in some situations, these points contradict each other. It's the same as "build fast" and "bug-free" or "monetize aggressively" and "implement freemium".