The consulting industry generates roughly $300 billion in annual revenue globally. A meaningful percentage of that spend produces beautifully designed slide decks that are never implemented, strategic roadmaps that are shelved within six months, and assessment reports that confirm what the leadership team already knew. The failure rate of consulting engagements is not well tracked - for obvious reasons - but the experienced estimate from both sides of the table is that somewhere between 40 and 60 percent of engagements fail to produce the intended organizational outcome.
Most of those failures are predictable. Three questions, asked honestly before the engagement begins, will tell you whether the conditions for success exist.
1. Have you defined what success looks like in terms the organization can measure?
"Improve our operational efficiency" is not a success criterion. "Reduce average process cycle time by 20% within six months" is. The single most common structural flaw in consulting engagements is a scope of work that describes activities rather than outcomes. When the deliverables are defined as workshops, assessments, and recommendations rather than measurable organizational changes, you have purchased effort instead of results. And effort, no matter how competent, does not create accountability.
Before signing any engagement, force clarity on the success metric. If the consultant resists defining measurable outcomes, that tells you something important about their confidence in delivering them.
2. Does the internal team have the capacity and authority to implement recommendations?
The most expensive consulting mistake in business is paying for strategic recommendations that the organization lacks the bandwidth, skills, or political will to execute. This happens constantly. A consultant produces a transformation roadmap. The CEO endorses it. The leadership team nods. And then nothing happens - because the same people who were already operating at 120% capacity are now expected to implement a major change initiative on top of their existing responsibilities.
Implementation capacity is not a secondary consideration. It is the primary constraint. If the organization cannot resource the implementation, the engagement will produce insight without impact. That is an expensive way to learn what you already suspected.
3. Are you hiring a consultant because you need expertise - or because you need cover for a decision you have already made?
This is the question nobody asks out loud. But a significant number of consulting engagements are commissioned not to discover what should be done, but to validate a decision that has already been made at the executive level. The consultant's real function in these engagements is to provide external credibility for an internal conclusion - to give the board, the investors, or the management team the third-party endorsement that makes an unpopular decision politically survivable.
This is not inherently wrong. Organizational politics are real, and external validation has genuine strategic utility. But it becomes destructive when the organization pays for expertise it has no intention of actually using, or when the consultant's independence is compromised by the implicit expectation that they will arrive at a predetermined conclusion.
These three questions are not designed to discourage hiring consultants. They are designed to ensure that when you do, the engagement is structured for genuine organizational impact rather than expensive organizational theater. The best consulting relationships start with honest answers to hard questions. The worst ones start with a scope of work and a handshake.