A 30/60/90 plan for a group-scale rollout: get everyone in, build the weekly cadence, and reach the second cycle with the habit intact, and without the rollout becoming one person's job to chase.
What this plan is built for
OKR rollouts start with energy and drain away by the second or third cycle, the point where the weekly cadence quietly stops and nobody decides to end it. This plan is built around that risk: the first 90 days get everyone in, make the check-in a habit the platform keeps running, and carry the momentum into cycle two.
Teams that run a weekly check-in complete 43% more of their OKRs — the one habit this plan is built to protect.
The OKR Benchmark Report →The plan
Three phases, each with one goal. Setup takes an afternoon; the rest is cadence.
Goal: everyone in, structure set, the first cycle live.
Goal: the weekly habit holds without anyone chasing it.
Goal: cycle two starts strong — the point most rollouts never reach.
SSO and SCIM are set up on a short, guided checklist — Microsoft Entra, Okta or any SAML 2.0 provider — with group-to-company mapping and roll-out mode so nobody gets an invite before the deployment is ready.
At 130 people, chasing everyone every week isn't sustainable. I needed a system where the tool did the chasing, not me.
Why it holds
Rollouts die when the weekly rhythm quietly stops. The platform keeps it running on its own: every owner gets prompted to update their key results, goals still sitting at zero are surfaced while there's time to act, and the weekly brief lands in the champion's inbox before anyone asks where things stand. The habit holds because the system carries the cadence, so it survives the weeks when the champion is heads-down elsewhere.
Start the rollout
Start a 14-day trial with no credit card, or talk to Steven about an enterprise rollout, SSO and SCIM provisioning, or a dedicated instance if your policy needs one.