A meeting doesn't live on in your calendar. It lives on in memory — and memory is a shameless editor. It cuts most of the footage, keeps a few frames, and then presents the result as if it were the whole film. Ask someone on Thursday how Monday's planning meeting went and they will not replay sixty minutes for you. They will give you a verdict: fine, brutal, a waste. That verdict was assembled from almost nothing — and one of the biggest pieces of it is how the meeting ended.
This is not a metaphor. It is one of the most replicated findings in the psychology of judgment, and it suggests that the most leveraged minutes of any meeting are the ones we habitually throw away: the last five.
The Two Selves in Every Conference Room
Daniel Kahneman, the psychologist whose work on judgment earned a Nobel Prize in economics, drew a distinction that turns out to matter enormously for how organizations run: the difference between the experiencing self and the remembering self. The experiencing self lives through each moment as it happens — the tedium of minute twelve, the small victory at minute twenty-five, the creeping dread as the clock runs out. The remembering self is the one that later tells the story, and it is the remembering self that makes decisions. It decides whether the offsite was worth it, whether the weekly sync "works," whether to accept the next invite or quietly decline.
Here is the uncomfortable part: the two selves disagree, systematically. The remembering self does not average the experience. It does not weight every minute equally. It builds its verdict almost entirely from two data points — the most intense moment, and the ending.
The Experiments Behind the Peak-End Rule
The evidence comes from studies that sound almost mischievous in their design. In a 1993 experiment, Kahneman and his colleagues Barbara Fredrickson, Charles Schreiber, and Donald Redelmeier asked participants to hold a hand in painfully cold water. In one trial, the immersion lasted sixty seconds. In another, it lasted those same sixty seconds plus an additional thirty seconds during which the water was warmed slightly — still unpleasant, just less so. Objectively, the second trial contained strictly more discomfort. Yet when participants were asked which trial they would rather repeat, most chose the longer one. The gentler ending had rewritten the memory of the whole episode.
Redelmeier and Kahneman then took the finding out of the lab. In a 1996 study of patients undergoing colonoscopies — at the time, a considerably more uncomfortable procedure — patients reported their pain in real time throughout. Afterward, their overall evaluations of the experience tracked two things: the worst moment and the final moments. The actual duration of the procedure barely registered in the memory at all. Researchers call this duration neglect, and together with the outsized weight of peaks and endings, it forms what is now known as the peak-end rule.
Read those findings again with a conference room in mind. Duration neglect means the remembering self doesn't much care whether the meeting ran thirty minutes or ninety. The peak-end rule means it cares intensely about the sharpest moment of friction — and about exactly how things felt when everyone stood up.
The Way Most Meetings Actually End
Now consider how meetings typically end, because the pattern is remarkably consistent. The agenda is two-thirds finished. Someone glances at the clock and says, "We're almost out of time." The last item gets compressed into a frantic ninety seconds. A decision that needed care gets deferred — "let's pick this up next week" — while half the room is already reaching for laptops, mentally rehearsing the meeting that starts in zero minutes. Nothing is summarized. Nothing is closed. The final sensory impression is of scramble and incompleteness.
By the logic of the peak-end rule, this is the worst possible design. A meeting could contain fifty minutes of genuinely good collaborative work, and the memory of it will still be tinted by those final chaotic moments. The verdict gets filed as another meeting that went nowhere — not because the work went nowhere, but because the ending did. And there is a practical casualty too: decisions made at minute twenty get buried under the rubble of minute fifty-eight. What was never said aloud at the close was never consolidated, and what was never consolidated quietly evaporates.
How to Engineer a Better Ending
The good news hiding inside the peak-end rule is that endings are cheap to fix. You do not need to redesign the whole meeting; you need to protect its final minutes and give them a job.
Make the close an agenda item. Stop discussing new content five to ten minutes before the scheduled end — not as a soft aspiration but as a hard boundary, the same way a pilot begins descent long before the runway. Whatever is unfinished at that point was going to be unfinished anyway; the only question is whether it ends in a scramble or a plan.
Say the decisions out loud. Use the protected time to restate, in plain sentences, what was decided and who owns what. This does double duty. It gives the remembering self a clean, competent final impression — and it exploits a separate, well-documented memory principle: information that is actively retrieved and restated is encoded far more durably than information merely heard once. A decision spoken aloud at the close is a decision three people can repeat tomorrow.
End on resolution, not on a new problem. If someone raises a fresh concern in the final minutes, capture it explicitly for next time rather than half-litigating it. The last note the room hears should be a chord that resolves.
End early when you're done. An unexpected gift of ten minutes is one of the few reliable peaks a meeting can produce. It costs nothing and people remember it for weeks.
Spend one minute on an honest post-mortem. A single closing question — did this meeting need to happen, and what would have made it better? — turns the ending into a feedback loop instead of an exhale. It is the organizational equivalent of the warmer water at the end of the cold-pressor trial, except it also makes the next immersion shorter.
Endings Compound Into Culture
Here is why this matters beyond any single hour. Recurring meetings are not judged on their merits; they are judged on their memories. The remembering self is the one that decides whether to prepare for next week's sync or coast through it, whether to speak up or multitask, whether "meetings at this company" are where work happens or where it goes to die. Every ending is a small deposit into that account. Fix the endings and you gradually fix the memory; fix the memory and you have, almost without anyone noticing, fixed the culture.
The experiencing self will still have to sit through minute twelve. But the story your team tells about its meetings — the story that determines everything downstream — is written in the last five minutes. Write them on purpose.
Where Meetingmortem Comes In
That closing minute of honest review is the habit most teams find hardest to keep, which is exactly why we built Meetingmortem around it — a lightweight post-mortem for every meeting, capturing what was decided, what it cost, and whether it earned its place on the calendar, so the verdicts your remembering self files away are backed by an actual record. If your team's meetings keep ending in a scramble and being remembered accordingly, try running your next few through Meetingmortem and see what the endings have been costing you.