Skip to main content

Product Vision: an elevator pitch for your product


On this blog, I write a lot about making data-driven decisions. But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.


Every product deserves a vision

Product vision, unlike company vision statement, is not about wishful thinking: "We want to be number one in all markets we operate in". Product vision is a clearly defined set of statements that describes a product, it's market and it's USPs.

Product Vision consists of the following information:

  • Whose problems are we trying to solve ? (customer, user personas) 
  • What top problem(s) we gonna solve? (customer, user needs)
  • What critical elements of our solution? (top marketable features)
  • What differentiates us from existing solutions?  (USPs)

Internal ones (communicated mainly internally)

  • How are we gonna make money from it? (business model)
  • Can we do it? (feasibility)

Roman Pichler has described Product Vision in his book "Agile Product Management with Scrum" and in the following blog post: Envisioning your Product.

Joel Spolsky has offered a simple template to capture a Product Vision:

  • For (target customer)
  • Who (statement of a need or an 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)

Here is a Product Vision example created using this template:
"For a mid-sized company's marketing and sales departments who need basic CRM functionality, the CRM-Innovator is a Web-based service that provides sales tracking, lead generation, and sales representative support features that improve customer relationships at critical touch points. Unlike other services or package software products, our product provides very capable services at a moderate cost."

You can also use Roman's template, the Vision Board (my favorite):


The importance of a Product Vision

Product Vision is a simple yet very powerful tool from informational, organizational, planning and leadership perspectives.

Information and communication

When anybody asking you: what your product is about? Tell your product vision. Need to present your product to a senior management? Tell your product vision. Got into an elevator with a CEO? Ask for a pay raise ... and tell him your product vision. Keep on repeating your product vision until everybody knows it and able to repeat it themselves.

Decision making

What do you do when you don't have enough data to make a decision? Follow highest paid executive's opinion? Trust your gut? Don't do anything?  Try to follow your product vision the next time when it happens. When you don't have a great deal of confidence in a decision - always check it with your product vision. If those align - proceed, if not - think again. Having a product vision also helps in setting the right priorities. Items that support product vision should always be up top on a priority list.

Common ground for the team

Product vision is usually a statement created by the entire product team. Despite the fact that product owner is a formal keeper of a product vision, the entire team is creating it and therefore owns it. This fact helps the team to make better decisions in product development.

Sum up

Every product needs a vision. It should include information about target customers, key problems, critical solutions and clear differentiation. Product vision is a joint creation of the entire product team. It also serves as the main reference when making product decisions. Communicate product vision widely and often until it'll become a common knowledge.

Comments

Popular posts from this blog

Fogg Behavior Model

Have you ever wondered why you do certain things? Why are some behaviors easy and joy to do while other not so? And your customers - have you ever struggled to understand their behavior?
BJ Fogg, from Stanford University, has created simple and powerful behavioral model for persuasive product design.


2017: Less of How, more of What, and a little bit of Why

Focusing less on how (methodologies, frameworks, processes). For me, that was the most important product management trend in 2017. Surely, "Agile" talks are bottomless. Yet, I noticed a certain tiredness and dare I say, boredom among product community with regards to this topic.
- Maybe that's enough? Haven't we discussed that like thousand times? Shouldn't we all have that figured by now?