Beyond Tech-First Thinking: Build Customer Transformation Strategies that Start with Problems, Not Solutions

A sobering statistic continues to haunt the business world: according to McKinsey research, nearly 70% of digital transformations fail to deliver their intended outcomes. Despite billions invested in technology initiatives, organisations struggle to realise meaningful business value. The culprit? A persistent tendency to begin transformation efforts with technological solutions rather than clearly defined customer or business problems.

This solution-first approach has become so embedded in corporate thinking that we barely recognise it anymore. We see competitors implement AI or blockchain and rush to follow suit. We hear about groundbreaking platforms and immediately begin planning implementations. We become enamoured with technological possibilities before thoroughly understanding the problems we’re trying to solve.

True transformation success requires reversing this approach — starting with customer problems and business challenges before considering technological solutions. As someone who has spent years helping organisations bridge technology capabilities with business outcomes, I’ve witnessed firsthand how problem-first transformation strategies consistently outperform their solution-first counterparts.

The Costly Cycle of Solution-First Thinking

Solution-first thinking follows a predictable pattern: an organisation identifies an emerging technology, becomes convinced of its transformative potential, initiates an implementation project, and only afterward tries to determine how the technology can solve business problems. While seemingly logical on the surface, this approach creates several fundamental issues.

Consider the cautionary tale of Marks & Spencer, reported to have invested £25 million in an AI-powered customer service overhaul across multiple touchpoints in 2019. The technology was cutting-edge, but customer satisfaction scores plummeted in the months following implementation. Post-implementation research revealed that customers weren’t struggling with service availability — they were frustrated with the complexity of return policies. The AI solution addressed a problem that customers didn’t have.

Similarly, a European financial services firm, BNP Paribas Personal Finance, is reported to have deployed an expensive CRM system that promised to transform customer relationships through better data integration. Two years later, adoption remained below 30%, and the anticipated revenue lift never materialised. The reason? The system solved the executive team’s desire for better reporting but failed to address the daily challenges of frontline employees managing customer relationships.

The costs of solution-first thinking extend beyond wasted technology investments. They include:

• Organisational fatigue: Employees become sceptical of transformation initiatives, seeing them as disconnected from real needs
• Missed opportunities: Resources allocated to unnecessary solutions can’t be directed toward solving actual problems
• Customer trust erosion: Solutions that don’t address genuine pain points signal to customers that you don’t understand their needs
• Competitive vulnerability: While you’re implementing irrelevant solutions, competitors may be solving real customer problems

What drives this persistent solution-first mindset? Several psychological and organisational factors contribute:

• Shiny object syndrome: Probably one that I see most frequently — new technologies promise excitement and competitive differentiation
• Competitive pressure: Fear of being left behind when competitors adopt new technologies
• Vendor influence: Technology providers often excel at selling visions rather than validating problems
• Technical bias: Technology-focused leaders naturally gravitate toward technical solutions
• Confirmation bias: We seek evidence supporting our solution preferences while discounting contradictory information

Fortunately, there’s a better way forward. One that fundamentally reorients transformation around customer and business problems before considering technological solutions.

The Problem-First Framework

A problem-first approach to transformation follows a structured framework with four distinct phases: Problem Discovery, Problem Prioritisation, Solution Exploration, and Technology Selection. Each phase builds upon the previous one, ensuring that technological solutions ultimately address validated customer and business challenges.

1. Problem Discovery

The transformation journey begins with systematic problem discovery — identifying and articulating the challenges facing customers and the business. Effective problem discovery can involve multiple approaches:

• Ethnographic research: Observing customers in their natural environments to identify unarticulated needs and pain points
• Data analysis: Examining customer behaviour patterns to identify drop-offs, friction points, and inefficiencies
• Voice of customer programmes: Collecting and analysing customer feedback across touchpoints, especially the contact centre
• Employee insights: Tapping into frontline employees’ knowledge of customer challenges
• Journey mapping: Documenting the customer experience to identify moments of truth and pain points

LEGO, the Danish toy manufacturer, provides an exemplary case of effective problem discovery. Before reimagining their retail strategy, LEGO spent months studying how children played with its products. They discovered that children valued mastery and achievement more than merely owning LEGO sets – an insight that fundamentally reshaped their approach to physical and digital experiences.

