Product Vision Writing

A product vision people can repeat and use: built from evidence and leadership interviews, written as a vivid one-page narrative with principles and non-goals, launched to the team and refreshed each year.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Vision Writing, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

🧩 Product Management

Product Vision Writing

Writing a compelling description of where the product is heading over several years, and why, that guides roadmaps and inspires the team.

  1. Inventory of every vision statement in use
  2. Vision horizon and scope decision
  3. Shared definitions of vision, mission, strategy and roadmap
  4. Evidence pack behind the vision
  5. Leadership interviews on where the product is heading
  6. Portrait of the customer five years from now
  7. Enduring customer problem statement
  8. Vision ownership and sign-off rules
  9. First complete draft of the one-page vision
  10. Single home for the vision and its change history
  11. Quarterly evidence check against the vision
  12. Monthly trace from roadmap themes to the vision
  13. Vision assumption register
  14. Annual vision refresh cycle
  15. Restate-the-vision pulse check
  16. Customer story bank for the vision
  17. Vision walkthrough for new starters
  18. Vision link in planning and spec templates
  19. Close reading of published product visions
  20. Writing vivid future scenarios
  21. Plain-language editing for vision prose
  22. Narrative structure for a vision story
  23. Scenario planning for the vision horizon
  24. Facilitating a vision workshop
  25. Two-minute spoken version of the vision
  26. Product principles drawn from the vision
  27. Press release from the future
  28. Vision pillars and strategic bets
  29. What the product will not become
  30. Choosing the vision format and companion piece
  31. Concept screens of the future product
  32. Rewriting an inherited vision nobody uses
  33. Pre-mortem of the vision
  34. Testing the vision narrative with five customers
  35. Leadership vision workshop day
  36. All-hands launch of the product vision
  37. Vision questions and FAQ after launch
  38. Vision progress paragraph in board updates
  39. One-year vision retrospective
  40. Founder's first product vision before product-market fit
  41. Vision narrative for a fundraising round
  42. New product leader inheriting a vision
  43. Vision rewrite after a pivot
  44. Combining product visions after an acquisition
  45. Team vision nested under the company vision
  46. Platform and ecosystem vision
  47. Layered one, three and ten year views
  48. Audit of whether the vision guides decisions
  49. Coaching product managers to write their own visions
  50. Honest vision for a mature product

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of every vision statement in use

Before writing anything new, most product leaders find three or four versions of the vision already in circulation: a line on the careers page, a slide in the pitch deck, a paragraph in the strategy document and whatever the founder says at all-hands. Collecting them in one place shows where they agree, where they contradict each other and which one customers and staff have actually seen.

First tasks

  • Search shared drives and chat for the words vision, mission and north star
  • Copy the about page, careers page and pitch deck wording into one table
  • Ask three colleagues to write the product vision from memory in two sentences
  • Mark the phrases that agree and the claims that contradict

Vision horizon and scope decision

A vision for the next eighteen months reads like a roadmap, and one for the next twenty years reads like a slogan. Deciding up front how far ahead it looks, whether it covers the whole company or one product line, and what it is not responsible for keeps the drafting focused and stops it turning into a feature list.

First tasks

  • Write down the horizon you instinctively want and why
  • List the products and customer segments the vision must cover
  • Draft three questions the vision will leave to strategy and the roadmap
  • Agree the horizon and scope with the person who signs off the vision

Shared definitions of vision, mission, strategy and roadmap

Arguments about the vision often turn out to be arguments about words, with one person meaning the mission and another meaning next quarter's plan. A one-page glossary with an example for each term, taken from your own product, gives everyone the same map before drafting starts.

First tasks

  • Write a one-sentence definition for each of the five terms
  • Add an example of each term from your own product
  • Ask an engineer and a salesperson whether the definitions are clear
  • Link the glossary at the top of the vision document

Make it yours.

Install Product Vision Writing, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.