The team has been struggling with priorities for weeks.
People keep receiving new requests. Projects that were urgent on Monday are suddenly less important by Thursday. Team members are starting work, stopping, switching, and then discovering that somebody else understood the priority differently.
So the manager calls a meeting.
For the first time in weeks, people speak openly. Someone explains how the constant changes are affecting customers. Another person admits that she no longer knows which deadline should win when two priorities collide. The manager listens instead of defending the decisions. By the end of the hour, everyone seems to understand the problem better.
Someone says, “This was a really productive discussion.”
People leave relieved.
Monday morning comes.
One person works on Project A because she understood that it remained the priority. Another moves to Project B because he thought the meeting changed the priority. A third waits for clarification because nothing was written down.
By Wednesday, someone suggests another meeting.
Everyone agreed that the old way was not working.
Agreement happened. Movement did not.
A conversation can feel productive before the work changes
This is one reason meetings are deceptive.
A good conversation can genuinely accomplish something. People understand one another better. A difficult issue finally gets named. Someone feels heard. Information that had been scattered across the team comes into the same room.
The emotional pressure drops.
That matters.
But the relief created by understanding can easily be mistaken for movement in the work itself.
“We need clearer priorities.”
“We should communicate sooner.”
“We need better coordination.”
“We have to become more customer-focused.”
Everyone can agree with statements like these. They can even leave the meeting believing that something important has been settled.
Then tomorrow arrives and nobody knows what to do differently.
The conversation moved.
The work remained where it was.
The meeting is not the work
A meeting is useful when people need to think together in order to do something they could not do as well separately.
Perhaps a decision requires several perspectives. Two teams need to resolve a dependency. A problem has become too complex for one person to understand alone. People need to surface disagreement before committing resources. A leader needs to hear what is happening before choosing a direction.
Those are legitimate reasons to bring people together.
But the meeting itself is rarely the final result.
The meeting changes the work.
If the purpose was to decide, the decision should alter what happens afterward. If the purpose was to coordinate, responsibilities should become clearer. If the purpose was to solve a problem, the team should leave with a different understanding of the problem or a move worth trying.
This does not mean that every conversation needs an action item.
It means the meeting should do the job it was called to do.
Some meetings are meant to understand before they decide
There are times when forcing an immediate action would make the meeting worse.
A team may need to understand why a project failed before choosing another approach. A leader may need to listen to employees after a difficult event without turning their concerns into a task list. A coaching conversation may need reflection before action becomes useful. A creative group may need to explore possibilities before narrowing them.
Those conversations can matter enormously.
The problem comes when a meeting that was supposed to produce coordinated action ends with nothing more than shared understanding—and everybody pretends the job is finished.
If the purpose was exploration, say:
“We are not deciding today. We are trying to understand the problem well enough to make the decision Thursday.”
That is clear.
If the purpose was decision, do not let another hour of thoughtful conversation disguise the fact that nobody decided.
A meeting becomes more useful when people know what kind of work they are doing together.
Vagueness feels safer than a decision
Suppose a team agrees:
“We need to respond to customers faster.”
Almost nobody objects.
Now make the statement specific:
“Beginning Monday, customer requests that cannot be resolved within four hours will be acknowledged before the end of the shift, and Ramon will own the new response process.”
Suddenly, questions appear.
Four hours?
What counts as resolved?
What if the request needs another department?
Why Ramon?
What happens to the current process?
Specificity creates friction because it reveals whether people actually agree about what should happen.
That discomfort is useful.
Vague agreement preserves harmony in the room. Specific decisions test whether agreement can survive outside it.
This is why teams often leave meetings with phrases everyone supports rather than decisions someone could actually execute. General language protects the feeling of agreement. Specific language exposes the trade-offs hidden underneath it.
But coordinated work cannot live on agreement alone.
Eventually, someone has to know what changed.
Ask what is different now
Before a meeting about coordinated work ends, ask a deceptively simple question:
What is different now because we met?
Perhaps the group made a decision.
Perhaps one priority replaced another.
Perhaps an option was rejected.
Perhaps the team discovered that the problem is different from what everyone thought at the beginning.
Perhaps a constraint became visible that changes the plan.
Perhaps nothing has changed yet because the purpose of the meeting was exploration.
That answer is also acceptable—if everyone knows it.
The danger is allowing people to leave thinking a decision was made when what actually happened was only discussion.
Once the difference is clear, two more things matter.
Who owns the first move?
And what will happen next, by when?
Keep this simple. You do not need to turn the final five minutes into another meeting.
You need enough clarity that tomorrow morning does not require everyone to reinterpret what yesterday afternoon meant.
One owner does not mean one person does everything
This is another place meetings can dissolve responsibility.
“We will work on it.”
“Marketing and operations will coordinate.”
“The team will follow up.”
Everyone is included.
Nobody is clearly responsible for getting the first move started.
Naming an owner does not mean that person performs all the work. A project may require ten people. It simply means somebody knows they are responsible for ensuring that the first agreed movement does not remain an intention.
If five people own the same next move, each person can reasonably believe someone else has started it.
That is not shared ownership.
That is distributed ambiguity.
A good meeting makes collaboration easier without making responsibility invisible.
The real test begins the next morning
Imagine your meeting ended at 4:30 yesterday afternoon.
At 9:00 this morning, what is different?
Has the priority board changed?
Has the work that no longer matters been stopped?
Did someone contact the customer?
Has the first decision been implemented?
Does the person who owns the next move know that they own it?
Or is everybody behaving exactly as they did before the meeting?
This is where Stop Measuring Effort. Look for Movement. becomes especially useful. A meeting is an easy form of activity to count. Ten people spending an hour together produces ten hours of visible effort.
But effort is not the question.
What became more possible because those ten hours were combined?
Sometimes the answer will justify the meeting many times over.
Sometimes it will make you wonder why the meeting existed.
Recurring meetings can become Machine Work
Weekly meetings are especially vulnerable because the calendar eventually starts making the decision for us.
Tuesday arrives.
Therefore, the Tuesday meeting happens.
People provide updates. Someone reads the numbers. Problems are mentioned. Minutes are recorded. The meeting ends.
Next Tuesday, everyone returns.
A place on the calendar is not proof that a meeting still has useful work to do.
A recurring meeting should still have a job. Perhaps it exists to identify exceptions that require a decision. Perhaps teams use it to resolve dependencies. Perhaps leaders use it to choose priorities for the coming week.
If that job still matters, protect the meeting.
But if the meeting mainly repeats information people could have read, ask whether the collective attention is being used well.
Maybe updates can be shared before the meeting and the meeting can focus only on decisions.
Maybe the hour can become twenty minutes.
Maybe this week there is genuinely nothing that requires everybody in the room.
Cancelling a meeting is not always evidence of efficiency.
But neither is holding one evidence of work.
Meetings create promises
The previous article, Build Trust by Completing What Others Depend On, looked at what happens when another person begins planning around your promise.
Meetings are one of the places where those promises are born.
“I’ll send it Friday.”
“I’ll talk with the client.”
“We’ll change the process next week.”
“I’ll get you the decision tomorrow.”
In the room, these statements can sound clear enough.
Then people leave with different memories.
If the commitment matters to coordinated work, give it enough form to survive the meeting.
What changed?
Who starts?
What happens next?
By when?
The purpose is not to create elaborate minutes.
It is to stop an important promise from disappearing into everyone’s separate recollection of the conversation.
Do not add action just to make the meeting look productive
There is another bad habit worth avoiding.
Teams sometimes end every meeting with action items because action items make meetings appear productive.
So people leave with tasks that did not need to exist.
“Prepare a summary.”
“Create another analysis.”
“Schedule a follow-up.”
“Draft a proposal for the next discussion.”
Activity multiplies even when the work does not need it.
A useful meeting does not necessarily create more tasks.
Sometimes it removes them.
A decision kills three unnecessary options. A clearer priority stops a project. A resolved issue means the follow-up meeting is no longer necessary.
Movement can look like less work.
That is perfectly consistent with making work matter.
The goal is not to leave the room with the longest action list.
It is to leave with the work in a better state.
Before people leave
Near the end of your next work meeting, resist the temptation to finish with a vague summary.
Do not ask only:
“Anything else?”
Ask:
What is different now because we met?
Let the group name it.
Then, if coordinated action follows, make sure somebody owns the first move and that the move has a real time boundary.
That may take three minutes.
Those three minutes can be the difference between a useful meeting and another hour everyone has to repeat next week.
Because the strongest evidence that a work meeting mattered is not how good the conversation felt while everyone was together.
It is what people can do differently once they separate.
The meeting is not the work. The meeting changes the work.
Once a decision, commitment, or next move leaves the meeting, someone will often have to turn it into a document, file, analysis, instruction, or other output another person can use. The next article asks whether the work itself is designed to survive that transition.
Continue with Do the Work the Next Person Can Use.