Team Objectives – Ambition

Once leaders assign a problem to a product team, they must also signal how ambitious the team should be in its discovery work. Cagan frames objectives as bets that spread risk across a portfolio, ranging from low-risk optimization to high-risk breakthroughs. He distinguishes ambition from effort or urgency, which are driven by culture and cash position. Leaders can assign a roof shot, a moon shot, or any level in between, and may run several teams at different risk levels on the same problem. Being explicit about the intended confidence level prevents the organization from mistaking a long-shot bet for a sure thing.

01Key takeaways

• Set the ambition level explicitly when assigning a problem, because it shapes how the team should do discovery.
• Treat objectives as bets and balance low-risk and high-risk efforts across your portfolio of teams.
• Keep ambition separate from work ethic or urgency, which depend on culture and finances.
• Use roof shots for reliable, incremental gains and moon shots when a breakthrough is needed.
• Consider assigning several teams different approaches to a critical problem to hedge risk.
• Communicate each objective's confidence level across the organization so expectations stay accurate.

02Key sections

Why ambition must be set explicitly

Leaders should tell teams how bold their discovery work should be, since the choice between safe and ambitious bets changes the work itself.

Ambition is not effort

Work ethic and urgency reflect culture and financial conditions, not the level of risk a team is asked to take.

Roof shots and moon shots

A roof shot is a conservative, likely win through optimization, while a moon shot targets a large, risky leap such as a 10X improvement.

Managing a portfolio of risk

Leaders should spread bets across teams and levels of ambition, including intermediate ones, rather than picking from only two extremes.

Communicating confidence levels

The intended ambition of each key result should be broadly communicated so no one mistakes a high-risk goal for a high-confidence one.

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.