06
Mahat Advisory
Intelligence Hub · White Paper Series
White Paper 06 of 07
Execution Firewall Series

The Execution
Crisis

Why ASEAN projects fail at implementation — and the leadership architecture that closes the gap between strategic intent and operational delivery.

95% GenAI pilots fail to show ROI 1 in 5 enterprise projects fails US$2.3T annual failure cost 4 execution layers mapped
Ts. Dr. Manju AppathuraiDual PhD · Licensed Psychologist · 21 Years WTO/World Bank · Founder, Mahat Advisory
Mahat Advisory
White Paper Series · 2025
mahatadvisory.com

The Project Management Institute's 2025 Pulse of the Profession report found that about 80% of enterprise projects met business goals — meaning one in five did not. The MIT 2025 report "The GenAI Divide" found an eye-popping 95% failure rate for enterprise generative AI pilot projects, defining failure as those not showing measurable financial returns within six months.

Globally, failed digital transformation efforts cost organisations an estimated US$2.3 trillion per year. ASEAN's share of that figure — given the region's extraordinary investment pace in digital infrastructure and AI — is growing faster than any other region. This is not a new problem. It is a persistent one: the failure rate of strategic implementation in ASEAN has remained stubbornly consistent across a decade of increasing investment, improving technology, and accumulating experience with what goes wrong.

This paper identifies the four layers of execution failure that account for the majority of that persistence — and the Execution Firewall architecture that addresses each layer structurally.

95%
GenAI pilot projects failing to show measurable financial returns within 6 months
MIT "The GenAI Divide" 2025
1 in 5
enterprise projects failing to meet business goals globally
PMI Pulse of the Profession 2025
US$2.3T
annual cost of failed digital transformation projects
Gartner, cited in MeltingSpot 2025–26
The Execution Crisis Anatomy

Four Layers Where ASEAN
Implementation Breaks Down

Strategic execution failure is rarely a single point of collapse. It is a cascade — each layer of failure making the next layer harder to address. The four layers below map that cascade in the ASEAN context.

CIO Magazine's 2025 analysis of why IT projects still fail identifies the evolution of "failure": today, failure does not mean a system technically doesn't work. It means "an IT project doesn't deliver expected benefits, runs so late as to be obsolete when completed, or doesn't engage users who then shun it." This redefinition of failure is important for ASEAN leaders — because it moves the diagnostic focus from technical delivery to strategic value realisation, which is where the real failure consistently lives.

