OKR Monthly Review Template

The OKR monthly review sits between the fast weekly check-in and the heavier quarterly grading. It is the altitude where trajectory becomes visible: a single week can mislead, but a month of movement tells the real story of whether an objective is on track.

When to use it

Run this once a month for teams or programs on quarterly cycles, or as the primary review rhythm for teams running longer annual OKRs. It is especially useful when weekly check-ins feel too granular to see the trend and quarterly grading feels too far away to course-correct.

Who attends

Bring the objective owners plus the leadership who can make resourcing and focus decisions, five to twelve people. The monthly cadence makes this a natural place for cross-team signals, so include people who can speak to dependencies beyond their own objectives.

How to run it

Open with a month of numbers so the trajectory, not a single data point, drives the conversation. Then climb to themes: what keeps moving, what keeps stalling, and what that pattern means. Use the bulk of the time for real decisions about where to invest and pull back. Share cross-team signals so the wider organization benefits, and close with a short list of what matters most next month. A monthly review earns its length only if it produces decisions a weekly check-in could not.

Facilitator tips

• Look at the month-long trend, not the latest single week.
• Rise from metrics to themes before deciding anything.
• Make this the place for resourcing and focus calls.
• Capture cross-team signals so the whole org benefits.

Common mistakes

• Repeating the weekly check-in at greater length with no new depth.
• Reacting to a single week instead of the monthly trend.
• Reviewing numbers without making any focus decisions.
• Keeping insights local when other teams needed them.

See the trajectory before it is too late to change it. Run it in OrgTP and keep monthly trends, themes, and decisions in one place.