Each week I scour articles, wading through the dogs, and bringing you the best insights to help product managers and innovators be heroes.

Questions product managers should expect when interviewing for a job.

Of course, there is the classic question, “What product are you most proud of launching and what did you learn from it?” Depending on the primary responsibilities of the position (such as platform management, community management, growth management, etc.) this article tells you the questions you can expect… https://hackernoon.com/interview-questions-for-the-6-types-of-product-managers-586f09a17fff

The difference between a user story and a requirement is the user’s perspective.

User stories have become the accepted form of communicating product feature requests to development/engineering. What happened to requirements? They are still around but the classic version of a requirement doesn’t provide sufficient context to explain why the feature is important to a user. It’s a problem I recognized when I first started writing requirements years ago before user stories existed and quickly “enhanced” them to provide the user context. Regardless of what you call them, that context is important. Read another perspective at https://blog.aha.io/user-stories-vs-product-requirements/

Innovation only exists if there is also distribution.

While numerous definitions of product innovation exist, they all contain the aspect of creating value for a customer or end user. Fundamentally, this means there is a way to reach the customer to tell them about the innovation and a distribution means of getting them the innovation. This aspect sometimes get’s lost. Product managers may get caught up in the importance of the innovation without considering reach and distribution. This is discussed further for consumer packaged goods… https://www.pymnts.com/news/retail/2018/general-mills-kroger-acquiring-boxed-competing-amazon-online-grocery-sales/