Crafting and Communicating a Compelling Product Vision

A vision must be lofty yet realistic, free of today’s constraints, and anchored in a potent user problem.

It should feel almost scary-exciting but still attainable; it should ignore current tech limits to force invention; and it must start from a real pain worth solving.

Why: Loftiness inspires, realism keeps it credible, freedom from constraints unlocks innovation, and a clear problem ensures relevance.

"it needs to be lofty... it almost scares you in an exciting way... it needs to be realistic and attainable... it needs to be in a vacuum from the limitations of today... grounded in a very clear and potent problem, user problem"

Vision is the postcard from the future; mission is the purpose and guiding principles.

Vision paints the picture of the destination (a city without parking); mission states why you’re going (reliable transportation everywhere for everyone).

Why: Separating the two prevents teams from confusing aspirational imagery with day-to-day purpose and keeps strategic narrative crisp.

"the vision would be once we're up there, me describing the picture... the mission is the purpose of why we're doing that"

Deeply understand the problem before inventing the future.

Use the product yourself, cat-food competitors, maintain a living “Top 10 Things You Should Know” doc refreshed quarterly, and force cross-functional partners to stack-rank their 10 pains.

Why: Clarity of the problem is the immovable North Star; without it vision drifts into fantasy.

"clarity of the problem... is missing... it's the North Star that doesn't move"

Compress the strategy into an evergreen two-page narrative: insights → strategy → big rocks.

Write it as if pitching a startup to investors; keep big rocks to 3-5 memorable items; publish as a living doc with comments open.

Why: A concise narrative aligns leaders, kills redundant meetings, and becomes onboarding material for new teammates.

"clarity and conviction... it's like you bring clarity and you have conviction"

Use formats humans remember: fairy-tale arc, future news headline, or single sketch.

Once-upon-a-time → problem → one day → result; or mock a TechCrunch headline and screenshot; or draw the future UI on a Post-it.

Why: Stories stick; numbers alone don’t. A picture or narrative travels further than a 40-slide deck.

"stories... are not numbers... the gap is so wide in stories alone"

Roll the vision outward in three concentric circles: team → stakeholders → leadership.

Start with triads (PM+Eng+Design), then bring in adjacent teams, finally pitch top brass—let them pull you back if needed.

Why: Early friction polishes the idea; late friction kills it. Each ring pre-wires the next, reducing surprise and resistance.

"quarantine the people who will actually build this thing... stakeholders... leadership"

A good vision is evergreen; you add fidelity, not replace it yearly.

If you’re rewriting the vision every year you haven’t done the work; instead layer higher-res mocks or sizzle reels on the same destination.

Why: Evergreen visions compound belief and allow multi-year bets to mature; constant resets erode trust.

"if you have to repeat the vision every year, you have not created a good vision"

Every level owns a slice: macro 3-5 year vision plus micro next-year vision.

Platform PMs need macro to future-proof foundations; feature PMs craft micro mocks for the next release.

Why: Scales vision work across org levels without diluting the big picture.

"all have a variation of a vision... micro vision... macro vision"