As product managers and product owners, we make a myriad of decisions – from shaping the product strategy and determining the product roadmap to deciding the detailed functionality of our products. But do we make all these decisions effectively? And do we secure the necessary buy-in? This post discusses five common decision rules and explains when to apply them
Decisions, Decisions
If you want people to move together in the same direction, you need to give them a clear indicator if a decision has been made: you should clearly state how the decision is reached and whose input is required
- You should apply the right decision rule
Learn More
Facilitator’s Guide to Participatory Decision-Making
- Sam Kaner et al.
- Great advice on building sustainable agreements
- Learn more about effective decision-making and using the right decision rule by attending my product leadership workshop
- You may also find it beneficial to read the book “The Facilitators’ Guide: A Practical Guide”
Decision Rules
Each decision rule has its benefits and drawbacks
- No single approach is always appropriate
- Make sure you involve the right people in the decisions
- As a rule of thumb, engage with the players – the stakeholders with an interest in your product and the ability to influence its success
Majority Vote
Most of the people required to decide agree with the solution
- Applying this rule creates a win-lose situation that can leave the minority frustrated and unwilling to support the decision
- Use this rule only if the stakes are not high
- You would be better off using consensus or product manager decides after discussion
Consensus
Deciding by consensus means that everyone required to make the decisions agrees with the proposed solution or idea
- This creates strong buy-in and shared ownership, and leverages the collective creativity and knowledge of the people present
- The drawback is that it can take a comparatively long time to reach consensus within a group
Product Manager Decides without Discussion
If you are certain that the stakeholders will agree with your decision and if you don’t need their input or advice, then just decide.
- Use consensus or product manager decides after discussion instead. If you use the approach for important decisions that have a significant impact on others, people may regard you as an autocratic leader and undermine or oppose your decisions
Product Manager Decides after Discussion
Discuss an idea or solution with the right people and poll them for their opinions
- Once enough discussion has taken place or the time is up, you decide
- The benefit of this approach is that it involves people in the decision-making process, but you retain control over the decision.
- It can also speed up the process by limiting the time spent to look for an inclusive decision
Delegation
Delegate a decision if others are better qualified to decide or if your input is not needed
- This helps ensure that the best qualified people decide, and it frees up your time
- When applied correctly, it also sends a positive signal to the appointed decision makers: it shows that you trust them and value their expertise
