Set OKRs that fit together across teams
Draft company objectives, branch each into measurable key results and team goals, and catch the ones that compete for the same people before the quarter starts.
Start from a template
An OKR template you can clone. Set your theme, draft each objective, and work out its key results in the branch under it.
How it works
Describe your company, its stage and the quarter you are planning. Each objective gets its own branch, and the key results and team goals for it sit underneath.
-
Draft objectives. Ask for candidate objectives that fit your situation. Keep the ones you agree with as branches and delete the rest.
-
Make key results measurable. Under each objective, ask for key results with a number and a date. “Improve onboarding” becomes “cut time to first value from 14 days to 5”.
-
Break them down by team. Under each key result, add a branch for each team that contributes to it, such as engineering, sales or customer success. Every team goal stays under the company objective it serves.
-
Check for conflicts. A branch only sees the nodes above it, so it cannot compare key results in other branches. Ask Milo, the assistant built into the map, which reads the whole map, whether any two key results need the same team in the same quarter. Milo is on the Promptmaps and Lifetime plans.
One view from company to team
OKRs set team by team in separate documents drift apart, and the conflicts tend to surface mid-quarter. On the map, every team goal sits under the company objective it serves. A crowded map is a sign you have committed to more than the team can deliver, and you can delete branches until it fits.
Example
Say you run a 50-person SaaS company and are planning Q3. The map gives you three objectives. Under retention, two key results, “ship the onboarding redesign” and “get P0 bugs to zero”, both need the same front-end team. You keep the redesign in Q3 and move the bug target to Q4.