TheProduct Playbook

How to Write a Product Vision

How to Prepare a Product Vision covered what a good vision is and why it matters. This page is the hands-on companion. It walks you through actually writing one, start to finish.

You don't need to be "inspired," an executive, in leadership, or especially good with words to do this. You need a real customer, an honest look at their world, and a willingness to write a rough draft and improve it. Follow the five steps in order. By the end you'll have a vision you can test, and a cheat sheet you can reuse every time you do this again.

Step 1. Get close to the customer and capture their world

You cannot write a real vision from your desk. A vision is about a customer and a future you want to create for them, so the first move is to understand that customer better than anyone else in the building.

Get close to them however you can. Interviews. Watching them do the work. Reading support tickets. Riding along for a day. You're listening for the problem that actually hurts, not the one that's easy to talk about.

Uri Levine says it well. Fall in love with the problem, not the solution. The solution will change. The problem is what stays put long enough to build a vision on.

Then write down the answers to three plain questions:

  1. Who is the customer? Be specific. Not "users," but the actual person and their role.
  2. What is the deep problem you're solving for them? The one that genuinely makes their life or work harder.
  3. What does their world look like once that problem is gone?

That third question is the heart of it. If you can describe their better future in vivid, plain language, where they spend their time now, what they no longer worry about, what they're able to do that they couldn't before, you're most of the way to a vision.

When you're done with this step: you can describe, out loud and clearly, the better future of one real customer.

Step 2. Think big, then face the obstacles

There's a mindset worth carrying into this: Think Big, Start Small, Scale Fast. Right now, you Think Big.

Give yourself permission to dream the destination without immediately worrying about how hard it'll be.

Ask: if everything went right over the next two to five years, what would be true for this customer? Don't shrink it to what feels safe or fundable this quarter. The vision is the mountaintop, not next week's hike.

One more lens, the old Wayne Gretzky line Cagan leans on. Skate to where the puck is heading, not where it's been. In that two-to-five-year window, what's changing in your customer's world, and what isn't? Aim the vision at where things are going, not where they sit today.

Then do the honest part. List the real obstacles standing between today and that future. The hard technical problems, the behavior people would have to change, the things that have stopped others from solving this already.

A vision that ignores the obstacles is just a fantasy, and people can feel it. A vision that names them is a dream with its eyes open, and that's the kind people trust and follow.

When you're done with this step: you have a big, honest destination, plus a short list of the real things in the way.

Step 3. Draft the vision statement

Now you write it. One or two sentences. The whole job is to make the destination clear and worth reaching.

Lead with who you serve and the change you create for them. Do not lead with features or technology. Those come later, in the strategy and the backlog. The vision is about the customer's better world, not your product's spec sheet.

Here's a simple scaffold to get words on the page. It isn't the final form, just a way to stop staring at a blank screen:

[The customer] will [the change in their world],
so they can [the deeper benefit, the why].

Write three versions, not one. Make them different from each other. Then read them out loud and keep the one that makes you feel something. If none of them do, you're probably still describing a feature instead of a future. Go back to your answer to question three in Step 1.

For the tone you're aiming for, look back at the real portal vision statement in How to Prepare. Notice how it leads with who it serves and the change it creates, and never lists a single feature.

When you're done with this step: you'll have a 1-2 sentence rough draft.

Step 4. Run it through the checks

A first draft is almost never clear enough yet. Run it through these checks and tighten as you go.

The clarity test. Back in the section opener, thirty people heard "we're all going to Disneyland" and pictured multiple different places. Your vision has the same risk. So test it. Read your draft to a few people and ask each of them, separately, to tell you in their own words where this takes the customer. If you get different answers, it isn't clear enough. Tighten it until everyone lands in the same place.

The "what it's NOT" check. A vision is not a solution, it's not a goal, and it's not a mission slogan. If your statement names a feature ("the best app for X") or a number ("grow revenue 20%"), you've drifted. And if it's a lofty line about your purpose that could sit on almost any company's wall, that's a mission, not a vision. Cagan finds that last mix-up the most common of all. Rewrite it around your specific customer and the change in their world.

The differentiation check. Could a competitor put their name on your vision? If yes, it isn't pointing anywhere special. A real vision aims at an unmet need you're set up to win, not the crowded space everyone's already fighting over.

The Cagan check. Marty Cagan and the team at SVPG have a well-known set of principles for what makes a great product vision: it should be aspirational, obsessed with the customer, big enough to be meaningful, and persuasive enough to rally people, among others. Pressure-test your draft against their list and adjust. It's a great reference for catching what's missing. You can find the full set of principles in Cagan's book INSPIRED, in the product vision chapter.

When you're done with this step: you have a tighter draft that's clear to others, centered on the customer, and free of features and numbers.

Step 5. Test it, then keep refining

Your vision is a hypothesis, the same as anything else in this playbook. You don't know if it works until it's in front of people.

Share it more widely. Watch for the spark. Do people lean in? Do they repeat it back to you? Do they get a little excited about it? That reaction is your signal. If it lands flat, that's information too. Refine and share again.

As you refine, hold the line Cagan borrows from Bezos: be stubborn on the vision, flexible on the details. The destination stays put. How you get there will shift as you learn, and that's fine.

This is the point where writing the vision ends and spreading it begins. Carry your draft into Evangelizing the Vision, which is about getting it out of your head and into everyone else's.

When you're done with this step: you have a vision you trust enough to start selling.

Want to take it further?

A written statement is the seed of a vision, and for most teams it's enough to align around. But Marty Cagan would push you to go bigger: turn that statement into a vivid, concrete picture of the future. A short narrative of your customer's day once you've won. A simple storyboard of how it plays out. Some teams even make a short video. The statement tells people where you're going. A richer artifact like that lets them feel it, which is what makes a vision spread. If your vision matters enough, it's worth the extra effort.