01
Layer One
Strategic Misalignment — Projects Without a Clear "Why"
The Failure Mechanism
The most consistent finding across execution failure research is that projects which cannot articulate a clear, measurable link between the initiative and a business outcome fail at a substantially higher rate than those that can. MeltingSpot's 2025 analysis finds that "companies treat digital transformation as a technology upgrade project rather than a business transformation. Goals are vague or overly tech-centric — 'implement an AI platform' — with no clear linkage to business outcomes." Without strategic clarity at the outset, projects meander, scope drifts, leadership attention wanders, and the initiative eventually dies of ambiguity. Asana's 2025 project management research identifies "unclear objectives" as the leading cause of project momentum loss.
ASEAN Amplifier
In ASEAN's hierarchical organisations, strategic ambiguity at the C-suite level is amplified through the hierarchy. If the C-suite is not clear about why a project exists, middle management will fill the gap with their own interpretation — which typically defaults to risk minimisation and compliance rather than value creation. By the time the strategic misalignment becomes visible in project outcomes, it has been institutionalised through months of middle-management decisions made in the absence of clear direction. The cultural norm of not challenging upward means the misalignment is never surfaced directly — it is simply delivered faithfully as the C-suite's ambiguous intention.
02
Layer Two
Governance Vacuum — No Single Point of Accountability
The Failure Mechanism
CIO Magazine's research identifies one of the most practically significant execution failure drivers: "expensive and highly visible projects get the benefit of being led by professional project managers, but small and midsize projects often don't." Projects assigned to business analysts or functional managers without project management training, time, or authority consistently underperform. The Asana analysis adds the leadership dimension: "even well-planned projects can slow down if leaders aren't involved. Without their support, teams may have trouble getting resources, budget, or help from other departments they need." Executive sponsors who were enthusiastic at launch and then unreachable at implementation are one of the most commonly cited drivers of project failure.
ASEAN Amplifier
In ASEAN's multi-stakeholder environments — where projects frequently require cross-functional and often cross-market coordination — the absence of a clear accountability owner creates coordination vacuums that cultural dynamics then fill in unhelpful ways. When nobody owns the outcome, everyone optimises for their own function. When nobody owns the timeline, face-saving dynamics make schedule slippage invisible until it becomes catastrophic. The governance vacuum is particularly damaging in multi-market ASEAN implementations, where the absence of centralised accountability allows each market to adapt the project to local preferences rather than deliver the consistent implementation that the original strategic intent required.
03
Layer Three
Process Acceleration — Technology Over Bad Foundations
The Failure Mechanism
MeltingSpot's analysis contains the most practically useful description of this failure: "automating a chaotic manual process in SAP without standardising it will simply produce chaos faster." The failure pattern is consistent: organisations deploy technology as the solution to problems that are fundamentally process or governance problems — and discover, expensively, that technology accelerates whatever it implements, including dysfunction. The 2025 MIT GenAI study's finding that 95% of pilots fail to show ROI within six months reflects this pattern: organisations are deploying AI tools into workflows that have not been redesigned to leverage them, producing expensive acceleration of existing inefficiency.
ASEAN Amplifier
ASEAN's organisations frequently carry particularly complex process legacies — the legacy of rapid growth that prioritised speed over governance, family enterprise norms that institutionalised informal decision-making, and multi-market operations that accumulated local variations in process over time. Deploying technology into these complex process environments without prior standardisation produces the chaos-faster outcome with greater severity than in organisations with cleaner process foundations. The deployment bias is compounded by ASEAN's rapid investment pace — the pressure to deploy AI quickly, driven by competitive and board pressure, creates structural incentives to skip the process redesign work that would make the deployment sustainable.
04
Layer Four
The Human Adoption Gap — Users Who Shun the Solution
The Failure Mechanism
The redefinition of project failure that CIO Magazine identifies — projects that "don't engage users who then shun it" — points to the layer that receives the least investment relative to its impact on outcomes. A project can be strategically aligned, governed well, and process-founded — and still fail if the people who must use it have not been brought with it. The research from Springer Nature's 2025 analysis of IT project failures identifies "human-related factors, such as leadership, change management, and training" as the key success factors — which inversely means their absence is the key failure factor. McKinsey's finding that only 16% of employees believe their company's digital reforms have improved productivity is the user adoption failure rate made visible.
ASEAN Amplifier
ASEAN's high-context cultures create a particularly acute version of the adoption gap. Users who are not adopting a system in ASEAN organisations do not typically communicate that non-adoption directly to the people who deployed the system. They find workarounds. They satisfy the metrics that trigger sign-off (login rates, completion of mandatory training) while maintaining their actual working practices unchanged. The result is a reporting environment that shows successful adoption and a business environment that shows unchanged outcomes — with the gap between them often not visible until a post-implementation review surfaces it months or years after the deployment. By that point, the sunk cost is substantial and the change momentum has been lost.
95%GenAI pilot projects failing to show measurable ROI within 6 months
MIT GenAI Divide 2025
20%enterprise projects failing to meet business goals
PMI Pulse of Profession 2025
70%of change initiatives failing due to employee resistance and management support absence
McKinsey Global Survey
16%of employees who believe DT reforms have improved productivity long-term
McKinsey Global Survey
US$2.3Tannual cost of failed digital transformation
Gartner 2025–26
"Failure today means an IT project doesn't deliver expected benefits, runs so late as to be obsolete when completed, or doesn't engage users who then shun it in response."
— CIO Magazine, "Why IT Projects Still Fail," October 2025
ASEAN-Specific Analysis

The ASEAN Execution Environment:
Why Generic Solutions Fail Here

ASEAN's execution failures are not simply higher-frequency versions of global patterns. They are qualitatively different — produced by cultural and organisational dynamics that generic execution frameworks were not designed to address.

The academic research on ICT project failure in emerging markets confirms that success in ASEAN contexts is "influenced by top management support" and "communication management in Malaysia" — findings that point to the specific leadership and relational variables that determine execution outcomes in the ASEAN context. Generic project management methodologies — which prioritise process, timeline, and technical delivery — miss the human and relational variables that are often the decisive factor in ASEAN implementation success or failure.

Five ASEAN-specific dynamics compound the four execution failure layers described above:

Five ASEAN-Specific Execution Dynamics
  • Face-saving suppresses failure signals: The cultural norm of face-saving means that project teams who are experiencing difficulty do not typically escalate honestly or early. The leader receives sanitised progress reporting while the project accumulates failure. By the time the failure becomes undeniable, the corrective window has often closed.
  • Hierarchy creates decision bottlenecks: Decisions that should be made at the implementation layer are escalated to leaders who are unavailable or uninterested — creating delays that compound through the project timeline. ASEAN's high-PDI cultures create structural disincentives for the delegation that effective project execution requires.
  • Multi-market complexity multiplies coordination costs: Most ASEAN C-suites manage operations across multiple markets. Each market has different regulatory environments, workforce cultures, and process maturity levels. A project designed for one market requires substantial adaptation for others — adaptation that is frequently underestimated in project planning and underfunded in project budgets.
  • Founder informal authority disrupts governance: In family enterprises, the formal project governance structure coexists with the founder's informal authority. A project that has formal board approval can be quietly countermanded by founder behaviour — or simply not prioritised in the informal decision-making environment that operates beneath the formal structure.
  • Relationship primacy conflicts with task primacy: In ASEAN's relationship-oriented business cultures, the relational health of the project team matters as much as the technical delivery timeline. A project that is driving relationship strain — between implementation partners and internal teams, between departments competing for resources, between the project and affected business units — will slow regardless of governance discipline, because relationship health is the unspoken prerequisite for organisational cooperation in high-context cultures.
