Coaching – Decisions

Marty Cagan argues that in empowered product teams, the quality of decisions depends not only on logic and data but on how they are made, so that teammates, executives, stakeholders and customers can understand and support them even when they disagree. Good decisions rest on integrity, dependability, and accountability for results. Cagan lays out five behaviors he coaches product managers on: right-sizing analysis to risk and consequence, collaboration-based decision making that defers to the right expert, resolving disagreements through testing, transparency via written narratives, and disagree-and-commit. The approach matters because it builds trust and keeps teams aligned as they push decisions down from executives to the product team.

01Key takeaways

• Size your analysis to the risk and consequence of each decision, not to how interesting it is to investigate.
• Identify who is affected by a decision early and surface their concerns and constraints before deciding.
• Defer to the team member with the most relevant expertise: tech lead for feasibility, designer for experience, PM with stakeholders for business viability.
• When experts disagree, run a low-cost test or prototype to gather evidence rather than relying on opinion or escalating.
• For consequential decisions, write a narrative with an FAQ that anticipates objections so the rationale is transparent.
• Once a decision is made, commit to it openly, even if you disagreed, and focus on making it successful.

02Key sections

Foundations of good decisions

Good decisions are judged by whether they are timely and effective and whether leaders and stakeholders respect the rationale, even when they would have chosen differently. Integrity underpins this.

Right-size decision analysis

The amount of analysis should match the risk and consequence of a decision, and the people affected should be identified early. Novices often misjudge which risks deserve discovery time.

Collaboration-based decision making

Decisions should defer to the expert on each dimension: the tech lead for feasibility, the designer for user experience, and the product manager with stakeholders for business viability. Consensus, voting, and benevolent dictator models are rejected.

Resolving disagreements and transparency

When experts disagree, the team should run the cheapest appropriate test, such as a prototype, to gather evidence. For major decisions, a written narrative with an FAQ addressing objections keeps everyone informed.

Disagree and commit

After debate, the product manager must commit publicly to the chosen decision, explaining the reasoning and working to make it succeed rather than undermining it.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.