Many meetings feel productive while they are happening.
There is discussion, information sharing, relevant opinions, and an agenda full of important topics. The problem appears when the meeting ends: no one can say with precision what was decided, who will do what, or by when.
Then a second, invisible meeting begins.
Messages are sent to confirm what was discussed. Someone interprets an agreement differently. Another thread opens to resolve what remained unclear. A decision returns to the agenda the following week.
The cost is not only the hour several people spent in the room. It is all the additional work required afterward to compensate for a conversation that did not create enough clarity.
An effective meeting should change something in the operation. It may produce a decision, resolve a dependency, assign responsibility, or generate concrete information for the next step.
If everything remains the same afterward, there may have been conversation, but little progress.
A meeting needs a defined outcome before it begins
One of the most common causes of unproductive meetings is starting with a topic but without defining what needs to happen with that topic.
“Review results.”
“Discuss the project.”
“Go over pending items.”
“Talk about the proposal.”
All of these describe subjects, not outcomes.
A more useful agenda frames objectives such as:
- decide between two alternatives
- identify the cause of a delay
- assign owners to three critical pending items
- decide whether a project moves forward, changes, or stops
- resolve a dependency between two areas
The difference may seem small, but it changes the conversation.
When people know what must be resolved, it becomes much easier to distinguish necessary information from information that could simply be shared elsewhere.
Informing, discussing, and deciding require different dynamics
Many meetings mix three activities without distinguishing them.
First, someone presents information. Then questions appear. A discussion begins and, when time is almost over, someone asks:
“So, what are we doing?”
That design leaves the decision for the moment when attention is lowest.
It helps to separate the blocks.
Information
What does the group need to know in order to work on the issue?
If something can be read beforehand, it probably does not need twenty minutes of presentation time during the meeting.
Discussion
Which perspectives, risks, or disagreements need to be processed?
What matters here is that different information emerges, not that everyone speaks simply because they are present.
Decision
What needs to be resolved?
This stage needs dedicated time. It also requires clarity about who has the authority to decide.
When these three moments are mixed together, the meeting may produce a lot of content and very little direction.
A decision needs an owner
There are meetings where everyone participates, but no one knows who decides.
That creates two problems.
The first is endless discussion. Every opinion appears to have the same weight because no one clarified how the issue will be closed.
The second appears afterward: the group leaves believing there is an agreement, but no one has explicit responsibility for it.
Before entering a decision, it helps to know:
Who makes the final decision?
It may be one person. There may be a previously agreed rule. In some cases, consensus may be required.
What matters is that the mechanism is visible.
Participating in a conversation does not necessarily mean having veto power. And having decision authority does not mean ignoring the team’s perspective.
Clarity around decision rights reduces unnecessary friction.
“We agreed to do it” is still not a commitment
A meeting can make good decisions and still fail in execution.
This usually happens when the agreement remains too general:
“We’ll review the budget.”
“We need to talk to operations.”
“Let’s see how we can improve this.”
“We’ll keep working on it.”
None of these allows precise follow-up.
An operational commitment needs, at minimum:
Action + owner + date.
For example:
“Mariana will present the new cost scenario on Thursday the 24th.”
Now there is something observable.
There should also be a simple rule: if the owner realizes the commitment cannot be met, they communicate before the deadline and propose a new condition.
That is how a meeting stops producing good intentions and starts producing coordination.
The record should capture decisions, not transcribe conversations
Long meeting minutes can become another problem.
Documenting every intervention creates files that very few people ever read again.
What matters after a meeting usually fits into a much simpler structure:
Decisions made
What was resolved?
Actions
What needs to be done?
Owners
Who is responsible for each action?
Dates
When must it be completed?
Open issues
What still needs information or a later decision?
The record should allow someone who left the room to understand what changed.
If they need to read five pages to discover that, the mechanism is probably too heavy.
Not everything deserves a meeting
An organization can improve its meetings significantly by reducing the number of issues that reach them.
A status update may be handled asynchronously.
A data point may be available in a system.
A simple decision may be made directly by the person with authority.
An individual question may be resolved between two people.
Meetings create the most value when real interaction is required:
- processing different perspectives
- resolving a dependency
- making a decision with shared consequences
- working through a disagreement
- coordinating actions across several people
Using meetings to transmit information that could circulate in another way consumes collective attention unnecessarily.
And collective time is one of the most expensive resources in an organization.
Meetings can also reveal system problems
When a company needs too many meetings, it is worth looking beyond the agendas.
Sometimes the calendar is compensating for other weaknesses.
Meetings are scheduled because decision rights are unclear.
Several areas meet because information does not flow.
The CEO participates because teams do not have enough judgment to close issues.
The same conflicts return every week because the underlying condition never changes.
That is why a recurring difficult meeting can be a useful signal.
Before improving the format, it is worth asking:
What organizational problem are we trying to solve over and over inside this meeting?
The answer may not require a better agenda.
It may require redefining a responsibility, a process, a priority, or the relationship between areas.
Executive meetings need to protect the level of conversation
Executive teams face a particular risk: spending too much time on operational issues that should have been resolved earlier or at another level.
An executive meeting loses value when its members arrive only to report what happened in their own areas.
Their time should focus especially on issues that require a cross-functional view:
- strategic decisions
- shared priorities
- relevant risks
- resource allocation
- dependencies between functions
- problems affecting the whole system
When each director uses the meeting to report to the CEO, and the CEO is the one connecting all the pieces, the executive team operates more like a collection of reports than a true space for collective decision-making.
A simple anatomy for an effective meeting
Not every meeting needs the same format, but a basic structure helps.
Before
Define what outcome the meeting must produce.
Send in advance any information that can be reviewed asynchronously.
Make sure the people required to decide are present.
During
Separate information, discussion, and decision.
Prevent a topic from consuming time without clarifying what needs to be resolved.
Make relevant disagreements visible instead of closing them artificially.
At the end
Confirm decisions.
Record action, owner, and date.
Identify what remains open and what is still needed to resolve it.
After
Follow up on commitments.
If certain issues keep returning, review the systemic cause instead of discussing them indefinitely.
A productive meeting creates less coordination work afterward, not more
The quality of a meeting can be evaluated by what happens next.
Do people know what to do?
Were decisions clear enough?
Can owners move forward without asking for interpretation again?
Were dependencies resolved?
Does the issue really need to return to the next meeting?
When a meeting works, it reduces ambiguity.
It also prevents the same issues from circulating for weeks across agendas, emails, and parallel conversations.
That is one concrete way to improve organizational capability: creating spaces where conversation produces decisions and decisions turn into action.