How to create a Check-In

Learn more about Check-Ins and Reminders and how they work together to build positive habits.

What is a Check-in

To record progress against a Key Result (either positive or negative!) you create a Check-In. This is a record of the current value, and a description of what's happened or changed since last time.

You can create Check-Ins from the Key Result detail page, or the Notification Centre (shown on every page).

Enter the current value and a comment.

When recording updates for Delivery KRs, set the value to your current estimated delivery date. Progress and "on track" or not is calculated using this value against the target date.

Further down the same page you can see the progress history for that Key Result. Whenever you record an update, the progress is calculated against the start and target values and drawn on a graph so you can see the KR move over time:

This is where the comments are super helpful. Describe what happened: what you did, what changed, why the metric has moved. Stakeholders can review progress and avoid coming to the Team to ask lots of questions because they have the answers already in front of them.

Multiple Check-In workflow

If you have lots of Check-Ins to complete, you can speed up the process by using the Check-In workflow, accessible from the reminder email you receive, or the Notification Centre.

It will step you through all your overdue Check-Ins one by one, allowing you to quickly enter the current value and comment for each Key Result. You can skip any if you're not ready to update them just yet.

Once you've completed all the Check-Ins, you'll see a summary of what you've done.

Check-in reminders

To help keep your OKRs on track, OKR Dash has multiple mechanisms to remind people to make Check-Ins on their Key Results.

First, on-site notifications:

Relevant owners will see a notification badge on every page, reminding them to make Check-Ins on their Key Results that are due for an update.

Notifications are cleared immediately when a Check-In is left and are updated twice per day in case OKRs, ownership or Teams have changed.

Second, regular email reminders:

Users responsible for Key Results will receive a summary email once per week about overdue Check-Ins. The day of the week is configurable. If there are no overdue check-ins, the user won't get an email.

Third, on-site nudges.

If a Key Result goes too long without a Check-In, anyone visiting the site will see an icon to remind them an update needs to be made.

Doing this creates a shared sense of accountability around making regular progress updates.

Workspace Administrators can configure the frequency and timing of reminders in Check-In Settings.

• Check-in frequency: how often you want Check-Ins, in weeks. This could be weekly, bi-weekly or monthly depending on how often you want progress updates.

• Day of week: which day of the week to send reminder emails. The default is Friday - so people write their Check-Ins ready for everyone to read on Monday morning.

Who gets the reminders?

We've developed a Hierarchy Of Accountability, to reduce the potential noise around reminders, and ensure that the right people get the right nudge at the right time.

These are the rules:

• If a Key Result has an owner, that User gets the reminder.

• If a Key Result has no owner, the Objective owner gets the reminder.

• If the Objective has no owner, any Team members assigned to the OKR get the reminder.

• If none of the above, no reminder is sent for that Key Result, BUT...

• If a Key Result goes too long without a Check-In, we start showing on-site nudges to everyone.