Team Objectives – Summary

Marty Cagan argues that team objectives are the mechanism for assigning work to empowered product teams in a way that still executes the company's product strategy. Product leadership chooses which problems matter and which team tackles them, but the key results should come from the team, since accountability only works when teams shape the solution. Leaders must also be explicit about the ambition level they want (moonshot, roofshot, or high-integrity commitment) and recognize that teams have ongoing operational work beyond objectives. Cagan stresses that the essential practice is a knowledgeable leader sharing strategic context and success measures in conversation, with formal tools like OKRs being secondary.

01Key takeaways

• Assign teams problems to solve and share the strategic focus and insights so they can decide well.
• Let teams write their own key results, since accountability requires ownership of the solution.
• Be explicit about whether you want a moonshot, a roofshot, or a high-integrity commitment.
• Assign the same hard objective to several teams, or pair teams with complementary skills, when the problem is uncertain.
• Refresh objectives quarterly and treat mid-quarter changes as exceptions.
• Account for business-as-usual work when setting expectations for objective capacity.

02Key sections

Empowerment through problems, not solutions

Teams should be assigned problems with the strategic focus and insights needed to decide well, then given space to solve them. Volunteering is welcomed but not always possible.

Who decides what and who writes the key results

Leaders choose the objectives and assign teams, but the teams must author the key results, with back-and-forth focused on whether the investment is worth the risk.

Overlapping and collaborative assignments

Multiple teams can pursue the same objective in different ways, or collaborate across complementary skills, which suits hard problems where outcomes are unpredictable.

Setting ambition and cadence

Teams need to know whether to aim for a moonshot, a roofshot, or a firm commitment, and objectives are normally refreshed quarterly, with mid-quarter changes as rare exceptions.

Keeping it in perspective

Objectives sit alongside business-as-usual work, and the core practice is the leader-team conversation rather than any particular framework.

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.