A note on perspective: This is part one of a five-part series. By Part 3, I make a specific case for Qlik Cloud Analytics as the platform that makes the argument practical and executable. I work with Qlik. That context is worth knowing upfront, because the argument only holds if I have earned your trust through honesty, not assumed it.
Written by GOODIN’s BI LEAD – Phuoc Tran Minh
If you work in data and analytics, you are used to the whiplash. Every few years, the industry promises a new architectural silver bullet that will finally solve the reporting backlogs, the data quality nightmares, and the governance headaches. Recently, that silver bullet has been Data Mesh.
I will be the first to admit I have been a strong advocate for it. The core promise of shifting data ownership away from a centralized IT bottleneck and putting it directly in the hands of the business sounded like the exact antidote large organizations desperately needed. And intellectually, it still does.
But after watching these implementations unfold in the real world, we need a serious reality check.
The War Story Nobody Publishes
I have watched some of the largest companies in the world, flagship enterprises, household names, fail at this problem repeatedly. Not once. Repeatedly. The pattern is almost identical every time.
They invest heavily in a centralized Data Warehouse. The project runs 18 months over schedule. By the time it delivers, half the business requirements have changed. The central data team, talented as they are, becomes a permanent bottleneck. They understand the technology but not the business, and every new report request joins a queue that never clears. The business loses patience and starts building its own analytics in spreadsheets, local databases, and disconnected BI tools. Shadow IT blooms.
Here is the part that rarely gets said out loud: most of these organizations do not actually choose between the two bad options. They end up with both simultaneously. A stagnating, increasingly outdated Data Warehouse on one side, and a sprawling mess of shadow self-service analytics on the other. They are paying for the warehouse they cannot retire and suffering the chaos of the self-service sprawl they cannot govern. The worst of both worlds, billed as a strategy.
When it fails, the instinct is to blame the technology or the consultant. Never the model itself.
The BI Manager’s Dilemma: both choices end in pain.
The Numbers Are Damning, Across the Board
The failure of centralized data platforms is not anecdotal. Gartner, IDC, and Forrester have consistently placed the failure or underperformance rate of traditional Data Warehouse initiatives at somewhere between 50% and 80% over the last fifteen years. The specific number varies by study and definition of failure, but the directional truth has been stubbornly consistent: most of these projects do not deliver their intended ROI.
The unsettling part? The decentralized alternative is not faring much better. Zhamak Dehghani first published the concept of Data Mesh already in May 2019 to much acclaim, but very few successful implementations have since emerged. In 2022, Gartner predicted that Data Mesh may become obsolete before reaching full maturity, and estimated that only 18% of organizations have the necessary governance maturity to successfully adopt Data Mesh architecture. Unfortunately, these estimates still seem highly accurate.
Two Books, One Argument
The industry’s frustration has recently found a voice in two very different books worth naming directly.
Martyn Jones’ F*CK DATA MESH says the quiet part loud. The title alone captures the mounting exhaustion with architectures full of grand theory about domain sovereignty that collapse the moment they meet an actual organization. The sentiment is valid. Data Mesh implementations have frequently produced fragmented, expensive messes that delivered less than the warehouses they were meant to replace.
At the other end of the conversation, Phil Le-Brun and Jana Werner’s The Octopus Organization, a recent Harvard Business Review publication, offers a compelling biological metaphor for what a genuinely decentralized, high-performing organization looks like: distributed intelligence at the edges, fast local decision-making, coordinated but not controlled from the center. It is a useful model, and one worth keeping in mind. But it is also a model that assumes the organizational foundations are already in place to support it.
Both books are participating in the same conversation: what does genuine, functional decentralization actually look like, and why does it keep failing in practice?
The Problem Is Not the Vision. It Is the Execution Trap.
Here is the reality CIOs must face head-on: the core principle of Data Mesh, business ownership of data, is fundamentally correct. Gartner’s recent CIO Agenda research is unambiguous on this point: the organizations winning at digital delivery are the ones with genuine business ownership of technology outcomes, not the ones that kept everything inside a central IT function.
The vision is not wrong. But the enterprise execution of it has been a disaster, for a specific and diagnosable reason.
Data Mesh implementations typically fail because they confuse organizational autonomy with infrastructure engineering. By asking business domains to take ownership of their data products, companies inadvertently require business analysts to master Git repositories, YAML configurations, dbt transformations, and CI/CD deployment pipelines just to publish a clean dataset. The autonomy on offer turns out to be an engineering curriculum in disguise.
Business units do not have the technical skills, the budget, or frankly the incentive to become software engineering teams. The result is anxiety, stalled adoption, soaring cloud costs, and, ironically, a new generation of exactly the same shadow IT silos the whole exercise was supposed to eliminate.
We gave domains the responsibility without giving them the means to carry it. That is not decentralization. That is delegation of blame.
The Question We Actually Need to Answer
So we are stuck. Going back to the centralized Data Warehouse means burying every request in an IT backlog and watching the business work around you. Pressing forward with a full Enterprise Data Mesh means handing business analysts an engineering toolkit they cannot use and watching the whole thing fragment.
The question is not which of these two paths to choose. It is how to escape the false choice entirely.
That is what this series is about. The argument is for a pragmatic middle path, one that keeps the principle of business ownership intact while stripping away the engineering complexity that has been killing it in practice. And by Part 3, we get specific about the technology that makes it executable.
COMING UP IN THIS SERIES
Part 2: Why real agility and ownership requires authority, understanding, and motivation, and why small business-driven teams are the only structure that delivers all three.
Part 3: How Qlik Cloud Analytics breaks the engineering bottleneck and lets your team focus on business logic instead of infrastructure and governance processes.
Part 4: How to escape data silos while doing fast domain owned data iteration without a data lakehouse?
Part 5: Four lean governance rituals that bulletproof your data products without complicated software or bureaucracy.
The era of the IT-driven rigid data factory is ending. But the era of the over-engineered, under-delivered Data Mesh needs to end with it.
