The product vision can be a powerful vehicle for creating a shared purpose, inspiring people, and galvanising them. Unfortunately, I have seen many visions that did not fulfil their potential, as they suffered from a number of mistakes. In this article, I discuss five common issues and explain how you can avoid and correct them.
The product vision can be a powerful vehicle for creating a shared purpose, inspiring people, and galvanising them. Unfortunately, I have seen many visions that did not fulfil their potential, as they suffered from a number of mistakes. In this episode, I discuss five common issues and explain how you can avoid and correct them.
Developing a winning product strategy is hard. Keeping the strategy relevant and achieving continued product success is even harder. In this article, I discuss how you can use the product lifecycle model to address this challenge. I explain how the model can help you make the right strategic choices, focus and evolve the product strategy, and effectively grow the product.
Developing a winning product strategy is hard. Keeping the strategy relevant and achieving product success on a continued basis is even harder. In this episode, I discuss how you can use the product lifecycle model to address this challenge. I explain how the model can help you make the right strategic choices, focus and evolve the product strategy, and proactively progress and grow the product.
Whenever you require more than a single development team to progress your product, you have to consider how to organise the teams. One choice is to use feature and component teams. This article explains why this distinction matters for product people, and it shares my advice on when feature teams are right for your product and when component teams might be better suited.
Getting the product roadmap prioritisation right is a common challenge. Which items should be addressed first? Which ones can be delayed? This article answers these questions and helps you effectively prioritise your product roadmap.
Rewriting an existing product is often a cost and technology-centric exercise that can feel like a joyless necessity. But instead of replacing like-for-like and providing a carbon-copy of the old product, you should see the rewriting effort as an opportunity to innovate, to create more value for the users and the business, as I explain in this article.
Similar to a company experiencing financial debt, products can incur “technical debt”: This happens when wrong or suboptimal architecture, technology, and coding decisions are taken. Consequently, the architecture may not be as loosely coupled as it should be, and the code may be messy rather than clean. This article explains why product people should care about technical debt and it offers strategies for addressing it.
Product strategy does not only matter for new and young products; it is equally important for older ones. This article discusses two main choices for mature products: extending the life cycle and revitalising the product, or leveraging maturity and turning the product into a cash cow.
Product strategizing refers to the activities required to determine if and why a product should be developed. Carrying out this work makes it more likely to create a product that users want and need. In this article, I share my recommendations to help you improve your product strategy work.