Breaking: Companies Capture Only One-Third of Digital Value – Experts Reveal Fix

New research from McKinsey reveals organizations realize less than one-third of the expected value from digital investments. The root cause: companies start with technology rather than customer needs. This fundamental flaw creates fragmented solutions and disjointed experiences, ultimately derailing transformation efforts.

Industry experts now champion a radical shift: customer-back engineering. This approach puts customer challenges and expectations at the center of technology development. Teams work backward from desired experiences to design nimble, agile solutions.

“When you get your engineers closer to customers, you get a lot more sideways innovation,” says Ashish Agrawal, managing vice president of business cards and payments tech at Capital One. “That leads to a multiplier effect, because engineers can approach a problem from a different dimension that can be unique to the sales or product perspective.”

The Customer-Centric Engineering Imperative

Engineers are natural problem-solvers. When they witness real-world customer friction, they leverage their proximity to systems and data to craft efficient solutions. Agrawal notes this creates a powerful motivational loop: engineers see their work directly improving lives.

“Fostering a customer-centric culture has a motivational effect on engineers when they actually start seeing how the core changes they’re making, or the features they’re adding, are having a direct impact on the lives of customers.” — Ashish Agrawal

But customer-back engineering demands discipline. Capital One requires every engineer in Agrawal’s organization to establish multiple customer touchpoints annually through initiatives like:

• Digital empathy sessions – observing user journeys to identify friction points
• Embedded customer support – deepening understanding of servicing needs
• Engineering ride-alongs – joining sales, support, or customer success calls and site visits
• Hackathons – building solutions around real customer problems

Background: The Old Playbook Fails

Traditional digital transformation starts with available technologies, then bolts applications onto them. This technology-first approach ignores customer context, leading to disjointed experiences and low adoption. McKinsey’s data underscores the magnitude of failure—67% of expected value evaporates.

Customer-back engineering flips this script. By anchoring development in actual user needs, companies ensure that every feature solves a genuine problem. This method, long used by design-thinking pioneers, is now gaining urgency as AI accelerates both challenges and opportunities.

What This Means: AI’s Next Frontier Depends on Customer Proximity

“The biggest challenge engineers within large companies face is a lack of direct access to customers,” says Agrawal. “This can make it harder for technologists to work with customers to identify problems and innovate solutions.” Without intentional customer immersion, AI investments risk building sophisticated tools for nonexistent needs.

The implication is stark: organizations that embed customer-back engineering into their AI strategy are poised to capture outsized returns. Those that don’t will continue wasting billions on technology that solves the wrong problems. As Agrawal warns, the lifecycle of launching AI products accelerates mistakes if customer input is missing.

In a hypercompetitive landscape, the message is clear: start with the customer, engineer backward, and let real-world friction guide innovation. The data—and early adopters like Capital One—suggest this is the only path to transformative value.