How Should Leaders Decide Which Customer Experiences Deserve Transformation?

Think about the last time you tried to get something done online and found yourself wondering, “Why is this so difficult?”

Maybe you had to enter the same information twice. Maybe you were passed from one team to another before someone could actually help. Or perhaps you simply gave up and went somewhere else. For the customer, these moments can feel like small frustrations. For the organization, they can be signs of something much bigger.

The problem is that organizations rarely struggle to find experiences that need fixing. There are usually plenty: checkout abandonment, slow onboarding, confusing portals, disconnected support journeys, and more.  But not every frustrating experience needs a transformation-level investment.

Some problems can be solved with a clearer interface or a simpler process. Others require a redesigned journey. And some point to deeper issues across the systems, data, processes, and teams that make the experience possible in the first place. The challenge is knowing which experience is which.

So, instead of asking which customer problem is the loudest, you need to ask a more useful question, "Which experience is failing in a way that matters to both the customer and the business, and what would it take to genuinely change it?"

This article explores how to answer that question and decide which customer experiences are worth improving, redesigning, or transforming.

Imagine a customer trying to open an account. They visit the website, complete a form, speak with sales, submit verification documents, wait for approval, and eventually begin onboarding. The website might be the part receiving the most complaints because the form is confusing.

It would be easy to redesign the form.

But suppose the real problem is that sales, verification, and onboarding use different systems. Customers are repeatedly asked for the same information, approvals sit in different queues, and nobody can see the full status of the application.

A better form might make that one moment easier, but the customer would still be asked to repeat information, wait for updates, and navigate disconnected steps. The real problem is not always the interaction they can see. It is often everything that makes that interaction possible behind the scenes.

That is the first distinction leaders need to make: improving what customers see is not the same as improving what they experience. This is where enterprise UX becomes important, connecting the experience people have with the systems, processes, and decisions that shape it.

Millipixels has seen this over years of partnership work: the problem customers can point to is often not the problem the organization actually needs to solve.

That matters because transformation carries a cost. It requires coordination across teams, changes to processes and technology, and often a significant investment of time and resources. Treating every UX problem as a transformation opportunity can create more disruption than value.

The right question is therefore not "How bad is this experience?" It is: "What happens when this experience fails, and what would it take to fix the reason it fails?"

A useful way to investigate an experience is to follow the customer through the entire task they are trying to complete. Consider:
Website → Form → Sales → Verification → Onboarding → Support

At each stage, ask three questions:

• What is the customer trying to accomplish?
• Where does the journey break down?
• What is causing that breakdown?

The third question is where prioritization becomes more meaningful.

A customer may complain about having to fill out a form twice. But the underlying cause could be duplicated databases. A customer may complain that onboarding is slow. The cause could be manual approvals. A customer may complain that support cannot answer a simple question. The cause could be that customer information is distributed across systems.

This is why journey-level investigation is more useful than simply collecting complaints. A complaint tells you where a customer experienced friction. Looking at the journey helps you understand how that friction developed, what happened before and after it, and whether the same problem is appearing across other touchpoints.

Recent CX Network research reinforces this shift: 76% of organizations identified siloed data and a lack of integrated systems as a major roadblock to successful customer journeys, while 79% said success means delivering seamless experiences across all touchpoints.

The lesson is not that every journey will generate those results. It is that the value of CX can extend well beyond an individual interface when the underlying journey is addressed.

Three levels of experience problems

That distinction should sit at the heart of any customer experience strategy.

Once a journey has been mapped, leaders can test the opportunity through four questions.

1. Does the failure materially affect the customer?

Start with the person's experience, not the company's dashboard.

How much effort does the journey require? Where do customers wait, abandon, repeat information, or ask for help? Does the failure create uncertainty or undermine trust?

Complaint volume is useful evidence, but it is not a priority score.

A problem reported by 10,000 customers might be a minor annoyance. A problem experienced by 500 customers at a critical moment could cause much greater commercial damage.

The scale of the problem and the consequence of the problem are not the same thing. This is increasingly important as expectations change. PwC's 2025 survey found that 70% of executives believe customer expectations are changing faster than their companies can adapt, while 29% of consumers said they had stopped using or buying from a brand because of poor customer experience.

Millipixels has seen this distinction matter in transformation work: the experiences worth prioritizing are often not the ones generating the most noise, but the ones creating meaningful friction at moments customers cannot easily work around.

2. What does the failure cost the business?

Now follow the problem beyond the customer. A poor experience may create:

• lost conversions
• higher support volume
• slower onboarding
• lower adoption
• additional operational work
• higher churn
• lower customer lifetime value

This is where experience decisions become business decisions. Gartner's 2025 research specifically recommends connecting CX to outcomes such as retention, sales, and referrals, rather than treating experience measures as an isolated dashboard. Gartner also identifies customer lifetime value as the leading CX metric among growth companies.

That changes the conversation from:

"Customers don't like this."
to:
"Customers struggle here, and that struggle creates a measurable business consequence."

3. Is the problem systemic?

This is the question that separates ordinary improvement from transformation. Look underneath the experience.

Is the problem caused by:

disconnected systems?
fragmented customer data?
manual processes?
unclear ownership?
multiple teams handling one journey?
policies that force unnecessary steps?
technology that does not support the intended experience?

