Thread by @nurijanian

Technical PMs: Your coding background is killing your product vision presentations.

Not because technical skills aren't valuable.

But because you're stuck presenting architecture diagrams when you should be telling stories.

I made this mistake for 2 years. Here's what actually works 🧵

1/ The biggest trap for technical PMs:

Leading with HOW instead of WHY.

Your engineering brain wants to show the architecture.
Your product brain needs to show the possibility.

Changing this one thing transformed how my vision landed.

2/ Three principles that changed everything for me:

- Start with the world, not your product
- Use tension and resolution
- Make it human-centric

Let me break these down...

3/ Start with the world:

❌ "We're building a distributed cache layer..."

✅ "Imagine a world where developers never worry about data latency..."

See the difference? One sells features, the other sells dreams.

4/ Use tension and resolution:

- Show the gap between today and tomorrow
- Make the pain real
- Paint the relief vividly

5/ Make it human-centric:

- Replace features with outcomes
- Use real user stories
- Focus on transformation

The best PMs make tech feel human.

6/ The structure that actually works:

30s: Hook (surprising insight)
2m: Current landscape
3m: Future state
5m: Your bridge there
1m: Clear call to action

Save this template. It works every time.

7/ Before and After:

❌ "We're building a Redis cache for 40% better performance..."

✅ "Imagine deploying code knowing it'll run as fast in prod as on your laptop..."

One focuses on tech. One focuses on freedom.

8/ Advanced moves that doubled my success rate:

The Contrast Method (Made to Stick):
- Paint two vivid pictures side by side
- Today: "Developers spending 2hrs debugging deployments"
- Future: "Push to prod with complete confidence"

The Contrast Method works because it triggers loss aversion:
- People are 2x more motivated by avoiding pain than gaining pleasure
- Show them both futures, make them choose
- Keep it concrete, not abstract

9/ The Narrative Bridge (Duarte):
- Alternate between "what is" and "what could be"
- Build tension by showing the gap
- Each gap = opportunity for your solution

Why the Narrative Bridge works:
- Our brains are wired for contrast
- Creates emotional peaks and valleys
- Makes your solution feel inevitable vs forced

10/ The Pyramid Principle:
- Start with the answer
- Group supporting ideas (3 max)
- Drill down only when asked

The power of Pyramid thinking:
- Execs process top-down
- They want conclusion first
- Details = credibility, not selling points

Bonus tip: I combine all 3 in big vision presentations:
- Pyramid for structure
- Contrast for tension
- Bridge for flow

Your first 90 days of better vision storytelling:

- Practice in team meetings
- Collect user stories
- Build your insight bank
- Get brutal feedback
- Iterate relentlessly

Save this thread for when you need to inspire action 🎯