Product managers with technical backgrounds have steadily increased over the years. Are heavy product manager technical skills good or bad for the product management profession?
It begs a lot of questions in which a yes or a no answer is entirely appropriate. Here are a few that come to mind. The Playbook:
Business requirements and value propositions are one and the same. What’s different is the purpose for which they’re written.
- Business requirements are written to communicate the WHO, WHAT & WHY value that’s required to justify building new products and features.
- Value propositions are written to communicate the WHO, WHAT & WHY value that existing products already satisfy.
The content that comprises clear business requirements and powerful value propositions is literally the same. Here’s the trick to writing something once and using it for both purposes. The Playbook: […]
Your product portfolio has more strategic value than the sum of its parts, especially from the customers’ point of view. Here’s the simplest definition of product portfolio management and it involves three simple concepts: […]
Have you ever seen a product business case, especially for a new product, that didn’t look like a blockbuster? They’re rare. And how often do the revenue projections match reality? It’s hard to say. No one ever compares projections to actuals after the product hits the market. Here are three steps for creating more realistic product business cases and simplifying apples to apples comparisons for multiple product investment opportunities. The Playbook: […]
There are many cases where salespeople are forced into giving presentations before adequate discovery has been completed. Here are a few sales presentation techniques that will yield valuable buyer motivations without formal discovery meetings. The Playbook: […]
Powerful product positioning usually boils down to the best story, which is not always the best product.
Adhere to these three guidelines and marketing and selling value will be a lot easier. The Playbook: