Question Page

When creating your product vision statement, what do you research?

Sriram Iyer
Freshworks Vice President of Products | Formerly Salesforce, DeloitteMay 3

Some elements to consider - 

1. Market - Market landscape, gaps, and market opportunities. You want to work on an impactful problem area. Key Geos you will play in. etc.

2. Key vectors - I also like to play at the intersection of 2-3 key growth vectors - so I know directionally I am betting in the right space. So, for example, you could be bullish on video as an explosive growth area for content and creativity and marketing, and you could be bullish on cloud as a universal enabler for key digital transformations across industries and domains, and you could be bullish on AI/ML as the key differentiator for step-change in productivity and efficiency gains - then, you could perhaps target a gap/opportunity that sits at the intersection of video, cloud and AI/ML. Research can provide you with the ammunition to establish these key growth vectors as foundational building blocks for your vision.

3. TAM - The TAM has to be worth it. What is the rTAM for your area? And how do you slice that rTAM by different personas?

4. Personas - You also research the key personas and other stakeholders who will benefit. Ideally, you have one persona who you are zoning in on. And your solution has a halo effect on other stakeholder personas.

5. Competition - who are existing incumbents or future competitors you have to be aware of as you get into this game?

6. Profitability / Share of wallet / Willingness to pay - This is key to identify right upfront so you know your path to monetization and profitability. What is your "profit puppy"? What are your COGS and how are you going to cover them? etc.

7. Key workflow - You want to nail the key workflows that your solution will enable and transform. Ultimately painting a picture using UX design and walkthroughs of these key workflows will help you sell your vision and make it a reality.

8. Winning aspiration - What does "winning" mean in this landscape? It's important to research and write that "key zen" statement out so it's crystal clear.

Once these elements exist, creating a crisp vision statement highlighting the problem areas, key gaps, key personas that this is for, and your winning "zen" etc. becomes easy.

3431 Views
Samantha Ugulava
Atlassian Senior Product Manager, Enterprise AgilityNovember 22

A product vision statement is a short, concise, and aspirational set of goals for your product. As a Product Manager, you will need to develop a deep understanding of your company, customers, compeititors, and teammates. Research will depend entirely on your level of understanding of these areas. 

For the past 2 years, I led the Confluence Content Experience team at Atlassian. My team owned the creating and publishing workflow and our product vision statement looked like this: Our goal is to help creators feel confident creating and publishing more types of content on Confluence.

For me, I was pretty familiar with my company and product group's vision, and I understood how to motivate my engineering team. Where I needed to spend time was building up my knowledge of our customers and competitiors before writing my team's product vision. Here are a few questions I wanted to answer:

  • What kind of persona research already exists for Confluence?
  • What's the difference between a creator, collaborator, and content consumer?  
  • What problems do creators face in Confluence today? 
  • When do creators publish their first page in Confluence?
  • What % of creators are repeat creators?
  • How do people create in other tools? 
  • Why do some Confluence users choose to create in competitive tools?

Great product vision statements ladder up to your organization's vision, focus on the customer, highlight how your product is different from others on the market, and motivate your team to rally around a shared vision as you collectively try to solve big-hairy problems together.

2224 Views
Kara Gillis
Splunk Sr. Director of Product Management, ObservabilityApril 16

First, we should define what a product vision statement is. A product vision statement defines the product's positioning - what we tell ourselves about our product in a market. This is different than messaging - which is what we tell OTHERS about our product in the market. How are these different?

Think about what you think to yourself about someone wearing an eccentric outfit in public. Perhaps you think to yourself, "Wow, he is not pulling off that hat" (positioning). You look closer at the person and you recognize the gentleman as your old friend from college that you haven't seen. He walks up to you, and he asks how he looks. You respond, "Not my style" (messaging). See the difference?

The closer our differentiation can match the perception customers have of your product, however, the better. The most referenced product vision template is from Geoffrey Moore's Crossing the Chasm:

For [our target customer], who [customer’s need], the [product] is a [product category or description] that [unique benefits and selling points].

Unlike [competitors or current methods], our product [main differentiators].

I think the answer to "what do I research" is stated in the bold parts of the template:

  • Customer segmentation based on customer needs

  • Product category / market

    • Existing products in the market

    • Gaps in customers being served in the market

    • Weaknesses of existing options

  • Competitors

    • How they make money

    • Product features

    • Differentiators

Once you understand the above three major areas, you can decide:

  1. Who you want to target within the segmentation, most likely based on a gap in customers not being served properly by the existing options in the market

  2. Customer needs within this segmentation

  3. An understanding of what product, based on these prioritized customer needs, you would be offering

  4. How your offering is different than your competitors

464 Views
Top Product Management Mentors
Tanguy Crusson
Tanguy Crusson
Atlassian Head of Product, Jira Product Discovery
Laurent Gibert
Laurent Gibert
Unity Director of Product Management
Farheen Noorie
Farheen Noorie
Grammarly Monetization Lead, Product
Deepak Mukunthu
Deepak Mukunthu
Salesforce Senior Director of Product, Generative AI Platform (Einstein GPT)
Mike Flouton
Mike Flouton
GitLab VP, Product
Tara Wellington
Tara Wellington
BILL Senior Director of Product Management
Paresh Vakhariya
Paresh Vakhariya
Atlassian Director of Product Management (Confluence)
JJ Miclat
JJ Miclat
Zendesk Director of Product Management
Reid Butler
Reid Butler
Cisco Director of Product Management
Aaron Bloom
Aaron Bloom
Bluevine Senior Director of Product Management