Implementation & onboarding

From kickoff to embedded. In 90 days.

Concierge implementation for teams rolling out OKRs Tool. Strategy alignment, admin setup, team workshops, training, and quarterly reviews — structured around a 90-day plan that makes OKRs stick past cycle one.

300+ teams onboarded 60% adoption guarantee Direct access to your implementation lead
4 phases
Strategy · Setup · Launch · Embed
90 days
From kickoff to measurable impact
7 / 30 / 90
Structured adoption reviews
Recorded
Every training session, ready to share
The four phases

A structured rollout, not a feature tour.

Most software onboarding focuses on configuration. Ours is built around strategy, ownership, and weekly habits — the things that decide whether OKRs survive cycle one.

1 Phase 1 · Pre-kickoff

Strategy — before we open a dashboard.

User imports and existing OKRs can be handled quickly. The more important work is defining what “good” looks like for the first cycle. Get this right and onboarding becomes the start of a disciplined execution rhythm. Skip it and you're configuring software that tracks disconnected goals.

If expectations are clear, onboarding becomes the start of a disciplined execution rhythm. If they're not, you're configuring software that tracks disconnected goals.
  • Success defined for 60–90 days out
    Agreed in writing before kickoff. What does “OKRs are working” look like by the end of cycle one?
  • Executive sponsor identified
    One leader accountable for the rollout. Without an exec sponsor, OKRs fade quietly rather than fail loudly.
  • Internal OKR champion
    Your day-to-day point of contact for the rollout. Usually the senior operator who's been pushing for OKRs.
  • Pilot vs full rollout decision
    Some teams launch company-wide on day one. Others pilot in one department first. We'll recommend based on your context.
  • OKR maturity assessment
    First-time OKRs? Coming off a failed Lattice rollout? Migrating from spreadsheets? Each starting point needs a different plan.
2 Phase 2 · Week 1

Setup — system reflects how you operate.

The admin session is less about exploring features and more about preventing confusion later. If scoring rules differ across teams or editing permissions are unclear, trust erodes quickly. Getting governance right upfront prevents delays mid-cycle.

After admin setup, we run a leadership strategy alignment session. This is where company-level OKRs get reviewed, refined, and locked in — before teams start writing their own. Technology cannot compensate for unclear direction; this session is where direction becomes explicit.

  • Admin configuration
    Permissions, cycle dates, scoring methodology, templates. Every choice documented so admins can manage independently.
  • Integrations connected
    Slack, Microsoft Teams, Jira, Asana, Google Workspace — whichever your team already runs in. OAuth-secure.
  • User imports
    Bulk user upload, manager hierarchy, team structure. No manual entry for orgs over 20 people.
  • Leadership strategy session
    Direct session with your leadership team. Company-level OKRs, alignment cascade, ownership rules, weekly cadence.
  • Internal launch plan
    A simple plan for how the rollout will be communicated internally. Templates included.
3 Phase 3 · Weeks 2–3

Launch — training on your real OKRs.

We run training once your team OKRs are drafted, so people learn using their own real goals — not dummy data. This is the single biggest change we've made to onboarding in the last two years, and it's why training sessions land differently here.

Live sessions are scheduled around your team's working hours — if you're spread across timezones, we run separate live sessions so nobody dials in at 2am. Every session is recorded and shared with anyone who misses it or joins later.

Updates should take minutes, not meetings. When updating OKRs feels heavy, engagement drops. When it feels straightforward, habits form.
  • Team workshops with team leads
    Strengthen objective language, tighten vague KRs, connect team OKRs to company priorities. By the end, every team has draft OKRs in the system.
  • Live end-user training
    Run on your real OKRs, not demo data. Scheduled to match your team's timezones. Recorded for anyone who misses it.
  • Guides & playbooks
    OKR writing guide, weekly check-in guide, manager playbook. Short, practical, available to everyone.
  • Structured go-live
    Treated as a deliberate launch, not a passive switch. Announcement template, clear expectations for first updates, optional facilitation of the first check-in.
  • First-week office hours
    Drop-in time during the first week of go-live. The first week sets behavioral precedent — early consistency makes the system feel real.
4 Phase 4 · Days 7–90

Embed — built-in review cadence.

Most OKR rollouts don't collapse — they fade. The 7-day, 30-day, and 90-day reviews exist specifically to catch the fade before it becomes terminal. Each review has a different focus, escalating from activation to quality to measurable impact.

