The Consultant's Dirty Secret: Why Strategy Without Execution Is Malpractice

The Consultant's Dirty Secret: Why Strategy Without Execution Is Malpractice

I want to tell you something that most consultants will not tell you, because telling you would be bad for business.

The strategy document is not the deliverable. The strategy document is the beginning of the work. And the consulting industry has spent decades convincing clients that the document is the deliverable — because the document is the part that is easy to sell, easy to produce, and easy to walk away from.

What happens after the document is someone else's problem. Usually yours.

How the Model Works (And Why It Doesn't)

The traditional consulting engagement follows a predictable structure. A firm is engaged to diagnose a problem and produce a recommendation. They spend six to twelve weeks interviewing stakeholders, analyzing data, and synthesizing findings. They produce a presentation. They present the presentation. They invoice. They leave.

The client now has a strategy. What the client does not have is the organizational capability, the technical infrastructure, the change management process, or the ongoing support required to execute the strategy. These things were not in scope. They are, in the language of consulting, "implementation" — a separate engagement, a separate budget, a separate team. And a separate team who often has to modify the strategy to make it practical to implement.

This structure is not accidental. It is the product of a business model that optimizes for the production of intellectual output rather than the delivery of outcomes. The firm's incentive is to produce something impressive enough to justify the fee and generate the next engagement. The client's incentive is to have their problem solved. These incentives are not aligned.

The result is a graveyard of excellent strategy documents that never became anything.

The Execution Gap

I have a name for the distance between a strategy document and a working system: the execution gap. It is the gap between knowing what to do and actually doing it. And it is, in my experience, where the vast majority of organizational value is either created or destroyed.

The execution gap is not primarily a technical problem. It is a human problem. It is the problem of getting the right people to change the way they work, to adopt new tools, to abandon comfortable habits, to accept short-term disruption in exchange for long-term improvement. It is the problem of maintaining momentum when the initial excitement fades and the hard work begins. It is the problem of making decisions under uncertainty when the strategy document did not anticipate the specific obstacle you are now facing.

None of these problems are solved by a strategy document. They are solved by presence — by having someone in the room who is accountable for outcomes, not just recommendations.

What Execution-Based Consulting Actually Looks Like

The model I have built at Intevate Labs is deliberately different from the traditional consulting model, and the difference is not subtle.

We do not produce strategy documents and leave. We embed with the organizations we work with and stay until the work is done. Not until the presentation is delivered. Until the system is running, the team is trained, the metrics are moving, and the organization has the internal capability to sustain what was built.

This is a harder model to sell, because it requires the client to commit to a longer engagement and a more intensive collaboration. It is also a harder model to execute, because it requires us to be accountable for outcomes that depend on factors we do not fully control — organizational dynamics, leadership decisions, market conditions.

But it is the only model that actually solves the problem. And it is the only model that I can defend intellectually.

The test I apply to every engagement is simple: if I walked away today, would the organization be better off than when I arrived? Not in theory — in practice. Is there a working system where there was not one before? Is there a team that can do something it could not do before? Is there a metric that is moving in the right direction?

If the answer is no, the engagement has not delivered value. It has delivered a document.

The AI Amplification Problem

This problem is becoming more acute, not less, as AI becomes more central to organizational strategy.

The consulting industry has responded to the AI moment by producing a new generation of AI strategy documents. These documents are, in many cases, technically sophisticated and intellectually serious. They identify the right opportunities, diagnose the right constraints, and recommend the right approaches.

They also have a half-life of approximately eighteen months, because the underlying technology is moving faster than any strategy document can keep up with.

An AI strategy that was correct in 2023 may be actively wrong in 2025. The model capabilities have changed. The cost structure has changed. The competitive landscape has changed. The organizations that built their AI strategy around a point-in-time assessment of the technology are now holding a document that describes a world that no longer exists.

The only antidote to this is building internal capability rather than external dependency. Organizations that understand their own AI strategy — that have the internal expertise to evaluate new developments, adapt their approach, and make informed decisions — are not vulnerable to the obsolescence problem. Organizations that outsourced their AI strategy to a consulting firm and received a document are.

The Accountability Question

There is a question I ask every prospective client, and the reaction to the question tells me a great deal about whether the engagement will be successful.

The question is: how will we know if this worked?

The organizations that answer this question quickly and specifically — with metrics, timelines, and clear definitions of success — are the ones that are ready for execution-based consulting. They have already done the work of defining what success looks like, which means they are ready to be held accountable for achieving it.

The organizations that struggle to answer this question — that respond with vague language about "improving capabilities" or "building alignment" — are the ones that have been trained by the traditional consulting model to think of strategy as an end in itself rather than a means to an end.

These organizations are not bad clients. They are clients who have been poorly served by the industry, and who need to be helped to reframe the question before the work can begin.

The Distance Advantage

I want to say one more thing about why I think the traditional consulting model is particularly broken right now, and why I think the organizations that will win the next decade are the ones that find advisors who are willing to be accountable for outcomes.

The consulting industry is concentrated in a small number of cities. The clients it serves are, in many cases, also concentrated in those cities. And the culture of those cities — the culture of the boardroom, the conference, the strategy offsite — is a culture that rewards the production of impressive intellectual output over the delivery of measurable results.

I work from Utah. I spend time in red rock canyons and national parks. I am, by design, at a distance from that culture. And I have found that the distance is clarifying. It is easier to ask the uncomfortable question — the one about whether the strategy is actually working — when you are not embedded in the social dynamics of the industry that produced the strategy.

The question I am always asking is the one that the strategy document cannot answer: is this working? Not in theory. In practice. Are the numbers moving? Are the customers happier? Is the team more capable? Is the organization better off?

If the answer is yes, the work is worth doing. If the answer is no, the work needs to change.

That is what execution-based strategy looks like. And it is the only kind of strategy I know how to do.


Christopher Roberts is the founder of Intevate Labs, an AI-native strategy and execution firm based in Utah. He works with mid-market and enterprise organizations on AI implementation and digital transformation. To discuss whether execution-based consulting is right for your organization, schedule a conversation here.