The weekly check-in is the most common ritual in operating teams, and one of the least useful. People report status, agree to next steps, and the meeting ends with no decisions and a vague sense of momentum. A week later, the same conversation happens again. The fix is the close-out: a ritual built around finished things, not in-progress things.
The difference is what the ritual optimises for. A check-in optimises for reassurance: everyone leaves feeling informed. A close-out optimises for completion: everyone leaves knowing exactly what the team finished, what is stuck, and who is unsticking it by when. Reassurance decays by Tuesday. Completion compounds.
What a close-out looks like
Each person comes with one list: what was finished this week, and what got blocked. Not in-progress, not planned, not "almost there." Finished or blocked. Anything blocked gets an explicit unblock owner and a date. The meeting ends with a one-line summary of the team's actual progress this week.
The mechanics that keep it honest: the list is written before the meeting, in the same shared place every week, so the meeting starts from reading, not from performing. "Finished" means the definition of done was met and someone other than the author can use the thing; a pull request awaiting review is blocked, not finished. And the blocked list is the meeting's real agenda: each item gets sixty seconds, one owner, one date. Discussion beyond that moves to the people who actually need to have it. A disciplined close-out for a team of eight runs fifteen to twenty minutes.
Why it works
Finished work is the only work that creates value. Tracking finished work makes the rate of finished work visible, which makes the team uncomfortable enough to actually finish things. Closing things out is a skill, and the close-out ritual forces it to be practised every week.
Two second-order effects show up within a month. First, work gets scoped smaller: when the ritual only credits finished things, people stop opening three-week epics and start cutting them into units that can close inside a week, which is exactly the granularity fast teams run on. Second, blockers stop aging: the average blocker in a check-in culture survives three weeks because it is mentioned but never owned; in a close-out culture it survives days, because it has a name and a date attached in front of the whole team.
The failure modes
The ritual decays two ways. Softening: "mostly done" starts counting as done, and within a quarter the close-out is a check-in again. The guard is a hard rule that contested items count as blocked, never as finished. Theatre: the summary line becomes marketing for leadership rather than a factual record. The guard is keeping the archive of weekly summaries in plain sight; a quarter of honest lines next to one inflated one is self-correcting. If four consecutive weeks show almost nothing finishing, that is not a ritual problem, and the close-out has done its job: it has made a planning or scoping problem impossible to ignore.
What you stop doing
Status updates as performance. "On track" with no evidence. Standing meetings where nothing is decided. The close-out replaces all of them, in less time, with more signal.
Start this Friday: cancel nothing yet, just ask everyone to bring the two lists and run the format once. Teams that try it rarely go back, and the meetings it makes redundant cancel themselves within a month.