There is an old Zen adage, articulated in numerous ways: spiritual insight is like a finger pointing at the moon — most people want to suck the finger instead of seeing where it’s pointing. What follows is finger competition, or finger adoration, and the point is obscured or forgotten entirely.
For thirty years of my consulting career across more than 200 companies on six continents, I have watched leaders make this same mistake. Not occasionally. Not in the badly run companies. Everywhere, and with a consistency that eventually stops looking like error and starts looking like appetite.
That is the argument of this essay, and it is not the one I set out to make. I began, as most people in my industry do, by blaming the supply side — the consultants who package insight into methodology and methodology into certification and certification into an annuity. That critique is fair and I will make it here. But it is incomplete, and it lets far too many people off the hook, including my clients and including me.
The uncomfortable truth is that methodology worship is not something done to organizations. It is something organizations reach for. It meets a set of human needs so reliably that the industry supplying it could disappear tomorrow and be reconstituted by Friday. This is a contagion, and like most contagions it requires a host that is receptive.
Understand why we want to be sold, and the pattern stops being mysterious. It also, finally, becomes preventable.
I. The Pattern
Frederick Taylor taught us scientific management, and the time-and-motion studies that followed ignored simple human factors like fatigue, or on the upside, motivation. The stopwatch took over from efficacy.
We embraced agile and set about perfecting the daily standup rather than assessing whether delivery had actually accelerated. Lean created a compliance bureaucracy while the waste elimination it was designed to achieve fell quietly by the wayside.
Not long ago, a colleague in Europe reported from a boardroom in Frankfurt where a $2 billion manufacturer was extolling its lean manufacturing achievement. Eighteen months in. No fewer than 47 documented procedures. Enforced compliance across all divisions. And lead times had increased by 30 percent. An exceptional operational insight had been meticulously bureaucratized, and had become a barnacle rather than a boon.
Over in Singapore, I was able to observe online as a technology company’s agile coaches facilitated — and a four-hour facilitation on a single topic is almost inevitably an oxymoron — a four-hour meeting for what became a fifteen-minute software release. In opportunity cost, the meeting was arguably more expensive than the development sprint itself. The nomenclature for this? Agile maturity. Which perversely means assessing how well agile tools are used, not how well the key aspirations behind them have been advanced.
Let me be clear: very intelligent and capable people were involved in all of the above. This is worse than bad execution. It is a disconnect between the original sponsoring intent and the action taken. In over 200 companies I can say with assurance that virtually every transformative management idea which focuses increasingly on the technical — on its own technique — and forgets the adaptive, the shift in behaviors, reflexes, communication and priorities, all the mortar in the midst of the bricks, has the seeds of its own destruction built into it. The more widespread and therefore apparently successful the approach becomes, the more emphatically it implodes.
From Taylor’s original insights mutating into factory feudalism, to the brilliant simplicity of Michael Hammer’s business process reengineering becoming a fast track to mass layoffs — shrinking the denominator rather than growing the numerator, all too often. Which led Tom Peters to intone, very aptly, that you cannot shrink your way to greatness.
The Six-Stage Death Spiral
How great ideas become great flops — and expensive ones at that.
Stage 1: Insight. A real problem is solved via genuine innovation. It is often context-specific, and where it succeeds, it tackles and transforms specific constraints.
Stage 2: Early Success. The results garner attention and attract copycats. As success stories emerge and spread, context — and how one might actually galvanize a team or a company to avail of the insight — is ignored. It is assumed that all you have to do is announce it and order it.
Stage 3: Codification. The veneer is enshrined. The visible methodology is elevated to orthodoxy and generates replicable process. Consultants declare best practice, which is all too often methodologically inward-looking rather than strategically or operationally results-driven. Frameworks and models proliferate. The tell-tale sign of this stage is multiplying complexity.
Stage 4: Institutionalization. The methodology becomes an industry standard. Certifiers abound. Training programs which confuse activity with the advancing of real goalposts expand. Kowtowing to compliance overtakes the challenging of real blinkers and recurring areas of organizational stuckness. Many otherwise excellent businesses manage to keep succeeding despite this — but there is no multiplier. On the contrary.
Stage 5: Ossification. Process-worship priests are elevated while real problem-solving becomes a drab sidebar. Teams excel at obliging the bureaucracy rather than exposing real problems or realizing true opportunities. The original need — the launch code — is forgotten. Sometimes it rears its head months or years later, just in time for the next fad du jour to come knocking.
Stage 6: Backlash. Poor results kill the entire approach. Michael Hammer once observed that we have to change how we hire if we are to do reengineering: that if you have complex processes, you need simple people for each step, but if you have a simple process, you need complex people who can exercise judgment, take calls, understand value. Nobody remembers this. It doesn’t work takes over from we implemented it incorrectly. Out goes the baby with the bathwater, and the next shiny object emerges.
Notice what the cycle costs beyond the money. Each turn of it leaves the organization more resistant to the next genuine insight. We develop antibodies. When the expensive CRM produces no better customer success — the real metric, not satisfaction alone — every subsequent attempt gets dismissed as consultant theater. Any genuinely adaptive approach is met with we tried that already. Defusing cynicism becomes the preoccupation, and the underlying wisdom, which was real, can no longer help us.
II. Why We Want To Be Sold
Here is where most critiques of management faddism stop, and where I think they go wrong. They treat the executive as a mark — a capable person separated from their budget by a persuasive stranger with a deck.
That is not what I have observed. I have watched extremely shrewd people, who would interrogate a supplier contract line by line, accept a 300-page transformation methodology with something close to relief. Relief is the tell. They were not fooled. They were served.
Six things are being served, and none of them are stupid.
The methodology manages anxiety. A real organizational problem is unbounded. You do not know its edges, you do not know if you can solve it, and you do not know how long it will take. This is genuinely difficult to sit with, particularly with a board expecting an answer next quarter. A methodology converts an unbounded problem into a bounded one: forty-five steps, eighteen months, quarterly assessments. Nothing about the underlying difficulty has changed. But the anxiety has somewhere to go. Human beings will pay a great deal for that, and rationalize the payment afterward.
The methodology is legible. You cannot present we are going to have a series of very difficult conversations and see what we learn to an investment committee. You can present a roadmap with phases and colors. The framework is a communication artifact before it is ever an operating one — and it is a superb communication artifact, which is precisely why it survives long after it has stopped operating. Much of what gets called transformation is, in truth, the production of evidence that transformation is being attempted.
The methodology diffuses accountability. This is the one nobody says aloud. If we invent our own approach and it fails, we failed. If we adopt a named, certified, industry-standard approach and it fails, the approach failed — or our execution of it did, which is a more junior person’s problem. Buying a methodology is buying insurance against blame. It is not cowardice; it is a rational response to environments where being wrong in an unusual way is punished far more severely than being wrong in the ordinary way. Change that incentive and you will find methodology worship drops sharply without anyone having to be lectured about it.
The methodology converts adaptive work into technical work. Ronald Heifetz drew the distinction that I have found more useful than any other in this field. Technical problems have known solutions and can be delegated to experts. Adaptive problems require the people with the problem to change — their habits, their assumptions, their relationships, what they are willing to say to one another. Adaptive work cannot be delegated. That is its defining feature and its unbearable feature. So we do the one thing that appears to make it delegable: we recast it as technical, hand it to a specialist, and buy a process. The specialist is happy to accept. Everyone has behaved reasonably and nothing will change.
The methodology confers belonging. There is real status in being the company that does what the admired companies do. This operates on the board, on the executive team, and in the labor market. Nobody is fired for being lean.
And truth-telling is dangerous. Telling truth to power remains a hazardous exercise in most organizations, which means rationalizing, rewriting history and hyping what was actually achieved has become an unfortunate art form. A methodology is enormously helpful here too: it supplies a vocabulary in which progress can be reported without anyone having to say what is actually happening. Compliance is reportable. Stuckness is not.
Read those six together and the supply side stops looking like a cause. Consultants who package complexity are not creating this demand; they are answering it, with great skill and considerable profit. Blaming us alone is comfortable and it is another way of not doing the adaptive work.
Which is why I have stopped treating this as a problem of vendor selection. It is a problem of what leaders are willing to tolerate feeling.
III. The Success Paradox
The most dangerous phrase in business remains best practice.
How many times over the years, in how many countries, did I hear from CEOs who wanted to implement what had worked at a peer’s company? It was legion. Show us how Google does innovation. How can we have Amazon’s customer obsession. Teach us Toyota’s lean principles.
This is finger-sucking writ large. Not intentionally, but by default. Who cares how any of these companies do anything, except insofar as you have identified issues and strategic priorities that need addressing? That is the moon shot — not injecting someone else’s ethos or techniques into your realities.
And when you hear that someone other than Google or Amazon or Toyota adopted these principles and had a breakthrough, beware. Trust but verify has never been more necessary. Such success stories, as I know from having been engaged in more than 200 adaptive transformation implementations — the good, the bad and frankly the ugly — are too often expensive lies. What worked in one specific context, with one set of leaders, with their unique culture, facing their specific challenges, at that point on their growth curve, becomes a template for failure if blindly copied.
Information always outpaces wisdom, which almost by its nature takes time. Not undue time, but the real openness to explore, to test, to calibrate and recalibrate, and to reflect collaboratively on what has been learned.
Rarely do the false starts get shared, or the numerous failed experiments that were mined for learning. The years of painful cultural change that preceded the breakthrough go unmentioned. The specific market conditions that allowed everything to come together are not highlighted. The change in the leadership team and its dynamics — and how that shifted mindset and execution culture — is not given the attention it clearly deserves. We are given the methodology Kool-Aid without being made privy to the journey, or invited to embark on our own.
The CEO’s Dilemma: Scale Versus Insight
Leaders must be prudent as well as visionary. For the first, replicable processes are sought. But breakthroughs require insight into the market, into our own organizational capabilities and dynamics, and into context. Yet boards, investors, even internal teams want proven solutions, or at least whatever is being touted by the well-known expert brands.
It is a perfect storm. Transformation must be shown to be systematic. Consultants want to offer replicable methodologies. Original thinking is unnerving when we have the misguided life preserver of best practice within reach.
The ability to solve problems, to have crucial conversations, to balance competing agendas and evaluate trade-offs — these are harder to package. We worked with a famed pharmaceutical company that hired a famed consulting firm to help restructure its R&D. Brilliant analytics followed, and an impressive intellectual construct that conceptually no one could fault.
Three years later, with the restructuring still undone, we received an agitated phone call. Millions had been spent, and heads were ready to roll if the mapped results were not delivered. We engaged the key people, and it became evident where critical conversations had not happened, how key people had not been enrolled, how downsides had not been interrogated, how passion-killers for the project had not been identified and tackled. Three months later — as these were very capable people once effectively mobilized, and as they had a frankly excellent roadmap to adapt from and build on — the restructuring was done.
Note what was actually missing. Not analysis. Not intelligence. Not even a good plan; they had one. What was missing was the adaptive work — the conversations nobody wanted to have — and no amount of technical excellence had substituted for it in three years. Three months of the real thing did what three years of the proxy could not.
Solving problems and executing solutions is a core competence we cannot afford to lose to methodological smokescreens.
IV. Three Exhibits From the Field
Exhibit One: The Manufacturing CEO Derailed by Lean Theater
European auto parts manufacturer, $800 million revenue, family-owned for three generations.
The setup. The CEO brought in a strategic ally of ours after visiting a Toyota plant. He was certain lean manufacturing would be the antidote to his struggling operation.
What he wanted to buy. Toyota’s operational discipline — waste elimination, kaizen, employee engagement especially on the front lines.
What he actually got. An 18-month consulting engagement with a 45-step lean implementation process, color-coded flowcharts, monthly compliance audits and quarterly lean maturity assessments.
Missed warning signs. More consulting time spent on PowerPoints than on the factory floor. An implementation timeline tracking training completion rather than business results. Success measured in lean tools deployed rather than measurable operational improvement. Workers complaining that they spent so much time in improvement meetings that they had no time to improve.
The moment of truth. Fourteen months in, a production line shut down when workers dutifully followed the 12-step problem-solving methodology — as they believed they were obliged to — rather than addressing an evident mechanical issue. Six hours of downtime. $2.3 million lost to delayed shipments.
Real cost. $12 million in consulting fees, 18 months of organizational distraction, and widespread workforce cynicism about improvement initiatives. My colleague, who provides exceptional value in this space, spent years afterward managing accusations that his actual process improvement work was more lean BS.
What Toyota actually does. Three simple principles: eliminate waste, respect people, improve continuously with measurement. No 45-point process. No compliance audits — just what Tom Peters called management by wandering around. Scant methodology worship, if any. Relentless focus and breathtaking pragmatism applied to true critical success factors.
Exhibit Two: The Tech CEO Who Bought Digital Transformation
Silicon Valley unicorn, pre-IPO.
The setup. Fast-growing SaaS company, brilliant technology, scaling challenges. A new CEO hired from traditional industry, intimidated by the digital-native culture rather than following Lou Gerstner’s example at IBM. Brought in a major consulting firm for a digital transformation roadmap.
What he wanted to buy. A systematic approach to scaling a technology organization, modern development practices, data-driven decision making.
What he actually got. A 24-month transformation journey with a 300-page implementation guide, close to 40 different digital maturity metrics, and unwieldy, time-leeching monthly transformation progress reviews.
The bureaucracy explosion. Engineering teams spent 40 percent of their time on transformation activities. Product releases slowed from weekly to monthly. Decision-making required consultation with a vexing transformation office. Simple changes required authorization from a newly instituted digital governance council.
The tipping point. A top engineer quit, citing death by a thousand standups. His exit interview: we used to ship code and solve problems, now we generate presentations and attend ceremonies.
The bottom line. Product velocity down roughly 55 percent. Engineering talent exodus. New hires with cutting-edge credentials would not join. A competitor captured the market opportunity during the transformation period. The company sold at a 40 percent discount to a strategic acquirer.
Note the anxiety underneath it. A CEO intimidated by a culture he did not understand bought a document that told him what to do next. It worked exactly as intended: he felt less intimidated. Everything else got worse.
What digital leaders actually do. They focus on customer outcomes delivered through technical excellence. They experiment rapidly and learn from failure. They remove bottlenecks through digital prowess. They keep transforming — it is in their DNA — so methodologies to do so are not needed. Key metrics and overarching principles provide a canopy, not a straitjacket. Ask our past client DBS Bank in Singapore. You could also ask Starbucks and Nike over that same period.
Exhibit Three: The Financial Services CEO Chasing Culture Change
Regional bank, $15 billion in assets.
The setup. A traditional bank facing fintech disruption. Board pressure for innovation. The CEO buffeted with cultural transformation stories from major technology companies.
What he wanted to buy. An innovation mindset in the C-suite and throughout, customer-centricity, fast and focused decision-making.
What the consultants delivered. An 18-month change journey playbook, 200 pages of culture-change bloviating, recurring pulse surveys, transformation scorecards, ongoing innovation workshops.
The reality check. Two years later, bureaucratic decision-making was still entrenched, the culture was still risk-averse, and customer complaints had grown more vociferous. There were, however, as a palliative, certificates galore on the wall and innovation checklists clogging internal systems.
The brutal truth. Culture is not software. It is built and encouraged and evoked and measured — not installed. Modeling the behaviors, rewarding those behaviors, and creating a team performance culture around them is what is needed, with real coaching and real metrics that matter to customers and to the market.
This is the purest case of adaptive work sold as technical work. Culture change is definitionally something the leaders must undergo. It was purchased instead as something that could be administered to the organization by a third party while the leadership continued unchanged. That was never going to work, and everyone involved was clever enough to know it.
What actually drives such change. Leadership decisions and priorities that reinforce shared values. Modeling from key leaders at all the critical epicenters of the business. Relentless communication live, where it matters, but also listening posts and relay stations so that leaders are not insulated. Hiring and firing on cultural fit. Performance coaching and accountability as non-negotiable focus areas. Time and consistency do this. None of it is new. Plato said it in ancient Athens: what is honored in a country is what is cultivated there. So too in companies.
Exhibit Four: The One Running Now
I will date this section deliberately, because the point is not the technology — it is the metronome.
I wrote a version of this essay in the autumn of 2025 and placed artificial intelligence, at that moment, at Stage Four. Chief AI Officers appearing in org charts. Governance committees convening. Certification programs beginning.
By mid-2026, IBM’s CEO study found that 76 percent of organizations had a Chief AI Officer — against 26 percent a year earlier. Beneath that role a whole stack had appeared: governance leads, ethics reviewers, auditors, risk managers. Maturity models were sufficiently standardized that vendor guides addressed themselves to “Stage 4–5 organizations” as though describing a settled taxonomy of the natural world. One widely circulated governance guide proposed a thirty percent rule — the heuristic that oversight should not consume more than thirty percent of AI development time. It was offered as a guardrail against excess.
And the results? MIT’s research found 95 percent of enterprise generative-AI pilots delivered no measurable impact on profit and loss. McKinsey found 88 percent of organizations using AI in at least one function, with roughly 6 percent capturing significant value. Two percent of C-suite executives described AI as genuinely transformative to their business. Meanwhile Stage Six had already begun to announce itself: surveys reporting that 54 percent of workers had bypassed their company’s AI tools within the past month and done the work manually, and that 29 percent of employees — 44 percent among the youngest cohort — admitted to actively undermining their employer’s AI strategy.
Stage Five, arriving roughly on schedule. Two turns of the cycle in eighteen months, where lean took a decade.
Every accelerant I listed for previous cycles applies with more force here — information velocity, board-level fear of being behind, consultants with a faster learning curve and fresher acronyms, and a technical mystique that lets a capable amplifier be sold as a next stage of evolution. But there is one that is genuinely new, and it deserves naming. Every previous cycle was rate-limited by human labor: codification took years because somebody had to write the frameworks, build the assessments and produce the training. That constraint is gone. The entire apparatus of Stage Three can now be generated in an afternoon, by the very tool in question.
None of which is an argument against the technology, which is real, and in some domains remarkable. It is an argument about us. Give this pattern a faster substrate and it does not become a different pattern. It just arrives sooner.
By the time you read this, the specifics will have moved. The cycle will not have.
Patterns as Early Warning Systems
Common leadership blind spots
- Methodology shopping — a mania for proven frameworks instead of customizing insight to your realities.
- Complexity comfort — taking undue reassurance from sophisticated (which is to say onerous) approaches, rather than from simplicity consistently and creatively implemented.
- Consultant dependency — outsourcing and delegating rather than integrating and building internal capability; being driven by external support rather than guided by it.
- Metric theater — the dance of compliance in place of the advancing of real, strategically exciting business outcomes.
Common signposts of consultancy derangement
- Expand the problem — mutate relatively simple (not necessarily easy) challenges until they are complex enough to justify a large ongoing engagement.
- Standardize the solution — solutions in search of problems; the same methodology irrespective of client reality, priority or context.
- Create certifications — ongoing revenue through a priest class requiring indoctrination and training.
- Redefine success — implementation completion against a stated game plan, rather than the advancing of the initially identified need.
The lesson in a nutshell: copying processes rather than principles. Toyota’s lean system grew organically, and their problem-solving discipline was the engine. Google’s innovation process came out of their customer obsession — and having that manifest in your company needs to be the priority, not a derivative checklist.
For any proposed step we must ask: so what? So what specific business problem does this solve? What specific opportunity does it help us realize? How does it create a culture where we improve both our performance edge and the passionate engagement of our team? These checkpoints ensure that whatever we undertake is calibrated and recalibrated against what matters — helping the best get better, or at least the currently floundering to rediscover a path to growth.
Real allies, true coaches, consultants who are genuinely expertise-rich collaborators with experience in organizational dynamics, will welcome such questions. Methodology sellers will hate them.
V. The Reframing Protocol
Having spent three decades watching brilliant insights get buried under protocol, four disciplines keep emerging. Each of them, you will notice, works by removing one of the six comforts.
Guideline 1: Institutionalize the problem, not the solution
The discipline. Document, preserve and highlight your understanding of the original challenge and the imperative flowing from it — not the methodologies galvanized to address it.
How it works. Create problem museums: real records, enlivened in reviews and added to corporate lore, of what had you stuck, what was not working, and why it mattered. This must be rendered with real examples, costs, customer laments, employee frustrations. Viscerally.
Living example. A German automotive supplier kept video documentation of their pre-lean line chaos — parts shortages, quality issues, worker frustration. Nobody could doubt there had been a genuine burning platform. When the lean effort veered toward bureaucracy, a reminder of why it had been embarked upon jolted everyone back to problem-solving and to what actually made a difference.
Leadership action. Ensure the original problem takes pride of place in every progress report and review. Everything flows from it.
Warning sign. Your team is articulate about the methodology and waffles when asked for the real critical success factors and how they connect to the identified problem.
What it removes. The anxiety relief. A problem museum keeps the unbounded thing in the room, which is uncomfortable, which is the point.
Guideline 2: Obsess over linked outcomes, not process compliance
The discipline. Measure business results, not implementation activities.
How it works. Only metrics that advance the identified aim, and the agreed definition of success or failure, get attention at any epicenter of the business.
Living example. A UK financial services company implementing customer-centricity focused on exactly four things: customer retention, Net Promoter Score, time-to-resolution of complaints, and customer business growth. When the transformation team wanted 15 additional metrics, the CEO had an easy time saying no. Retention and customer value both improved, ahead of schedule.
Leadership action. Establish the right measures early, with a clear line of sight to the imperative and the sponsoring aspiration.
Warning sign. Rewards, incentives and attention are not flowing to those measures. Leadership behavior and attention, not rhetoric, broadcasts the priorities.
What it removes. The legibility dodge. Four hard numbers are less presentable than a phased roadmap, and far more honest.
Guideline 3: Adapt, don’t adopt
The discipline. Distill the insight from the methodology. Then adapt ruthlessly to your realities.
How it works. Understand what constraints and contexts shaped the strategies in the exemplary cases. Then mine for what those insights would look like in yours.
Living example. A hotel group applying kaizen approaches in South Asia realized they were dealing with human behavior as well as product, brand and communication — and had to create before-and-after measures for each, as the Japanese did in bringing quality to core processes. They needed structure and rigor, but not a straitjacket. They needed enough interactive fluidity, with process quality guardrails. SOPs with off-ramps, they called them. Leadership and onsite team reviews, and living service values with visible and trusted metrics, mattered more to them than standard quality circles or fishbone diagrams.
Leadership action. Our practice, informed by best practice — never a mindless imitation of what others did elsewhere.
Cultural reality check. A Silicon Valley startup differs from a Japanese corporate expansion. The passion for legacy process evidenced in the world’s leading shipping and logistics company in Denmark will not mirror the exigencies of a growing Mexican family business building a regional brand. Core principles do cross borders, but cultural filtering — appreciation of context, not pandering — is what allows them to.
What it removes. The blame insurance. Adapt rather than adopt and you own the result. That is the cost and it is also the entire value.
Guideline 4: Keep the adaptive work in your own hands
The discipline. Identify, before you buy anything, which part of this problem requires you to change. That part is not for sale.
How it works. Split the work honestly. The technical portion — analysis, systems, architecture, sequencing — can and often should be bought, and good specialists will do it better than you. The adaptive portion — the conversations not being had, the priorities in conflict, the person everyone is working around, the belief the leadership team holds and has never examined — cannot be delegated to anyone. Any proposal that appears to delegate it is selling you a very expensive absence.
Leadership action. Insist on transfer of learning from your consultants. The best foster your independence rather than perpetuating your dependence. They become trusted advisors, not solution merchants. Meetings should be about results and agreed metrics. Hero stories should be about adaptation, problem-solving and the removal of barriers to execution — not about implementing a playbook. Change approaches as needed and keep the spirit of prototyping alive: be informed by exemplars as benchmarks, not as gospel.
Warning sign. The engagement is well underway, everyone is busy, and no senior person has yet had to say anything difficult.
What it removes. The delegation of what cannot be delegated — and with it, most of the reason the cycle runs at all.
Your people invariably know when something is real, valuable, delivering results and making their work better, more engaging and more effective. Keep a finger on that pulse. Remember those listening posts and relay stations.
The Real Choice
This is not merely about wasted financial resources, considerable as those are. It is about time, energy, credibility and bandwidth. If we succumb to successive methodology worship, we lose the ability to adapt and to genuinely solve current, emerging, or as-yet-unglimpsed problems.
Business environments and success factors keep changing rapidly. A capability gap in locating the right problems, focusing on real opportunities and bringing all our acumen to bear becomes fatal. Change efforts then have roughly the impact on outcomes that most rain dances have on the weather.
I called this a contagion at the outset, and I want to be precise about what I meant. Contagions are not caused by the pathogen alone. They require conditions — density, movement, susceptibility. The methodologies are the pathogen and they will keep arriving; there is no version of the future in which nobody tries to sell you a framework. What we can change is the host. An organization that keeps its original problem visible, measures only what matters, adapts rather than adopts, and refuses to outsource the work that only its own leaders can do, is not immune to fads. It simply cannot be colonized by them.
The future belongs to organizations with the highest-performing, best-led teams focused where it matters most. If leadership is largely about the value we add to the assets entrusted to us, the future belongs to those who can extract real insight from genuine innovation without being captured by the methodology built around it.
And the prize will go, finally, to those who provide adaptive capability in response — not merely technical compliance, however glittering the methodological talisman may be.
Every generation gets its own finger to suck. The moon has not moved.
Supporting Elements
Sidebar 1: The Consultant Interview Checklist
Reflection before the meeting
- Can you clearly articulate the business problem you are trying to solve?
- Do you know what success would look like in measurable terms?
- Have you documented the current-state problems in detail?
- Which part of this requires you to change? Who else knows that?
Questions to ask
- What is the simplest version of this that could work?
- Show me a company that solved this differently and succeeded.
- What is your biggest failure with this approach?
- How will we know this is working after 90 days?
- What will you need us to do that we will not want to do?
Red flags
- Complexity disproportionate to the size of the problem
- Inability to describe the approach without methodology jargon
- Success stories but no failure stories
- Timelines focused on training completion rather than results
- Nothing in the proposal requires the leadership team to change
Green flags
- Simple explanation of core principles
- Multiple examples of successful adaptation
- Honest discussion of the approach’s limitations
- Focus on your specific context and constraints
- Willingness to name what you are avoiding
Sidebar 2: Global Patterns — How Management Fads Die Differently Across Cultures
United States: speed and scale. Fads arrive fast and get implemented broadly. Focus on competitive advantage and efficiency. They die quickly when results fail to materialize, and are replaced rapidly by the next innovation.
Europe: process and compliance. Methodical adoption with regulatory consideration. Integration with existing quality systems. Death comes slowly, through bureaucratic ossification, and is harder to reverse once institutionalized.
Asia: hierarchy and harmony. Top-down implementation through organizational layers. Adaptation to consensus-building culture. Death arrives through loss of senior leadership support, though the practice may persist as ceremony long after effectiveness ends.
Emerging markets: adaptation and pragmatism. Quick adoption of whichever pieces solve immediate problems. Less concern with methodological purity. Death arrives when economic pressures shift focus — and approaches often evolve into hybrids.
Sidebar 3: The Consulting Industry’s Uncomfortable Economics
Why complexity pays
- Simple solutions mean short engagements, which mean less revenue
- Complex methodologies mean long implementations and recurring income
- Certification programs create ongoing revenue streams
- Transformation sells better than improvement
The productivity paradox
- Consultants succeed when clients need them
- Clients succeed when they no longer need consultants
- This creates perverse incentives toward dependency
What to look for in a true consulting partner
- A revenue model based on results, not time
- Focus on knowledge transfer, not ongoing dependency
- Willingness to work themselves out of a job
- A track record of clients who succeeded independently afterward
About Omar Khan
Omar Khan is founder and principal of 3S Catalyst Consulting. Over thirty years, he has advised organizations in more than fifty countries. He is the author of Loving Assertiveness, Timeless Leadership, Liberating Passion, and The Global Consultant.