2. Problem Prioritisation

Not all problems deserve immediate attention. Problem prioritisation helps organisations focus on challenges that matter most:

• Impact assessment: Evaluating each problem’s effect on customer or employee satisfaction, loyalty, and business outcomes
• Frequency analysis: Determining how often customers or employees encounter each problem
• Strategic alignment: Considering how solving each problem contributes to strategic objectives
• Solvability evaluation: Assessing the organisation’s ability to address each problem

Effective prioritisation tools might include:

• Problem prioritisation matrices that score problems based on impact and solvability
• Customer journey importance mapping that identifies moments of disproportionate influence
• Value stream analysis that pinpoints where customer value is created or destroyed

3. Solution Exploration

Only after thoroughly understanding and prioritising problems should organisations begin exploring potential solutions. This phase includes:

• Solution ideation: Brainstorming multiple approaches to solving each prioritised problem
• Concept testing: Validating solution concepts with affected stakeholders
• Rapid prototyping: Creating low-fidelity representations of potential solutions
• Solution evaluation: Assessing each solution against criteria like effectiveness, feasibility, and sustainability

This phase should intentionally remain technology-agnostic, focusing instead on the fundamental approach to solving each problem.

4. Technology Selection

The final phase involves selecting and implementing technologies that enable the chosen solutions:

• Technology mapping: Identifying technologies capable of supporting each solution
• Vendor assessment: Evaluating technology providers based on capabilities and fit
• Implementation planning: Developing realistic implementation approaches
• Value tracking: Establishing mechanisms to measure whether the technology solves the intended problem and drives business outcomes

Monzo Bank exemplifies this problem-first approach in the UK fintech space. When developing their banking services, they began by thoroughly mapping customer pain points with traditional banking. Their discovery process identified that customers struggled with real-time transaction visibility and budget management. After identifying these core problems, the bank explores solution approaches, ultimately building a mobile-first platform with instant notifications and budgeting tools that directly addressed validated customer pain points.

Organisational Enablers for Problem-First Transformation

Successfully implementing a problem-first approach requires more than just a methodological framework — it demands organisational structures, capabilities, and mindsets that support this way of working.

Cross-Functional Discovery Team

Problem-first organisations establish cross-functional teams dedicated to ongoing problem discovery and validation. These teams typically include:

• Customer research specialists
• Data analysts
• Business domain experts
• Technology representatives
• Design thinkers

Nationwide Building Society, one of the UK’s largest financial institutions, structures its innovation teams around customer life events rather than products or technologies. Their customer-focused teams include members from various disciplines who collectively understand both the customer’s needs and potential solution approaches.

Customer Insights Capabilities

Organisations need robust mechanisms for continuously gathering and analysing customer insights:

• Voice of customer programmes that systematically collect and analyse feedback
• Customer data platforms that unify customer information
• Journey analytics capabilities that identify pain points and opportunities
• Closed-loop feedback systems that validate whether solutions solve problems

Governance Models

Governance structures should reinforce problem-first thinking by:

• Requiring problem validation before approving solution investments
• Allocating discovery funding separate from implementation funding
• Including customer impact metrics in project approval criteria
• Conducting post-implementation assessments focused on problem resolution

Siemens, the German industrial manufacturing conglomerate, requires teams to complete a “customer problem statement” document for new initiatives before beginning development – a practice that forces clarity on the problem being solved and the value to customers.

Leadership Mindset

Perhaps most importantly, leaders must embrace a problem-first mindset by:

• Asking “what problem are we solving?” before “what technology should we use?”
• Celebrating problem discovery as much as solution delivery
• Acknowledging uncertainty and encouraging learning
• Modelling curiosity about customer needs and challenges

Jean-Pascal Tricoire’s transformation of Schneider Electric exemplifies this mindset shift. By reorienting the French energy management company around sustainability challenges and customer problems rather than product categories, he has guided one of the most remarkable corporate transformations in European business.

Measuring What Matters – New Metrics for Problem-First Change

Traditional technology project metrics — on time, on budget, features delivered — reveal little about whether initiatives solve customer problems. Problem-first transformations require a different measurement approach focused on outcomes rather than outputs.

Problem Resolution Metrics

These metrics assess whether identified problems have actually been solved:

