Team Objectives – Commitments

Cagan argues that while most team objectives should be aspirational, some situations require high-integrity commitments: deliverables with dates leaders can rely on, driven by trade shows, contracts, tax deadlines, marketing campaigns, or dependencies on other teams. Such commitments are only credible when the team has done enough product discovery to judge whether a solution is valuable, usable, feasible and viable. Unlike ambitious objectives, these commitments are binary, tracked explicitly and separately from key results, and they build trust with leadership. Cagan warns that they must remain the exception, since too many turn objectives back into a reformatted roadmap.

01Key takeaways

• Reserve high-integrity commitments for true external or dependency-driven deadlines, not routine planning.
• Only commit to a date after discovery confirms value, usability, feasibility and viability.
• Track committed deliverables separately from key results, since they are binary outcomes.
• Flag risks at the first sign of trouble and ask for help early rather than hiding slippage.
• Use commitments to build leadership trust, but guard against letting them crowd out outcome-based objectives.

02Key sections

Why high-integrity commitments exist

Businesses sometimes must deliver something by a fixed date tied to events, contracts, or campaigns. Leaders often fall back on command-and-control roadmaps because they need predictable dates.

Making dates leaders can count on

Empowered teams must provide reliable dates when needed. Running discovery in parallel with delivery makes high-confidence dates achievable, provided the company waits for discovery to finish first.

Investigating before committing

Before promising a date, the product trio should validate the solution through discovery and often build a feasibility prototype so engineers understand the scope.

Tracking and trust

These commitments are binary, not measured by ambition, and are tracked explicitly, sometimes with CTO sign-off. Raising problems early is expected.

Keeping them the exception

High-integrity commitments should be rare; if they dominate, objectives degrade into a list of deliverables and dates.

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.