If the answer is yes, redesigning the interface may only move the problem around. This is also why digital customer experience cannot be evaluated only through screens and channels. Gartner reported in 2025 that 51% of customer service journeys now begin on third-party platforms such as Google, YouTube, and ChatGPT, rising to 74% among Gen Z customers.

The customer's journey no longer begins and ends inside the company's website or app. The experience is distributed across an ecosystem.

4. Does the opportunity justify transformation?

Even a serious problem may not be the right transformation priority. Leaders need to weigh the expected value against the effort required.

For someone getting a COVID-19 test, the experience needed to be straightforward: find the right information, complete the necessary steps, and access their results without having to understand the complexity behind the process.

But making that possible meant designing for people with different needs, using different devices, and accessing testing through schools, workplaces, and other organizations. The experience also had to keep working as requirements changed.

Millipixels worked with Ambrygen’s clinical and product leadership to create a flexible UX framework that could adapt to these different situations without forcing people through a completely different experience each time. A mobile-first approach made testing easier to access, while an integrated patient portal brought key testing services together.

The result was a platform launched across schools and organizations in just 10 days, supporting thousands of concurrent users without a UI overhaul. Mobile engagement increased by more than 50%.

The bigger lesson is that a simple experience for people often requires considerable complexity to be solved behind the scenes.

The four questions can be reduced to one practical test: Transform when the customer consequence is high, the business consequence is meaningful, the underlying problem is systemic, and the expected value justifies the effort.

This also changes how teams use data. Instead of giving every issue a score from one to five across seven categories, start by building a simple evidence chain:
Customer problem → Journey consequence → Business consequence → Root cause → Transformation value

For example:

That is a much stronger business case than saying, "Our onboarding experience has a low satisfaction score."

Before funding a major transformation, establish a baseline. Choose a small set of measures that answer three different questions:

The point is not to collect every possible metric. It is to create a line between what changed for the customer and what changed for the business. That discipline matters because better experience does not automatically mean better business performance.

Forrester's 2025 CX Index found that 25% of U.S. brands experienced a statistically significant decline in CX scores, while only 7% improved. Across Australia, Singapore, and India, 37% of brands declined and only 5% improved.

The opportunity is therefore not simply to measure experience more often. It is to identify where intervention can actually change the outcome.

Gartner's 2025 research makes a similar case for linking CX measures to financial outcomes, while its research on customer success recommends looking beyond lagging retention measures toward progression through onboarding, adoption, value realization, and expansion.

Customer experience transformation should not begin with a technology decision, a list of complaints, or a request to "fix the UX." It should begin with a customer trying to accomplish something and the organization understanding exactly where that experience breaks down.

From there, the decision becomes clearer:

How much does this failure matter to the customer?
What does it cost the business?
What is actually causing it?
And is changing the underlying system worth the investment?

That is also where customer experience design becomes more than interface design. The work is not simply to make an interaction easier. It is to understand what customers are trying to accomplish, identify what prevents them from doing it, and determine what the organization must change to make the better experience possible. Having the right UX expertise at this stage can make the difference between improving what customers see and solving what they actually experience.

The best transformation candidates are rarely the problems that are simply annoying. They are the ones where a better customer experience and a better business outcome depend on changing the same underlying system. That is where transformation earns its name.

For years, digital customer experience has been about helping people complete tasks themselves. Find a product. Compare options. Fill out a form. Book an appointment. Contact support.
That is beginning to change.

People are increasingly turning to AI not just to find information, but to get things done. Gartner’s 2026 research found that 58% of customers who use GenAI have used it to complete a task on their behalf. Among B2B customers, that figure rises to 74%.

The next step is a customer journey where the person may explain what they want, and an AI agent handles more of the work.

Instead of searching for the right product, a customer could ask an agent to find one that meets their needs. Instead of navigating a support portal, they could ask the agent to resolve an issue. Instead of filling out several forms, they could ask the agent to complete the process for them.
The customer still has the goal. But they may no longer be the person navigating every step.

What happens when the customer is no longer the one navigating?

Imagine asking an AI agent to find the right product, book a service, or resolve a problem for you. You still know what you want. You just do not have to navigate every step yourself.

That changes the customer journey. The experience now depends on whether the agent can find the right information, understand your needs, and take the right action.

For CX leaders, that means asking: What happens if the information is outdated? What if the agent misunderstands a policy? And when should a person step in?

Trust becomes essential. Inaccurate product details, inconsistent policies, or fragmented customer data can lead an AI agent to give the wrong answer or take the wrong action. So the goal is not simply to make experiences easier for AI. It is to make them more reliable for people, even when AI is helping behind the scenes.

Every customer experience begins with a person trying to get something done.

They may be trying to open an account, find the right product, get help with a problem, or simply complete a task without having to repeat themselves. When that experience becomes difficult, the frustration they feel is often only the visible part of a much larger problem.

That is why the most valuable customer experience transformation does not start by asking what technology to introduce or which touchpoint to redesign. It starts by understanding what the customer is trying to accomplish, where they struggle, and what is getting in their way.

The aim is simple: make it easier for people to get where they need to go, while creating better outcomes for the business.

At Millipixels, we help organizations uncover the problems behind difficult customer journeys and identify where meaningful transformation can make the biggest difference. If you are trying to understand which experiences are worth transforming, talk to our experts.