Product Vision

The importance of product vision doesn’t go away as a product matures, but how you apply it changes and so do the kinds of people and problems you need to solve.In the ea...

• Use various communication methods: in-product nudges, tooltips, release notes, email digests, demo videos and short “before/after” demos.• Tie every announcement to a s...

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 & Stra...

Right off the bat, the very first thing here to do would be a deep dive into market trends, competitive landscape, and internal data. You need a holistic view of where th...

This is one of the most critical steps in the product vision process. Defining what to research sets the course for the whole project - since the fact base is the basis f...

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

To define a product vision statement, start with customer feedback sessions, including interviews, surveys, and support tickets, to understand their pain points and desir...

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

The process I use for creating a product vision is a rather simple 6 step process: (1) Write key questions / hypotheses (2) build fact base / research to answer questions...

Product vision distills why a product does what it does and how it envisions the future. As we saw above, it's critical to spend time crafting the product vision and the ...

When engineering resources are minimal, I really tend to follow the money or follow the vision. The work we're doing has to either provide immediate customer value that c...

My answer to product strategy depends on where I am in the role. If I'm new to a role, I tend to look at the existing product strategy and determine what's working and wh...

This really depends on the organization, the stage, and how much detail you want to include in your vision. I'd say if you're just starting out, it's much more important ...

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

A product vision statement defines the long-term goal and direction of a product. It’s where the product aims to be in the future, independent of the current state or com...

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

With product vision, we need to carefully tread the line between making it too generic/vague or too technical. Other things to consider are - it should clarify what impac...

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

Love this question! Planning for product vision is usually done in 3 horizons: 10 years, 3 years, and 1 year. The 10-year vision is your guiding, north-star approach that...

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

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