What I Witnessed Inside Fortune 500 Organizations That Shapes Every Coaching Conversation

There is a kind of attention that most people in organizations have stopped expecting from anyone. Not agreement. Not reassurance. Just the experience of being heard by someone who is tracking what you are saying closely enough that you do not have to say it twice.

I learned how rare that is during my consulting years, working inside Fortune 500 organizations on large-scale transformation programs. I was partnered with senior leaders across finance, operations, and technology functions, helping them navigate changes they had not initiated but were expected to carry. And the lesson that shaped my coaching more than any framework or certification was not about methodology. It was about what happens when you waste an expert's time, and what opens up when you do not.

What a financial leader said in private

I was working on a large-scale organizational transformation at a global financial institution. My role was to serve as a bridge between a centralized program management office, an external consulting partner, and the business leaders whose organizations would absorb the change. One of those leaders was a senior financial executive. His background was in accounting, but his career had taken him into a business leadership role sitting one level below the executive suite for his part of the organization.

In a private conversation, he said something I have carried with me since. The sentiment was this: people kept telling him to simplify things, to make it easier, to reduce the complexity. And his response was that not everything is meant to be reduced. Some systems are complex enough that you need people who can understand the complexities well enough to interpret them and translate that understanding into what others need to do to support those systems.

Not everything is meant to be dumbed down. Some things need people who can hold the complexity and translate it, not flatten it until what mattered about it is gone.

He was not being difficult. He was describing a truth that most change initiatives skip past. There is a difference between making something accessible and stripping it until the thing that made it true is no longer there.

The cardinal sin with experts

That conversation confirmed something I had learned earlier in my consulting career, something I had felt but had not yet put words to clearly. When you work with someone who has mastered their craft, someone who is reputable, who sees patterns more naturally than others do, who has spent years building depth in their domain, there is an unspoken contract.

You can ask them questions. They expect that. They will give you their time, their knowledge, and often additional context and resources to help bring you up to speed. But there are two things they will not tolerate.

The first is questions that have not been thought through. Questions that show you did not do the work before you came to them. The second, and this is the one I call the cardinal sin, is asking the same question again. Coming back without having retained what they gave you. Without having understood why it mattered. Without having done the work to integrate what they offered before you asked for more.

That is what wasting an expert's time looks like. And I learned early that violating that contract costs you something you cannot easily recover: their willingness to open up to you at all.

Why this shapes how I coach

This is the lesson that sits underneath my coaching practice today. Not as a technique. As a discipline.

A leader who cares deeply about their craft, who has spent years developing a level of depth that most people around them do not fully appreciate, is not going to open up to someone they do not believe is listening to understand. They will not share what is actually going on if they sense that the person across from them is performing attention rather than giving it.

And the default in most developmental relationships is to take what someone shares and route it through a predetermined path. An assessment. A framework. A growth model that was built before the conversation started. People do this. Organizations do this. Parents and friends do this. It is the natural reflex when you are trying to help someone. You reach for the structure you already have rather than staying with what is actually in front of you.

But what I learned from working with those leaders, the ones who had real depth and expected you to meet them there, is that the work begins with listening for what the person is actually saying. Checking that you are in sync with what that reflects about where they are and what matters to them. And then, once you have that understanding, the discipline is to not violate it. Not to circle back to things you should already know. Not to move so fast that you are performing growth rather than doing the work of it.

Performed listening vs. the real thing

There is a version of listening that looks right from the outside. Eye contact. Nodding. Writing something down. And then when it is your turn to respond, what comes out is clearly not connected to what the person just said. It is connected to whatever the listener was preparing to say next.

I have felt that from the receiving end. I have also caught myself doing it. And what I have come to understand is that the people who matter most to my work, the senior leaders who are navigating real complexity, can tell the difference in about thirty seconds. They are not fooled by performed listening. They have been in too many rooms where people pretended to track what they were saying and then came back with something generic.

What those leaders are looking for is not someone who has all the answers. They are looking for someone who will stay with them long enough to understand the actual terrain before reaching for a map. And that requires a kind of attention that is not unlimited. You can hold it for a certain number of people and a certain number of contexts. Past that, you start performing rather than doing the real work. Managing that limit honestly is part of the practice.

What needs to stay complex

There is a version of helpfulness that simplifies everything. It takes a situation with real texture, with layers that matter, and reduces it to a framework that is easy to communicate but has lost the thing that made it true.

And there is a different version that recognizes when something is complex because the reality underneath it is complex. When the right move is not to reduce it but to sit with it long enough to see which parts can be simplified and which parts need to stay whole.

That is the discipline I am still learning. The capacity to hold complexity without collapsing it, while also knowing when something truly can and should be made simpler, is not a skill that scales without limit. There is a ceiling on how many people, how many contexts, how much subtlety you can track at the depth required. Knowing when you are at that ceiling, and being honest about it rather than pretending you are still tracking, is part of the work too.

The question I carry forward

I think about that financial leader's words more than he probably realizes. Not everything is meant to be reduced. And the corollary I carry into every coaching conversation is this: not every person is going to tell you what is actually going on until they believe you have the attention and the capacity to hold it.

The question I sit with is how often we miss what someone was about to say because they decided, in a split second, that we were not ready to hear it.