OKR Alignment Meeting Template

The OKR alignment meeting is where individual teams stop optimizing in isolation and start pulling together. Drafting produces good team-level OKRs; alignment makes sure they add up to the company goal instead of quietly working against each other.

When to use it

Run this after teams have drafted their OKRs but before the cycle is locked. It is essential whenever multiple teams share goals, depend on each other, or compete for the same resources. Skip it and you discover the conflicts mid-cycle, when they are far more expensive to fix.

Who attends

Bring the team leads and cross-functional owners who can speak for and commit their teams, six to fifteen people. Each attendee needs the authority to renegotiate scope on the spot, otherwise alignment becomes a round of note-taking followed by another meeting.

How to run it

Anchor on the company objectives so every team is measured against the same direction. Have each team present its draft, then deliberately hunt for dependencies and conflicts rather than hoping they surface. Work through them in the room: renegotiate scope, resequence work, and resolve duplication until teams truly agree, not just nod. Close by confirming the reconciled set and naming owners for every shared dependency. Real alignment is uncomfortable, because it forces trade-offs into the open.

Facilitator tips

• Keep the company objectives visible as the reference point throughout.
• Actively hunt for dependencies; do not wait for them to surface.
• Resolve conflicts live, not in a follow-up that never happens.
• Assign a named owner to every cross-team dependency.

Common mistakes

• Letting teams present in isolation with no reconciliation.
• Ignoring dependencies until they break mid-cycle.
• Inviting people who cannot commit their teams to changes.
• Declaring alignment when teams have only stopped arguing.

Make sure every team rows in the same direction. Run it in OrgTP and keep cross-team objectives and dependencies aligned all cycle.