The Moment I Realized I Was Listening to the Wrong People

For a long time, I assumed I was listening to the right people. Consultants are trained to engage leadership. We brief executives, facilitate boards, gather input from senior teams, and turn those perspectives into strategy.

On paper, that approach makes sense. Leaders hold authority. They control resources and make decisions. If you want an organization to move, you work with the people in charge.

Still, a pattern started to bother me. The people most affected by decisions often had the least influence in the room. The loudest voices shaped strategy by default.

This occurrence has been documented for years. People with lower status speak less in decision-making settings, even when they know the work best. When they do speak, their input carries less weight (Morrison, 2014).

The realization came slowly. Not one dramatic moment, more like a series of small observations that added up.

In one strategic planning session, frontline staff spoke for a few minutes near the start of the meeting. Then they spent the rest of the day listening to interpretations of their work from people several layers removed. Their comments were acknowledged politely and folded into summaries that sounded tidier than the reality they had just described.

That pattern is common. In The Wisdom of Crowds, James Surowiecki notes that the people closest to a problem often hold the most practical knowledge about how a system actually works.

I saw the same thing in community conversations. Participants described barriers in plain language, such as communication gaps, paperwork hurdles, and policies that made sense on paper but failed in practice.

Those details rarely appeared once the discussion moved into boardrooms. By the time the issue reached the strategy level, the language had shifted. The lived experience that made the problem visible had been filtered out.

Leadership meetings often followed a similar script. The conversation revolved around what felt “realistic,” usually defined by budgets, timelines, or habits. Meanwhile, the people doing the work had already found ways around those constraints.

Occasionally, planning processes include focus groups with frontline staff or surveys. Their insights are gathered, then quietly sidelined when the strategy takes shape. The voices closest to the consequences became background input instead of evidence.

No one was acting in bad faith. The imbalance was subtler than that. Airtime and authority were doing their usual work.

Most organizations say they want input from across the system. Many mean it. But when the moment arrives to define the problem or choose a direction, influence concentrates around the people who already have it.

Strategy ends up shaped by those with the most influence, confidence, and positional authority. Scholars have pointed out that strategies developed at the top often overlook practical knowledge from people closest to the work (Scott, 1998).

Hierarchy explains part of this phenomenon. Higher status participants receive more airtime and exert more influence over decisions, even when others hold better information (Anderson & Brown, 2010). Over time, authority and voice start reinforcing each other.

At first, I assumed this situation could be resolved through more effective facilitation. Maybe meetings needed a better structure. Maybe quieter voices just needed encouragement. Sometimes that helps. But the issue runs deeper than meeting technique.

It comes down to power. Who defines the organization’s problems. Who decides what counts as data. Who draws the line between realistic and unrealistic.

Once those definitions are set, the rest of the conversation tends to follow. Research on power and voice shows that people with formal authority often frame the problem and shape what counts as legitimate evidence in the discussion (Magee & Galinsky, 2008).

Consultants are not immune. In fact, the system often rewards us for reinforcing the pattern. Leadership signs the contract, and leadership evaluates the work. When a project runs smoothly, it usually means leadership felt heard. The people living with the consequences rarely complete the evaluation form.

None of this means leaders should step aside. Organizations need leadership alignment to function. But noticing the imbalance changed how I approach the work.

Now I pay attention to how conversations unfold. Who speaks early and who waits. Whose comments redirect the discussion and whose remarks earn a polite nod and then disappear.

I also ask different questions. Not just “What do leaders think the problem is?” but “Who deals with this problem every day?” Furthermore, the question “What strategy seems reasonable at the executive level?” can be enhanced by, “What happens to the people who have to implement it?” Sometimes the answers line up. Often they do not.

That shift changed how I design projects. Data collection now goes beyond leadership interviews. Conversations with frontline staff carry more weight. Community perspectives appear early instead of as a courtesy step at the end.

I also watch airtime. If the people who will experience the least disruption dominate the strategy discussion, the analysis probably is not finished.

Most of the time, restructuring the process can help integrate a 360-degree view of the organization. In many planning processes, leadership defines the problem first, and staff input arrives later. By then, the frame is already set. The discussion changes when the sequence is reversed. When planning begins with implementation insight, leaders begin with a clearer view of operational reality.

Ethan S. Bernstein (2014) found that employees often change their behavior when they know leadership is watching closely, which can hide the operational problems leaders need to see.

Participation also shifts when people feel safe to speak. Amy Edmondson’s (1999) work on psychological safety shows that small structural adjustments can increase participation from lower-status members of a group.

The goal is not to undermine leadership. It is to help leaders see the full system they are responsible for running. When that picture becomes clearer, strategy improves. It becomes less theoretical and more grounded in how the work actually happens. Sometimes the most useful insight was sitting in the room the whole time. It simply needed someone willing to listen in the right direction.

Implementation introduces another problem. Stakeholder input can turn into window dressing. Organizations run focus groups, distribute employee surveys, and gather feedback from multiple angles. Then the strategy appears, and very little of that information shows up in the final decisions. This phenomenon sometimes happens after my contract has ended.

One way to reduce the risk is to treat staff insight as data. Analyze it alongside financial information, program outcomes, and environmental scans. If staff perspectives live only in an appendix titled “themes we heard,” they rarely shape decisions.

Leaders still make the decisions. But when staff insight stays visible, strategy reflects how the organization actually works, not just how it looks from the conference room. Present those insights as evidence about how the organization operates. They become harder to ignore once they appear in the same analysis.

Some organizations also build simple mechanisms to keep staff insight visible. Staff representatives review draft strategies. Implementation teams maintain feedback loops. Strategy proposals explain how frontline input shaped the recommendation.

None of this requires a major structural overhaul. It simply prevents knowledge from the front lines from disappearing once the planning process ends.

Leaders still make the decisions. But when staff insight stays visible, strategy reflects how the organization actually works, not just how it looks from the conference room.