The OKR Starter Kit

Pre-built OKRs to help your team get started today

About

The OKR Starter Kit helps new Tability teams run their first OKR cycle with confidence.

If you’re unsure what your goals should be, this kit gives you ready-to-use OKRs you can start with immediately.

They won’t be perfect but that’s intentional.

The goal is to build the habit, learn what matters, and improve next cycle.

❌ Success is not hitting every key result. ✅ Success is running a full cycle with honest check-ins and clear learning.

What you'll need:

  • A Tabilityarrow-up-right trial or subscription (you can sign up for a 14-day trial)

  • That's it! You'll find templates that you can import in this guide


How a week with OKRs should run

OKRs only work if they’re part of a simple, repeatable rhythm.

  • Monday — OKR Review (30 min, 10:00am) Review progress, surface risks, and decide what matters this week.

  • Friday — Demo & Wrap-up (30 min, 3:00pm) Demo what shipped, share learnings, and close the loop.

Add this cadence to your calendar

Create both recurring meetings with one click.

[ Add OKR Meetings to My Calendar ] (Works with Google Calendar, Outlook, Apple Calendar, and Teams)


How to run the weekly meetings (non-negotiable)

Monday OKR Review — 30 minutes

Agenda

  • 20 min — Review KR status (green / amber / red)

  • 10 min — Decide 1–2 concrete actions for the week

Rules

  • Skim over green KRs (but don't ignore them)

  • Don't try to solve everything on the spot, plan initiatives in separate meetings

  • If everything is green, end early


Friday Demo — 30 minutes

Agenda

  • 20 min — Demo what shipped or progressed

  • 10 min — Share learnings, surprises, and blockers

Rules

  • Show real work, not slides

  • Learning beats polish


How this works

1. Pick a Starter Kit

Choose the kit that best matches where your team is today. Each kit contains pre-built OKRs you can import and run as-is.

Default path If you’re unsure: pick Product-Market Fit, import it as-is, and run it for one cycle.

2. Import the OKRs into Tability

Duplicate the Google Sheet, update the numbers where necessary, and then use the magic import feature to add your OKRs to Tability.

How to use the Magic Import

  1. Download a CSV export from Google.

  2. Go to Tability and create a new plan.

  3. From the options, click on Use magic import

  4. Select your CSV file

  5. Click on Import from CSV file

After a couple of seconds you should see all the OKRs added to your workspace.

Rules

  • Don’t rewrite everything

  • Rename only if something is clearly wrong

  • Do not aim for perfect OKRs

Momentum beats accuracy.

3. Assign owners

For each key result:

  • Assign one owner (not a team, not “shared”)

4. During the quarter: track progress weekly check-ins (this is the work)

OKRs are only as useful as the check-ins you write.

Bad check-in

“Still working on this. No major updates.”

Good check-in

“Activation increased from 22% → 26% after onboarding copy change. Still below target. Main blocker is drop-off on step 2. This week we're planning to _______”

5. End of the quarter: learn and reset (end of cycle, 60 minutes)

At the end of the cycle:

  • Run a retrospective

  • Identify what was unclear, wrong, or missing

  • Adjust or replace OKRs for the next cycle

Your second cycle will be significantly better than your first.


What will make this process successful

Read this once. It will save you weeks.

  • Commit to the weekly check-ins If you skip weekly updates or write vague check-ins, this process will not work.

  • Embrace a lean approach Weekly 30-minute reviews will help you refine execution faster than long monthly workshops.

  • Only track what matters Resist the temptation to add more OKRs for your first cycle. Business-as-usual work, KPIs and detailed plans live elsewhere.


If this happens, you’re doing it wrong

  • Your OKRs look like a series of tasks to execute

  • There's only one person that is updating all the OKRs for everyone

  • Using OKRs to evaluate individual performance

  • Skipping check-ins because “nothing changed”

  • Often skipping OKR review meetings because "we don't have time this week"

Fix these first before changing your OKRs.


Time investment (keep it lightweight)

  • Initial setup: ~30 minutes

  • Weekly cadence: 60 minutes total

  • End-of-cycle review: 60 minutes

If OKRs take more time than this, simplify.


What to do now

  1. Add the weekly meetings to your calendar

  2. Pick a Starter Kit

  3. Import it into Tability

  4. Run one full cycle before changing anything

That’s it. You’re officially running OKRs.

Last updated

Was this helpful?