• Problem frequency reduction: How often customers or employees encounter the problem after implementation
• Resolution rate improvement: How successfully customers and/or employees can resolve issues when they arise
• Customer or employee effort reduction: How much easier it is for customers or employees to accomplish their goals

Business Outcome Metrics

These metrics connect problem resolution to business performance:

• Revenue impact: How solving problems affects customer acquisition, retention, and expansion
• Operational efficiency: How addressing problems improves operational performance
• Employee productivity: How solutions impact employee ability to serve customers

Adoption and Usage Metrics

These metrics indicate whether solutions are being used as intended:

• Adoption rate: Percentage of target users actively using the solution
• Usage patterns: How, when, and why people use the solution
• Feature utilisation: Which capabilities are most valuable in solving the problem

Vodafone’s Customer Success framework exemplifies this outcome-focused approach across their European operations. Rather than merely tracking implementation milestones, they measure improvements in customer satisfaction scores, first-contact resolution rates, and customer retention – metrics that reflect actual problem resolution and business impact.

The Competitive Advantage of Understanding Before Solving

In a business environment obsessed with technological disruption, the most powerful competitive advantage may be surprisingly fundamental: thoroughly understanding problems before implementing solutions. Organisations that master this problem-first approach consistently outperform their solution-obsessed counterparts in delivering meaningful transformation.

Shifting from solution-first to problem-first thinking isn’t easy. It requires patience when the pressure to act is high, humility when technological excitement is tempting, and discipline when shortcuts appear attractive. But the rewards – higher transformation success rates, more efficient resource allocation, and true customer-centricity – make the effort worthwhile.

Consider taking these immediate actions to begin your shift toward problem-first transformation:

1. Audit your current initiatives for solution-first bias by asking whether each one addresses a clearly-articulated customer or business problem
2. Implement one problem discovery practice, such as customer journey mapping or systematic analysis of customer feedback
3. Revise your success metrics to focus on problem resolution rather than solution implementation

In the rush to digital transformation, we often forget that technology is merely a means to an end. The organisations that thrive will be those that keep the end — solving meaningful customer and business problems — firmly in focus.

Sources and Bibliography

Adamson, B., Dixon, M., & Toman, N. (2023). The Challenger Customer: Selling to the Hidden Influencer Who Can Multiply Your Results. Portfolio Penguin.

Blank, S. (2020). The Four Steps to the Epiphany: Successful Strategies for Products that Win. Wiley.

Boston Consulting Group. (2024). “Why Digital Transformations Fail: Closing the €900 Billion Hole in Europe’s Digital Ambitions.” BCG Henderson Institute.

Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2022). “Know Your Customers’ ‘Jobs to Be Done’.” Harvard Business Review, 94(9), 54-62.

Digital McKinsey. (2023). “Unlocking success in digital transformations.” McKinsey & Company.

Financial Times. (2023). “Marks & Spencer’s Digital Overhaul: Lessons from a Retail Giant’s Transformation.” Financial Times Special Report on Digital Business.

Gothelf, J., & Seiden, J. (2021). Lean UX: Designing Great Products with Agile Teams. O’Reilly Media.

Kesler, C., Kearney, M., & Lamb, G. (2024). “Digital transformation trends in the UK and Europe.” Journal of Digital Business Strategy, 12(3), 156-172.

Maeda, J. (2019). How to Speak Machine: Computational Thinking for the Rest of Us. Portfolio.

Monzo Bank Ltd. (2023). “Building a Bank Around Customer Problems.” Monzo Engineering Blog.

Osterwalder, A., & Pigneur, Y. (2021). Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers. Wiley.

Palladium Digital Research. (2024). “The European Digital Transformation Index 2024.” Palladium Management Consultants.

Reichheld, F., & Darnell, D. (2023). “Customer-Inspired Growth: A Special Collection.”Harvard Business Review.

Ries, E. (2021). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Currency.

The Economist Intelligence Unit. (2023). “BNP Paribas: Lessons from a CRM Implementation. The Economist.

Vodafone Group. (2024). “Customer Success Metrics Framework. Vodafone Business Solutions.

Westerman, G., Bonnet, D., & McAfee, A. (2023). Leading Digital: Turning Technology into Business Transformation*. Harvard Business Review Press.