When Change Needs Both a Consultant and a Coach

I’m excited to be on the path toward a coaching credential, and in my recent organizational development coaching classes we’ve been talking a lot about the difference between consulting and coaching during change. This has been really interesting as it’s so easy for me to focus on “fixing” mode by default as a consultant. As I reflect on my work over the past few years, I’ve definitely had projects that required a blended balance between prescriptive consulting and inquiry-based coaching.

At first glance, consulting and coaching can look surprisingly similar. Both involve helping organizations solve problems, navigate uncertainty, and move toward something better. Each discipline also requires thoughtful questions, trust, and the ability to make sense of complexity. And ultimately, if both are done well, they should help people and organizations move forward with more clarity and confidence.

I think the notable difference between them, however, is that they often work on different layers of the same system.

A strong plan isn’t the same as readiness

In consulting work, I’m often brought in because something needs to be designed, clarified, implemented, or improved. For example, a team might need help selecting software, redesigning a process that has become tangled over time, clarifying who owns what, improving a hiring process, or creating a more sustainable operating rhythm. Those are real business challenges, and consulting brings real value to them.

Sometimes an organization genuinely needs an outside perspective, a practical framework, recommendations based on experience, and someone who can help translate ambiguity into an actionable plan. I really enjoy that work, and the privilege of seeing the inside of so many different organizations. Give me a messy workflow, unclear role definition, or three different versions of the same process, and I’m probably starting a cluster map before anyone has finished explaining the problem.

But I’m also becoming even more aware that a strong plan isn’t the same thing as organizational readiness.

A project roadmap can be thoughtful, logical, and even beautifully designed, but that doesn’t mean your people are ready, willing, or equipped to implement it confidently or successfully. That doesn’t make the roadmap less important, but it does remind me that change has both a technical side and a human side…and the human side is not a soft afterthought. In fact, it’s usually where the real work of change begins.

The questions beneath the implementation plan

Let’s think about software selection as an example. A consultant can help an organization define requirements, compare vendors, select a platform, redesign supporting processes, build an implementation plan, and guide the rollout. Those pieces really matter, and if you were to skip them it would surely mean some chaos for the project!

But even the best implementation plan does not automatically answer the questions leaders and employees are likely carrying underneath the surface:

• How do I explain this change to my team when I’m still making sense of it myself?

• Why do I feel resistance to something I intellectually agree is necessary?

• What assumptions am I making about why people are not adopting the new process?

• What does my team need from me right now that is different from what they needed before?

Those are coaching questions at their core!

That distinction has been helpful for me. Coaching is not a lighter version of consulting, and it is not simply a warmer delivery mechanism for advice. I see it as a different yet very complementary discipline working a different layer of the organizational change system. Where business consulting often helps identify what should change and how the work should be structured, coaching helps leaders examine how they are experiencing the change, what beliefs or habits may be shaping their responses, and how they want to show up as they lead others through uncertainty.

If you’re like me (and probably most humans who have ever been in a leadership position), when change is moving quickly, it’s easy for a leader to default to familiar and comfortable behavior and responses. They explain more, schedule more meetings, answer questions faster, work longer hours, and try to remove every obstacle themselves. These are likely the activities that they have most experienced and practiced when under pressure in the past.

The value of a coaching conversation in this type of scenario is that it can create room to notice the difference between how we’ve always done it, and what might be possible and worth trying.

Coaching support can give leaders space to pause long enough to ask, “What is actually happening here?” What looks like a simple adoption issue may actually include:

• anxiety disguised as resistance

• grief over the loss of a process or role identity

• a lack of understanding why the change matters

• insufficient psychological safety to allow employees to talk about what they are trying to make sense of

When consultants and coaches share the change space

This is where consulting and coaching can work well together, as long as their roles are clear.

In a process redesign or operating model project, a consultant may help define decision rights, redesign workflows, clarify roles, establish governance, and recommend implementation milestones. Those decisions can reveal the new behaviors and capabilities the organization will need. For example, their leaders may need to delegate differently, managers may need to communicate more consistently, and/or teams may need to collaborate across functions in ways they have not had to before.

Those consulting insights can help inform a coaching engagement, but they should not turn the coach into an enforcement arm of the consulting plan. The consultant can help identify what the organization is trying to change, and then the coach helps the people inside the organization build the awareness, capacity, and ownership to move through that change. That boundary matters, especially when coaching happens inside an organization.

Sponsor-aligned, client-owned

Another thing we’ve discussed at length in my coursework is that organizational coaching is both sponsor-aligned and client-owned. What do I mean by that? Well, the organization may sponsor coaching (aka hire coaches) because it wants stronger leadership communication, better collaboration, healthier decision-making, or greater confidence during a change initiative. Those are legitimate business outcomes, and it makes sense for coaching to be connected to them.

At the same time, the coaching relationship still belongs to the person being coached. If a leader believes their coaching conversations are simply being packaged up and reported back to the sponsor, the possibility for honest reflection narrows quickly. Coaching depends on trust, and trust depends on clear agreements about what will be shared, what will remain confidential, and how progress will be discussed.

Protecting confidentiality doesn’t mean disconnecting coaching from organizational goals, though. Rather, it boils down to being thoughtful about what is shared, how it’s shared, and who owns the learning. Rolled up themes may be useful for the organization, but individual coaching conversations should be protected (between the coach and the coachee) unless there is a clear and ethical agreement otherwise.

This is one of the areas where I think organizations can unintentionally blur the lines. They want coaching to support business outcomes, which is reasonable. But if coaching becomes a compliance mechanism, or a way to make leaders adopt a predetermined answer, it loses the very thing that makes it valuable.

The kind of support the moment requires

The more I learn, the more excited I am about positioning consulting and coaching as complementary approaches within a project. Organizations often need both. They need thoughtful plans, useful frameworks, and practical implementation support; but, they also need leaders who can regulate their own reactions, communicate with clarity, notice patterns in the human system, and make intentional choices when the path is uncertain.

That feels especially relevant to me right now, as organizations navigate AI adoption, software implementations, process redesigns, leadership transitions, mergers and acquisitions, shifting operating models, and changing customer expectations…often while trying to keep the day-to-day work moving and the proverbial wheels on the wagon (while it’s streaking down the hill!). The technical work matters, but so does the capacity of people to absorb, interpret, and act on that work.

Coaching becomes transformational when it truly helps clients build awareness and capability that they can carry into the next change, the next ambiguity, and the next moment when their most familiar response may not be the most effective one.

My more disciplined study of coaching recently has helped me appreciate consulting more by helping me see where its boundaries are and where another kind of support may be needed.

Because organizations don’t just need better roadmaps…they need people who are equipped to navigate them with awareness, confidence, and intention, too! Before deciding whether you need a consultant, a coach, or both, it may be worth asking: Are we missing a plan, or are we missing the capacity to move through the plan?

That’s a useful question to ask before the roadmap is built. I'd be happy to talk through it with you and learn more about your situation. Contact me at Mosaic BizOps.