The Power of Minimal Robust Action in Product Management
Advice on how to be biased for action while delivering impactful product.
As a "Product in Action" girl, it's fitting that my inaugural Substack post focuses on action. After all, we Product Managers are tasked with prioritizing actions - not just our own, but our entire team's. It's a weighty responsibility that begs the question: When is it time to act, and when do we need more research?
Balancing Action and Research
We often hear about "bias for action" as a common job requirement. However, acting on insufficiently vetted ideas can lead to:
Failed products
Wasted effort
Subsequent grief
So, what's a PM to do?
Introducing Minimal Robust Action (MRA)
My solution? Minimal Robust Action (MRA) - small, impactful steps that bring us closer to our goals. For many of us, the goal is hitting the sweet spot in the product trinity:
The 'Robust' in MRA
The 'robust' in MRA acknowledges that time and momentum are crucial. We need to make sure we make sizeable progress even in small steps. Else we are at risk of loosing steam.
Prioritization Tactics
We should prioritize pain points that are
Severe, and
Impact customer segments that deliver the most business opportunity, and
We are capable to address, and
Are aligned with the overall strategy (I do want you to keep your job!)
What Are We Validating?
We're validating that there's indeed an overlap:
We can address widespread, painful issues
We can create a sustainable business model
We can actually build the solution
How Are We Validating?
Competitive and market research (so yes, research is also action as long as it does not paralyze you - more on that below)
User research
Experiments (e.g., fake ads or A/B tests)
Design sprints
MVP
Choosing the Right Method
Each situation is unique, and what's available to one team might not be to another. Brainstorm with your partners early and often about:
How to answer existing questions
Which methods will provide the most learning in the shortest time
Pro tip: Don't shy away from design sprints. Despite scheduling challenges (you need to find a week to set everything else aside to be on the sprint), they often provide the most learning in just one week.
Overcoming Obstacles
A common obstacle to fast action is the belief that engineering teams should be building 100% of the time. Here is what I often see: PMs are trying to shoulder all of the validation saving UX time to only user testing and specking for build and engineering - for building only. The truth is that PM alone cannot deliver the action that’s robust enough. This often results in:
Ideas dying on the vine waiting for validation
Poor validation leading to mediocre products
To deliver impactful products, cultures need to shift to support fast and robust discovery.
The Takeaway
Remember: Take action, but make it as small and robust as possible and make sure you are supported to do it fast. Your product's success depends on it. What do you think about product discovery and minimal robust action? Share your thoughts in the comments below!