Writing good check-ins!
A check-in is a formal update which should include a crisp yet well-thought out update on an OKR.
What Makes a Good Check-In?
A well-written check-in should include:
What’s working / what’s not working: A brief update on progress and challenges.
Root cause analysis: Clear reasons if progress is not moving as planned.
Action items or solutions: Steps being taken to bring the OKR back on track.
Support required: Any help needed from stakeholders or leadership to move forward.
Consistent, thoughtful check-ins help improve alignment, accountability, and execution across teams.
Status guide:
The following status tags are available to give users a quick understanding of the current state of an OKR based on the latest check-in. These tags help teams instantly assess progress and identify where attention is needed.
Not-Started
No work is expected at the moment
On-track
A high possibility of achieving the OKR as expected
Needs Work
A risk of achieving the OKR on time; Low confidence for the rest of the quarter
Off-track
An OKR that is behind and has serious danger of achievement on time
Dropped
This has been postponed for later
Achieved
At the end of the quarter when goals are met
Not-Achieved
At the end of the quarter when goals are missed (delayed achievement or quality is un-satisfactory)
Last updated