Consultants Сan’t Fix Your Business

Why external expertise doesn't guarantee results and what actually does.

by Anna Ortynska

---

Most consulting engagements fail before the work actually starts.

I've watched this from both sides of the table. Twelve years inside a corporate world, watching consultants come and go - some left a mark, most left a deck. Now that I'm a consultant, the patterns I noticed from the inside are the same ones that decide…

A consultant isn't there to fix your business.

Most companies wouldn't put it this way out loud, but the underlying expectation usually goes something like: hire a strong expert and the problem takes care of itself. This is where most engagements start to fall apart.

A good consultant isn't there to fix your business. They're there because they've already done, at least once, what you're trying to do now. They've been through some version of the problem you're sitting in front of. They know which turns look promising but lead nowhere, which trade-offs come back to bite, which shortcuts look efficient in the moment and cost you later.

That experience is what you're actually paying for. It's what makes your work faster, saves your time and money. A consultant doesn't bring you answers you couldn't find on your own - they shorten the time it takes to find them.

But the path is still yours to walk. They can't decide for you, can't manage your team, won't be there twelve months from now living with the consequences of a decision made in a workshop. Their job is to show you the way. Your responsibility is to take it.

That's where most engagements break - when companies hire someone to point the direction and hope, somewhere underneath, that pointing will be enough.

Defaults always win.

In the first few weeks after a consultant comes, the work feels different. Conversations go deeper than usual. The team picks up new concepts. The direction of where the company is going suddenly feels more meaningful than it has in months, and there's a real sense that something has shifted this time, the change might actually stick. For a little while, it does.

Then life happens - existing operational reality reasserts itself the way it always does. Day-to-day priorities begin to compete with the new ones, and there's never quite enough room for both. Urgent work, the kind that always feels like it can't wait until tomorrow, keeps crowding out the important work, and the team gradually slips back into habits that are older than the consulting engagement and far more familiar than whatever was just introduced.

This is one of the most reliable patterns of human behavior I've observed in organizations: under pressure, teams don't rise to new knowledge. They fall back to old habits. The new concept requires effort and skills to maintain. New frameworks require attention and energy. Old patterns require neither - they're the team's default mode, and in the gap between the workshop and the next quarterly deadline, defaults always win.

The space required to think, decide, and actually implement something new becomes harder to protect with every passing week. Decisions that should have taken a week begin to stretch into a month. Insights that felt sharp and obvious in the workshop lose their force in the noise of routine operations, and after a while no one is entirely sure what was actually agreed.

There's no single moment where you can point and say things broke down. What happens instead is a drift - quiet, almost imperceptible from day to day, between what was discussed in those early conversations and what actually ended up changing.

This is why I tell leaders the same thing every time: don't hire a consultant to teach your team. Hire them to change the way your team works. Knowledge fades within weeks of leaving the room - it always has. Habits, once they take root, become the new operational reality. If an engagement ends with a smarter team but the same defaults, nothing has really changed. You've upgraded the facade, not the system.

But the shift from teaching to habit-building only works when both sides are clear about what they're actually doing. And in practice, that's where most engagements fall apart. The drift between what was discussed and what actually changed isn't random. It follows patterns I've now seen play out across industries, company sizes, and continents.

Pattern 1:” We need help with strategy” is not a scope.

"We need help with strategy" is the sentence I hear at the beginning of many meetings - it almost never means what it sounds like. Usually, it means the underlying problem hasn't been translated into anything specific yet, and the conversation has started before the thinking really happened. When the scope is this vague, the work becomes open to interpretation by everyone involved.

A good consultant, like any experienced professional, naturally defaults to patterns they've seen before - frameworks they trust, solutions that have worked in similar situations elsewhere. That's not a flaw - it's how expertise actually works in the real world. But without grounding that expertise in a clearly articulated problem of your own, the work begins to drift away from your actual reality. You stop solving the problem you came in with, and start solving a version of it that exists somewhere between the consultant's prior experience and your own ambiguous brief.

This isn't the consultant's failure, though it often gets read that way. In most cases, it started long before the consultant was hired.

