Brifing

Why Digital Projects Fail: Separating Data Quality from System Usability

Digital transformation misdiagnoses stem from conflating productive cognitive engagement with interface friction.

Sloan Management Review3 min

1The Chronic Failure Misdiagnosis

When digital transformation tools underperform, leadership teams routinely blame poor user adoption, inadequate training, or change management breakdowns. However, treating data quality and system usability as a single unified variable obscures root causes. These two factors operate via entirely different cognitive mechanisms and fail in structurally distinct ways across organizations.

2Empirical Study on Decision Making

Researchers from Case Western Reserve University and Vanderbilt University Medical Center surveyed 564 practicing physicians across 32 medical specialties using electronic health records. Clinical medicine provided an ideal environment to study high-stakes knowledge work under extreme time constraints, uncovering how system architecture shapes professional judgment and cognitive capacity.

3Germane Versus Extraneous Cognitive Load

Data usability directly increases germane cognitive load, which represents the productive mental effort required for deep reasoning and complex judgment. Conversely, system usability reduces extraneous cognitive load, eliminating unproductive waste caused by visual clutter, excessive navigation steps, and misaligned workflows that drain mental bandwidth without improving decision outcomes.

4Statistical Evidence of Two Pathways

The empirical findings revealed that data usability had a strong direct positive effect on cognitive load, with a path coefficient of 0.597. System usability partially and negatively mediated this relationship with an indirect effect of negative 0.571, proving that interface design and underlying information quality operate independently.

5The High-Data High-Friction Trap

Upgrading data quality without refining interface design increases mental friction. High-quality data triggers deeper reasoning, but complex navigation structures and excessive clicks increase total cognitive burden simultaneously. Users suffer from severe fatigue, overall decision throughput drops, and executives mistakenly conclude that the entire digital project underdelivered.

6Usable Interfaces with Flawed Data

The inverse failure occurs when companies streamline interfaces and reduce clicks without enhancing data integrity. Navigation becomes effortless and extraneous cognitive load falls sharply. However, if the underlying information remains incomplete or unorganized, workers never trigger the germane cognitive processing needed to produce accurate, high-value strategic judgments.

7Four Imperatives for Information Governance

Effective governance requires four structural actions: eliminating duplicate data points, displaying data lineage to prevent source verification overhead, mandating mission-critical input fields, and recalibrating notification thresholds. Preventing alert fatigue ensures user attention remains directed toward vital operational anomalies rather than being trained away from the system entirely.

8Why AI Deployments Underdeliver

Organizations investing heavily in artificial intelligence face identical misdiagnoses by evaluating tools solely on model accuracy and adoption metrics. High-quality algorithmic recommendations activate germane reasoning, but poor interfaces, missing context, and uncalibrated alerts generate extraneous friction that completely negates the core value of the underlying artificial intelligence.

9Reframing Digital Performance Reviews

Leaders must evaluate enterprise systems through cognitive architecture rather than traditional IT metrics like uptime. Assessing whether workflow logic reduces friction or provokes decision quality degradation reveals true operational bottlenecks. Interface logic and data governance are fundamental strategic management choices, not minor technical settings delegated to IT vendors.

Original article: Sloan Management Review — Why Digital Projects Fail: Separating Data Quality from System Usability