Pain-Solution-Proof-Point Vision Pitch
Sell a vision by looping pain, solution, and a real user proof point instead of describing it in words.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 93%
A method for crafting and delivering a vision pitch so people feel it rather than just hear it. Rather than the traditional sequence of pain points, then solutions, then timeline and cost, Kapoor structures the pitch as repeating triplets — pain point, solution, proof point — where the proof point is a real prototype, mock, or user testimonial. The whole thing is a single artifact the cross-functional team builds together.
Origin
Mihika Kapoor's approach honed at Figma, a 'see to believe' culture; she cites 'The Medici Effect' by Frans Johansson on how a confluence of ideas from different fields drives innovation.
Core principles
- 01Words only get you so far; seeing and feeling the pain is what convinces
- 02A vision cannot be created in a vacuum — it requires cross-pollination of research, design, and engineering
- 03The team should rally around ONE combined artifact, not separate research/design/product deliverables
- 04Design and prototype before the project is even green-lit — 'see to believe, see to feel'
- 05Root the vision in engineering feasibility from the start
How to run it
- 1
Cross-pollinate before you draft
Gather research insights that let you feel what the user feels, beautiful designs and prototypes that show the future world, and engineering feasibility — working together, not in a linear handoff.
Pro tip Avoid the linear trap of user research -> designs -> engineering; have the functions work simultaneously so ideas cross-pollinate.
Watch out You cannot go into a vacuum and come out with a compelling vision — skipping user immersion produces a hollow pitch.
- 2
Build one unified artifact
Create a single deliverable (often a deck built in Figma) that the whole team owns together, rather than a separate research readout, design crit, and product review each person pours energy into alone.
Pro tip When everyone owns the combined artifact, you get a unified team believing in a singular set of insights.
Watch out Separate per-function deliverables make each teammate optimize their own piece instead of the shared vision.
- 3
Structure it as pain-solution-proof-point loops
Instead of pain points then solutions then costing, alternate: pain point, solution, proof point; pain point, solution, proof point. The proof point is a testimonial on top of a prototype or mock so the audience feels the pain and the payoff.
Pro tip Pair a user testimonial directly on top of a prototype so the emotional pull and the solution land together.
- 4
Make it real even without design/eng skills
If you lack design or prototyping ability, use AI tools to lower the floor, or simply walk around and ask people to help — pitch the idea until someone says yes and builds it with you.
Pro tip Never let your own skill gaps stop you from making the pitch; recruit a designer or engineer partner — it is a superpower.
In the wild
Kapoor noticed brainstorms worked far better in FigJam than other meeting types because they are democratizing — ideas come from anyone, not just the loudest person. She built a vision around making every meeting (kickoffs, all-hands) as generative as a brainstorm, backed by proof points like the kudos-board ritual and features like music and voting to get people into flow.
→ A concrete, feelable vision of a 'more democratic workplace' that guided a roadmap of shipped FigJam features.
Common mistakes
Describing the product only in words
Simply describing a product idea in words is far less compelling than showing a user testimonial on top of a working prototype — words fail to create the emotional pull.
Waiting for a green light before prototyping
Deciding to invest based only on market sizing, then building later, misses the 'see to feel' emotional case; Figma prototypes before green-lighting precisely to generate that pull.
Is it for you?
Best for
A PM or founder who needs internal buy-in for an ambitious idea and can assemble even a rough prototype or mock.
Not ideal for
Incremental, well-understood features where a short written spec is faster and a full vision pitch is overkill.
From the transcript
“how can a vision pitch effectively be like pain point solution proof point, pain point solution proof point”
“simply describing a product idea in words is not as compelling as seeing a testimonial from a user on top of a prototype or a…”
“you cannot go into a vacuum and come out with a compelling vision”
“we lean heavily into designing and prototyping even before a project gets a green light”
“there is like a single artifact that the team is creating together”
From the episode
Vision, conviction, and hype: How to build 0 to 1 inside a company
Mihika Kapoor (Product at Figma)