Product strategy

What is a product vision, and how do you write a good one?

A product vision describes, in specific terms, what the world would look like if your product were wildly successful. It does two jobs: it makes the destination clear, so your stakeholders agree on what will be true when you've completed your mission, and it moves people towards a common goal. A good one is a statement you can picture.

To write one, run a workshop: ask your stakeholders what will be true if you are wildly successful, then turn their answers into one statement, yourself or with an AI's help. In a company with several products, it adapts the company vision to yours.

By Cyril Le Roux · Published · 5 min read

Disclosure: Produxity builds Scaffold, which appears below where it helps. The page stands without it.

What Makes a Good Product Vision (and How to Write One) · 5 min · Watch on YouTube
Read the transcript

0:00 Why you need a product vision

So you already know that it's impossible to have a great product strategy without a great product vision. And this is what we're gonna talk about in this video. What is it, what does it look like, and how to come up with one. But first of all, for those who don't know me, my name is Cyril Le Roux, I've founded Produxity, and I build Scaffold, which is an AI-native product strategy platform that helps product managers like you to come up with a great product strategy.

0:25 What a good product vision looks like

So, what does a good product vision look like? Well, there's a good description from Simon Sinek in his book Leaders Eat Last. He says, a good vision statement explains in specific terms what the world would look like if everything we did was wildly successful. So you see the first purpose is to make your destination clear. Where are you going with your product? And this aligns your stakeholders on what will be true when you've completed your mission.

But it does something else. And I really like this quote from Chris Voss, he's a former FBI negotiator, and he was involved in a number of high-stakes hostage-taking situations. And he says this: vision drives decision. In other words, when negotiating in hostage situations, you stand a much better chance of getting a decision and therefore getting an action from the person in front of you if they can visualise what you're offering.

Now, hopefully your stakeholders will not be as difficult as hostage takers. So it should work even better for them because this is the second objective. A good product vision also motivates and drives people towards a common goal.

1:35 The test: can you see it?

Now, what does that mean in practice, that you can visualise it? Well, I'd like you to think back about the 80s and what the situation was like when it comes to computers. You would have, you would find computers in offices, you would find computers usually old terminals, but it wasn't really that widespread. Yet in the 80s, Microsoft had this vision for their employees. A computer on every desk at work and at home running Microsoft software.

And this is really something you can easily imagine. You can really close your eyes and see what that situation would look like. So this is what you're looking for. You're looking for a statement that can easily be imagined.

2:15 Company vision vs product vision

Now, if your company is a startup with a single product, then your product vision is probably not too different to the company vision. There might even be a case for not having a separate product vision at all, especially in the early days. But if you're a multi-product, then you need to take the company vision and adapt it to your product. So you keep the mindset, you keep the high-level objectives, but you adapt it.

You essentially explain what it means for your product.

2:42 Example: Apple and the iPhone

So if we take an example, last time I checked Apple's vision, it said this: to make a contribution to the world by making tools for the mind that advance humankind. So that's the overall vision for Apple. And you could argue that's a bit fluffy, but that's understandable because there's a lot of product, you know, from an AirTag to an iPhone through a Mac or an iPad or a Vision Pro.

Those are very different products. So the vision statement for the company needs to fit all those products, but it's the role of the product manager to then adapt this to their respective product. And for the iPhone, it goes like this: make a phone that is truly smart, user-friendly and improves the lives of users across the globe. And if you think about what that means: truly smart, I think it's a little bit debatable at the moment with Siri, but hopefully that will improve.

User-friendly, yes, definitely. And improves the lives of users across the globe, and this is, this explains why Apple puts so much emphasis on accessibility. Whatever disability you have, whatever the impairment, they try to make the iPhone usable for you so that you can enjoy life better. So those are how you get a vision from a company vision.

3:57 How to write a product vision

So how do you make one? Well, this is not a solo exercise coming up with a product vision. Use this as an alignment workshop, and the earlier you bring people in on this journey, the more support you will have. So don't spring a product vision on them that they haven't seen. Make them part of the journey. And you could do this. You could have a workshop where you ask people what they would what would they like to be true in the future if the company is wildly successful.

And you can have a lot of fun talking about all those statements that would be true.

4:24 Write it yourself, or with AI

And then you have two options. If you're good at copy, then you can turn this into a statement yourself. Or if, like me, English is not your mother tongue, or if like me, you've never really been good at writing copy, then this is an AI job where you feed all those statements that have been provided by people, and you ask an AI to create three to five different options for a vision statement.

And you use this to pick and mix the best bits and assemble your final vision statement from all those different options that have been provided.

4:57 Your turn

So that's how you get to a great product vision. Give this a try and let me know in the comments how it went.

What a product vision is for

