Communities
Sign Up / Sign In
Back to Your Feed
What do product teams get wrong when defining their product vision?
2 Answers
Bhaskar Krishnan
Meta Product Leadership - Ads, Commerce & AI • June 8
- Vision statements should be simple, describe the value and stand the test of time (atleast one or two market cycles)
- Every product is built to solve a user/ people problem or help solve a pain-point. This should be the main focus when building a product vision and the most important questions are ‘Who is this product for’ and ‘What problem is it solving’?
- Teams that answer the two questions above typically get their vision statement right and teams that focus on teh urgent, immediate or playing catch-up to competition (btoh real & perceived) usually do not
- One of the best examples is is that of the iPhone vs Blackberry - the iPhone focused on solving real-consumer problems in accessing the internet & online content from your phone while the Blackberry foucssed on adding features for their Corporate customers
- The interesting sub-plot here is that Sony Ericsson & Nokia had smartphones that were much more capable than the iPhone when it launched and Sony Ericsson was a leader world-wide. But, they almost didn't have a Vision (or didn't seem to have one) and threw away their marketshare & lead by throwing features & specs at consumers that didn't help them in any manner
- This brings us to another critical point in Product Vision - Timing! Great products could be ideated years or decades before the Technology allows them to be! General Magic almost launched the first smartphone in early 90s, almost 20-years before the iPhone! Apple itself launched the first tablet in the early 90s (but killed it). This mix of market awareness, technology limitations or capablities, consumer willingness to pay, etc all matter when defining a Prodcut Vision
840 Views
Tracy Montour
HiredScore Head of Product Marketing • July 29
The product vision should reflect the needs of the customer, the current market, and the longterm strategy. I often see companies so myopically focused on their shortterm vision that they don't align with the market, the compeition, or customer needs and they lose product market fit. I find that it helps defining a broad vision for the year and then refocusing the roadmap quarterly to ensure the vision is still aligned to turbulent times.
251 Views
Related Ask Me Anything Sessions
Splunk Sr. Director of Product Management, Observability, Kara Gillis on Product Vision
April 16 @ 10:00AM PST
Oracle Director of Product, Oracle Cloud Infrastructure, Devika Nair on Product Vision
November 1 @ 10:00AM PST
GitLab Director of Product Management, Jacqueline Porter on Product Vision
May 17 @ 10:00AM PST
Related Templates
Top Product Management Mentors
Poorvi Shrivastav
Meta Senior Director of Product Management
Richard Shum
Splunk Director of Product Management
Chris Omland
Workiva Vice President Of Product Management
Natalia Baryshnikova
Atlassian Head of Product, Enterprise Agility
Deepak Mukunthu
Salesforce Senior Director of Product, Generative AI Platform (Einstein GPT)
Patrick Davis
Google Group Product Manager
Paresh Vakhariya
Atlassian Director of Product Management (Confluence)
Zeeshan Qamruddin
HubSpot Senior Director of Product Management, Flywheel
Omar Eduardo Fernández
GitLab Director of Product Management
Jacqueline Porter
GitLab Director of Product Management
Related Questions
In what tangible ways should your product vision dictate the day to day decisions your product development team makes?What kind of metrics do you use to track your product vision? Is it necessary? What exercises help you to define a product vision statement?How does the approach vary between a software product and a hybrid product (e.g. a router with embedded sftware)?Is a product vision statement worth user testing? Can you give an example of a bad product vision statement? What would you do to improve it?