Elements of an Effective Product Strategy

The Three Elements of an Effective Strategy Product strategy is about imagining the future of your product: What product will it become? Who will it benefit? How will it create value? It’s a high-level plan that helps you realise your vision or overarching goal. More specifically, the product strategy should describe who the product is for and why people would want to buy and to use it; what the product is and why it stands out; and what the business goals are and why it is worthwhile for your company to invest in it, as the following picture shows. The market describes the target customers and users of your product, the people who are likely to buy and to use it. The needs comprise the main problem your product solves or the primary benefit it provides. Think of a product like Google Search or Bing that solves the problem of finding information on the Internet. Compare it to a product like Facebook that allows you to stay in touch with family and friends. The key features and the differentiators are those aspects of your product that are crucial to address the main problem or create the primary benefit and that make people choose it over competing offers. Don’t create a mini backlog or a wish list. Instead focus on the three to five key aspects that make people buy and use the product. Take, for example, the first iPhone with mobile Internet, iPod-like digital music player, and touch screen as its key features; or the Google Chrome browser with its focus on speed, safety, and simplicity. The business goals capture how your product is going to benefit your company. Is it going to generate revenue, help sell another product or service, reduce cost, or increase the brand equity? Being clear on the business goals allows you to select the right key performance indicators (KPIs) and to measure your product’s performance. Take the iPhone and the Google Chrome browser mentioned earlier. While the iPhone currently generates the largest portion of Apple’s revenue, the Chrome browser does not earn any money for Google. But it allows the company to control the way people access the Internet and it has reduced Google’s dependency on third-party browsers such as Mozilla’s Firefox and Microsoft’s Internet Explorer. Both are important business benefits. You can capture your product strategy with the Product Vision Board, a simple yet effective tool shown in the following picture. You can download it from romanpichler.com/tools/vision-board or by clicking on the picture below. The Product Vision Board above captures the vision at the top. The four sections underneath it describe the strategy. The questions help you provide the right information. You can find more information about the tool in my post “The Product Vision Board”. Strategy Focus and Inflection Points The product strategy is not a static, fixed statement or document that you create for a new product. It changes as your product grows and matures. The following picture shows the product lifecycle with four key events: launch, product-market fit, rejuvenation, and end-of-life. The strategy for a new product should first help you get to launch, then achieve product-market fit (PMF), and finally sustain the growth of your product. Think, for instance, of the changes Apple has made to the iPhone since its launch in 2007 to keep it attractive and preserve its growth, from adding apps to changing the its size. Once the growth starts to stagnate you have reached another strategic inflection point: You either revitalise your product, for instance, by rejuvenating it or taking it to a new market, or you let it mature and eventually decline and die. To use the product strategy to proactively manage your product, you should review and adjust it on a regular basis – I recommend once a quarter as a rule of thumb. The Product Strategy in Context If the product strategy describes the key elements required to develop a success product as I suggested above, then where are the

Om Podcasten

Expert Training & Management | Agile Product Management and Scrum