At 45–60 days, we run a structured executive OKR health review with your leadership team. The goal isn't just to check progress — it's to assess whether OKRs are functioning as a leadership system or quietly becoming a side project.

  • 7-day adoption review
    An early diagnostic. Percentage logged in, percentage of OKRs updated, friction points, admin confidence. Most fade happens early.
  • 30-day health review
    Shifts focus from activation to quality. OKR clarity, scoring discipline, governance refinements, opportunities to deepen usage.
  • 45–60 day executive review
    Direct session with leadership. Alignment gaps, stalled objectives, scoring patterns, engagement across teams.
  • 90-day impact review
    Adoption data, outcome progress, opportunities to strengthen execution. Onboarding is complete when OKRs operate as a repeatable system.
  • Direct line to your implementation lead
    A single point of contact throughout. Email, video — whichever works for you.
What you get

Everything you need to run cycle two well.

Templates, recordings, guides, and a direct line. Built so the work outlasts the implementation lead.

OKR Kickoff Template
30-minute guided kickoff agenda, pre-filled company / team / individual OKR examples.
Recorded training sessions
Every live session is recorded. Shareable with the team, anyone who misses, and new joiners.
OKR writing guide
Short, practical. The patterns that separate outcome KRs from activity tracking — with examples.
Weekly check-in guide
Cadence, format, and language. Teams that check in weekly hit 43% more goals — this guide makes the habit stick.
Manager playbook
How to run team OKR reviews, escalate at-risk KRs, and use OKRs in 1:1s. Built for line managers, not HR.
Direct implementation lead
A single point of contact for the whole 90 days. Not a ticket queue — a human you can email directly.

Concierge implementation is included with the Expand plan. Launch and Scale customers get self-serve onboarding with guides, recordings, and email support — designed to get a team live without a call.

What makes it work

Five things every successful rollout has.

Strong OKR onboarding is not about configuration. It is about behavior change.

1. Strategic alignment before configuration
Company-level priorities are clarified before teams begin entering goals into the system. Skip this and the OKRs become disconnected wishlists.
2. Outcome-focused OKR writing
Teams learn to write measurable, meaningful key results that drive real progress — not activity tracking dressed up as outcomes.
3. A sustainable weekly review cadence
Clear, lightweight check-in rhythms so OKRs stay active throughout the cycle. 30 seconds per KR, not a 90-minute meeting.
4. Adoption measured with real data
Usage, updates, and alignment metrics monitored throughout the rollout to prevent silent drop-off before it sets in.
5. Ongoing executive involvement
Leadership stays engaged beyond kickoff. The 45–60 day exec review is the moment where OKRs either become a management system or fade into a side project. Without exec involvement, even well-written goals drift.
FAQ

What customers ask before signing.

When do you do user training?
Training runs after team OKRs are drafted — so people learn using their own real goals, not dummy data. This usually lands in week 2 or 3 of the rollout, after the leadership strategy session and team workshops.
How is user training delivered?
Live, interactive sessions scheduled around your team's working hours. If you're spread across timezones, we run separate live sessions so nobody's dialling in at 2am. Every session is recorded and shared so anyone who misses it — or joins the team later — can catch up.
Do we get a dedicated implementation lead?
Yes. On Expand, you get a single point of contact for the full 90 days. Not a ticket queue, not a rotating CS team — one human you can email or video with throughout the rollout.
How long does the full implementation take?
Most teams are live within 2 weeks. The full 90-day plan extends beyond go-live because that's when the work matters most. Implementation is complete when OKRs operate as a repeatable system — not when the software is live.
Can we pilot in one team first instead of rolling out company-wide?
Yes — and for larger or distributed teams, we often recommend it. A pilot in one business unit lets you validate the cadence and surface friction before scaling. We'll suggest the right path during the Strategy phase based on your team size, structure, and OKR maturity.
What if we've already started writing OKRs in a spreadsheet?
Most teams have. We can import existing OKRs in bulk and use Phase 1 to assess whether the current draft is strong enough to launch with, or whether the team workshops should refine them first. You don't start from scratch.
What happens if adoption is low at the 7-day review?
We diagnose the cause — it's usually one of three things: unclear ownership, weak check-in cadence, or KRs that are hard to update. We adjust and re-engage. The 60% adoption guarantee at 30 days means if it's not working, you get your money back.
Ready to roll out OKRs that stick?

From kickoff to embedded. In 90 days.

Book an implementation call and we'll walk through the four phases together, map them to your timeline, and answer anything you need before signing. No sales pitch, no slide deck — just a working session.

Book your implementation call
Concierge implementation included with the Expand plan