Before you start
Company OKRs should already be drafted (typically from Quarterly Planning Step 2) so you can identify which ones need cross-team effort. Each team involved should have a named lead with authority to commit.
The 7 steps
7 steps · sequentialDefine the shared purpose
Ensure every team understands the overarching goal they are collectively working toward. If teams can't state the shared purpose in one sentence, you don't have one yet.
- Start with the company-level OKRs or strategic priorities
- Host a leadership session to identify which objectives require cross-team effort
- Clearly articulate the "why" — the business impact of achieving these goals
- Document this shared purpose in writing for reference
Identify stakeholder teams & owners
Map out who needs to be involved and exactly what role they play. "Who owns this?" should never need to be asked again.
- List all teams affected by the shared objective
- Identify one primary owner for each team — not a committee
- Define clear roles: lead, contributor, reviewer
- Make each team's involvement visible to everyone — no surprises
Host a cross-team kickoff meeting
Create a shared understanding of goals, timelines, and dependencies. Everyone in the same room, agreeing out loud.
- Present the shared purpose and expected outcomes
- Walk through each team's role and contributions
- Surface dependencies, risks, and potential conflicts early
- Agree on how success will be measured
Create the integrated plan
Build a single, coordinated execution plan. Not three plans — one plan.
- Combine initiatives from each team into one shared roadmap
- Map dependencies visually (Gantt chart, Kanban board, or simple table)
- Set milestones that require cross-team collaboration
- Assign a project manager or alignment lead to oversee progress
Establish communication cadence
Maintain alignment throughout execution. Frequency over duration — short syncs beat long monthly meetings.
- Schedule regular syncs (weekly or bi-weekly) with key owners
- Use shared dashboards or reports for visibility
- Create a single source of truth for documentation
- Encourage asynchronous updates to reduce meeting load
Monitor progress and resolve issues
Keep teams moving together and quickly address misalignment. Escalate fast, not gracefully.
- Track each team's contributions against agreed milestones
- Flag blockers early and escalate if needed
- Revisit dependencies if timelines shift
- Celebrate shared wins to reinforce collaboration
Conduct a cross-team retrospective
Capture learnings for future alignment efforts. Same teams, same goal next cycle? This retro is the difference between Round 2 going well and repeating the same mistakes.
- Hold a joint review session at the end of the cycle
- Discuss what worked well and what caused friction
- Document improvements for the next planning round
- Share insights company-wide if they have broader value
Outputs of this workflow
- A written one-sentence shared purpose every team can repeat back
- A stakeholder map with one named owner per team and clear roles
- An integrated plan showing every milestone, dependency, and owner in one place
- A regular communication cadence — weekly or bi-weekly, scheduled, with format defined
- A retrospective document capturing lessons for next cycle
Manage cross-team work inside OKRs Tool.
Shared KRs, dependency tracking, cross-team dashboards, and automated nudges — all connected to your OKRs. Free for up to 5 users.