The meeting where the decision was orphaned: the anatomy of an organisation where everyone speaks and nobody decides

At nine o'clock, everyone was in the room.

The director at the head of the table. The managers with their laptops open. The heads of departments with their reports in front of them. On the screen was the problem that had caused the meeting: an operational failure that had repeated several times and was already affecting the results.

For two hours they talked about causes.

Mistakes were analysed. A lack of communication was mentioned. Procedures were discussed. Someone asked for more training. Another suggested a new control system. Everyone agreed that the situation could not go on like this.

In the end, the director closed his laptop.

“Very good. I think we had a productive discussion.”

Everyone nodded.

Chairs were pushed back. Laptops were closed. People returned to their offices.

The problem stayed where it was.

Nobody had taken on a decision. Nobody had defined what had to change, who would do it and by when.

And yet the meeting had ended successfully.

At least according to the calendar.

There is a kind of bureaucracy that needs no forms, stamps or long administrative corridors.

It can thrive inside a modern organisation, with smart screens, collaboration platforms and people who use the language of contemporary management with mastery.

There are objectives, performance indicators, analyses and carefully prepared presentations.

Only one thing is missing.

Someone to take responsibility for what has to be done.

In such organisations the problem is rarely denied. On the contrary, it is discussed with admirable seriousness. It is circulated by email, entered in reports, put on the agenda and passed from one meeting to the next.

With each pass it gains a new document.

Not necessarily a solution.

And the longer the process lasts, the more it creates the impression that someone is dealing with it.

Because people are busy.

The calendar is full. The discussions are long. The documents are updated. Everyone can show they took part in a serious effort.

Only operational reality goes on behaving as if nothing had happened.

But it would be too easy to blame meetings.

A meeting can be one of the most useful tools of leadership. It brings together knowledge that no single person has, brings to light risks that may have gone unnoticed and gives people the chance to oppose a decision before it causes consequences.

There are problems that are not solved by a quick order.

There are decisions that need extra data, technical consultation and time to understand the consequences.

Asking for more information is not weakness.

Refusing a hasty decision can be a sign of responsibility.

The problem starts when the need for care turns into an excuse never to decide.

When every answer produces a new request for analysis. When every proposal must be examined by yet another committee. When nobody can explain what information is really missing and why it is indispensable.

At that moment the organisation is no longer trying to reduce uncertainty.

It is trying to live with it, without answering for the consequences.

And that is a form of decision-making in itself.

Because even inaction is a choice.

Only it is usually the choice nobody wants to sign.

In many meetings there is a sentence that sounds like a solution:

“We need to improve communication.”

It is a convenient sentence. Acceptable to everyone. It rarely causes objections.

Nobody wants to speak publicly against communication.

But what does it mean in concrete terms?

Who has to communicate what, to whom and at which moment? Which information is not arriving? What happens when it is missing? Who checks whether the change has worked?

Without these answers, improving communication is not a plan.

It is a wish phrased in professional language.

The same goes for expressions like “we need to be more proactive”, “we must strengthen cooperation” or “we must raise awareness”.

Proper words. Words that fit into any presentation.

But an organisation does not change because it has learned to describe its problem beautifully.

It changes when someone takes it on, with a clear responsibility and a result that can be verified.

Otherwise the language of management begins to perform a strange function.

It no longer serves to make action understandable.

It serves to replace it.

There is also a more human reason why decisions are left without an owner.

Fear.

A decision creates the possibility of error. And error can have consequences for reputation, career or relations with superiors.

A discussion, however long, rarely exposes anyone in the same way.

You can back a proposal without taking on its implementation. You can voice reservations without offering an alternative. You can ask for another analysis and look prudent.

If the situation improves, everyone can recall their contribution.

If it gets worse, each can recall the warning they gave.

So the collective process begins to offer individuals a protection that personal responsibility does not guarantee them.

But fear is not always born of a lack of character.

Sometimes the organisation itself has created it.

When managers punish every decision that turns out inaccurate, even when it was taken with the best information available, people learn not to decide.

When a manager is responsible for results but has no authority to change the process, he learns to pass the problem up a level.

When an organisation asks for initiative but requires the approval of five people for every meaningful change, it is not developing leaders.

It is training people who know how to wait.

And waiting, over time, becomes part of the culture.

