Check-In and Check-Out

It looks like the softest practice in this whole body of work, and it is the one most often dropped when a meeting is busy. It is also the practice that most reliably prevents the two most expensive failures a group has: conflict that comes out sideways, and burnout that nobody sees coming.

Two minutes at each end. Here is why it earns them.

What a check-in is

Going around the group, one at a time, uninterrupted, each person says where they actually are.

Not a status report. Not what they are working on. Where they are.

"I'm here. I slept badly and I'm short on patience, so if I'm blunt today it isn't about anyone in this room."

"I'm distracted. My mother's test results come this afternoon."

"I'm good. Genuinely looking forward to this one."

That is it. No fixing, no responding, no advice. The next person goes.

Why it is not a nicety

People arrive carrying things, and it comes out sideways. Someone who is grieving, exhausted or angry about something outside the room will bring that into the objection round, into a code review, into a disagreement about scheduling. It will present as being about the work, and the group will treat it as being about the work, and everyone will be confused about why the conversation got sharp.

Named at the start, it stops being a distortion and becomes context. The group can hear a blunt comment as tiredness rather than as an attack. This one effect is worth the whole practice.

It gives you a read on load. This is the function nobody designs for and everyone needs. In a self-managing group, nobody is checking whether you are drowning. The whole point is that no manager is watching. Check-in is often the only structured moment where somebody would notice that a person has said "I'm exhausted" in a mild voice four weeks running.

Which is why someone should be listening across time, not just in the moment. See What Replaces the Manager for why "noticing overload" needs a home.

It slows the group down for two minutes, which matters more than it sounds. People arrive from other contexts at speed. Without a transition, the first ten minutes of the meeting are spent arriving anyway, less usefully.

It practises saying true things in a low-stakes moment. A group where people routinely say "I'm frustrated" about small things can say it about big things. A group that only speaks carefully will not surface a real problem until it is a resignation.

What a check-out is

At the end, one round: how was that.

"Useful. I got what I needed on the budget thing."

"I'm frustrated. I don't think we actually decided anything about handovers and that's the third time."

"Fine, but I was quiet because I didn't feel like there was room."

Check-out is where you find out that your process is failing someone. That second and third response are the entire value: without a check-out, that frustration goes home with the person, and comes back next month as disengagement.

It also closes the meeting deliberately. Meetings that trail off leave people unsure what was decided.

How to run it

Everyone speaks. Every time. The moment it becomes optional, the people who most need to say something will pass. Include the quiet person, the founder, the visitor.

No responding. The hardest rule. Someone says something difficult and the instinct is to help. Do not. It converts a round into a conversation, the remaining people never speak, and the person who shared learns that sharing costs the group twenty minutes.

If something needs following up, do it after, one to one. Facilitator's job to notice.

Short. One or two sentences. If your check-in takes fifteen minutes with eight people, it has become therapy, and people will start resenting it.

"I pass" is allowed, but noticed. Someone passing three weeks running is a signal, worth a private conversation.

Do it even when time is short. Especially then. The meeting where you skip check-in to save two minutes because everyone is stressed is exactly the meeting where everyone is stressed.

Where it goes wrong

It becomes a status update. "I'm here, I finished the API work, today I'm on tests." That is a stand-up, and it is worth nothing at the start of a governance meeting. If this creeps in, change the prompt: not "how are you", but "what are you bringing into this room that isn't about the work?"

It becomes performance. Everyone says "good, busy, fine" in rotation. Usually means the group is not safe enough for the honest version yet, and the fix is not a better prompt. Someone with standing goes first and says a real thing. Once. That is usually enough.

It becomes therapy. The opposite failure. One person uses it every week at length. Kind to allow, corrosive to the practice. The facilitator holds the boundary: "that sounds like it needs more time than the round has, can we talk after?"

Only doing check-in. Check-out is the one that improves your meetings, because it is where the feedback about the meeting lives. It is also the one groups drop first, because by the end everyone wants to leave.

Doing it with no one holding it. Needs a facilitator to open, hold the no-responding rule, and close. See Governance and Operations Meetings.

What good looks like

Somebody says "I'm at about 70% today, my kid was up all night" and nobody makes anything of it, and later, when they are short in a disagreement, everyone reads it correctly.

Somebody says at check-out "I don't think that decision was actually made" and it gets fixed in the next two minutes instead of festering for a month.

And somebody notices, out loud, that a colleague has checked in tired for a month, and asks them about it privately, before it becomes a resignation.

Try this week

Add a check-out to your next meeting, even if you have no check-in. One round, one question: how was that.

Then do the thing that makes it real: act on what you hear. If someone says the meeting did not decide anything, decide something. If a check-out changes nothing twice running, people will stop telling you the truth in it, and you will have lost the instrument.