What Is Your Organization Pretending Not to Know Because Acting on It Requires Courage?

Organizations have never had more ways to collect information about themselves. Employee surveys, pulse checks, performance dashboards, exit interviews, customer feedback, listening sessions, risk assessments, project reviews, and operational data give leaders a steady stream of information about what’s happening across the business.

Despite all this data, why do some problems persist? Why do the same concerns appear in three consecutive employee surveys? Why does turnover remain unusually high in one part of the organization? Why does a process everyone complains about continue to create delays and rework? Why does one senior leader continue to leave a trail of exhausted managers behind? How is it that a major initiative continues to struggle while the language used to describe its progress becomes increasingly “creative” month after month?

Eventually, you have to wonder whether the organization is still trying to understand the problem or has simply become very skilled at only discussing it at best—or strategically ignoring it at worst.

What is your organization pretending not to know because acting on it requires courage?

I use the word pretending carefully because organizational avoidance is rarely as simple as a room full of senior leaders knowingly conspiring to ignore the truth. Organizations are complex systems, and knowledge is distributed throughout them. The people closest to the work may see one part of a problem while managers and leaders may recognize another. Customer complaints may reveal a pattern which financial data has not yet captured. Senior leaders may receive a version of the story that’s been softened as it travels upward. I’ll leave you to ponder why that possibly happens.

There comes a point when enough signals begin to point in the same direction, to the point that continued uncertainty becomes difficult to defend. This problem leaves a trail of clues behind. You can see them in the workarounds and shortcuts people create to keep a broken process functioning. You can hear them in the warnings that seasoned managers give to new leaders about “how things really work around here.” They keep recurring in survey themes, repeated project failures, customer complaints, turnover patterns, and concerns that surface in one department only to appear six months later in another.

Sometimes, the organization already has a remarkable amount of information; but what it lacks is the willingness and courage to face the music and accept the cold hard truth that information is giving.

Asking for the Truth and Being Prepared to Hear It Are Two Different Capabilities

Research on employee voice and silence gives us a useful place to begin. In her extensive review of the research, organizational scholar Elizabeth Morrison examined why people either choose to raise concerns, ideas, and problems at work, or deliberately withhold them. The two considerations that matter are whether people believe speaking up is safe and whether they believe speaking up will make a difference. That second one deserves far more attention than it often receives.

Organizations spend considerable energy encouraging people to speak. They hold town halls, launch engagement surveys, create suggestion channels, conduct listening sessions, and assure people that they want honest feedback. Yet people also observe what often happens after someone boldly tells the truth.

Unfortunately, far too often a concern isn’t examined seriously. An important decision doesn’t get scrutinized or get a second look. Nobody explains why action could or could not be taken. And ever worse, sometimes the person who raised the issue is treated differently afterward. So, what’s happening here? Did the organization quietly wait for the conversation to disappear, or the issue to resolve itself? People learn from those experiences.

Gallup has warned that employee surveys without meaningful follow-through can actually be counterproductive. When organizations repeatedly ask for feedback but fail to act on what they hear, people become more disengaged and less willing to participate honestly in the future. That makes sense. If you ask people what is wrong five times and do nothing with their answer, eventually they will conclude that your question is ceremonial, your display of “concern” is performative, and in general, leadership is disingenuous.

This is where many organizations confuse the ability to collect information with the ability to listen. A listening mechanism only strengthens organizational capability when credible information can influence examination, decisions, and action. Otherwise, the organization has simply built a very efficient system for documenting concerns it has no intention of confronting. The uncomfortable truth may be that leaders are genuinely interested in feedback until the feedback requires something from them—the courage to act.

Perhaps it requires reversing a decision they championed. Or maybe it means confronting a powerful colleague, ceasing a favored initiative, changing an incentive system, investing money the organization hoped to save, or acknowledging that people who identify a problem leadership fails to see shouldn’t be labeled as “resistant.” Those are very different propositions from adding a question to the annual engagement survey.

The Standard of Proof Often Changes When the Truth Becomes Expensive

Having spent much of my career in performance consulting and change management, I’m a strong advocate for disciplined analysis. The loudest complaint in the room is not automatically the root cause of a performance problem. One person's experience should not always drive an enterprise decision. What’s needed is evidence, context, and the willingness to challenge initial assumptions. However, I’ve watched organizations continue to “gather data” long after the pattern was clear enough to warrant action.

Usually, you will find that they don’t need another survey, the latest quarter’s performance data, more stakeholder interviews, another needs analysis, or even an outside consultant to validate what the people on the inside have already found. While more evidence may sometimes be necessary, sometimes, the fact of the matter is that the likely conclusion is staring leaders in the face but the solution has become inconvenient.

Imagine that several teams have raised concerns about a senior leader. Turnover in that leader's area is high. Other departments consistently report difficulty working with him or her. Managers describe an environment where people are reluctant to challenge decisions. Similar themes appear in exit interviews. But the challenge is that this senior leader also produces excellent financial results. Now we have arrived at the interesting and most inconvenient—and uncomfortable—part.

If the organization accepts what the pattern is telling it, someone with authority needs to make a difficult decision. Leaders must confront a commercially valuable executive even when they may risk losing revenue or critical expertise. They must acknowledge damaging behavior that’s been tolerated for years. Worse, they must examine whether the organization's own reward and accountability systems helped protect the toxic person. Suddenly, another assessment sounds very reasonable and much preferred.