Before bringing in external support, take the time to do the internal work first. Get clear on what exactly feels like a problem and where it actually shows up day to day. Ask yourself what would be visibly different if it were solved, and what kind of outcome you're really trying to influence, whether that's decisions, structure, execution, or alignment between teams. You don't need perfect clarity to begin - you need a shared starting point that both you and the consultant can build from.

Here's the nuance, though - defining the scope can absolutely be part of the engagement itself. A strong consultant won't rush into solutions in the first meeting - they'll slow the conversation down, challenge your initial framing, and help you find the actual problem underneath the one you described. That slowness is the work, even though it doesn't always feel like it. A consultant who agrees with your framing without challenging itis a warning sign worth paying attention to.

Pattern 2: Activity gets mistaken for impact.

If you can't describe what success actually looks like before the work starts, you've already guaranteed two things at the same time. The first is that real progress will be hard to measure even if it happens. The second is that disappointment becomes almost inevitable, even when the work being delivered is genuinely valuable and relevant.

Success criteria don't have to be elaborate to be useful. They just have to be clear and connect to the underlying change you're actually trying to create.

Take employee churn as an example. The problem looks like high turnover, and the common goal that gets attached to it is something like reducing the churn rate to a specific percentage. But what high churn usually reflects is something deeper: unclear roles, weak management practices or a misalignment between what people were promised when they joined and what they actually experienced in the company. Stronger success criteria, then, would focus on those underlying drivers - clearer role expectations measured through internal feedback, faster time-to-effectiveness for new hires, improved manager feedback scores in regular check-ins. The churn rate may well come down as a result, but you'll know why.

My point here isn't precision for its own sake - it's that well-defined criteria make progress visible and decisions easier to align around when things get complicated. Defined success criteria also create a more honest relationship between you and the consultant, because once success is defined, it becomes much harder to mistake activity for impact, or to talk past each other about whether the approach is actually working.

Pattern 3: Responsibility was assigned - authority wasn't.

This is one of the most common and most expensive. Consultants bring thinking, structure, and direction to the work. Implementation, though, always stays inside the company. But a lot of organizations behave as if execution can be partially outsourced together with the advice, as if recommendations, once delivered, will somehow integrate themselves into reality without anyone having to push them through the existing system. They won't.

Every real change needs ownership - a specific person who turns insight into decisions, decisions into actions, and actions into consistent follow-through over time. Without that actively in place, even the clearest direction stays theoretical and slowly fades from view as other priorities take over.

In practice, ownership is usually misunderstood. It gets treated as a formal assignment rather than a functional role. Someone gets named "responsible" sometimes thoughtfully, sometimes by default because they happened to be available and are expected to "drive the change". Beyond the role label itself, very little actually changes in how the work is set up around them, which is where the whole model breaks down.

The truth is that real ownership requires three things together: responsibility, authority, and context. It's the combination that matters, not any one piece on its own. Without the authority to make calls, the person can't actually influence decisions when it matters. Without enough context, they can't make the right ones even when they have the power to act. And without alignment from people around them, they end up spending more of their time navigating resistance than actually driving the change forward. Over time, the role becomes performative - accountable on paper, but ineffective in the daily reality of how decisions get made.

A more reliable approach involves a few connected choices:

• Choose the owner based on proximity to the problem rather than seniority or availability - the person already feeling the impact is usually the right one to drive the change, even if they're not the most senior name on the org chart.

• Give them real authority to make decisions in their scope, not just the expectation to coordinate other people's input. Coordination without authority is one of the most exhausting positions you can put someone in.

• Define the scope of ownership explicitly from the start. Be clear about what they can decide on their own, and where escalation is genuinely required.

• Identify the key stakeholders early in the process and build their support actively, rather than assuming alignment that hasn't been confirmed in conversation.

• Make sure the wider team understands what's changing and how it affects their work, especially in cases where the owner doesn't have direct authority over people they need to influence.

If these conditions are in place, ownership becomes the engine that drives execution forward. When they're not, the same role quickly turns into the bottleneck holding everything back. Change doesn't fail at the level of ideas it fails at the execution - when no one in the organization can fully carry it through.

