Picture the Monday standup. Eight people in a circle, or eight tiles on a screen. The third person is explaining why the deployment is stuck. You are the fifth. You are nodding at the right moments. You have not heard a word.
You are rehearsing. You are trimming your sentence, deciding whether to mention the slip, wondering whether "almost done" sounds like a lie, rehearsing the tone that says confident but not cocky. By the time your turn arrives, the deployment story has evaporated. You were not rude. You were not on your phone. You were doing exactly what the format asked of you, and that is the problem.
Here is the uncomfortable truth about every go-around meeting you have ever sat in: almost nobody is listening to the person right before them. The colleague who spoke just before you, the one who may have been quietly asking for help, was speaking into a room where the next person to pick up the thread had already left. And when it is your turn to be that colleague, the same silence is waiting for you.
A circle of readers, and a dent in memory
In 1973, the psychologist Malcolm Brenner ran a deceptively simple experiment. He seated people in a circle and had them take turns reading words aloud from cards, one person after another, the way a team might go around a table. Afterward, he tested how many of the words each person could remember.
The results showed the familiar shape memory researchers expect. Words from the beginning and the end of the sequence were recalled well, the standard primacy and recency pattern. People also remembered the words they had read themselves. But there was a dent in the curve, and it was always in the same place. The words read by the people immediately before a participant's own turn were recalled markedly worse than words from anywhere else in the sequence.
Brenner called it the next-in-line effect, and it has held up well enough over the decades to earn a place in memory textbooks. It is not a quirk of word lists. It is what happens to a human mind in the moments before it has to perform.
What your brain is doing instead of listening
The mechanism is not mysterious once you look at it plainly. Working memory, the mental workspace where you hold and manipulate information in the moment, is small. It can juggle only a few things at once, and it does not multitask so much as time-share. Encoding what another person is saying, turning their speech into something you can retrieve later, takes a real slice of that workspace. So does composing and silently rehearsing your own upcoming sentences.
When your turn is far away, the two tasks barely compete. As your turn approaches, rehearsal starts winning. The psychologist Charles Bond and colleagues later argued that the effect is driven by anticipation itself: the nearer the moment of performance, the more attention swings inward, toward how you will sound and how you will be judged. Their work also found that people high in social anxiety show a larger next-in-line deficit. The more a person worries about being evaluated, the less of the preceding speaker they retain.
That last finding deserves a moment, because it describes the quiet geometry of a lot of teams. The newest hire, the person who already suspects they do not quite belong, the one who was criticized two weeks ago and still feels it, these are the people rehearsing hardest. They are also, by the same mechanism, the people hearing least. And afterward they often carry a second, private cost: the guilty sense that they were not paying attention, that they are somehow a worse colleague than everyone else. They are not. They were caught in the exact spot where attention collapses for everyone, only more so.
The go-around is a machine for not listening
Once you see the next-in-line effect, the round-robin format looks different. The daily standup. The "quick check-in around the table." The retrospective where everyone names one thing that went well. Each of these gives every person one slot, and in front of every slot sits a dead zone where the upcoming speaker's attention has gone dark.
The chain of attention breaks at every link. The person who speaks right before the most anxious member of the team is speaking into the deepest void. If there are twelve people, there are twelve small blackouts, and the information that falls into them is not randomly distributed. It is whatever your nearest colleagues happened to say, often the people whose work sits closest to yours and who would most benefit from you having heard them.
There is an emotional layer here too. When we feel unheard in meetings, we tend to read it as indifference. He didn't care. She wasn't interested. Sometimes that is true. But often the cause is architecture, not character. The person who glazed over while you described your blocker was not dismissing you. They were silently drafting their own two sentences, terrified of fumbling them, exactly as you were a minute later while someone else spoke. Knowing this does not make the sting disappear, but it does redirect it. The fix is not to resent your colleagues. The fix is to stop asking a format to do something human attention cannot do.
Why reading it later does not fully fix it
A natural objection: fine, I missed it live, but the notes exist. The trouble is that the next-in-line effect is a failure of encoding, not a failure of retrieval. What was never stored cannot be remembered, and the written summary you read afterward is a different thing from having heard a colleague's hesitation, the half-sentence they trailed off from, the thing they almost asked for. Notes catch facts. Listening catches the person. A team that only ever reconstructs its meetings from the minutes slowly loses the second kind of information, and that is the kind that tells you who needs help before they say so.
Your next moves
- Write your update before the meeting, and have it in front of you. Two or three sentences in a doc or chat thread. Once it exists on paper, your brain can stop rehearsing it and the slice of working memory it was hogging comes back to the people speaking before you.
- Volunteer to go first. The moment your turn is over, your attention is free for everyone else. If you run the meeting, ask who would like to go first rather than defaulting to seating order, and consider gently offering the slot to whoever seems most nervous. Some people will prefer to go later, so ask rather than assign.
- Keep a one-word log. For each speaker, write a single word that captures their update. Not a sentence, one word. The act of choosing it forces encoding, and it is small enough to do even while your own turn is looming.
- Back-reference the person before you. When your turn comes, begin by picking up something from the previous speaker: "Before mine, on what Priya said about the deployment..." If you genuinely did not catch it, say so and ask them to repeat the key point. You will be surprised how often someone else in the room thanks you.
- If you facilitate, replace the go-around with silent reading. Have everyone post updates in a shared document, open the meeting with a few minutes of quiet reading, then spend the live time only on exceptions and questions. Amazon famously opens its narrative-driven meetings this way. It removes the dead zones entirely, because nobody is waiting for a turn.
Hearing the meeting after it ends
The next-in-line effect is a reminder that a meeting is not one shared experience. It is a dozen partial recordings, each with a gap in a different place, and the gaps fall precisely where a colleague was speaking. That is the idea behind meetingmortem: a way for teams to look back at a meeting once it is over, to see what was actually said and decided and who was actually heard, so that the two minutes you lost to rehearsing your own line do not vanish for good. If your team's standups feel like everyone talking and no one quite listening, you can see how it works at meetingmortem.lumenlabs.works.