What Consultants Actually Do

The word "consultant" makes a lot of people uncomfortable.

It conjures a specific image: an outsider who arrives with a PowerPoint deck, interviews a handful of people, repackages what they already know, and bills handsomely for the privilege. Then they leave — and nothing changes.

That version of consulting exists. We've all seen it. But it's not what good consulting looks like, and it's worth being clear about the difference — especially if you're considering bringing someone in to help with a team or organizational challenge.

At its core, a consultant's job is to help an organization see itself more clearly and act more effectively.

That sounds simple. It isn't.

Organizations are complex adaptive systems. They have histories, politics, informal power structures, and deeply embedded assumptions about how things work. The people inside them are often too close to see the patterns clearly — not because they're not smart, but because proximity distorts perception. When you're inside the system, you're also subject to its pressures, its norms, and its blind spots.

A good consultant brings distance. Not detachment — distance. They can ask the question that everyone in the room is thinking but no one will say out loud. They can name the dynamic that's been present for three years but never acknowledged. They can hold up a mirror without flinching.

That's the first thing consultants do: they see what insiders can't.

Here's what separates useful consulting from the PowerPoint-and-leave variety: the best engagements start with genuine curiosity, not pre-loaded solutions.

We've worked with organizations that came to us convinced they had a communication problem. After two weeks of structured interviews and observation, it turned out they had a decision-rights problem — nobody was clear on who could commit to what, so everything got escalated, and the escalation bottleneck looked like poor communication. The fix wasn't a new communication tool. It was a clearer accountability structure.

If we'd arrived with a communication framework already in hand, we'd have solved the wrong problem.

Good consulting is investigative. It involves listening more than talking, asking more than telling, and resisting the urge to pattern-match too quickly. Every organization has its own specific version of a common problem, and the specific version is what matters.

The job isn't to deliver the answer. It's to find the right question.

When a consultant is sitting in your meetings, interviewing your team, or reviewing your processes, here's what's actually happening:

Pattern recognition. We're listening for what gets said repeatedly, what never gets said, and what gets said differently by different people. Gaps and contradictions are data.

Structural analysis. We're mapping how work actually flows — not how the org chart says it flows. Who talks to whom? Where do decisions stall? What gets done informally that should be formal, and vice versa?

Cultural reading. We're paying attention to what behaviors get rewarded, what gets tolerated, and what's treated as undiscussable. Culture isn't what's on the values poster. It's what happens when no one senior is watching.

Hypothesis testing. We're forming and revising theories about what's driving the symptoms you're experiencing. A good consultant holds their hypotheses loosely and updates them as new information arrives.

None of this is magic. It's disciplined observation combined with a framework for making sense of what you're seeing. The value isn't that consultants are smarter than the people inside the organization. It's that they're not subject to the same constraints.

One of the most important things a consultant can do — and one of the most frequently neglected — is build internal capability rather than create dependency.

The goal of a good engagement isn't to make the organization reliant on external support. It's to leave the organization with better tools, clearer thinking, and stronger internal practices than it had before. The measure of success isn't how much the consultant contributed. It's how well the organization functions after they leave.

This means the work has to include knowledge transfer. It means involving internal people in the diagnostic process, not just presenting findings to them. It means building frameworks that the team can use independently, not proprietary methodologies that only make sense with the consultant in the room.

We're explicit about this in how we structure our engagements. The Diagnostic Sprint isn't just about producing a report — it's about building shared understanding inside the leadership team. The System Build isn't just about designing new processes — it's about developing the internal capability to maintain and evolve them.

The best outcome of a consulting engagement is that you don't need us anymore.

It's worth being honest about the failure modes, because they're predictable.

When the brief is too narrow. Organizations sometimes bring in consultants to validate a decision that's already been made. That's not consulting — that's cover. The work produces a report that says what leadership wanted to hear, and nothing changes because nothing was ever really up for examination.

When there's no internal sponsor. Consulting recommendations don't implement themselves. If there's no one inside the organization with the authority, the will, and the bandwidth to drive change, the work sits in a drawer. The best external thinking in the world can't substitute for internal ownership.

When the organization isn't ready to hear what it needs to hear. Sometimes the diagnosis is uncomfortable. The problem isn't the strategy — it's the leadership team's dynamics. The problem isn't the process — it's a structural misalignment that would require a difficult conversation to fix. Organizations that aren't willing to sit with that discomfort will find ways to dismiss the findings, however well-evidenced they are.

We've walked away from engagements where the conditions weren't right. It's not a comfortable thing to do, but it's the honest thing. Consulting that doesn't produce change isn't consulting — it's expensive noise.

The engagements we're most proud of share a few characteristics.

The leadership team was genuinely curious — not just about the symptoms, but about the underlying causes. They were willing to have the hard conversations, including about their own role in the patterns we identified.

The work was collaborative. We weren't delivering findings to a passive audience. We were building understanding together, with internal people as active participants in the diagnostic process.

The recommendations were specific and actionable, not generic best practices dressed up in new language. And there was a clear plan for implementation, with internal ownership at every step.

And when we left, the organization was stronger — not because of what we'd done, but because of what they'd learned to do for themselves.

That's what consultants actually do. At least, the good ones.

If you're wondering whether your team or organization could benefit from this kind of work, the Team Resilience Assessment is a good place to start. It takes about fifteen minutes and gives you a structured picture of where your system is strong and where it's under strain.