Visibility is a bridge
Why communicating direction isn’t the same as building understanding
One of the humbling things about riding and training horses is realizing that, at first, they don’t know what you’re thinking or what you want.
You may know exactly what you’re envisioning or trying to teach them. You know when you want to stop, change direction, or ask for more speed. But unfortunately, last time I checked, they don’t speak our language.
We have to build a bridge across that communication gap through our cues. The horse only knows what we’ve made visible through pressure and release. When those cues are clear and consistent, understanding begins to develop. When they’re late, conflicting, or nonexistent, the horse gets confused, frustrated, and often disengaged.
Our employees and the teams we lead aren’t all that different.
As leaders, we often have earlier access to the full picture—the conversations, financial realities, customer insights, competing priorities, risks, and decisions that eventually lead to a change in direction or strategy. We’ve had time to process the information, build context, and understand why the change is coming.
Then everyone else gets the announcement.
Leadership experienced the journey. Everyone else received the destination.
And somehow, we expect immediate alignment, understanding, and buy-in.
But the announcement isn’t the end of the work. In many ways, it’s the beginning.
The people receiving the decision haven’t had the same opportunity to build context as the people making it. They didn’t sit through the conversations, weigh the tradeoffs, or see the information that shifted the thinking along the way.
They know what has changed. They may not understand why.
And that understanding doesn’t happen overnight. This is where I think visibility becomes one of the most underestimated bridges in leadership. When I say visibility, I don’t mean physical presence. I don’t mean being seen walking the halls, attending every meeting, or making sure people know what you’re working on.
I mean visibility into the why.
The context. The considerations. The tradeoffs. The direction. The connection between the decision being made and where the organization says it wants to go. Communication can tell people what is happening.
Visibility helps them understand why.
What does visibility actually look like?
Visibility into the why: Instead of simply announcing, “We’re consolidating these two teams,” give people the strategic reasoning. What problem are we solving? What changed? What alternatives did we consider? Why did this option make the most sense? People don’t need every confidential detail, but they need enough to understand the logic.
Visibility into the tradeoffs: Leaders often announce the chosen path without acknowledging what had to be sacrificed to choose it. Saying, “We knew this would create additional workload in the short term, and we weighed that against…” shows people that leadership saw the consequences they may be experiencing. It doesn’t make those consequences disappear, but it can change how the decision is perceived.
Visibility into the destination: People need to understand what we’re trying to create, not merely what we’re changing today. Where is this supposed to take us? What should be better six months or three years from now? What does success look like?
Visibility into connection: Help people understand what the decision has to do with them. How does their work connect to the broader direction? What changes about their priorities? What doesn’t? What decisions can they make differently because they understand where we’re headed?
Visibility into progress: Don’t explain the why once and disappear. Come back to it. Here’s what we’ve learned. Here’s what’s working. Here’s where our original assumption was wrong. Here’s what we’re adjusting. Strategy isn’t always a perfectly linear march forward. We are all human, after all.
And then there’s visibility into the process before the decision, when appropriate. This one might be my favorite.
Sometimes the best way to create understanding isn’t explaining a finished decision better. It’s allowing people closer to the problem while you’re still working through it. Ask for input. Share the problem you’re trying to solve. Let people see some of the constraints.
Even if they don’t ultimately get the outcome they preferred, they’ve had visibility into how everyone got there—together.
As leaders and conveyors of information, we need to get used to asking:
What do I know about this decision that they don’t?
What did I learn during the journey that makes the destination make sense to me?
What assumptions might people make if I don’t provide context?
What tradeoffs do they need to understand?
How does this connect to the direction or other key initiatives we’ve already rolled out?
Visibility may not eliminate disagreement, but it can reduce the confusion, frustration, and resistance created when people are asked to move without understanding why.
If our people understand the direction, the why, the guardrails, and the tradeoffs, leaders don’t have to prescribe every decision.
When visibility is missing
When there is a lack of visibility and a culture of top-down announcements made without context or the why, I often see division begin to form.
It becomes an “us versus them” battle.
I hear the broken record of phrases like, “Corporate said this,” “They decided,” “They want us to…” or “That came from leadership.”
Pay attention to the language.
They. Them. Corporate. Leadership.
Those words create distance and division. And quite frankly, they make me cringe.
Sometimes that distance reflects genuine disagreement. But often, I think it’s a symptom of something much simpler: people are being asked to execute decisions they were never given enough visibility to understand.
The people making the decision may have spent weeks or months reviewing information, considering alternatives, weighing tradeoffs, and eventually arriving at something that feels completely logical.
The people receiving it may have had a 30-minute meeting.
When we leave a gap between the two, people naturally begin filling it with their own assumptions:
They don’t understand what it’s like out here.
They don’t care how this impacts us.
They’ve already made up their minds.
They’re losing focus on what really matters.
But the same thing happens in the other direction.
Leaders hear resistance and begin telling their own stories:
They don’t understand the bigger picture.
They just don’t like change.
They aren’t thinking strategically.
They just want it to be the way it’s always been.
Now both sides are assigning intent to behavior without having visibility into the perspective of the other.
That’s why I don’t think visibility can be a one-way bridge.
Leadership has information and context that people closer to the work may not have. But the people closest to the work have customer insight, operational realities, local knowledge, and experiences leadership may never see.
Both sides have visibility that the other needs. It takes all of us.
The goal isn’t for everyone at every level to see and know everything. It’s to build enough of a bridge that we can understand what the other side can see from their lens.
Visibility isn’t the same as transparency
As a younger, emerging leader, I leaned heavily toward transparency. I believed that if people had access to the information, they could better understand the decisions being made.
With experience, I’ve come to understand that not every detail needs to—or even can—be shared. There are legitimate reasons for confidentiality. Personnel matters, negotiations, financial information, legal considerations, and plenty of other conversations require discretion.
However, the reality is that most of us aren’t working for the CIA.
Not every conversation is classified. Not every piece of context is proprietary. And not every decision needs to arrive wrapped in secrecy simply because it was made at a level of the organization where others weren’t in the room.
There is almost always something we can share that creates a pathway to understanding.
Maybe we can’t share every detail of the financial situation, but we can explain the financial pressure we’re trying to address.
Maybe we can’t share the specifics of a personnel decision, but we can reinforce the principles guiding how we’re structuring the team.
Maybe we can’t discuss everything that happened during a negotiation, but we can explain the strategic considerations behind the direction we chose.
Maybe the decision itself isn’t up for debate, but we can still explain why it was made.
Visibility doesn’t require full access. It requires a pathway to understanding.
Confidentiality can be necessary. Opacity shouldn’t be the default.
Sometimes “I can’t share that” is absolutely true. But sometimes it has simply become the easiest answer.
The better question might be:
“What can I share that will help people understand?”
Which brings me back to the horse—Pressure and release work because it’s a conversation. We ask. We listen for a response. We adjust. We release. Over time, what started as a communication barrier becomes a shared language. But imagine if all we ever did was apply pressure.
More leg. More rein. More asking. More demanding.
Without ever paying attention to what was coming back. Eventually, we’d find ourselves with a confused, frustrated, or disengaged horse—and wondering why our cues weren’t working or why things weren’t moving forward as quickly as we’d hoped.
I think organizations can do the same thing.
We announce. We communicate. We roll out. We cascade. We ask people to execute.
Pressure. Pressure. Pressure.
But visibility requires some release.
It requires enough give and take for people to ask questions, challenge assumptions, share what they’re seeing, and understand the context behind what they’re being asked to do. And just like with a horse, that understanding isn’t built through one perfect cue or one great ride. It develops over time through consistency.
Leaders make the why visible. People closest to the work make the realities visible. Both sides adjust based on what they’re learning from each other.
That’s the bridge.
It doesn’t mean everyone gets every piece of information. It doesn’t mean every decision becomes a democracy. And it certainly doesn’t mean leaders stop leading. It means we stop confusing an announcement with understanding.
So, before the next announcement gets sent, the next strategy gets rolled out, or the next change gets handed down, maybe the question isn’t simply:
“Did we communicate it?”
Maybe it’s:
“Have we built enough of a bridge for them to understand it?”
-HL
The Strategic Cowgirl

