It starts with one sentence, and it's usually a true one. Well, procurement is never going to approve that anyway. Someone laughs. Someone else adds that procurement took six weeks to approve a monitor last spring. Someone else says it's the whole company, really. Twenty minutes later the meeting ends. Everyone feels oddly close and a little lighter, and nothing has moved. The uncomfortable part is this: if you've ever left a meeting like that feeling understood, you may have been the one who started it.
Complaining in meetings doesn't feel like a problem while it's happening. It feels like candor. It feels like the one moment when people stop performing optimism and say what they actually think. That's why it's so hard to see clearly, and why the research on it is so useful.
What happens when researchers code every sentence
Most meeting research asks people afterward how the meeting went. A line of work led by organizational psychologists Simone Kauffeld and Nale Lehmann-Willenbrock did something more painstaking. They recorded real team meetings in companies and coded them statement by statement with a detailed scheme called act4teams, which tags each utterance as problem analysis, proposing a solution, planning action, supporting a colleague, criticizing, complaining, and so on.
Two findings stand out. First, the dysfunctional behaviors, complaining most of all, were linked to worse outcomes. Teams whose meetings had more of them tended to report lower satisfaction with their meetings and were rated as less productive. Meanwhile, functional behaviors like proposing solutions and committing to action pointed the other way.
The second finding is the one that should change how you sit in your next meeting. Using sequential analysis, which looks at what tends to follow what, the researchers found that complaints come in chains. A complaint made the next statement more likely to be another complaint. They called these complaining cycles. The good news is that the same thing worked in reverse: solution-focused statements tended to pull in more solution-focused statements.
So a meeting isn't just a set of separate opinions. It works more like a conversation with momentum, and each sentence quietly suggests what kind of sentence should come next.
Why a complaint is so easy to follow
It helps to understand why the cycle locks in so easily, because it isn't a character flaw. Several well-documented forces push in the same direction.
Complaints are socially cheap and rewarding. Agreeing with a complaint costs nothing. You don't have to own a fix, take a risk, or volunteer for anything. You just nod and add your own example. That small exchange produces a real feeling of belonging: we see the same thing, we're on the same side. Offering a solution is the opposite. It exposes you, because it can be criticized and it might become your job.
Bad is stronger than good. In a well-known 2001 review, Roy Baumeister and colleagues pulled together evidence from many areas of psychology showing that negative events, feedback, and information tend to carry more psychological weight than positive ones of the same size. In a meeting, that means a complaint lands with more force than the progress update before it, and it grabs the room's attention.
Venting doesn't drain the tank. It's tempting to think a bit of complaining clears the air so the real work can start. The research on catharsis doesn't support that. In Brad Bushman's experiments, people who were angered and then hit a punching bag while thinking about the person who provoked them ended up more aggressive, not less. Rehearsing a grievance tends to keep it alive. A meeting that spends fifteen minutes on how broken procurement is doesn't end with people at peace about procurement. It ends with procurement more firmly established as the villain.
Put those together and you get a slope. Each complaint is a little easier to follow than to redirect, and the meeting slides down it.
The trap of thinking the fix is silence
The wrong lesson is don't let anyone complain. Many complaints are accurate and important. A team that can't name problems will never solve them, and banning negativity just pushes it into side chats and private messages, where it can't be fixed.
The act4teams scheme makes a useful distinction here. Problem analysis, which means describing a problem, its causes, and how it connects to other things, is a functional behavior. Complaining is different: it's an expression of dissatisfaction that doesn't lead anywhere, often with a hint of helplessness. This is broken and nothing can be done.
So the difference isn't whether a sentence is negative. It's whether it's heading somewhere. Procurement takes six weeks, so we should submit by the 3rd names the same problem as procurement is hopeless, but it ends in a completely different place.
This is why breaking the cycle doesn't take a cheerleader. It takes one person willing to turn the next sentence.
How to turn the next sentence
The sequential finding hands you a lever. You don't need to change the whole culture of your meetings. You only need to change what comes after a complaint, because that's where the chain either goes on or breaks.
The move that works best is to acknowledge, then add a direction. Skipping the acknowledgment sounds dismissive and makes people dig in. Stopping at acknowledgment just adds another link to the chain. The combination sounds like: Yeah, six weeks is brutal. What would we need to know now to get ahead of it? The first half honors the frustration. The second half gives the next speaker something different to respond to.
There's a reason questions work especially well. A question asks the room for a particular type of answer. Whose call is this, actually? or What's the smallest version we control? makes the obvious next sentence a solution, an owner, or a fact, not a fresh complaint.
The second lever is noticing your own first link. Complaining cycles rarely start with the team's chronic grumbler. They often start with someone tired, stretched, or quietly anxious, saying the true thing that has been bothering them all week. Catching yourself halfway through that sentence, and finishing it with so here's what I'd propose, is one of the most valuable small habits a person can build at work.
The third lever is structure. Cycles do best in open, unstructured discussion. A meeting with a clear decision to reach, or a point where the facilitator asks what are we committing to?, gives the conversation a direction strong enough to resist the slope.
Your next moves
- Write down your redirect question now, before your next meeting, so it's ready when you need it. Pick one: What part of this do we control? or What would we need to decide today to make this better? Having the words ready is what lets you use them in the moment.
- In your next meeting, count the links. Quietly tally how many complaints in a row happen before someone turns the conversation. You're not judging anyone. You're learning to notice the cycle as it forms, which is what makes interrupting it possible.
- Audit one complaint of your own today. Think of the gripe you're most likely to bring up this week. Rewrite it as problem analysis: the problem, one likely cause, and one possible next step. Say that version instead.
- Add a closing line to the agenda of a meeting you run: Decisions and owners. Spend the last three minutes there, so even a meeting that drifted ends on something actionable.
- Name the pattern once, gently. If your team often spirals, share the idea of complaining cycles with them as an interesting finding, not a criticism. Once a team has a shared name for the pattern, anyone can say we're cycling and redirect without singling anyone out.
Seeing the shape of your own meetings
The hardest thing about complaining cycles is that you can't see them from inside. In the moment they feel like honesty, and afterward they feel like a vaguely draining hour you can't quite explain. That gap is what MeetingMortem is built for. It helps you look back at a meeting clearly: where the conversation went, what actually got decided, and whether the time moved anything forward. That way you can spot your team's patterns, including the twenty-minute spirals, and start turning the next sentence. If you'd like a clearer view of what's really happening in your meetings, you can try MeetingMortem here.