Simon Sinek gives a good description in his book Leaders Eat Last:

“A good vision statement explains in specific terms what the world would look like if everything we did was wildly successful.”

Simon Sinek

That is the first job of a product vision: to make your destination clear. Where are you going with your product? A clear destination aligns your stakeholders on what will be true when you've completed your mission.

The second job is to move people. Chris Voss, a former FBI negotiator who worked on high-stakes hostage situations, puts it in three words: vision drives decision. You stand a much better chance of getting a decision, and then an action, from the person in front of you if they can visualise what you're offering. Your stakeholders will hopefully be easier than hostage takers, so it should work even better on them. A good product vision motivates people and drives them towards a common goal.

The test: can you close your eyes and see it?

Think back to computers in the 1980s. You would find them in offices, usually as old terminals, but they were not widespread. Yet Microsoft had this vision for its employees:

“A computer on every desk, at work and at home, running Microsoft software.”

Microsoft, the 1980s

You can close your eyes and see that world straight away. That is what you are looking for: a statement that can easily be imagined.

Company vision and product vision

If your company is a startup with a single product, your product vision is probably not too different from the company vision. There may even be a case for not having a separate product vision at all, especially in the early days.

With several products, take the company vision and adapt it to your product. Keep the mindset and the high-level objectives, and explain what they mean for your product.

An example: Apple and the iPhone

Apple's vision for the company reads:

“To make a contribution to the world by making tools for the mind that advance humankind.”

Apple

You could argue that it is a bit fluffy, and that is understandable: it has to fit very different products, from an AirTag to an iPhone, through a Mac, an iPad or a Vision Pro. It is the product manager's role to adapt it to their product. For the iPhone, it goes like this:

“Make a phone that is truly smart, user-friendly and improves the lives of users across the globe.”

For the iPhone

Each part shows in the product. The first, smart, is a little debatable with Siri at the moment. User-friendly, definitely. And improving the lives of users across the globe explains why Apple puts so much emphasis on accessibility: whatever the impairment, it tries to make the iPhone usable for you, so that you can enjoy life better.

How to write a product vision

Coming up with a product vision is not a solo exercise. Use it as an alignment workshop: the earlier you bring people in on the journey, the more support you will have. Don't spring a product vision on people who have never seen it; make them part of the journey.

1. Run it as a workshop

Ask people what they would like to be true in the future if the company is wildly successful, and take the time to talk through all those statements.

2. Turn the statements into one

If you are good at copy, write the vision statement yourself from what people said.

3. Or give them to an AI

Feed it every statement people gave you and ask for three to five options for a vision statement. Then pick and mix the best bits into your final statement.

4. Check that people can see it

Read it aloud to someone outside the team. If they cannot picture the world it describes, it is not finished. If it could describe any product in your category, it is not yours.

Where it fits: vision, strategy and roadmap

The vision is where you are going. The product strategy is how you get there, and what you will not do on the way: the principles that link where your product is today with the destination. The roadmap is what you build next. It is impossible to have a great product strategy without a great product vision, so the vision comes first.

Next: what a product strategy is, and how to build one in six steps.

Where Scaffold helps

In Scaffold, the product vision is the destination on your strategy map. Research looks for it in the documents you share, and anything it finds is shown with where it found it. When your material doesn't cover it, you say it, in your own words or from a document, and rough is fine. The route, where you work out how to get there, opens once you validate it.

Questions product managers ask

What is the difference between a company vision and a product vision?

The company vision has to fit every product the company makes, so it is often broad. The product vision adapts it to one product: it keeps the mindset and the high-level objectives, and says what they mean for that product. A startup with a single product may not need a separate one in its early days.

What is the difference between a product vision and a product strategy?

The vision is where you are going. The strategy is how you get there: the principles you follow at every decision point, including what you will not do. The vision comes first; it is impossible to have a great product strategy without a great product vision.

How long should a product vision be?

A sentence or two, specific enough to picture. Microsoft's fitted in one: a computer on every desk, at work and at home, running Microsoft software.

Who should write the product vision?

Adapting the company vision to the product is the product manager's role. It is not a solo exercise, though: bring your stakeholders in early, through a workshop, so that by the time the vision is written down it is theirs too.

Can AI write a product vision?

It can help with the wording. Give an AI the statements your stakeholders came up with in the workshop, ask for three to five options, then pick and mix the best bits. The statements, and the final choice, come from your people.

How often should a product vision change?

Rarely. The roadmap moves every few weeks and the strategy changes when the evidence does; the vision is the destination they both point to.

About the author

Cyril Le Roux teaches Product Focus's flagship product management course and co-authored its AI course. He has been a senior product leader at BT, Photobox, Zoopla and TransferGo, and founded Produxity, which builds Scaffold.

Start with what your company already knows.