What Happens After Someone Speaks Up?
A behavioral test for leaders who want more than a listening culture
The employee said it in the meeting. The manager nodded. The agenda moved on. Three weeks later, the problem is still there, and the employee has stopped mentioning it.
From a distance, the team looks open. People are invited to speak. There is a survey, an office hour, perhaps a standing question at the end of each meeting. But the employee has learned a different lesson: speaking up has a cost, while silence keeps the day moving. Culture is not the statement that feedback is welcome. It is what people predict will happen after they give it.
Jonathan Westover has written about the gap between being allowed to speak and feeling heard, and about the small, repeated invalidations that can lead people to withdraw or leave. His question deserves an operational answer. What can a leader observe, change and test before another valued colleague decides the organization is not listening?
The Prediction Beneath the Policy
A policy can promise psychological safety. A person still has to decide whether to contradict a manager in front of peers, admit a mistake, or name a problem that nobody wants to own. That decision is social. It draws on what happened the last time someone spoke, who held the floor, whose idea received credit, and how the leader behaved when the answer was uncomfortable.
A team may insist that dissent is welcome, then reward the fastest agreement. A leader may thank someone for a warning, then ask them to fix it alone. A manager may invite ideas but leave the person who raised one out of the decision. Each moment teaches a rule more effectively than a values poster. These are not necessarily malicious acts. Their meaning depends on the pattern employees can see.
In my work at the intersection of behavioral science, social psychology and organizational culture, I have found it useful to ask not simply, "Do people feel safe?" but, "What consequence do they expect if they speak here?" The first question can yield an aspiration. The second points to a testable prediction.
Consider a team that says junior staff rarely challenge a plan. Rather than prescribe a generic confidence workshop, ask people privately to complete one sentence: "If I question the plan in this meeting, the most likely thing that happens next is..." Do not collect names or treat a single sentence as a diagnosis. Look for repeated expectations: being branded difficult, creating extra work without authority, losing credit, or watching the point vanish. Then compare those expectations with what actually happens in the next few meetings. The mismatch is the work.
Change the Next Visible Response
Leaders cannot order a team to feel safe. They can change the next response that teaches people whether speaking was worth it. This is where Westover's emphasis on follow-through and shared accountability becomes concrete. The unit of change is not the campaign. It is the response to a particular piece of information.
Try a four-part response when someone raises a concern:
Name the information without judging the person. "You are seeing a handoff fail between the service and operations teams."
Ask what would make the concern more or less likely to be true. This turns disagreement into inquiry, not a loyalty test.
Give the next step an owner and a date. "I will check the handoff with both leads by Thursday."
Close the loop in public, within the right privacy limits. Explain what changed, what did not, and why. If the idea is not adopted, say how it was considered. Silence after the conversation is itself a message.
This is a practice, not a script to recite. A leader who does the four things mechanically while retaliating later has made the problem worse. The point is consistency between words, consequences and decisions. People need to see that disagreement does not erase their standing, and that the work their input creates is shared fairly.
A Small Experiment, Not a Culture Launch
Imagine two comparable team meetings over several weeks. In the first, the leader uses the usual open-ended "Any concerns?" and notes what happens. In the second, before the decision is settled, the leader asks everyone to write one risk or missing perspective, reads the themes without names, assigns an owner to each issue that needs investigation, and reports back at the next meeting. Keep the invitation and response predictable for a few cycles.
The measure is not how many comments the leader can harvest. Count whether people raise a concern before it turns into a surprise. Track whether concerns get a documented response, whether the person who raised one stays engaged, and whether the team can explain what happened to input that was not adopted. Ask privately whether the expected consequence of speaking has changed. If it has not, examine the leader's response rather than declaring that employees need more courage.
This is not a claim that one meeting technique will cure an organization's power dynamics. People may face real risks that a meeting format cannot remove. A leader should not ask for vulnerable disclosures without protection, confidentiality where promised, and a route for issues that cannot safely be aired in a group. Nor should a manager invite dissent merely to increase performance while ignoring fairness. The test is worthwhile only if leaders are prepared to change their own behavior and share authority over the response.
What Leaders Should Ask at the Next Meeting
Westover argues that voice needs validation and visible follow-through, not just a channel. The behavioral complement is to make the unspoken prediction observable. Before asking for another survey, ask: Which person took a risk here last month? What did everyone see us do next? Whose idea was credited? Which concern has no owner? What would a reasonable person predict if they raised a similar issue today?
The answer is culture in its working form. It is a forecast built from the team's history. Change the next consequence, show the change, and ask whether the forecast moves. That is a more honest beginning than telling people, once again, that the door is open.
Jordan Bridger is the founder of Nudge Culture and works across behavioral science, social psychology and organizational culture. He holds a PhD from the University of Exeter and an MA in Cultural & Social Theory. This article is written for workplace practitioners and makes no claim that the suggested exercise has already been tested as a formal study.
