Product management, new ideas - often ignored corner cases
Many of you would have read books or articles on product management (PM). A consistent message in PM literature is that products are built to solve customers problems. The product roadmap, prioritisation, etc. should be aligned with customer needs. It's important to speak to customers regularly and be in-synch with their problems/pain areas. Following these basic tenets would help the PM and tech teams build products that customers want to use/buy. The above message seems logical and pragmatic. But is there more to this? Have PM books/ articles missed a few corner cases? A few cases that come to mind are: Do customers always know the problems they are facing? Do they care about their problems? If the customer problem involves several external and internal entities, where does one start? Isn't the MVP going to be difficult? Does one only take up new or unsolved problems? How do PM teams of mature products(like Windows 10, Gmail) spend their time? Lets go over these cases and ...