Team Objectives – Accountability

Marty Cagan argues that empowerment in product teams must be paired with accountability, and that how accountability applies depends on the ambition of the objective. A team that misses a bold "Moon Shot" goal is largely expected to fall short, while missing a conservative "Roof Shot" or a high-integrity commitment is where accountability really matters. He suggests treating a substantial failure like a production outage: the team convenes peers, especially those affected by the miss, to examine root causes and what could have been done differently. Such post-mortems are uncomfortable but constructive, and they reinforce the value of taking commitments seriously and tracking progress closely.

01Key takeaways

• Expect misses on ambitious goals, but hold the team to account on conservative goals and firm commitments.
• Match accountability expectations to the stated ambition level of each team objective.
• When a team substantially misses, run a structured post-mortem with peers, including affected teams.
• Ask what could have been done differently, such as escalating early or having dependent teams make other arrangements.
• Take commitments seriously and monitor progress closely to surface problems before they become failures.

02Key sections

Empowerment Requires Accountability

Teams get space to find solutions to their assigned problems, but that freedom comes with responsibility for results.

Ambition Shapes Expectations

Failing a Moon Shot is largely expected, whereas failing a conservative Roof Shot or a high-integrity commitment calls for accountability.

Treat Failures Like Outages

After a significant miss, the team should review root causes with peers, especially those who were affected, as with an incident review.

Team Objective Post-Mortems

These reviews are uncomfortable but usually constructive, revealing whether earlier escalation or coordination could have prevented the failure.

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.