The Weekly OKR Check-in: Turning Data into a Decision

Fifteen minutes, once a week, on the same day. The check-in reads your board, scores the four KRs and makes you choose what changes.

OKRs fail quietly. Nobody abandons them; they simply stop being looked at, and three
months later somebody opens the spreadsheet to write the quarterly report. The check-in
is the ritual that prevents that, and it costs fifteen minutes.

What it does

Step 10 of the menu — verificar_krs.py — reads your board and calculates
the four Key Results without asking you anything. It prints each one with a traffic
light, compares this Sprint with the last, and tells you what is missing.

The conversation, not the number

The step also hands you a prompt with the KR report already inside it. You paste it
into your AI and it does the check-in with you: for each KR, the confidence of hitting
the target and why, then one to three concrete actions for the week.

One to three. Not ten. A check-in that produces ten actions has produced none.

Reading confidence

• Green — 70% or better. Keep going; do not change the plan.
• Amber — 40–69%. Something specific needs to change this week.
• Red — below 40%. Either the approach is wrong or the target was. Both are
  findings; neither is a failure.

Make it the same day

Friday afternoon works for most people: the week is visible and the next one has not
started. What matters is not which day, but that it is always the same day. A
ritual you reschedule is a ritual you are ending.

Next

Lesson 18 closes the course: the final presentation, the lessons learned, and your certificate.

Agile Together is a free course. The package — scripts plus a portable Python — is a single download: get the course package. You install nothing.

Go deeper in the book

Scrum in Action

Three real Sprints on a project of your own, from the OKR to the final presentation, with the AI you already use at every event.

See the book — US$ 5.99 →