First things first: we do not build our product roadmap in a vacuum. We have a pretty sophisticated process.
Here you go:
1โฃ MOALs
These are the Mid-term goals on a company level and they are the guiding stars for one year (e.g., 2024).
We discuss these in the leadership team towards the end of the year for the next year. We have six different themes: Financials, Product, Technology, Scalability, Customer, People.
The descriptions are pretty high-level, however they shall give all the teams guidance for their planning.
2โฃ Product Strategy
The product strategy is revised every three months (minimum), especially after the MOALs process we recheck whether anything from the MOALs can or must be derived for the product strategy.
3โฃ Product Goals
The Product Goals are derived from the Product Strategy and MOALs and shall give the team guidance.
The Product Goals shall support achieving the MOALs.
Per product and depending on the team size we set a maximum of four Product Goals.
4โฃ Outcomes
Based on the Product Goals we derive specific outcomes we want to achieve. These Outcomes are measurable and shall give us an understanding whether we have achieved the Product Goals. We usually have multiple defined Outcomes.
5โฃ Product Roadmap
We derive what we need to do to achieve these Outcomes. Lots of the work is actually Product Discovery. But eventually, topics will be derived for the actual product roadmap and later developed.
---
As you can see, the Product Roadmap is tied to many steps before and all is connected.
Yes, it takes quite some time to build all of that. On the other side, it gives alignment and everyone knows on what the things they are working actually pay into.
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
@herbigt @ttorres Here is a great definition (and visual) by @herbigt
"Product Discovery is about the data-informed reduction of uncertainty in regards to problems worth solving and solutions worth building through a series of non-linear activities, conducted as a cross-functional team."
@herbigt @ttorres There is a very simple definition by @ttorres:
"Product Discovery is used to describe the work that we do to make decisions about what to build"
Further she makes a clear cut to Product Delivery:
"Product Delivery is the work we do to build, ship and maintain a product:"
@herbigt @ttorres Here is a great definition (and visual) by @herbigt
"Product Discovery is about the data-informed reduction of uncertainty in regards to problems worth solving and solutions worth building through a series of non-linear activities, conducted as a cross-functional team."
@herbigt @ttorres There is a very simple definition by @ttorres:
"Product Discovery is used to describe the work that we do to make decisions about what to build"
Further she makes a clear cut to Product Delivery:
"Product Delivery is the work we do to build, ship and maintain a product:"
For Product Manager working on one product is quite a task, but overseeing multiple products is next level.
It can be quite a challenge to get all of this together.
A very helpful method for this is the Growth-Share-Matrix.
Let me explain this in a ๐งต
๐ช๐ต๐ฎ๐ ๐ถ๐ ๐ฎ ๐๐ฟ๐ผ๐๐๐ต-๐ฆ๐ต๐ฎ๐ฟ๐ฒ-๐ ๐ฎ๐๐ฟ๐ถ๐ ? It is a strategic tool that categorises products or business units based on market growth and share.
PMs can use this when they oversee multiple products (for example I'm currently responsible for three different products).
๐ช๐ต๐ถ๐ฐ๐ต ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ ๐ฑ๐ผ๐ฒ๐ ๐ถ๐ ๐๐ผ๐น๐๐ฒ? It supports the strategic portfolio analysis and supports decision processes.
PMs can use the method to prioritise investments, allocate resources effectively, and optimise the product portfolio.
Sometimes our beloved engineers can fell in love with their technical language.
Let me help you to understand your partners in crime better.
Here are 14 words/phrases engineers use plus a Product Manager readable explanation ๐งต
To make it explicit: pretty much every PM has been there. Not understanding the engineer, maybe too shy to ask for clarification. I can tell you: engineers are nice people! Ask them! They will help you and you earn trust by showing them you care.
Now some explanations ๐
๐๐ผ๐ฎ๐ฑ ๐๐ฒ๐๐๐ถ๐ป๐ด
Process of simulating user traffic and usage demands on a software product to ensure it can handle it at scale. Helps identify and fix performance issues, prevent crashes or downtime, and optimize product performance. It's like a stress-test!
What do a Product Manager and Rocky Balboa have in common?
Let's find out ๐
๐๐ฒ๐๐ฒ๐ฟ๐บ๐ถ๐ป๐ฎ๐๐ถ๐ผ๐ป: Both a product manager and Rocky Balboa are highly determined individuals who are willing to go to great lengths to achieve their goals. They do not give up easily and are willing to put in the hard work required to succeed.
๐ฅ๐ฒ๐๐ถ๐น๐ถ๐ฒ๐ป๐ฐ๐ฒ: Both a product manager and Rocky Balboa face a lot of obstacles and setbacks on their respective journeys. However, they are both highly resilient and are able to bounce back from these challenges and continue moving forward.