How EY’s $100 Billion Bet Collapsed Under Its Own Weight
What could sink an international transformation project worth over $100 billion, led by one of the world’s biggest organisations?
The answer is grudges, collusion, and Borgesian-level corporate politics.
The kind of plotline that would not feel out of place in Succession, only this time it did not unfold on HBO. EY spent years designing a future-defining restructure, only for it to crumble under internal politics, misaligned incentives, and organisational fatigue.
A Vision Unravelled
In 2023, EY attempted something unprecedented within the Big Four: a full structural split. Project Everest was positioned as a fundamental reconfiguration of the business: AuditCo on one side, NewCo on the other. The restructure was meant to resolve systemic challenges around conflicts of interest that had stymied growth for years and unlock a new era of advisory autonomy and success. Independent valuations placed NewCo above $100 billion, and internal projections promised significant acceleration on getting projects end-to-end, something teams had been calling for a significant period of time.
“A once-in-a-generation restructuring that promised to transform the firm.”
The Financial Times
Public narrative aside, internal resistance escalated immediately. The strongest opposition came from US tax partners, who believed the separation would weaken their unit economically and dilute their long-term influence. Their position became so entrenched that, by the time the global audience heard the name Project Everest, the initiative was already collapsing.
The decisive moment arrived when the US member firm, the most profitable and politically dominant part of the network, refused to support the split. The final, fatal blow revealed that the highly publicised notion of global alignment had no real foundation in reality and that the idea of a shared vision was little more than a false flag.
Internal Fault Lines Exposed
What brought Project Everest down was not a deficit in vision, strategy, or resources. It was the inability to address the deep-rooted dissidence surrounding the initiative from the very beginning. The resistance was structural. It existed within economic interests, historical grievances, regional priorities, and the unspoken negotiation of who would benefit and who would not.
Key inhibitors were clear:
- Entrenched loyalties within specific service lines
- Conflicting economic interests across regions and functions
- A governance structure that awarded veto power instead of shared accountability
- Consistent cultural norms across more than 100 semi-autonomous member firms
- Accumulated change fatigue left little appetite for additional disruption.
“Leaders underestimated the cultural and governance complexity of coordinating more than 100 member firms.”
Accounting Today
It’s important to note that Project Everest didn’t create these tensions, but rather exposed them to plain light. The further the project advanced, the more diametrically opposed the internal positions became. Instead of building alignment, the initiative triggered defensiveness, avoidance, and a rapid escalation of territorial behaviour, spelling disaster for everyone involved.
The Agile Alternative
If Everest had been built through an iterative, embedded model rather than a global, all-at-once restructure, the trajectory could have been materially different. The issue was never the scale of the ambition. It was the insistence on deploying a major transformation with no pilot environment, no evidence base, and no mechanism for identifying organisational appetite or resistance.
A more adaptive consultancy approach would have taken a different route:
- Begin with one region or service line and assess the real-world impact
- Identify conflicting incentives at the start rather than after escalation
- Embed cross-functional teams within affected units to understand friction directly
- Create short, structured feedback cycles between local partners and global leadership.
- Build a case for expansion based on operational evidence, not visionary ideals.
“Partners feared the split would weaken their units, triggering a chain reaction of opposition.”
Bloomberg
An agile approach treats this type of reaction as critical information. It shows where the organisational architecture contradicts the intended strategy and triggers a protocol to stop and reassess before moving ahead. It requires the plan to adapt, rather than forcing the organisation to absorb a trajectory it fundamentally doesn’t support.
This distinction is entirely operational. You either design with the organisation, or you design against it, and the Everest Project demonstrated the consequences of the latter with absolute clarity.
The Takeaway
Project Everest is not an isolated event. It is the most publicly documented case of a deeper organisational pattern. Large enterprises consistently overestimate internal alignment and underestimate the practical realities required for transformation. The same sequence appears across industries: ambitious announcements, strong projections, and then a predictable collapse upon implementation.
The failure was not about EY’s scale, the complexity of its work, or the ambition behind the strategy. It stemmed from ignoring a fundamental organisational truth – you cannot impose a transformation that the system is structurally and culturally unable to absorb. When incentives, governance structures, and operating realities are misaligned, the outcome has been decided long before execution begins.
Organisations that succeed are not those that make the largest declarations. They are the ones willing to test early, adapt quickly, and build momentum through smaller, verifiable steps rather than committing to an untested enterprise-wide redesign.
If your organisation is navigating a high-stakes transformation, or if you need an agile, embedded approach that aligns strategy with reality, get in touch.
Disagree with our take? Join the conversation on LinkedIn or share this article with your network and see what your peers think.