For this reason, responsibility cannot be set simply by writing a name next to a task.

The person must have the authority, the means and the information needed to fulfil it.

You cannot ask for operational responsibility from someone who cannot change a single element of the operation.

You cannot declare an employee responsible for a problem that needs decisions beyond his competence.

And you cannot call it delegation when the manager passes the consequences to the subordinate but keeps every right of decision for himself.

This is not a distribution of responsibility.

It is a distribution of risk towards the people with the least power to control it.

A serious organisation must define not only who is responsible, but also which decisions that person may take without asking permission at every step.

Because responsibility without authority is a promise that a person cannot always keep.

And authority without responsibility is a privilege the organisation may pay for very dearly.

Let us return to the meeting.

The same problem. The same people. The same difficulties.

But this time, before the discussion closes, someone asks a few questions.

What have we decided?

Who is responsible for implementation?

What is still unclear?

When will we check the result?

Ordinary questions, almost boring in their simplicity.

Yet they can change the nature of the meeting completely.

Because they force a distinction between what has been said and what has been taken on.

Perhaps the answer will be that there is not yet enough information for a final decision.

That is acceptable too.

But then it must be known who will provide the information, what it has to find out and when the next decision will be taken.

Perhaps it will turn out that the problem needs approval from the board.

Then it must be set who will present the request, what the alternatives are and when an answer is expected.

Perhaps the proposed solution does not work.

Then it must be revised.

But at least the organisation will have a process in which people can tell progress from repetition.

Because a problem that stays unsolved may be the sign of a real challenge.

A problem that keeps being discussed without a single defined step is the sign of leadership that is not doing its job.

This becomes even clearer when a mistake is repeated.

The first time it may be chance.

The second time it may point to a weakness in the process.

But if the same problem has been discussed several times, minutes have been written and recommendations circulated, while nothing has changed on the ground, then the way the organisation takes decisions must be investigated too.

Because the first problem is by now only half the story.

The other half is the inability to deal with it.

That is why a manager must not be satisfied with the number of meetings held, the participation of departments or the quality of presentations.

He must look for the trace they leave in reality.

What decision was taken? What changed? Was the task done? Did the intervention work? What did we learn when the result was not what we expected?

This is where management begins to be told apart from the endless administration of discussions.

Not in the ability to always have the right answer.

But in the readiness to build a responsible path towards it.

A manager who decides may be wrong.

He may even be badly wrong.

That is why important decisions must be examined, opposed when there is reason and corrected when the facts change.

But a manager who turns every issue into an endless discussion creates another problem: he deprives the organisation of the chance to learn through action.

Because a decision that is taken, carried out and evaluated produces knowledge, even when the result is poor.

A decision postponed again and again produces mostly waiting.

And waiting has its cost.

It is paid by the employees who face the same problem every day.

It is paid by the customers who do not know their concern has been discussed in three meetings.

It is paid also by the capable people, who slowly tire of proposing solutions that never get an answer.

In the end they may stop proposing.

Not because they no longer care about the work.

But because they have understood that the organisation is more interested in hearing the problem than in taking responsibility for its solution.

There is a special moment in every meeting.

It is that brief instant before people get up from the table.

The discussion is over. The arguments have been heard. Everyone has said their piece.

At that moment the manager can ask a question that is worth more than many pages of minutes:

“Who takes this on?”

There may be silence.

Someone may look at the documents. Another at the clock. It may turn out that the person who should decide is not even in the room.

That too is a useful truth to discover.

Because silence sometimes tells more about an organisation than all the speeches that came before it.

If nobody has the authority to take the responsibility, leadership must close that gap.

If the authority exists but nobody wants to use it, then the culture that made decision-making so frightening must be examined.

And if the responsibility is clear but keeps being avoided, there must be accountability.

Without these distinctions, the organisation will go on holding ever more professional meetings about ever older problems.

In the end, a meeting has not failed because people could not agree.

There can be different views, strong objections and questions left open.

It fails when everyone leaves without knowing what happens next.

Because a problem does not become a collective responsibility just because many people have discussed it.

And perhaps this is the greatest irony of some modern organisations:

They have learned to document every decision they take, but not to answer for the decisions they avoid.

In the meeting room, everyone had an assigned seat.

Only the decision was left without an owner.

And when the problem came back, nobody was surprised.

After all, it had been discussed.