The Product vision describes the purpose of a Product, what it aims to achieve for customers and users. Having a clear and inspiring Product vision helps in motivating and inspiring people, like the Project Team, the customers, and the users. To be able to create the Product Vision, you need to try to answer the following questions:
What is the product to be developed? What type of system it will be (e.g. a Web API, a Web frontend, a mobile app, a desktop app?) and what will the system allow its users to achieve? Additionally, what makes this product different from competing products? Knowing the type of the system to be developed will help the development team understand the target customer and some of their goals as well as technical issues.
Why should customers buy this product? What problem it will solve or what opportunity is it meant to exploit? The team needs to clarify the problem that the project is intended to solve by focusing on key points such as Problem description, Impact of the problem, and Expectations of the successful solution.
Who are the target customers and users?
It’s important to identify the Users but also the other Stakeholders of the system, as the latter may also positively or negatively be affected by the project outcome. So every stakeholder should be identified together with their influence and role in the project.
The "Product Vision" should be written as a separate entry in the Wiki. It should separately include the answers to the abovementioned questions, and it should also be summarized in the form defined by Moore's template, provided here: FOR (target customer) WHO (statement of the need or opportunity) The (PRODUCT NAME) is a (product category) THAT (key benefit, compelling reason to buy) UNLIKE (primary competitive alternative) OUR PRODUCT (statement of primary differentiation)
