When the Meeting Is Not the Problem
Same meeting. Same problem. Same conversation. Sometimes recurrence is not a scheduling problem. It is a signal that we may be managing the symptom, assigning the issue, and moving on without ever understanding why it keeps coming back. This Monday Morning is about what happens when unresolved problems become familiar — and eventually stop looking like problems at all.
MONDAY MORNINGTHINKING DIFFERENTLYPROBLEM SOLVING
When the Meeting Is Not the Problem
Coffee on the table.
And the feeling that it may not be enough for what’s coming.
Same people.
Same problem.
Same conversation.
We often try to improve recurring meetings by changing the agenda, the cadence, the participants, or the facilitation.
But sometimes the meeting keeps coming back because the condition that created the need for it has never changed.
In that case, the meeting is not the problem.
It is the symptom.
And symptoms can be managed for a very long time without ever changing the condition underneath them.
A weekly escalation meeting may exist because decisions are not being made where the work happens.
A daily coordination meeting may exist because information does not flow when people need it.
A recurring alignment meeting may exist because responsibilities were never made clear.
But the strongest signal is not simply that the meeting repeats.
It is that the same problems, the same people, and the same topics keep returning with it.
When recurrence becomes normal, we often respond by managing the symptoms better.
Clearer agendas.
Tighter follow-up.
More tracking.
More escalation.
More action lists.
Sometimes even more meetings.
But if the underlying condition remains unchanged, the meeting becomes part of the containment system.
Recurrence is often evidence that the problem was managed, not solved.
And over time, recurrence does something else.
It erodes attention.
When people expect the same problems, the same explanations, and the same follow-up every week, they stop listening with the same level of interest.
The meeting may still happen.
People may still attend.
But attention quietly leaves the room.
Eventually, people learn from the pattern.
They learn that the same issues will return, that little will move, and that today’s suggestions may have no visible effect on tomorrow’s work.
So they may still participate, but they stop investing the same attention, energy, and judgment.
Not because they do not care.
Because the system has taught them that caring makes little difference.
When participation repeatedly produces no visible change, disengagement becomes a learned response.
And then something even more dangerous happens.
We normalize it.
The same delay.
The same workaround.
The same escalation.
The same discussion.
What repeats becomes familiar.
And what becomes familiar stops looking like a problem.
The condition has not disappeared.
We have simply stopped seeing it as abnormal.
Normalization is how recurring problems become part of the system.
Then, when the problem becomes visible enough, another pattern often appears.
Leadership looks for an owner.
Sometimes ownership is necessary.
But when recurring problems are repeatedly reassigned instead of resolved, people learn another lesson:
visibility can turn into ownership.
So they speak less.
They volunteer less.
They make themselves a little smaller in the room.
Not because they have nothing to contribute, but because they do not want to become the next owner of a problem the system has failed to solve.
When ownership becomes a way to transfer unresolved problems, participation becomes risky.
And over time, being associated with a problem can become more dangerous than helping expose it.
So the organization loses something much more important than meeting efficiency.
It loses information.
It loses attention.
It loses participation.
It loses the willingness of people to expose what is really happening.
Recurring meetings are not necessarily a problem.
Recurring unresolved conditions are.
A useful meeting should help the system learn, move, or resolve something.
If week after week the same issue returns unchanged, the meeting may be doing little more than containing it.
And sometimes a problem returns not because nobody acted, but because we never understood it well enough.
We addressed what was visible.
We assigned actions.
We contained the effects.
But the condition that keeps producing the problem remained untouched.
Recurrence should therefore be a signal to question our understanding, not only our execution.
Before assigning the problem again, perhaps we should ask:
What are we still not understanding about this problem?
What condition keeps allowing it to return?
What have we been treating as the problem that may only be a symptom?
Because sometimes the reason we keep having the same conversation is simple:
we are still solving the wrong problem.
And that may be the real purpose of the next meeting.
Not to revisit the same problem more efficiently.
Not to find a new owner for it.
But to understand it well enough that, one Monday, it no longer needs to be on the table.
A good recurring meeting should eventually make some of its own conversations unnecessary.