WP-13
The 90-second daily check-in
Fill it in on screen and save a PDF · Read Chapter I · Build your Workpaper Suite
This check-in puts Pillar IV (“Tune how you send and receive”) to work, with a nod to Pillar V, Notice the quiet incentives. In you: you take a quick reading of your own day. Between you and others: small daily corrections keep you in tune, and a daily thank-you keeps things steady.
Purpose: a short, easy check-in you do every day. The idea comes from electronics, where a small circuit keeps two signals in step by making constant small corrections instead of occasional big ones. Here it becomes a daily habit that keeps the "frequency drift" described in Chapter I from building up into a squeal.
Why small and frequent beats big and rare
That circuit doesn't wait for two signals to drift far apart and then yank them back into step. It makes tiny corrections all the time, so the drift never builds up. At home, it works the same way: a 90-second daily check-in heads off most of what would otherwise become a 45-minute weekend argument.
The daily loop (about 90 seconds)
Pick the same moment each day: after dinner, before bed, the start of a shift, whatever is realistic. Each person answers these out loud, in one sentence each:
- Load: "Today I was at about [low / medium / high] capacity."
- Appreciation: "One thing I appreciated about you (or us) today was ___." On a team or in a shared house, name the person you're thanking. Specific beats general: name the thing and the moment. Research on everyday connection suggests these small moments of noticing matter as much as fixing what went wrong. See Turning Toward.
- Friction: "One small thing that didn't feel great today was ___." (Optional — skip if there's nothing.)
- Ask: "One thing that would help tomorrow is ___." (Optional.)
No debating, no solving, no arguing back. One of you talks, and the other just listens. Anything that needs a real discussion gets saved for the weekly closing, your short end-of-week review (Chapter V). Don't argue it out in the 90 seconds.
For a team, or for housemates
A team: a 5-minute stand-up, at the start or end of the day. Same questions, one sentence each, going round once: load (low, medium or high), one thank-you to someone on the team, one thing that got in the way (a process, not a person), and one thing that would help tomorrow. Anything bigger gets its own follow-up. A "high" is useful information, never a complaint, and nobody's answers go into a review. More on At work.
Housemates: once or twice a week is plenty, at a time you're all home, like Sunday evening. Same questions. Keep the thing that didn't feel great about a shared thing (the bins, the noise, the bills), never someone's character. Jobs that keep slipping go on One owner per job.
The weekly catch-up
Once a week, when you do your weekly closing:
- Skim the week's daily loop notes for anything that repeated more than twice.
- A sore spot that keeps coming up moves to the job list (WP-03) or Say it so it lands (WP-09), instead of staying a low-level irritation.
Failure mode to watch for
If the daily check-in starts being used to deliver criticism ("well, since we're doing check-ins...") instead of a plain update, you'll both start avoiding it. And avoidance causes exactly the drift this check-in is meant to prevent. Keep the daily version to plain facts. Save any judgments about how things are going for the weekly catch-up.
When a repeated sore spot does need a real conversation, don't stretch the 90 seconds. Use Check-ins instead: pick a time, wait until you're both settled, and acknowledge each other before arguing back. Test the one sentence you plan to open with in the Chat analyzer first. The daily check-in stays a quick update, not a hearing. Don't let either one turn into overload, blame, or criticism of the person. Stick to one topic. If a second one shows up, set it aside for later. The ground rules explain how to say you're not against them, and how to stop before things spike.
☐ We’re agreed on this. Look at this again on: ____________