The Daily Check-inDaily Check-inA 15-minute daily ritual where the team surfaces reality and unknowns rather than reporting status. is the team’s pulse. It answers one question every day: are we on track for the weekly delivery, and if not, what changed and what do we do about it? It is the smallest ritual and the one teams most often turn back into a status meeting — resist that. Its job is to surface reality, learning, and blockers, not to report progress to a manager.

Purpose

Make the day’s reality and the day’s unknownsUncertaintyWhat the team does not yet know — sized and tracked deliberately rather than hidden inside estimates. visible to the whole team, fast, and confirm the team is still pointed at the week’s plan.

Cadence

Daily, 15–30 minutes. It is a hard time-box: anything that needs more than a few sentences belongs in Collab Time.

Attendees

The Team. No one presents to anyone; the Daily Check-in is for the team, by the team.

The Check-in is prepared asynchronously. Before the meeting, each person fills in their own sections of the Check-in artifact. The running order is fixed, and the team works through it top to bottom.

Running order

1. Is everyone prepared? Ask up front. If not, give everybody five minutes to fill in their sections before starting — a prepared Check-in is short and sharp; an unprepared one drifts into discussion and runs over.
2. Questions / FYI. Answer the open questions; mention the new FYIs.
3. Lessons Learned. Go through them together and, where a new insight warrants it, plan an action on the spot.
4. Things to Figure OutThings to Figure OutEach person's one thing to figure out today, framed as a Why/How/What/When question that resolves into a Lesson Learned. (TFO). Each person commits to the one thing most important to figure out today.
5. Final check. Two questions before signing off: are you still on track for delivery this week — and if not, how will you get back on track? Don’t close the Check-in until everyone has at least one TFO.

What goes in each section

• Questions / FYI — holidays, disruptions, good or bad news; questions that can wait; questions that need several people’s input; things to raise in Collab Time.
• Lessons Learned — what you’d normally save for a retro; useful links, docs, or blog posts; surprises, good or bad, that came out of your TFOs; the result of any TFO that reduced an Uncertainty. Every completed TFO produces a lesson; that is the Learning rateLearning rateThe speed at which a team turns uncertainty into knowledge — the method's true KPI, driven by the expectation→change→review loop. loop in action.
• Things to Figure Out (TFO) — “What are you going to figure out today?” is a better question than “What will you do today?”, because it splits a big multi-day task into a single day’s learning. A plain todo (“Release Y”) is fine when that genuinely is the thing.

In the meeting itself, the team goes through the artifact in order and only talks about what needs talking about. The week’s plan stays in view as the backdrop — eyes on the prize — so each TFO visibly moves the team towards what it committed to demo this week. New unknowns are pushed onto the Uncertainty ListUncertainty ListThe team's living list of open unknowns — sized 1/3/5, phrased as questions, reviewed daily and in planning, chipped away each week. rather than debated in the room.

Outputs

• A documented daily focus — one TFO per person.
• Surfaced blockers and what is being done about them.
• Captured lessons, feeding the Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics. and the ApproachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success..
• A team still aligned on the week’s delivery.

Common pitfalls

• Deep discussions in the room. Problem-solving belongs in Collab Time, not the Check-in.
• Not preparing. An unprepared Check-in becomes discussion-heavy and runs over.
• Skipping the TFO. Without it there is no daily commitment and no lesson to capture tomorrow.
• One person typing for everyone. When a single person administers everyone else’s TFO and lessons, accountability evaporates.