When Closed Doesn’t Mean Solved
Completing an action does not necessarily mean solving the problem. Many organizations are very good at assigning actions, tracking them, and marking them closed — but much less deliberate about checking whether those actions actually changed the condition they were meant to improve. This article explores the difference between action closure, follow-up, and learning closure — and why a good system should remember what people should not have to.
PROBLEM SOLVINGLEADERSHIPTHINKING DIFFERENTLY
When Closed Doesn’t Mean Solved
There is a word organizations love to see next to an action:
Closed.
It feels good.
Someone was assigned.
Something was done.
The box was checked.
The action disappeared from the list.
But there is a question we do not ask nearly as often:
What exactly did we close?
Because completing an action and solving a problem are not necessarily the same thing.
And somewhere between those two lives one of the most persistent creatures in organizational life:
Follow-up.
The follow-up problem
Almost every company struggles with follow-up.
Managers ask for it.
Meetings review it.
Spreadsheets track it.
Emails remind people about it.
And experienced managers develop an almost supernatural ability to remember unfinished actions.
Three weeks later:
“What happened with that issue?”
Everyone else had forgotten.
The manager had not.
We often interpret this as discipline.
Sometimes it is.
But sometimes it is also telling us something about the system:
The organization is using people’s memory as part of its control system.
If an action remains alive only because someone remembers to ask about it, then follow-up is not really built into the process.
It is built into a person.
Closing the action
Suppose a problem appears.
We investigate it.
We decide to change something.
Someone receives an action.
The action gets completed.
Closed.
From an execution perspective, that may be perfectly correct.
The person did what was agreed.
But the original question was not:
Did we complete the action?
The original question was:
Did the action change the condition that created the problem?
Those are different questions.
Completing the action proves that we did something.
It does not yet prove that what we did worked.
Three different kinds of closure
Perhaps part of the confusion comes from treating several different moments as if they were one.
There is action closure:
We did what we said we would do.
There is follow-up:
We checked what happened afterward.
And there is learning closure:
We have enough evidence to understand whether the change produced the result we expected.
Those moments may happen at very different times.
An action can be completed today.
The effect may only become visible next week.
Or next month.
Yet many systems use only one status:
Open / Closed.
So the moment the action is finished, the problem quietly disappears from view.
Not because we learned.
Because the task was completed.
When the problem comes back
Then something interesting happens.
Weeks later, the same problem returns.
Someone says:
“But we already fixed that.”
Maybe we did.
Or maybe we completed an action and assumed the rest.
This is where recurrence becomes valuable information.
The problem is not simply telling us that the previous solution failed.
It may be telling us that we never actually verified the solution in the first place.
The action was closed before reality had enough time to answer.
And when reality finally answered, nobody was listening.
The system should remember
Good follow-up should not depend on a manager having an exceptional memory.
The system should remember.
Not through endless reminders or more administrative work, but by making the learning cycle visible.
If an action is intended to produce a result, the system should preserve at least three things:
what we expected to happen,
when we expect to know,
and what evidence will tell us whether it worked.
Then follow-up stops being:
“Did you do it?”
and becomes:
“What did we learn from what we did?”
That is a very different conversation.
It also changes the role of the manager.
Instead of being the person who remembers everything, the manager can help the organization learn from what happened.
Maybe “closed” needs a different meaning
There is nothing wrong with closing actions.
Actions should be completed.
But perhaps we should be more careful about what the word closed tells us.
Because the action can be completed before the learning is complete.
And a system that confuses those two moments can become very efficient at closing tasks while repeatedly rediscovering the same problems.
Maybe the real question is not:
“Is the action closed?”
Maybe it is:
“Has reality had enough time to answer?”