There’s the agenda, and then there’s what’s actually happening.
The stated agenda might be “quarterly planning” or “project update” or “product roadmap discussion.” Fine. Standard stuff. But if you’re paying attention to what people are actually doing in the room—what they’re defending, what they’re checking, who’s quiet, who needs to hear themselves talk—you realise the real agenda is something else entirely.
Sometimes a meeting is really about someone wanting to feel heard before a decision gets made without them. The decision’s already made, but they need the ritual of being consulted. Sometimes it’s a manager trying to get visibility over their team’s work because they don’t trust async updates. Sometimes it’s a team that doesn’t actually trust async communication, so they’ve learned to default to synchronous because otherwise nothing moves. Sometimes someone’s protecting their territory: making sure nobody makes decisions about their domain without them in the room. Sometimes it’s just that someone likes meetings and has built their identity around being essential to them.
None of these motivations appear on the calendar invite.
I spent nearly a decade in L&D and compliance training, where we knew exactly what real meetings looked like. The stated purpose was always “roll out new policy” or “make sure everyone understands the compliance requirements.” The real purpose was to document that we’d told people, so if something went wrong later, we had records. The meeting was a liability cover. We needed the attendance sheet, the sign-in, the acknowledgement. We weren’t actually trying to change behaviour. We were trying to protect the organisation from a lawsuit.
That’s an extreme example, but the principle holds across most corporate meetings. The stated purpose is what gets put in the calendar invite. The real purpose is why people are actually showing up, and it’s often not that different from what I just described—covering themselves, protecting a position, maintaining visibility, ensuring control.
Here’s what you need to understand: figuring out the real agenda isn’t about cynicism. It’s about getting things done. Because if you’re responding to the stated agenda while everyone else is responding to the real agenda, you’re talking past each other. The meeting accomplishes nothing except burning time and frustrating everyone.
Let me give you some real-world examples.
The “Status Update” Meeting. Stated agenda: brief the team on where we are. Real agenda (usually): the manager needs to confirm that things are moving and that nobody’s in crisis without them knowing. The status could be delivered in a Slack message in two minutes. But the manager needs to see your face, hear you confirm you’re on top of it, watch how you respond to their questions. They need the performance of competence, not just the information. If you come to this meeting with a perfectly written status update and try to get through it in three minutes, the meeting will mysteriously extend by 20 minutes because the real work hasn’t happened yet. You need to understand what your manager is actually after—reassurance, or information, or the ritual of being in control—and you need to give them that.
The “Alignment” Meeting. Stated agenda: make sure all teams are heading the same direction. Real agenda: someone’s been cut out of a decision and wants to reopen it. Or multiple people have built different solutions independently and now we’re in the meeting to see whose approach wins. Or the person calling the meeting is anxious that something’s being decided without them having enough influence. The alignment meeting isn’t actually about alignment. It’s about power. You can sit through hours of discussion about whether to use TypeScript or Go, but the real question is: who gets to decide? Once you know that, the meeting is actually 15 minutes instead of 120.
The “Deep Dive” Meeting. Stated agenda: understand the technical or business problem in detail. Real agenda: someone needs to feel like they’ve been heard and understand before they sign off, or someone else wants to prove how complicated their work is so they can’t be easily replaced, or there’s a gap between technical and business perspectives and everyone needs to be forced to sit in the same room until it gets resolved. A real deep dive is useful. A performative one where you’re explaining the same thing repeatedly to people who don’t actually care is a waste of everyone’s time. You need to figure out which one this is before you dive.
The “Retrospective” or “Lessons Learned” Meeting. Stated agenda: understand what happened so we can improve. Real agenda: assign blame, or protect someone from blame, or make sure everyone knows the project was doomed from the start and it’s not anyone’s fault, or prove that you personally did the right thing even though the outcome was bad. A real retrospective is genuinely about moving forward. A defensive one is about positioning. You can usually tell by who does the talking and what they’re defending.
The skill here is learning to read the room. It’s not sinister. It’s just how human beings work. We say one thing and mean another. We state an intention and pursue a different one. And in meetings, where people are self-conscious and performing, it’s especially true.
Here’s how you actually use this knowledge: instead of fighting the real agenda, you acknowledge it and move the meeting toward resolution. Someone wants to feel heard? Spend five minutes actually listening, then move forward. Someone needs to protect their territory? Give them decision-making power over the bits that matter to them, not the bits that are actually blocking progress. Someone is anxious about control? Give them visibility, not veto power. You’re not manipulating them. You’re just responding to what they actually need instead of what they said they need.
The other option is to pretend the stated agenda is the real agenda and watch meetings drift, circle back, get rescheduled, and ultimately accomplish nothing. I’ve seen organisations full of intelligent people who can’t make decisions in rooms because they’re all responding to different unstated agendas and nobody’s saying it out loud.
The pragmatic move is to name it. Not aggressively or accusingly, but clearly. “I sense there’s some concern here about how this decision gets made. Can we talk about that?” or “It sounds like we need to decide whether this is a product decision or a technical decision, and then figure out who decides.” You’re not calling anyone out. You’re just moving the conversation toward what’s actually blocking progress.
The organisations that move fastest are the ones where people are honest about what meetings are actually for. They don’t pretend a decision meeting is a brainstorm. They don’t call a power-consolidation meeting a “team alignment.” And when people show up, they know what they’re actually there for, so the meeting can actually do its job. Everything else is just theatre, and everybody knows it.