Pattern 4: You hired a thinker, but used them as labor.

When consultants are treated as extra capacity instead of external thinkers, the nature of the work itself becomes transactional, and the value of what they can bring erodes.

Instead of challenging assumptions and expanding perspective, a consultant gets pulled into delivery: preparing materials, supporting existing initiatives, executing tasks the team doesn't have the capacity for. The work feels productive and creates real motion in the short term, but it removes the entire reason for bringing them in to begin with: the ability to see things differently from how the team already sees them.

This shift rarely happens intentionally - it's almost always pressure. Deadlines are tight, teams are overloaded, and there's a constant need to keep things moving forward. In that environment, it feels natural to use any available resource to "help get things done." It's a reasonable response to a real constraint, which is exactly why it's so easy to slip into without noticing.

Over time, the role gets reframed in everyone's mind. Instead of being someone who challenges the direction the company is heading, a consultant becomes someone who supports whatever direction has already been set. Instead of slowing things down to ask better questions, they're expected to keep up with the existing pace of execution. And that's where the real trade-off happens.

The moment a consultant fully adapts to your existing way of working, their external perspective starts to disappear with surprising speed. They become integrated into the system instead of standing outside of it and they lose the ability to meaningfully influence things they were brought in to influence in the first place.

Avoiding this dynamic doesn't require slowing everything down or pulling the brakes on the work. What it does require is protecting space for actual thinking - making room for the consultant to question, reframe, and challenge what's being assumed, even when the instinct in the room is to move faster. It also means being willing to sit with some discomfort, particularly around decisions that already feel internally settled but might benefit from being examined again.

External expertise creates value not by adding capacity to your team, but by changing how you and your team see the problem in front of you. Those are very different things, and confusing them is what turns a consulting engagement into expensive staff augmentation.

Pattern 5: You paid six figures to be told what you wanted to hear.

This is the most expensive failure mode I’ve seen, the one companies almost never recognize in themselves when it's happening.

A consultant is brought in. The first findings start to surface. They don't match what leadership was already convinced was true. And instead of treating that mismatch as the most valuable sign and starting to build on it (which is exactly why the consultant was hired) - the company shifts its posture. The conversation stops being about understanding the problem or finding the solution - and starts being about proving a consultant is wrong .

Every meeting becomes an attempt to walk the consultant back toward the conclusion the company already preferred. Counter-evidence gets surfaced. Edge cases get raised as if they were the rule. Findings get reframed in ways that soften the parts that were uncomfortable to hear. And because consultants are professionals who want the relationship to keep working, they often start adapting. The sharp, useful version of their analysis gets sanded down into something everyone in the room can live with - which means it becomes comfortable and stops being useful.

By the end of the contract, two things have happened. The company has paid full consulting rates for a deliverable that mostly confirms what they already believed, minus a few edges trimmed off and some new vocabulary to dress it up in. The bigger problem hasn't moved at all, because no one was ever willing to act on a version of the truth that contradicted the assumption they walked in with.

This is not a small mistake. It's months of senior leadership time, six-figure fees, a missed opportunity to actually change something - all spent producing a more articulate version of the status quo.

The dynamic is almost always invisible from inside the room. Leaders don't think of themselves as resisting the consultant; they think of themselves as "stress-testing the analysis" or "providing context" or "making sure the recommendation is realistic." Sometimes that's what's happening. Often, it's something more uncomfortable: the company hired someone to be challenged, and is now spending real money to make sure the challenge is contained.

If you want external expertise to actually change something, the discipline is simple but hard to implement. When a consultant tells you something you didn't want to hear, slow down. That moment is what you're paying for. Walking past it - professionally, with strong arguments and senior backing is one of the most valuable things a leadership team can do.

Summary

After years on both sides of this table, my conclusion is that the decisive variable in any engagement isn't the consultant - it's what leadership is willing to do after the consultant leaves. A consultant can show you the road and shorten it considerably. Consultants can stop you from making expensive mistakes others have already made for you, and can show you new opportunities. Whether you walk the road, and whether you finish, has always been yours to decide.

The deck doesn't matter. The responsibility you take - does.