Research on organizational defensive routines helps explain how this happens. Building on the work of Chris Argyris, researchers describe defensive routines as patterns people and organizations develop to protect themselves from embarrassment or threat. These routines can restrict organizational learning because they make it easier to protect existing assumptions than to examine them honestly.

The fascinating thing about organizational avoidance is how respectable it can sound. Leaders may say they’re being prudent, waiting for the right time, protecting stability, avoiding overreaction, or ensuring they have the complete picture. Any of those explanations may be legitimate. However, the question is: “What happens when the same caution is repeatedly applied to one problem while the people carrying its consequences are expected to continue adapting around it?”

Organizations Are Very Good at Finding Safer Problems to Solve

Organizations frequently present a performance problem with a preferred solution already in place. How nice and convenient. Honestly, this is where my Performance Consultant brain begins to twitch. It often starts with the usual assumptions: people need training, managers need to learn how to coach, teams need to collaborate better, communication needs to improve, individuals need to become more resilient, people need to embrace a change. Perhaps they do. However, a competent performance analysis still needs to be conducted to examine the conditions surrounding the work.

Are expectations clear? Do people have the necessary tools and information? Are priorities aligned? Do the processes support the desired performance? Do people have sufficient authority to make the decisions for which they’re being held accountable? What behaviors are rewarded, tolerated, or quietly protected? When we examine those conditions, the original problem sometimes becomes much less convenient.

• The manager, who supposedly needs better time-management skills, is carrying an impossible workload.

• A team sent to a collaboration workshop is being measured against targets built around competing priorities which encourage protection of one’s own self interests.

• Individuals receiving resilience training are working inside a system that added six major priorities without removing a single existing responsibility.

• The so-called communication problem is actually a leadership team that hasn’t resolved its own disagreement about an important strategy.

• A training request is intended to correct behavior that senior leaders continue to model and reward or that stems from navigating broken business processes or enduring a toxic work culture.

Organizations can spend an extraordinary amount of money intervening at the level where they feel most comfortable while leaving the conditions producing the problem largely untouched. This is not always deliberate. Leaders may genuinely believe they have correctly diagnosed the issue. That is precisely why disciplined performance analysis matters. Is the organization willing to investigate whether it’s solving the actual problem it has? Or will it continue choosing to resolve the problem it prefers to believe it has?

The preferred problem is usually easier to fund, easier to explain, and much less likely to make an executive meeting uncomfortable. Funny how that works.

Is Your Organization Functioning Because People Are Good At Hiding the Damage?

Of all the patterns I’ve seen over the years, this may be one of the most deceptive. Organizations can live with serious problems for a very long time because capable people become extraordinarily good at compensating for them.

A broken process continues to produce acceptable results because an experienced person maintains an unofficial spreadsheet and manually checks every transaction. A project appears healthy because a manager spends evenings resolving problems that never make it onto the dashboard. Customers remain happy because frontline individuals improvise around a system that makes serving them unnecessarily difficult. Two departments appear to coordinate effectively because three people have spent years building personal relationships that allow them to bypass a failed formal handoff.

Leadership looks at the output and concludes that the system is working. Meanwhile, the system may be held together with human duct tape. This matters because organizations can mistake compensated performance for organizational capability. They see the outcome but fail to account for the hidden judgment, effort, relationships, and exhaustion required to produce it. The people carrying that hidden load may even be praised for their dedication. They are the go-to people. The problem solvers. The ones who always find a way. Then one of them leaves—and another, and another.

Suddenly, the process collapses, customers complain, deadlines slip, or leaders discover that no one else knows how the work actually gets done. The organization describes the problem as a loss of critical talent or an unexpected performance decline. The warning signs were there all along. The consequences were simply being silently absorbed by someone else.

This is one reason organizational avoidance is so dangerous. As long as capable people continue compensating for unresolved problems, leaders can underestimate the severity of the conditions beneath the performance they see. The organization appears capable right up until the human subsidy disappears.

So, What Does Your Organization Already Know?

I don’t believe every unresolved organizational problem is evidence of cowardice. Leaders operate with incomplete information. Resources are finite. Competing interests are real. Some decisions require patience, due process, confidentiality, and careful analysis. Courage without sound judgment can create just as much damage as avoidance.

But organizations should be willing to examine their own patterns. How many times has the same concern surfaced? How many different groups have described a version of the same problem? What workarounds have become normal? Which issues require endless proof before anyone will act? Which leaders, initiatives, or assumptions seem unusually difficult to question? Where has the organization repeatedly chosen an intervention that addresses the people experiencing the problem rather than the conditions—the root causes—producing it?

Those questions matter because an organization's ability to execute its mission, adapt to change, learn, continuously improve, and sustain worthy performance depends on the quality of the reality it’s willing to confront. Employee voice cannot strengthen the organization when speaking up is futile. Change Management cannot improve adoption when legitimate signals are automatically categorized as resistance. Coaching cannot build sustainable leadership capability when people are continually developed to compensate for broken systems. Performance Consulting cannot improve results when the organization has already decided which causes are safe to examine and which ones will consistently be ignored.

Eventually, another survey, assessment, listening session, or leadership retreat becomes one more way to postpone the question everyone is circling. Perhaps your organization does need more information. Or perhaps it already knows enough to begin. The harder question is what acting on that knowledge would require someone to risk.