The Echo Chamber – When Silence Looks Like Agreement

The first trap in The Leadership Trap is the Echo Chamber. If there is one pattern that shows up in almost every major failure Aravind Sakthivel has studied, it is this one.

Somewhere in the story, someone saw the problem early. They tried to raise it and were ignored, sidelined or quietly punished. They gave up or moved on. By the time the concern reached the top table, the damage was already well advanced.

On the surface, an echo chamber does not look broken. Meetings are full. Reports are produced. Leaders ask, “Any concerns?” and hear polite silence. Everyone seems aligned. The organisation feels calm.

Underneath, dissent has gone underground. People talk in private, not in the rooms where decisions get made.

The Echo Chamber rarely arrives through explicit orders. Most leaders do not say, “Stop bringing me bad news.” It forms through quieter mechanisms.

First, people watch which messages get rewarded. Leaders react more warmly to optimistic updates than to critical ones. The people who bring good news get praise and airtime. Those who raise issues are seen as negative or difficult. Over time, anyone paying attention learns which behaviour advances careers.

Second, stories travel about what happened to past messengers. If the last person who challenged a pet project was sidelined or labelled “not a team player”, everyone else remembers. No one needs to say, “Do not speak up.” The system has already delivered the lesson.

Third, attention is stretched. Senior leaders are busy. When they are tired and pressed for time, they cut off complex, nuanced updates in favour of simple, upbeat summaries. After a while, their teams stop bringing complexity and nuance.

None of this requires malice. It only requires a system that values short term comfort over uncomfortable truth. That is one of the points Aravind Sakthivel keeps returning to. The system quietly trains everyone how to behave.

From the inside, an echo chamber can feel like strong alignment. Meetings are smooth. There are fewer visible conflicts. Decisions are made quickly and often unanimously.

The problem is that the alignment is shallow. It has not been tested. People leave the room with unspoken doubts, implement decisions half-heartedly, and look for ways to protect their own area from the consequences. By the time disagreement becomes visible, the organisation has already committed resources and reputation to a path that is hard to reverse.

The standard response is to say, “Leaders should invite feedback” or “Employees should be brave and speak up.” These are fine sentiments but weak systems. It is not enough for a leader to say, “My door is always open.” What matters is who actually walks through it, what happens when they do, and what stories travel afterward.

If speaking up consistently leads to extra work, social risk or career damage, people will stay quiet, whatever the posters on the wall say.

Breaking the Echo Chamber is a design job. Leaders need structures that make challenge a normal part of the process rather than an act of courage.

You can appoint a named challenger for each major decision and track how often their input changes the plan. You can start meetings with written concerns rather than open discussion, so hierarchy has less influence. You can run occasional red team reviews where a group is asked to stress test a strategy as if they were a competitor or regulator.

None of this is especially novel. The real test is whether you are prepared to accept the discomfort that comes with it. A functioning challenge system will slow some decisions, expose blind spots and occasionally kill pet projects. That is not a side effect. That is the purpose.

In your next leadership meeting, try one simple shift. Instead of ending with “Any questions”, ask “What is the strongest argument against this plan, and who here is least convinced by what we have just agreed.” Then stop talking and listen.

The Echo Chamber will not disappear in a week. This is slow work. But that is how the walls start to crack.


About the Author

Aravind Sakthivel - read the bio

View all posts by Aravind Sakthivel