OKR Setting and Tracking

Objectives and key results that trace back to strategy, a weekly and quarterly tracking rhythm teams actually keep, honest scoring, and the lessons that make each cycle better than the last.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for OKR Setting and Tracking, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

♟️ Strategy & Leadership

OKR Setting and Tracking

Writing objectives and key results that connect teams to strategy, checking progress regularly and learning from what was missed.

  1. OKR readiness check before the first cycle
  2. One-page OKR house rules
  3. Choosing the OKR cycle length
  4. Tracing objectives to the strategy
  5. Baselines for every candidate key result
  6. OKR tool or spreadsheet selection
  7. Naming the OKR programme owner and coaches
  8. Pilot OKR cycle with two teams
  9. Grading scale and confidence conventions
  10. Weekly team OKR check-in
  11. Key result data refresh routine
  12. Monthly leadership OKR review
  13. Quarter-end scoring and retrospective
  14. Quarterly OKR drafting window
  15. Mid-quarter OKR health check
  16. Company OKR dashboard upkeep
  17. OKR change log and re-scoping rules
  18. Individual OKR updates in one-on-ones
  19. Cross-team dependency register for key results
  20. Writing objectives people can remember
  21. Outcome key results instead of task lists
  22. Leading and lagging key results practice
  23. Committed versus aspirational OKRs
  24. Running an OKR drafting workshop
  25. Coaching managers on OKR conversations
  26. Reading the OKR literature critically
  27. Pruning to three objectives per team
  28. Keeping health metrics out of OKRs
  29. Balancing top-down and bottom-up OKRs
  30. Decoupling OKRs from performance ratings and pay
  31. Fixing sandbagged and gamed key results
  32. Kill or keep decision for stalled key results
  33. Simplifying the OKR process after year one
  34. Cascade or alignment mapping for team OKRs
  35. Company OKR launch at the all-hands
  36. Annual OKR programme review
  37. First quarter-end scoring session
  38. OKR progress summary for the board pack
  39. OKR kick-off for a new financial year
  40. OKRs for a newly formed team
  41. OKRs for platform and shared-service teams
  42. Inheriting OKRs mid-quarter as a new manager
  43. OKRs through a reorganisation
  44. Asynchronous OKR check-ins across time zones
  45. Scaling OKRs from ten teams to a hundred
  46. OKRs alongside a fixed annual plan and budget
  47. OKR maturity assessment
  48. Analysing three years of OKR score data
  49. Internal OKR coaching guild
  50. OKR design for a multi-business group

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

OKR readiness check before the first cycle

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. OKRs fail most often in organisations that have no written strategy, no reliable numbers or no leader willing to sponsor them for at least four quarters. An honest two-week check of those three conditions tells you whether to launch now, fix a gap first, or start smaller with one team.

First tasks

  • Find the most recent written strategy or annual priorities document
  • Ask the intended sponsor whether they will chair four quarterly reviews in a row
  • List the five numbers the business already measures every week without effort
  • Write the launch, delay or pilot decision and share it with the sponsor

One-page OKR house rules

Every organisation that runs OKRs ends up with its own dialect: how many objectives, what a 0.7 means, who can change a key result mid-quarter. Writing those conventions on one page before the first cycle stops each team inventing its own and saves hours of argument at scoring time.

First tasks

  • Draft one-line definitions of objective, key result and initiative
  • Choose the limits on objectives per team and key results per objective
  • Write the rule for who may change a key result after the cycle starts
  • Publish the page in the shared drive and link it from the planning calendar

Choosing the OKR cycle length

Quarterly cycles suit fast-moving product teams, but a finance or infrastructure function may find twelve weeks too short to move anything meaningful. Deciding the rhythm deliberately, including whether to pair annual company objectives with quarterly team key results, avoids a cycle that is either frantic or forgotten.

First tasks

  • Put the budget, board and planning dates for the year on one page
  • Ask three team leads how long their main results take to move
  • Decide between quarterly, four-month and half-year cycles
  • Add every cycle start, mid-point and end date to the shared calendar

Make it yours.

Install OKR Setting and Tracking, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.