Full deep dive with real examples, plus a mega spreadsheet of every prioritisation framework I could find:
youtube.com/watch?v=cGIojZaw…
31
13 spots. Then it's gone.
We sold out both live cohorts last year, and we're almost there again.
Only 13 spots remain for Product Strategy in Practice March cohort. We kick off in 2 weeks!
There's still a window to get it expensed
If you've been sitting on it, now's the time.
Grab one of the 13 spots 👉 productpathways.com/course/p…
Got stakeholders asking for dates on your roadmap? And you can't just say no. Try this👇
youtube.com/watch?v=rgUYY5UU…
If it's not on your watch list 😉👉 youtube.com/watch?v=9N4XnlBG…
Q: "I get that your roadmap should be a reflection of your strategy but what if I don't have a product strategy? How do I create a product roadmap then?"
Here's exactly how I tackle this scenario with a PM in the Product Mentorship on Product Pathways:
Step 1: 'Bring Out Your Dead'
I call this step 'bring out your dead' the idea is to go and gathering everything. From ideas, to features, user requests, opportunities, etc. Just pull them all into one place.
Step 2: Extract Narratives
Instead of jumping to prioritizing, go through the list and start to synthesize. Talk to each item, what is it, why do we need to do it, what is it related to, etc.
The idea is to start to extract narratives that explain intent behind the items. The outcomes and the problems they solve.
This is where you start to make the leap from laundry list to a roadmap that tells a story!
Step 3: Prioritise Narratives
Once you have narratives, sequence them. It's important that you prioritize the narratives themselves not the individual features. I'd recommend doing a simply Now / Next / Later.
Step 4: Map the Work
Now that you have your narratives in order. You have your backbone for the roadmap. In a way it's a rudimentary strategy.
Once you've got that, now you can start to map all those features and ideas that you collected in step one to the narratives.
If something no longer fits, it's a good reflection point on whether it's actually going to move the dial.
Note: if you prioritise the ideas first - which is what most people do - you end up with a laundry list that doesn't have cohesion. This way you can look at everything in the 'now' column and you have a story (narrative) as to why they're there.
Step 5: Add Outcomes
Finally, you can start to add outcomes to your roadmap. Ask yourself what success looks like. This could be at the individual item level, or at the narrative level (or both).
And voilà!
You now have a product roadmap that:
→ is strategic
→ tells a story
→ and is outcome-oriented
BONUS and you have the start of a product strategy!
===
📌 See this in action. Full live stream where I walked through this exact example: youtube.com/watch?v=9oeeoeRf…
Don't rely on a single product roadmap.
This is where I see a lot of Product Managers go wrong.
They overload their product roadmap trying to make it work for everyone and for every situation.
From dependencies, delivery timelines, releases, opportunities, solutions, alignment to high level goals, etc... you end up needing a PhD to read it.
As the adage goes; "if it's for everybody, it's for nobody"
It's then no wonder they're struggling to get buy-in.
And their messages aren't landing.
So if you to influence stakeholders, then you need to start treating your roadmap as a communication tool.
Start with the audience:
→ who am I presenting this roadmap to?
→ what information do they want and what don't they need?
→ what format would be best? (this is important because sending the CEO of a Fortune 500 company a link to Jira isn't going to cut it)
And tailor your roadmap to them.
Of course this doesn't need to mean you're recreating a new roadmap every time.
You'll find that you'll have 2-5 groups of audiences:
The most common I see are:
1) for executives
2) for external teams (eg sales, marketing, even a public roadmap)
3) a detailed version for product and engineering
4) public roadmaps for customers
Different audiences.
Each with different levels of information and formats.
Yes it's more work, but this can be the difference between influencing a stakeholder and getting bogged down into unnecessary details.
===
More on roadmaps:
📌 How to Build a Product Roadmap: 5 Steps From Features to Outcome Roadmap (REAL EXAMPLE): youtube.com/watch?v=9oeeoeRf…
📌 Best Practices for Building Effective Product Roadmaps: youtube.com/watch?v=XAnPLKp7…
There's no one way to do Product Strategy.
Because it's contextual.
Your context drives
→ the constraints
→ the problems to solves
→ the questions you need to answer
→ the choices you need to make
Eg. The product leaders I work with in government and not-for-profit organizations don't need to make pricing decisions, but you might.
However for those new to product strategy I know starting with a blank page or being told "it depends" is not helpful either.
So to make this practical I'd recommend starting lightweight with a one-pager - like this one: productpathways.com/blog/pro…
And answer:
WHY = Vision/Winning Aspiration
WHO = Target Market
HOW = Unique Value Proposition/Differentiation
WHAT = Product Offering/Bets
WHEN = Distribution
+ Success Measures
This will be a small step from where you are today, rather than trying to do a giant leap.
Start here. Iterate and learn.
You’ll still have a long way to go building a detailed product strategy but it’ll be better than doing nothing because it seems to big and daunting.
BONUS: If you're more progressed in your product strategy journey. You can still use one-pagers as a communication tool. Add a link to your product strategy doc for those who want more information.
===
🎁 FYI I have just pulled together two templates, plus a bunch of real product strategy examples, all for FREE here: productpathways.com/strategy
Bonus, you’ll also get a couple of emails and videos from me to help you level up your product strategy craft.
Let’s be real. You likely don’t need another prioritization framework.
You’ve probably tried them all - RICE, WSJF, value vs effort and a dozen spreadsheets in between.
I’ve been there too. Frustrated by ambiguous advice of "prioritize based on value"
And what I realised was the solution wasn't finding some magical framework. It was understanding how prioritization works from a principle level.
Since then I've gone deep on this topic. I've dissected every prioritization framework I could find and I found that they can all be striped back to four core components.
Understanding this has helped me move past frameworks, pick and choose which and when they're the most appropriate - even create my own when necessary.
And I’m going to share the mental model I use to do all this!
By the end of this live stream my goal is that you stop reaching for a formula and start making decisions from first principles.
If any of this resonates, then join 👉 streamyard.com/watch/Xq3qMDT…
See you there!
Let’s be real. You likely don’t need another prioritization framework.
You’ve probably tried them all - RICE, WSJF, value vs effort and a dozen spreadsheets in between.
I’ve been there too. Frustrated by ambiguous advice of "prioritize based on value"
And what I realised was the solution wasn't finding some magical framework. It was understanding how prioritization works from a principle level.
Since then I've gone deep on this topic. I've dissected every prioritization framework I could find and I found that they can all be striped back to four core components.
Understanding this has helped me move past frameworks, pick and choose which and when they're the most appropriate - even create my own when necessary.
And I’m going to share the mental model I use to do all this!
By the end of this live stream my goal is that you stop reaching for a formula and start making decisions from first principles.
If any of this resonates, then join 👉 streamyard.com/watch/Xq3qMDT…
See you there!
You don't have a prioritization problem, you have a strategy problem.
The first prioritization question you should be asking yourself:
Does this align to our strategy?
Because ideas are cheap.
“Value” is ambiguous.
Without strategy have nothing to prioritize against. Nothing to define what’s valuable.
This is why many revert to spreadsheets and prioritization by formulas.
But what you’re really doing is outsourcing your product strategy to RICE or WSJF or similar - not a good idea.
===
FYI: I've created a library of product strategy templates and real world examples, all FREE. You can grab it here if you're interested: productpathways.com/strategy
5 books that changed the way I approach product strategy:
1. Playing to Win by Roger L Martin
Finally gave me the framing for what strategy actually is.
2. Good Strategy Bad Strategy by Richard Rumelt
Helped me see and explain why bad strategy happens, what to look out for and gave me a mental model for developing a strategy.
3. Thinking in Bets by Annie Duke
Helped me make better decisions in uncertainty.
4. Crossing the Chasm by Geoffrey Moore
Gave me a powerful mental model for thinking about how products are adopted and grow (I include "Diffusion of Innovation" in here too)
5. 7 Powers by Hamilton Helmer
Gave me several different ways to think about and apply leverage (Good Strategy Bad Strategy did too)
Honourable mentions to:
+ Thinking Fast and Slow by by Daniel Kahneman
+ Business Model Generation by Strategyzer
+ Good to Great by Jim Collins
+ the HBR article from Michael Porter I read once
+ Marty Cagan's framing of "product strategy = deciding what problems to solve"
+ Art of War by Sun Tzu
+ I also got some good food for thought recently from reading Steven Bartlett's Diary of a CEO book
+ and the dozen of psychology books that helped me understand how users behave.
What did I miss?
What should I read next?
====
For those interested in learning more about Product Strategy I have two FREE things:
1. Product strategy templates + library of real product strategy examples: productpathways.com/strategy
2. Live stream on How to Build a Product Strategy (where I build one live) 👉 youtube.com/watch?v=DPGhd1y1…








