Communication · a life skill
Simple Meeting Recaps
one name and one day on every action
A meeting ends, everyone nods, and a week later nothing has moved, because “we'll look into it” left each person sure someone else would. A recap fixes that in five lines: what you decided, who does each thing, and by when. The rule that matters most is the smallest one: every action gets exactly one name.
- Easy to start
- Medium impact
- Learn it: 1 week
- Five minutes a meeting
Each person was alone in a room the whole time; only their belief about who else was listening changed. Darley and Latané, 1968.
The habit
Try it now.
-
Write it before the next thing starts
Five minutes straight after the meeting, while you still remember who said they'd do what.
-
Lead with what was decided
One line per decision, in plain words: “We're moving the launch to the 14th.” Not the discussion, just the result.
-
Put one name on each action
Not “we”, not “the team”, not “Sam and Priya”. If two people share it, one owns it and the other helps.
-
Give each action a day
“By Thursday” beats “soon”. If nobody knows yet, the action is to find out, and that has a day too.
-
Send it to everyone who was there
End with “Tell me if I got anything wrong.” A wrong name caught today is cheaper than a missed task next week.
Decided, who, by when, sent.
Example: “Decided: the newsletter goes monthly from June. Priya drafts the first one by May 20. Sam books the photographer by Friday. Still open: who signs off. Tell me if I got anything wrong.”
The owner check
Who's actually doing it?
Fill in what the meeting decided and what has to happen next. The check marks every action that belongs to nobody (a “we”, a team, two names, or a blank) and every one with no day, then writes the recap for you to send.
Start from an example
Actions
Actions with one owner and a day
Your recap
Nothing you type is saved or sent anywhere; the check runs on this page. It reads the owner box only, so it can't tell whether the person named actually agreed.
The study behind it
Everyone heard it, so nobody moved.
In 1968, John Darley and Bibb Latané put students in separate rooms to talk over an intercom, one voice at a time. Partway through, one of the voices (a recording) began to have what sounded like a seizure. The only thing that changed between groups was how many people each student believed were on the line.
Students who thought they were the only one listening went for help before the seizure ended 85% of the time. With one other listener, 62%. With four others, 31%. Each one could reasonably assume that someone else might already be doing it.
A meeting isn't an emergency, but the pull is the same. An action said to the whole room has as many possible owners as there are people in it, and each of them can reasonably think it's someone else's. A recap that names one person per action turns the room back into one listener.
The idea
Why it works.
Responsibility spreads thin across a group. When a task is said out loud to six people, each of them carries a sixth of it, and a sixth of a task feels like none. A single name concentrates it back into one person, who now knows it's theirs and knows everyone else knows too.
The recap also turns a spoken “I'll do it” into a written one, sent to the room. That's the small step that makes it easy to follow up later without sounding like you're checking up.
When it goes wrong
Habits that help.
- Name the owner in the room. “Sam, is that yours?” before you move on is easier than assigning it in the recap.
- Unowned is still worth writing. If no one took it, put it under “still open” so the gap is visible.
- Short beats complete. Decisions and actions. Skip the minutes of who said what.
- Reuse the same shape. When every recap looks alike, people learn to scan straight to their name.
Keep this going in the app.
HourLife turns these ideas into a daily system — goals, habits, focus, and reflection in one private place.
