A project meeting ends with a final call for questions, and silence fills the room. The leader assumes the team is aligned and ready to execute. But minutes later, employees gather in the hallway. They spot operational roadblocks, question the leader’s assumptions and find workarounds to keep the plan from failing.

The issue isn’t that employees stopped learning or analyzing, but rather that their insights never traveled upward to the person holding the decision-making authority.

Silence Does Not Always Mean Learning Has Stopped

Field data from a high-power-distance organizational setting points to a different picture: Upward silence does not mean employees have checked out. When hierarchy makes direct challenges feel risky, questioning rarely stops. Instead, problem-solving and critical analysis migrate laterally. Peers talk to peers.

This is silent action learning — peer-to-peer inquiry thrives while vertical communication goes dark. If learning and development (L&D) programs measure cultural health simply by tracking who “speaks up,” they miss the real story. The absence of upward dissent often masks a highly active, largely invisible network of lateral questioning. L&D must teach leaders not only to invite feedback but also to understand where it goes and how it informs decisions. Here are a few steps to get started:

1. Train Leaders to Look for Where Questions Go

Leaders must stop asking, “Does my team speak up?” Instead, L&D should train managers to understand where and how employees actually raise concerns. Leaders should ask: Where do objections surface? Who do frontline staff consult after a major announcement? What operational fires are constantly put out at the peer level but never formally escalated?

Vertical silence routinely coexists with intense lateral problem-solving. By mapping where questioning naturally flows — and exactly where it hits a wall — L&D can help management pinpoint the specific hierarchical thresholds blocking learning across the organization.

2. Practice Receiving Challenge, Not Just Inviting It

Many leadership development programs emphasize encouraging employees to speak up, with messages like, “Keep an open door” or “I want your pushback.” But the real test of leadership comes after an employee raises a concern: How does the leader respond?

L&D must design simulations where an employee directly questions a core assumption or flags a severe operational exception. Watch the leader’s reflex. Do they immediately defend the original plan? Do they thank the employee politely but change nothing? Real capability means practicing how to take friction productively, without penalizing the person who brought it.

3. Give Questions a Route Across Hierarchy

An employee might feel perfectly safe speaking up but still lack a clear path to reach the decision-maker. L&D can help bridge this gap by building explicit organizational routes for upward challenge.

Rather than relying on abstract conversations about culture, build concrete mechanisms into the work: structured challenge rounds during planning, mandatory peer-questioning phases before project sign-off or predecision challenge sessions. The key question for L&D is purely structural: If a frontline employee sees an impending failure that a senior executive doesn’t, how does that warning reach the person who can act on it?

4. Show That Challenge Truly Changes Things

People often stop sharing insights when they realize their input changes nothing. Closing the learning loop takes more than simply thanking employees for sharing their thoughts. L&D must train leaders to make the lifespan of a challenge visible.

Build a clear sequence: A concern is raised, a response is delivered and the decision is retained, revised or escalated. Even if a leader rejects an objection, providing a substantive response proves the process works. You don’t have to agree with every challenge, but serious concerns must be consequential enough to force a definitive answer.

What L&D Should Measure

While self-reported confidence surveys have value, they are insufficient on their own. Measurement must shift to observable behavioral indicators. Consider:

• Do managers actively pull for counter-arguments during operational reviews?
• Do warnings escalate before an incident hits, rather than in the post-mortem?
• Does a valid concern have the power to pause or modify a live decision?
• Do teams know the final outcome of the objections they raise?

Conclusion

Leadership development should help organizations capture and act on the questions employees are already raising. That means paying attention not only to whether people speak up, but also to where their concerns go once they are raised.

When hierarchy keeps questions circulating among peers, organizations may solve problems locally without giving leaders the information they need to make better decisions. The leader’s job is not just to ask for feedback, but to create clear channels for it to reach decision-makers.