The Consulting Mindset vs. The Coaching Mindset: How I Use Both Deliberately

She was a leader who had been with the organization for years. She knew the people, the history, the informal structures that actually made things work. She was competent, respected, and deeply invested in her team. And she was running at a pace that was outrunning everything she knew how to do.

The organization was a large Midwest financial services company navigating its most significant transformation by dollars spent. Multiple Big Four consulting firms were in the building. I had come in as a program manager and moved into a release management role, working to help teams of highly skilled, long-tenured leaders organize, communicate, and move together through a pace of change none of them had signed up for.

On a call with a small group, she started crying.

Not dramatically. Not as a performance. She was trying to hold her team together, navigate the change herself, and care for the people around her simultaneously, and the weight of all three hit at once. There was a moment of stillness on the call. And something shifted in me too.

What the Consulting Toolkit Cannot Reach

Up to that point, my role had been to provide structure. Templates. Heuristics. Frameworks for how to take what these teams already had and move it forward faster and more efficiently. I was helping leaders who knew where the bodies were buried learn to operate at a speed the organization was suddenly demanding. That is legitimate consulting work, and I was doing it.

But in that moment, no template was going to help. No framework was going to reach what was actually happening. What she needed was not a solution. She needed someone to stop moving long enough to see her.

I put down every tool I had. I stopped offering guidance. I stopped thinking about the project. I asked one question, something simple that created an opening rather than narrowing toward an answer, and then I held the space and let her respond.

What came out was not project-related. It was personal. It was about what she was carrying, what the pace of change was costing her at a level that no status report would ever surface. And once she said it out loud, something shifted for the others on the call too. They recognized it. They were carrying versions of the same thing.

The Switch Is Not Soft

I want to be clear about something, because this story is easy to misread. What I did in that moment was not a departure from the work. It was not a detour into feelings before getting back to business. It was the most useful thing I could have done for the engagement.

Once she said what was actually underneath it, I had real information. Not the information that appears in a project plan or a risk log, but the kind that explains why certain changes are not landing, why certain teams are slowing down, why the resistance to a particular process shift is more stubborn than the plan anticipated. That conversation gave me a map of what was actually happening beneath the surface of the transformation.

The consulting mindset asks what needs to change and how we get there. The coaching mindset asks what is actually happening for the people who have to make that change. You need both. And the moment tells you which one to use.

Most consultants stay in one mode. They arrive with answers, stay with answers, and leave the human material for someone else to handle, or no one. That is not a character flaw. It is how consulting engagements are designed. The deliverable is the work product, not the person.

But I had spent enough time in coaching rooms by that point to know what the switch felt like, and to know that the switch was available to me. That is what made the difference.

What Long-Tenured People Actually Need During Change

There is a specific kind of difficulty that arises when you ask experienced, deeply embedded people to change quickly. It is not resistance in the ordinary sense. These were not people who wanted the organization to fail. They were people who had given years to building something and were now being asked to move at a pace that felt like it was erasing that investment.

The consulting response to that is usually more structure, clearer requirements, better change management communications. All of those things matter. But they do not reach the identity question underneath the resistance, the question of who I am in this organization if the thing I have spent years building is now being replaced.

That question requires a different kind of conversation. It requires someone willing to ask what is actually going on and then stay with the answer rather than redirect it toward a solution. It requires, in other words, a coaching orientation, even when the context is explicitly a consulting engagement.

How I Hold Both Deliberately Now

The experience of that call crystallized something I had been intuiting for years. The two mindsets are not in conflict. They are sequential. Consulting without coaching misses the human material that determines whether the consulting work actually sticks. Coaching without the consulting lens can miss the organizational reality that the human material is embedded in. You need both, and you need to know which one the moment is calling for.

In practice, I read for signals. When a leader's language shifts from describing a problem to describing how the problem feels, that is a signal. When someone goes quiet in a meeting where they are normally vocal, that is a signal. When the resistance to a change is out of proportion to the change itself, that is almost always a signal that something else is going on underneath.

When I notice those signals, I stop the consulting work. Not forever. Not to abandon the deliverable. I stop long enough to ask one question and hold the space. Sometimes that takes three minutes. Sometimes it takes the rest of the call. But what comes out of that space is almost always more useful for the consulting work than whatever I would have produced by pushing forward.

I came away from that engagement with a much richer understanding of what the organization actually needed. Not the stated needs in the project charter, but the real needs of the people who were going to have to carry the change forward after the consulting firms left. Those are not the same thing. And knowing the difference is what separates change that lands from change that sits in a slide deck.

The Question Organizations Rarely Ask

Most organizations hire consultants to solve a defined problem and coaches to develop individual leaders. The two rarely get integrated deliberately. The consultant is in the room for the work. The coach is in the room for the person. And the assumption is that these are separate conversations.

But the people doing the work are also the people being developed, or not being developed, by the experience of doing it. A transformation that treats the human experience of change as a separate workstream from the change itself is missing the mechanism by which change actually happens. People do not implement changes they do not understand. They do not sustain changes they do not believe in. And they do not believe in changes that have not acknowledged the cost of making them.

I do not know if I would have understood that as clearly without the moment on that call. What she said out loud in those few minutes gave me more useful information than weeks of status meetings had. Not because the status meetings were poorly run, but because no one in a status meeting is going to say what she said. You have to create a different kind of space to hear it.

The question I still sit with is how many consulting engagements end without that space ever being created, and what it costs the organizations that paid for them.