Being Right Isn’t Enough

The meeting ended at eleven.

By five past, the chairs were empty, the screen was black and the remains of several interrupted coffees had begun to form rings on the table.

The idea was still there.

It had been described carefully. The evidence supported it. Nobody had found a serious flaw in it. There had been nods at appropriate moments and even a few variations of this makes sense.

But nothing had moved.

The person who had brought the idea into the room stayed behind for a moment, gathering papers more slowly than necessary. It was difficult to understand what else could have been done. The problem was real. The proposed answer was reasonable. The logic connecting the two was clear.

The idea was right.

Surely that should have been enough.

There is a particular kind of frustration that comes from watching an organisation hesitate in front of something obvious.

It is not the frustration of losing an argument. At least an argument has edges. Somebody disagrees, a position is defended and eventually a decision is made.

This was softer than disagreement.

Nobody had said no.

They had asked whether the timing was right. They wondered whether the evidence was complete. They suggested involving another team. Someone remembered a related initiative that might eventually solve part of the problem. Another person worried about creating expectations that could not yet be met.

Every concern was reasonable on its own.

Together, they formed a fog.

The idea disappeared into it.

At first, the response was to make the case stronger.

More evidence was gathered. The diagrams became clearer. The risks of doing nothing were quantified and placed alongside the risks of change. Questions raised in the first meeting were answered before they could be raised in the second.

The presentation improved.

The decision did not.

This felt deeply unfair.

We are taught to believe that organisations make decisions by weighing evidence. If the evidence is insufficient, we should find more of it. If the explanation is unclear, we should explain it better. If somebody identifies a weakness, we should strengthen it.

It is a comforting model because it suggests that progress is largely within our control.

But organisations are not machines into which we insert facts and receive decisions.

They are collections of people trying to act without losing control of everything else.

Evidence matters, but so do trust, timing, authority, attention, memory, capacity and fear. An idea can be logically sound and still arrive in an organisation that is not yet able to hold it.

That does not make the idea wrong.

It does not necessarily make the organisation foolish either.

Weeks passed.

The idea began to appear in other places.

A conversation in a corridor revealed that another team had encountered the same problem from the opposite direction. A routine report contained a figure that did not quite make sense. Somebody tried to answer a simple question and discovered that the answer depended on asking the one person who knew where the information was kept.

None of these moments was dramatic.

Individually, they proved very little. Collectively, they began to change the atmosphere around the problem.

The language changed first.

People stopped asking whether there was a problem and began asking how extensive it was. Later, they asked what would be required to address it. Eventually, someone asked how quickly the work could begin.

The idea itself had barely changed.

What changed was the organisation around it.

There was no cinematic moment of acceptance.

No one returned to the original meeting room and announced that the argument had been correct all along. There was no apology for the delay and no satisfying recognition of who had first seen the problem.

Instead, the idea slowly became familiar.

Then it became plausible.

Finally, it became necessary.

By the time the decision was made, it no longer felt like anybody’s idea. Different people had added to it, tested it and translated it into the language of their own part of the organisation. Some of the people who had once been cautious now explained its importance to others.

For a moment, that was irritating.

Then it became clear that this was what acceptance looked like.

The idea had ceased to depend upon its author.

It could survive the room without them.

Being right can become part of our identity.

We begin with a concern about the work, but after enough resistance the concern becomes personal. Every delay feels like a judgement. Every request for more evidence sounds like doubt. We stop trying to understand the system and start prosecuting a case against it.

We may still be right.

But we become less useful.

The hardest part is recognising that other people are rarely responding only to the idea in front of them. They may be remembering an earlier project that promised more than it delivered. They may be protecting a team already carrying too much. They may agree with the diagnosis but doubt the organisation’s ability to complete the treatment.

They may even fear what accepting the idea would reveal.

A problem can remain tolerable while it is thought to be isolated. Once it is understood as systemic, it creates obligations. Somebody must own it. Something must be funded. Existing priorities may have to move. Decisions made in the past may need to be reconsidered.

Sometimes the real question is no longer:

Is this correct?

It is:

Are we ready for what becomes visible if it is?

Waiting, then, is not always passivity.

Sometimes waiting means continuing to gather evidence without turning every new fact into an accusation. It means finding the people who experience different parts of the same problem and helping them see the connection.

It means allowing uncertainty to be recorded instead of tidied away.

It means replacing judgement with curiosity.

It means giving other people enough space to change their minds without demanding that they admit they were wrong.

And sometimes it means watching someone else repeat your idea and resisting the urge to reclaim it.

None of this appears in the original argument.

Yet it may determine whether the argument ever becomes action.

The decision, when it came, was almost ordinary.

It appeared on an agenda. Responsibilities were assigned. Dates were discussed. The same organisation that had once seemed unable to acknowledge the problem was now impatient to solve it.

Looking back, it was tempting to see the intervening period as wasted time.

Some of it probably was.

Organisations can use assurance as a refuge. Calls for more evidence can conceal an unwillingness to decide. Consultation can become repetition, and caution can protect the status quo long after the risks of inaction have overtaken the risks of change.

But not all delay is denial.

During that waiting period, the idea had been tested against experiences its author did not possess. The problem had acquired witnesses. The proposed answer had gained owners. People had moved from understanding the logic to believing that the organisation could act on it.

The evidence had not merely become stronger.

It had become shared.

I once thought that seeing the answer early was the difficult part.

There is a kind of confidence in that belief, but also a kind of innocence. It assumes that insight naturally produces movement and that resistance is simply a failure to understand.

Experience has made me less certain.

Being right is only one part of the story.

You must also learn whether the organisation trusts the evidence, whether people can see themselves in the answer, whether those carrying the risk have been heard and whether the system has enough confidence to move.

Sometimes an idea is rejected because it is wrong.

Sometimes it is rejected because it is threatening.

And sometimes it is not rejected at all. It is simply waiting for the conditions in which people can act upon it together.

The meeting ended at eleven.

The idea did not leave the room with us.

It stayed behind, quietly waiting for the organisation to catch up.