Someone says, “Let's quickly talk about the new deployment pipeline.” Four people nod. And four people picture four different meetings.
One thinks it's about a decision: which way do we go? Another thinks she's supposed to explain something she built last week. A third is waiting for someone to finally answer the one question that's been blocking him for days. And the fourth just wants someone to pick up a task that's been sitting untouched.
The conversation starts. One begins to explain, another cuts in with his question, someone raises a point of principle, and ten minutes later everyone is talking, but no two people about the same thing. It feels productive because a lot is being said. Yet by the end there's no decision, the blocking question is still open, and the task still has no name.
Nobody had done anything wrong. And that was exactly the problem.
The unspoken goal
Every topic someone brings into a meeting carries an intent. The person wants to achieve something, even if they don't say it out loud. Usually they don't say it out loud because they aren't quite sure themselves what it is.
That sounds strange, but it's the normal case. We phrase topics as headings, not as needs. “The deployment pipeline” is a heading. Underneath it could be anything: information I want to share. Information I'm missing. A task I want to hand off. Or a decision we need to make together.
The topic is the same for everyone. The intent behind it is not. And as long as the intent stays invisible, the group first works out, without ever saying so, what kind of conversation this even is. Should I listen or contribute? Are we deciding something here, or just reporting? That part burns the most energy, and it happens without anyone naming it. Each person quietly braces for a different conversation, and no one notices that the others are in a different story altogether.
The four intents behind a topic
Look closely, and almost every topic in a team sync traces back to one of four intents.
The first is sharing information: I know something you should know. Nobody wants an answer here; the group just needs to hear where things stand. The conversation is short when you treat it as what it is. The mix-up happens when someone turns a simple piece of information into a discussion, even though no question was ever on the table.
The second is getting information: I'm missing knowledge that someone here has. Now the goal isn't to broadcast but to receive. The most important person in the room is the one with the answer, and the group's job is to let them speak instead of papering over the question with their own guesses.
The third is requesting an action: I want to hand a concrete task to someone. The outcome isn't shared understanding but a name and a next step. Everything else is decoration. A topic like this is only done once it's clear who takes it on and by when.
The fourth is a team decision: we need to decide together how to proceed. This is the only one of the four intents that genuinely needs everyone. And it's the one the other three get mistaken for most often, because any topic can feel, in conversation, like something the whole group has to chew over.
Four intents, four completely different conversations. Someone sharing information needs no discussion. Someone who needs a decision gets nowhere with a status report. Most of the talking past each other happens because two people are looking at the same topic while silently working toward two different intents.
The uncomfortable question to yourself
Here comes the part that sounds almost silly: the most effective move is for each person to ask themselves, before the meeting, what they actually want from their topic.
Not ask the others. Ask yourself.
It sounds trivial until you actually do it. Then you notice how often the honest answer is, at first, I'm not really sure. I just wanted to bring it up. And inside that “I just wanted to bring it up” lies the reason so many agenda items go in circles. If you don't know what you need, you can't get it either.
But once you've settled it for yourself, that you need a decision here, the way you raise the topic changes. “Let's talk about the pipeline” becomes “we need to decide whether to switch to the new tool, and I need your vote on it.” Same topic, but now with a direction. The group knows immediately what's expected and doesn't have to spend ten minutes guessing which story it's in.
This self-clarification is uncomfortable because it makes you honest. It forces the admission that sometimes you walk into a meeting without knowing what you want. That's not an accusation. It's just how it is. But it's also where most lost meeting time comes from, long before the first word is spoken.
When a topic fits no box
Sometimes you try to sort your topic into one of the four intents and it simply won't fit. It feels like sharing information, but also like a decision. Or like a question that ends in a task.
That resistance isn't a flaw in the system. It's the most valuable signal the method gives you.
A topic that won't sort cleanly is almost always two topics. Two different needs squeezed into a single agenda item because they share the same heading. “The deployment pipeline” is at once the information that the old one no longer runs reliably and the decision about which new one should replace it. Those are two conversations with two goals, and they need two spots on the agenda.
As long as they're glued together, they block each other. The information turns into half a discussion, the discussion gets lost in status details, and in the end both are only half done. Split them, and each topic suddenly becomes small and solvable. Splitting feels like more effort at first, like more items on the list. In truth it's the opposite. Two clearly named needs get resolved faster than one fuzzy agenda item where both circle each other without ever touching.
Why structure has to carry this, not discipline
You could say: then people should just think harder before they bring up a topic. But appeals to self-discipline rarely last. Making the intent visible can't depend on how sharp any one person happens to be that day.
So the question about the goal belongs in the process, not in good intentions. When every topic gets an intent as it's added, share, get, request, or decide, then everyone has to ask themselves this one question before their point even lands on the list. Not as a chore, but because the structure doesn't move forward without it.
The nice part: the question doesn't lecture anyone. It only surfaces what's already there. Every topic always had an intent. The method just drags it into the light before the conversation starts, instead of letting the group spend ten minutes guessing at it.
Just start with yourself
The best thing about this idea is that you don't have to convince anyone to try it. You need no decision, no new format, no sign-off from the group. You can do it entirely on your own, at the next meeting, without anyone noticing.
Before the meeting, take your two or three topics and ask yourself the one question for each: do I want to share something here, get something, hand off a task, or do I need a shared decision? That's all. Then watch, during the meeting, what happens when you raise your topic with that clarity instead of with a bare heading.
Most of the time you feel the difference right away. The group figures out faster what to do. Your points get resolved sooner. And sometimes a topic you'd planned to talk about for half an hour dissolves in two sentences, because it suddenly turns out it was just a piece of information and not a discussion at all.
A topic with a clear intent is an invitation for the group to do the right thing. A topic without one is an invitation to talk past each other. And between the two there's often just a single short question, one you asked yourself before you walked into the room.
What would change in your next meeting if, for just one topic, you worked out beforehand what you actually want to achieve with it?