In my last two posts, I shared my observations about why well-meaning teams struggle to overcome complexity and create clarity in their organizations. The more I think about it, the more I believe the visible issue is often not the real issue.
No one enjoys difficult conversations. But when people keep working around the same problem instead of naming it, the problem does not disappear. It usually shows up somewhere else.
It may show up as unclear ownership, vague feedback, or quiet workarounds. Over time, people adjust to the dysfunction instead of addressing what is causing it.
Ignoring an Underlying Issue Doesn’t Make It Disappear
Avoidance often feels like keeping the peace, but over time it creates more tension and the underlying issue usually shows up somewhere else. People will quietly work around the problem instead of solving it.
Do leaders consciously avoid uncomfortable conversations about root problems?
I honestly don’t think so. Rather, I believe most often most leaders genuinely do not realize they are solving the wrong problem.
They may sense something is off, but if the current arrangement has been producing a result they care about, they are not motivated to look too closely at the dysfunction underneath it.
In other words, I do not think avoidance typically occurs when someone knowingly says, “I am not going to address this.”
Instead, I think leaders mistake momentum for organizational health, activity for alignment, or short-term results as proof that the system is working.
Where the Avoidance Shows Up
Here are some patterns I’ve observed when core issues remain under the radar.
Growth outpacing infrastructure.
I have seen companies scale quickly and then try to solve surface-level problems without addressing the operational issues underneath. From the outside, the problem may look like a content issue, a communication issue, a customer service issue, or a performance issue. But the deeper issue is that the company’s systems, people, compliance standards, and communication rhythms have not caught up with the growth.
In one case, the visible problems were showing up in social media: ad claims affecting community management, paid activity complicating organic performance, and unclear feedback as expectations changed.
But the real issue was that while paid, organic, community management, and customer experience are all connected, leadership was treating them like separate lanes.
The uncomfortable conversation to be had was not simply, “This person is difficult to work with” or “This campaign is creating problems.”
Instead, it was, “Are we letting short-term growth excuse long-term risk?”
That is where avoidance becomes costly. If a company hires outside expertise to help manage risk, volume, strategy, and growth but does not listen when that expertise identifies a deeper issue, the company ends up reacting to symptoms instead of addressing the underlying problem.
Attempting a “reset” by setting new goals or objectives.
A new goal is not the same thing as alignment. I have seen what happens when leadership changes strategic direction but does not fully realign the people, systems, partners, and expectations underneath that direction. The broader lesson for me is that a goal is not a strategy if the people responsible for executing the work do not understand how their work fits into it.
In one long-term client relationship, the #Strella team was originally brought in by leadership to professionalize and elevate the organization’s social media presence. A few years later, leadership changed and the new priority became massive digital growth within a specific time frame.
There is nothing wrong with a new leader changing direction. The issue is that when strategic direction changes, the operating model has to be realigned too. The organization needs to clarify what success now means, how existing partners fit into the strategy, who owns what, how feedback will be handled, and whether organic, paid, brand, and internal priorities are still working together.
Unfortunately, that’s not how this client approached it, and we experienced a lot of downstream confusion. Different managers had different expectations. Some were unresponsive. Some did not attend meetings. Some gave unclear or conflicting feedback. Some escalated concerns around us instead of directly to us. Outside consultants were brought in, but it was not always clear how their role connected to ours.
One moment that has stayed with me is when I asked to meet with a leader because I wanted alignment and clarity. He agreed to the meeting, but he never asked what I wanted to discuss. He assumed I was asking for more work and spent much of the conversation responding to a question I had not asked.
That taught me something important. While many leaders say, “Come to me anytime,” but giving their team members access is not the same as listening. And listening is not the same as alignment.
Another lesson from that experience is that vague feedback creates more confusion than clarity. If alignment is an issue, leaders need to define what alignment means.
Alignment can mean strategy, brand, process, or internal expectations, and people often assume they are talking about the same thing when they are not.
Alignment is not useful unless leaders define what people are supposed to be aligned around. Without that clarity, “alignment” becomes a vague explanation instead of a solvable issue.
Responsibility without authority creates drag.
I’ve also observed what happens when someone is given responsibility without the authority, scope, or decision-making clarity needed to fulfill the role.
In one situation, I was brought into a strategic role, but the scope was not clearly defined from the beginning. It was essentially described in a couple of sentences.
After the kickoff, the scope expanded significantly, and more work was added. A larger playbook was requested, and there was agency-led paid strategy, internal boosted posts, internal communications work, organic content, and multiple teams involved in different parts of the ecosystem.
There was also a call to align organic and paid efforts, but “paid” meant different things depending on who I talked with. Everyone agreed we needed alignment, but it had not been clearly defined.
Alignment between which teams? Around which decisions? And who actually owned the final call?
What I experienced was responsibility without authority. And responsibility without authority creates the illusion that a problem is being solved while making it nearly impossible to solve.
I was responsible for creating strategy and helping bring alignment to the work, but I did not have the authority to require alignment from the teams involved. Everything needed multiple layers of review, and there was no clear decision-making structure that allowed the work to move forward cleanly.
When I raised concerns about needing clarity, the response was often relationship-oriented rather than operations-focused. For example, there was lip service about the team being “like a family,” but that did not answer the practical questions centered on who owns what and who has decision-making authority?
The cost was a lot of wasted time and mental energy. Instead of focusing only on the strategy itself, I had to spend time interpreting what the role actually was, navigating internal politics, and trying to build something effective inside a structure where ownership was unclear.
That is one of the most significant hidden costs of avoiding hard conversations: work gets created around the work.
Not Every Tension Needs a Meeting
I do not think every tension needs to become a major conversation. Sometimes people need time, space, or perspective before they can name what is really happening.
But when the same issue keeps showing up in different ways, I have learned to pay attention. That usually means the visible problem is carrying something larger.
The hard part is that uncomfortable conversations rarely feel urgent until the cost of avoiding them is already part of the culture. By then, people may not even recognize it as avoidance anymore. They may just think, “This is how things work here.”
