Why Business-Led Digital Transformation Fails: Governance Gaps, Not Method Flaws

The reader's comment summarizes four core doubts: (1) Business silos and departmental walls prevent global planning. (2) Digital transformation requires breaking functional divisions and restructuring authority — no one volunteers to disrupt themselves. (3) Business units lack the capacity to articulate true requirements from a global perspective. (4) Traditional IT that refuses to penetrate business processes becomes marginalized. The comment concludes that only a bridging process/transformation department can break the deadlock, and ultimate success depends on top leadership's cognition and resolve.

The author agrees with the comment's accuracy and states the core conclusion: "Business-led, IT-enabled" is not a flawed theory; most enterprises fail because they misunderstand and mis-execute it — turning "business value leadership" into "individual business units making isolated decisions," and turning governance-level top-level design into functional buck-passing.

01. Business Silos and Departmental Walls: Who Does Global Planning?

First, correct the most common misconception: "Business-led" ≠ "Individual business units lead separately." Many enterprises interpret it as: Sales owns CRM, Production owns MES, Procurement owns SRM. This inevitably creates silos, departmental walls, and chimney systems — this is not "business-led" but "business decentralization," rooted in absent top-level governance.

True "business-led" is layered:

Layer 1: Executive leadership. The chairman, CEO, or business VP sets digital strategy, priorities, and resource allocation from a whole-company operating perspective. This is the governance layer (EDM domain) per ISO 38500 and COBIT. Global planning must come from the highest decision layer, not middle management.

Layer 2: Business units own outcomes. Within the set global direction, each business unit is responsible for its domain's business results, data quality, and adoption.

Many enterprises fail because the top layer pushes its own global planning responsibility down to middle business units, resulting in "everyone sweeps their own doorstep," then blames "business-led doesn't work." The problem is misplaced responsibility, not the method.

02. Transformation Requires Self-Disruption: Who Will Volunteer?

Agreed: no one volunteers to disrupt themselves. Therefore "business-led" never means letting business units initiate revolution and cut their own authority. Instead: Governance sets transformation direction, business owns implementation accountability, IT provides capability support.

Transformation drive can never come from middle management; it must come from the top. Process restructuring, authority realignment, interest redistribution — these require board/CEO mandate and forceful push. Business leads execution within the mandated direction: running processes end-to-end, cleaning master data, driving adoption, delivering quantified results — not deciding "whether to transform."

Many enterprises' farce: the CEO lacks transformation resolve, avoids touching interest structures, dumps the transformation burden on business and IT, then complains "business uncooperative" or "IT incapable." This is top-layer responsibility evasion, unrelated to the "business-led" method itself.

03. Business Can't Articulate Requirements: The Rider Doesn't Design the Car

This is the precise trap 90% of enterprises fall into: they equate "business-led" with "business writes detailed requirements, IT just builds." This is a fundamental misunderstanding.

Business leads "business goals and business value," not "system functional details." The rider need not know how to build the car; they only need to specify three things: destination, speed, payload. In digital terms: what business pain to solve, what quantified results to achieve, what business objectives to support. That is business's remit.

"How to build the car — engine, chassis, design" — i.e., system functional design, technical solution — is IT's professional duty. "IT empowerment" does not mean passively waiting for requirements; it means actively penetrating business scenarios, translating vague pain points and naive goals into professional system requirements and technical designs.

Business not understanding systems is normal; IT not understanding business is dereliction. Many enterprises invert this: forcing business to write functional specs, IT waiting for tickets, delivering mismatched solutions, then blaming each other. This is not a method error; it's a responsibility boundary inversion.

04. Traditional IT That Doesn't Penetrate Business Is a Dead End

Fully correct. "Business-led, IT-enabled" is not about IT being a hands-off custodian of its technical turf; it raises the bar for IT: must understand business processes, operating logic, frontline scenarios. Technology detached from business has zero value.

But a boundary must be drawn: IT understands business to better support it with technology, not to replace business decisions or own business outcomes. IT can propose solutions, advise, even guide digital awareness, but the primary accountable party for "is this worth doing, did we achieve results" must be the business side.

Reality shows two extremes:

Pure tech IT, detached from business, reduced to tooling, inevitably marginalized.

Enterprises that make IT the scapegoat, loading all business-value responsibility onto IT, inevitably producing "technology for technology's sake."

Healthy state: Business owns value, IT owns delivery, mutual commitment — not one-way buck-passing.

Regarding the reader's suggestion of a "bridging department" (process/transformation office, PMO): this is exactly right and aligns with mature governance frameworks. It is not a negation of "business-led" but a necessary supplement for execution. This bridging department fills three gaps:

Global planning gap: Enterprise-wide process restructuring, architecture planning, breaking departmental parochialism, doing global design on behalf of business units.

Requirements translation gap: Turning business's vague pains and scattered asks into standardized business requirements and value targets, bridging the cognition chasm between business and IT.

Transformation push gap: Carrying top-layer transformation resolve, cross-department coordination, tackling the hard bones of adoption.

Even with this bridging department, one core principle remains: Ultimate business value, data quality, usage effectiveness — first accountable party is still the business unit. The bridging department is lubricant and accelerator, not a scapegoat, and cannot replace business's primary responsibility.

05. Closing Thoughts

Back to the original question: it's not that "business-led" is wishful thinking or unworkable; too many enterprises only learned half the slogan and never built the supporting governance system.

They pushed top-layer responsibilities downward, outsourced IT's empowerment duty, turned collaboration into buck-passing, then concluded "this method doesn't work." Old methods yield no new answers because most people never actually used the method correctly.

Real implementation is never just shouting "business-led"; it's a complete combination punch:

Top leadership steps up: sets direction, drives transformation, owns ultimate accountability.

Middle bridging organization established: breaks walls, designs global processes, clarifies requirements.

Business anchors value outcomes, IT penetrates business scenarios, each in its proper place, each owning its proper accountability.

Ultimately, it's a test of the CEO's cognition and resolve, because the first accountable person for IT governance is always at the very top.