Why People Are Right to Be Skeptical of Organizational Consulting

The Skepticism Is Earned

Most people who have sat through a consulting engagement have a version of the same reaction: a smart-sounding deck, a set of recommendations that made sense in the room, and then very little that actually changed six months later. That reaction is not cynicism. It is an accurate read of what usually happens.

The industry's own literature admits it, even while the marketing rarely does. A model, a framework, or a well-researched best practice can be entirely correct in general and still fail to change a specific company, because the company was never the thing the model was built to describe. That gap - between what the theory says should happen and what actually happens inside one particular business - is the real story. It is a less dramatic story than the one usually told, and it is also a more useful one, because it points at something fixable.

What the Research Actually Shows

The number most people have heard is that 70% of change initiatives fail. It shows up in decks, in articles, in consulting pitches - including some of mine, before I checked it properly. It traces back loosely to a 1993 estimate about reengineering projects and later got attached to a specific figure by John Kotter. In 2011, management researcher Mark Hughes published a peer-reviewed review in the Journal of Change Management that traced the 70% claim across five separate published sources that cite it. He found no valid, reliable empirical evidence behind any of them. He returned to the same finding in a 2022 follow-up. The number is repeated constantly. It has never been demonstrated.

That does not mean implementation is easy. Harvard Business Review reported in 2022, citing Wharton research, that some 60-90% of strategic plans never fully launch - a wide range, honestly reported as a range rather than a single precise figure, which is closer to what the evidence actually supports. The difference between the two numbers matters: one is a scary statistic with no basis, used to sell urgency. The other is a wide, honestly-labeled range that says the same simple thing every operator already knows - getting a plan from paper into daily practice is genuinely hard, and most of what makes it hard has nothing to do with whether the plan was smart.

The global management consulting industry is large - core management consulting services are valued at roughly $358 billion globally in 2025 (Mordor Intelligence, an industry estimate). A lot of that spend produces a document. Not all of it produces a change.

A Model Is Not a Company

Here is the part that is rarely said plainly: a framework is built by generalizing across many companies, which means it describes none of them exactly. It assumes a budget. It assumes a certain size, a certain culture, a certain existing team, a certain appetite for risk. The recommendation that follows from the framework is correct for the average company the framework was built from. Your company is not the average company. No company is.

So the recommendation lands on a desk, gets nodded at in a meeting, and then quietly stops being anyone's job, because it was never actually sized to what this specific company has and can run. That is not a failure of the people in the room. It is a failure of fit, and fit is not something a generic framework can solve, because fit is specific to one company by definition.

The Identity-First Fix

The alternative is to diagnose the company's own situation before recommending anything: its culture, its market, its structure, its technology, its vision, and - critically - the budget and the people it actually has right now, not the budget and people a best-practice framework assumes it should have. The same underlying risk can call for a completely different fix depending on what the company is actually able to run.

This is slower to start than opening a standard framework and filling in the blanks. It is faster to finish, because the plan that comes out the other end is sized to something the company can actually execute with what it already has, instead of a plan that requires the company to first become a different, better-resourced company.

A Real Example - They Didn't Need Me

One client, a civil-engineering company, came into the first meeting with a long list of things they believed they needed - better documentation, more structure around their process, a way to capture decisions that kept getting lost. It was the kind of list that usually turns into a multi-month engagement.

I spent three hours listening. By the end, the honest read was smaller than the list: they didn't need a consultant. They needed a note-taker and a small set of agents to organize what it captured. That was it.

The only real work left was research - finding which transcription tools could actually handle their industry's dense technical jargon, in a language most transcription tools handle poorly, accurately enough to be useful on a real job site or in a real meeting. Not a platform decision. Not a six-week engagement. A specific, tested answer to a question they hadn't known how to ask.

That is the same identity-first read, working in the other direction. Sometimes the fix that fits a company is smaller than the company expected, and saying so plainly is the job.

Why It Matters That I Have Also Built the Thing

Ten-plus years before becoming a consultant, I was a full-stack developer, then a technical program manager, then a product and project manager - across fintech, digital banking, and adtech. I built credit and risk infrastructure that processed over 500,000 loan requests. I built the onboarding process for an R&D team that grew from 30 to 150 people in a year.

That background changes what I'm able to recommend, not just how I explain it. Someone who has only advised can tell a client to "get a note-taker" as a category of solution. Someone who has also built and shipped technical systems can tell them which specific tool will actually hold up against their own dense, jargon-heavy language, because knowing whether a tool's real accuracy survives a hard case is a skill built by testing things, not by reading a vendor's pitch deck.

This Is the Work I Do

Operating Architecture is the discipline I practice - reading a company's people, processes, and technology against its own identity, not against a generic playbook, and building fixes sized to what the company can actually run. That includes the first diagnosis, and it includes going back to a report or a plan that already exists and did not stick, and retailoring it to fit.

If a recommendation sitting somewhere in your company never turned into anything, that is usually not a sign the recommendation was wrong. It's a sign it was never built to fit what your company actually has.

Related Reading

• The assessment is the product - why a clear diagnosis beats an open-ended retainer.
• Why fast growth breaks companies without the right structure - the Icarus Paradox and premature scaling, the same identity-first argument applied to growth.
• The Operator-Consultant Method - the four-phase methodology behind every engagement.
• Already have a report that didn't stick? - the entry point built for exactly this situation.

Sources

• Hughes, M., "Do 70 Per Cent of All Organizational Change Initiatives Really Fail?", Journal of Change Management, 11(4), 451-464, 16 December 2011. Peer-reviewed review tracing the widely-cited 70% figure across five published sources; finds no valid empirical evidence for it.
• Belk Olson, A., "4 Common Reasons Strategies Fail", Harvard Business Review, 24 June 2022. Reports, citing Wharton research, that some 60-90% of strategic plans never fully launch.
• Mordor Intelligence, Management Consulting Services Market Analysis, 2025. Industry estimate: core management consulting services valued at approximately $358 billion globally in 2025.