Product Vision

Yes. At some point, you want to have a set of key workflows and key personas nailed as a part of the vision canvas. And using low code or UX mocks etc. - you want to test the validity of the hypothesi

Product visions should always be customer-focused. I'm not sure that you need to actually show your vision statement to users to get their feedback, but your vision should be informed by the user prob

Absolutely! How you test your product vision with users is really the question. I don't think I'd ever just put a product vision statement in front of users for feedback. Instead, use your product vis

I’m assuming the question is about setting a ‘team’ vision/mission and one doesn’t exist yet. The mission statement is the “What” and the vision statement is an ambitious future state of what the worl

Every new job I've taken has had a pretty specific challenge I was hired to solve, and I was fortunate to have that clarity (at least at a high level).  When I start in the new role, I focus on the f

I like to start by understanding the historical context and how teams arrived at where they are. What decisions were made and why. What worked well and what didn't go according to the plan. Starting

Product Vision is similar to a compass for explorers! Product Vision sets the North Star for the product teams and ensures that the Product Principles, Values & Strategy aligns with the Vision on

Great product visions rally a team around a set of clear and concise goals. That vision represents the team's focus and can be a helpful tool when the team needs to make a decision or is starting to b

Pretty much the same stencil that I used to answer the previous question. If you are pivoting, I'd assume that one or more of these elements below have changed. So I'd use this framework to re-examine

In my experience, I've found the best way to successfully pivot your product vision is to make sure your stakeholders are clear on the why, when, and how. Part of bringing a vision to life is rallying

Hybrid products are exponentially harder to build than pure software products. Software can be updated via the cloud, at any time and with any frequency but hardware cannot The form factor, the physi

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 t

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

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, compeiti

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.

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

This is a question that is close to my heart and I love to see folks transition from Product Owners to Stellar PMs. Taking a step back, I truly love to see people become the best versions of themselve

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

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 ->

Product teams and firms should think about the relatioship between the Product, features & goals, the products' & companies' roadmap and finally the company strategy & mission! All these