Back to Your Feed
3 Answers

Sriram Iyer
Adobe GM / Head of Strategy, Product & Partnerships • May 4
Metrics are absolutely necessary when building your vision board. As you think of metrics, think of what will really define success? And how will we as a team measure success? Here are a few examples of key questions teams try to answer as they think of crafting metrics for their vision canvas - ......Read More
543 Views

Jacqueline Porter
GitLab Director of Product Management • May 18
I don't usually have metrics to validate the vision, because usually the execution plan and product adoption will tell the story of if it resonates with the market. Interviews and qualitative data are nice inputs to the product vision and help validate if the word choice is appropriate. Some e......Read More
401 Views

Bhaskar Krishnan
Meta Product Leadership - Ads, Personalization & ML/ AI • June 8
* Data & Metrics are at the heart of every product, be it Consumer, Enterprise or Platform. A metrics tree or hierarchy is critical and should follow the Execute -> Features -> Roadmap -> Strategy -> Vision structure highlighted in another question * The metrics dashboard should track ......Read More
450 Views
Related Ask Me Anything Sessions

GitLab Director of Product Management, Jacqueline Porter on Product Vision
May 17 @ 10:00AM PST

Atlassian Product Leader, Enterprise Agility, Samantha Ugulavaon Product Vision
November 23 @ 10:00AM PST

Meta (Facebook) Product Leadership, Bhaskar Krishnanon Product Vision
June 7 @ 9:00AM PST
RELATED

Bhaskar Krishnan
Meta Product Leadership - Ads, Personalization & ML/ 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 importan......Read More
549 Views
RELATED

Jacqueline Porter
GitLab Director of Product Management • May 18
Both product lifecycles require a strong long-term vision in order to effectively motivate the team and attract users. Without a strong vision, the 0 to 1 product would not be able to focus on goals/exit criteria for launch while the mature product would get stuck in a routine problem-solving app......Read More
381 Views
RELATED

Sriram Iyer
Adobe GM / Head of Strategy, Product & Partnerships • May 4
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 i......Read More
731 Views
RELATED

Samantha Ugulava
Atlassian Senior Product Manager, Enterprise Agility • November 23
I think the biggest difference between crafting software vs. hybrid product vision statements comes down to scale. It's much faster to build, test, and learn with software product than products that touch hardware. With software, you can scale your product and customer base very quickly, whereas,......Read More
614 Views
Related Questions
What do product teams get wrong when defining their product vision?How does the importance of a product vision change from 0-1 products to a growing product to a very mature product?When creating your product vision statement, what do you research?How does the approach vary between a software product and a hybrid product (e.g. a router with embedded sftware)?