The Execution Firewall

The Execution Firewall:
Closing the Gap Before It Opens

The Execution Firewall is a protective leadership architecture — designed to prevent execution failure before it occurs rather than diagnose it after the fact. It operates across four layers that map directly to the four failure patterns identified above.

Execution Failure LayerPrimary CauseExecution Firewall ResponseASEAN Cultural Adaptation
Strategic Misalignment Vague "why" — no measurable link to business outcome Strategic alignment workshop: define the outcome before the solution. Document the specific, measurable business problem the project must solve. Facilitated in small groups — ASEAN leaders are more candid in peer settings than in formal plenary. Separate the strategic clarity work from the implementation planning work.
Governance Vacuum No named owner, absent executive sponsor Single-owner governance design: one named executive with accountability for outcomes, decision authority, and stakeholder escalation. Structured check-in cadence with non-negotiable dates. Named ownership is particularly important in ASEAN's high-PDI environments, where the owner's seniority signals the project's organisational priority. A junior named owner communicates low priority regardless of formal project status.
Process Acceleration Technology deployed over unchanged processes Process-first assessment: document and standardise the process before selecting or deploying the technology. Separate the "what we're fixing" work from the "how we're fixing it" work. In ASEAN's multi-market organisations, process standardisation requires explicit market-level consultation. What appears standard at headquarters is often significantly varied at market level — and the variation is never surfaced unless specifically sought.
Human Adoption Gap Users not brought with the change Adoption architecture: user involvement in design, honest communication about implications, manager-level trust investment, behavioural adoption metrics rather than deployment metrics. In ASEAN, the direct manager is the primary adoption lever — not corporate communications. Investing in manager-level capability and honest communication is the highest-return adoption investment available in high-PDI cultures.

The Execution Firewall is not a project management methodology. It is a leadership architecture — the set of specific C-suite behaviours, governance decisions, and communication disciplines that create the conditions in which project management methodologies can function. Without the Execution Firewall, the best project management in the world will fail to produce consistently successful outcomes in ASEAN's cultural and organisational environment. With it, organisations create a structural advantage that compounds with every successful implementation — building the execution credibility that makes future transformations progressively easier to land.

White Paper 06 · Conclusion
The Execution Gap Between Strategy and Delivery Is Closable — But Not Through Technology or Process Alone.

95% of GenAI pilots are failing to show ROI. One in five enterprise projects fails to meet business goals. US$2.3 trillion is destroyed annually in failed transformations. These are not acceptable baseline statistics — they are evidence of a systematic, structural leadership failure that has remained unaddressed because the diagnosis has consistently pointed to technology and process while the actual cause has been relational and cultural.

The Execution Firewall addresses that actual cause. It begins with the diagnostic assessment that identifies which of the four failure layers is most active in your organisation — and produces the specific leadership intervention architecture required to close each gap. The conversation starts at success@manjuappathurai.com.

Request the Execution Firewall Assessment

A structured diagnostic identifying which execution failure layers are most active in your organisation — and the precise leadership interventions required to close each one.

Request the Assessment →
Sources & References
1.CIO Magazine (October 2025). "Why IT Projects Still Fail." PMI Pulse of Profession 2025 and MIT GenAI Divide 2025 cited. cio.com
2.MeltingSpot (2025–26). "Digital Transformation Failure Rate 2025." US$2.3T Gartner figure. blog.meltingspot.io
3.Project Management Institute (2025). Pulse of the Profession 2025. 80% meeting business goals (20% failure). pmi.org
4.Asana (June 2025). "Why Projects Fail: 8 Causes and How to Prevent Them." asana.com
5.Springer Nature / ComSIA (2026). "From Analysis to Action: Categorizing and Addressing IT Project Failures for Enhanced Success Rates." link.springer.com
6.McKinsey & Company. Multiple survey data on transformation failure: 70% resistance, 16% productivity belief. Referenced across multiple secondary sources 2024–26.
7.ResearchGate / International Journal. "An Exploratory Study of ICT Projects Failure in Emerging Markets." Malaysia-specific success factors: top management support, communication management. researchgate.net
8.Gartner. Digital transformation project failure data — US$2.3T annual cost. Referenced in MeltingSpot 2025–26 analysis.
9.Prosci (November 2025). "Digital Transformation Made Real With Change Leadership." Human factors in transformation. prosci.com
10.PETADIRI (December 2025). "Leadership Development in Southeast Asia." Southeast Asia digital economy context. petadiri.com