The value of listening to customers does not lie in generating an ever-growing list of opportunities, but in having better criteria for deciding where to act, where not to act, and what deserves further exploration.
Many organizations have made significant progress in their ability to listen. They have research, surveys, operational data, journeys, interviews, complaints, and Voice of the Customer programs. The problem comes next: when all that information needs to be turned into decisions.
Between understanding what is happening and starting to design solutions lies a step that is often oversimplified: deciding what truly deserves attention. Effective prioritization of customer experience initiatives requires combining evidence about people with business impact, strategy, and the organization’s ability to execute. Above all, it requires accepting that prioritization also means choosing what not to do.
More insights do not necessarily lead to better decisions
Having more information about customers does not guarantee better decisions. In fact, the greater an organization’s research capabilities, the easier it is to end up with dozens of needs, pain points, and potential opportunities competing for attention.
The problem arises when every relevant finding is automatically interpreted as a call to action. A customer expresses a need, a pain point appears in the journey, or a recurring friction is identified and, almost immediately, the conversation turns to possible solutions. But customer insights should inform decisions, not replace them.
There is also the opposite problem: organizations that conduct research repeatedly, produce increasingly sophisticated diagnoses, and yet barely change their priorities. Knowledge grows, but the decisions remain the same.
We saw this clearly in a project for a service organization. There were several previous quantitative studies and a substantial body of accumulated knowledge. We expanded that evidence through focus groups with customers, interviews with internal stakeholders, and input from employees. When we analyzed these sources together, insights and opportunities emerged across different areas.
There were more than 30 opportunities on the table. The challenge was no longer finding more things to improve, but deciding which ones truly justified mobilizing the organization.
That space between listening and ideating is critical. If it is overlooked, research ends up becoming an initiative generator. An organization does not need to act on everything it discovers; it needs to make better decisions based on what it discovers.
From an interesting insight to an opportunity worth pursuing
An insight, an opportunity, and an initiative are not the same thing. Distinguishing between them prevents organizations from jumping too quickly from evidence to solutions.
An insight provides a relevant understanding of what is happening: why a particular friction occurs, which need remains poorly addressed, or what pattern explains a behavior. An opportunity emerges when we interpret that understanding as an area where intervention might make sense. An initiative comes later: it is a concrete response that will require resources, ownership, capabilities, and implementation decisions.
Therefore, not every insight needs to become an opportunity, and not every opportunity needs to become an initiative.
Before elevating a finding, it is worth asking about its relevance to people, its intensity and reach, the strength of the supporting evidence, and the consequences of not acting. It also matters how closely it relates to the value proposition we want to build and whether there is reasonable potential to create value.
This is where combining sources becomes particularly useful. In the project, we found considerable overlap between many of the frictions identified by customers and those described by employees. This convergence strengthened certain findings and helped us understand what was happening from different perspectives.
But even a well-supported friction does not automatically require action.
Listening to customers does not mean literally implementing what they ask for. Some opportunities may be highly relevant but affect only a minority of customers. Others may affect many people but have limited consequences. And some may be important to customers while still falling temporarily outside the organization’s ability to act.
This initial filter is necessary before solutions are even discussed.
Four questions for deciding which opportunities should become initiatives
The prioritization of customer experience initiatives requires assessing four dimensions: value for people, business impact, strategic alignment, and the organization’s actual ability to execute.
The purpose is not to turn them into an automatic scoring system. Their role is to make trade-offs visible and help justify which criterion should carry more weight in a particular context.
An opportunity may be highly relevant to customers but poorly aligned with strategy. It may offer attractive business impact while exceeding the organization’s current capabilities. Or an initiative may be perfectly feasible but barely change anything that truly matters.
Prioritization is precisely about comparing these tensions and deciding where committing resources is justified.
1. Is it relevant enough to people?
The first dimension is value for people: proving that a need exists is not enough; we need to understand how much it matters.
That means assessing how many people it affects, how often, with what intensity, and with what consequences, as well as the evidence supporting that conclusion. A striking request expressed by a handful of customers does not necessarily carry more weight than a less visible friction that repeatedly affects a substantial part of the customer base.
This is why volume data matters when it is available. If we claim that an opportunity is a priority, we should be able to explain the evidence behind that conclusion.
This does not mean that only widespread problems deserve attention. A low-frequency friction can have serious consequences at critical moments in the relationship. The key is to understand reach and intensity together rather than allowing a single metric to determine the decision.
2. What business outcome could it change?
The second dimension is business impact: a customer experience strategy needs to formulate a hypothesis about which business outcome could change and why.
Depending on the opportunity, we might expect changes in retention, conversion, repeat business, revenue, cost to serve, incidents, efficiency, productivity, usage, or risk.
This also requires distinguishing between experience metrics and business outcomes. Improving a rating, reducing perceived effort, or increasing satisfaction may be relevant, but it does not automatically demonstrate a financial return.
The hypothesis should exist before prioritization; proof will come later, if the initiative is implemented and its impact can be measured appropriately.
We do not need to promise an ROI we do not yet know in order to justify an initiative. We need to explain rigorously what we expect to change and which signals will allow us to determine whether it has.
3. Is it aligned with the strategy and the experience we want to build?
The third dimension is strategic alignment. The fact that an initiative could improve the customer experience does not necessarily mean the organization should pursue it.
Strategy is also about deciding what not to do. It requires defining what kind of experience we want to build, where we want to differentiate, and which capabilities deserve investment. Without that filter, an organization can end up spreading resources across many reasonable improvements that, taken together, fail to build a recognizable direction.
This question becomes particularly important when considering attractive or novel opportunities. Innovation can generate enthusiasm, but novelty alone is not a reason to prioritize something.
In the project, an opportunity related to new services initially seemed overly ambitious. However, there was no need to begin with a full implementation. The organization could first develop the value proposition and test it with existing customers.
This illustrates an important trade-off. Difficulty should not automatically cause a strategically relevant opportunity to lose out to an easier one. Sometimes the right decision is to find a reasonable way to learn before committing significant investment.
4. Can the organization make it happen and sustain it?
The fourth dimension is the actual ability to execute. An initiative is not viable simply because it can technically be built; it needs to be able to exist within a real organization.
That involves capabilities, resources, processes, technology, dependencies, regulation, maintenance, and the ability to make decisions.
In our case, some relevant opportunities depended on other parts of the organization and crossed different areas of responsibility. Certain decisions required involvement beyond the team working directly on the customer experience, without there being a single owner with clear authority to move them forward.
A solution might exist on paper. Organizationally, the path could be much less obvious.
That is why feasibility should form part of prioritization before an initiative is finally selected. Not necessarily as a reason to discard it: in some cases, the first step may be to resolve a capability gap, dependency, or governance issue that currently prevents the opportunity from being addressed.
The four dimensions do not eliminate judgment. They structure it. When they conflict, the decision is about making the trade-off explicit and justifying why, in that particular context, one dimension should carry more weight than another.
Why an impact-effort matrix is not enough for prioritization
An impact-effort matrix can be extremely useful. The problem begins when we ask it to make a decision it cannot make.
Plotting opportunities according to their expected impact and the difficulty of implementing them helps compare alternatives and prompts necessary conversations. We used these criteria ourselves during the process. But they were part of the decision, not the entire decision.
An apparently simple, high-impact initiative may contradict a strategic priority, depend on a capability that does not exist, or increase operational complexity elsewhere. It may also address the visible symptom while leaving the underlying cause untouched.
In the project, impact and effort prompted discussions about other criteria. Those conversations were more valuable than the exact position of an opportunity within the matrix.
From more than 30 opportunities, we arrived at 11 concrete solutions, but not through a linear elimination process in which the 11 highest-scoring opportunities survived. Some opportunities were discarded because of their complexity or because they were difficult to address in that context; others were grouped because a single solution could address several related opportunities.
A matrix helps visualize a decision. It should not make the decision for us.
Decisions improve when the people who will make them possible are involved
Bringing different areas into the prioritization process introduces operational, technological, and organizational knowledge that can change how an opportunity is assessed. It does not mean putting initiatives to a vote.
Ignoring that knowledge until implementation is often a very expensive way of discovering dependencies and constraints that could have been identified earlier.
However, bringing many areas together does not automatically guarantee a better decision either. If each area only defends its own interests, prioritization can turn into an internal negotiation. That is why it helps to establish a shared evidence base and common decision criteria first.
In our case, the findings were shared with different stakeholders, and workshops were used to compare perspectives, prioritize opportunities, and subsequently develop solutions. Disagreements also helped reveal differences between areas and constraints that were not visible to everyone.
Participation creates value when it improves the information available for decision-making. Co-creation does not replace judgment. It makes judgment better informed.
A priority has not really been decided until it can be translated into execution
A priority is sufficiently defined only when the organization can explain what happens next.
At a minimum, it should be clear which problem or opportunity it addresses, what its objective is, what impact hypothesis exists for both customer and business, who should lead it, which areas are involved, what capabilities it requires, which indicator will be used to monitor progress, and what the next concrete action is.
In our case, the selected opportunities were grouped and transformed into 11 solutions with a specific definition, expected impact on customers and business outcomes, KPIs, initial steps, and a transformation roadmap. Some were subsequently implemented with modifications.
This does not mean that defining a KPI proves impact, or that placing an initiative on a roadmap guarantees execution. Implementation introduces new decisions and constraints.
A useful roadmap shows what will be done, in what sequence, what it depends on, and what real capacity exists to move forward. If everything is described as a priority but nothing has an owner or a next decision, we are still looking at an inventory of good intentions.
Prioritizing well means knowing what to do, what not to do, and what to revisit later
Listening provides evidence. Interpreting that evidence turns findings into opportunities. Prioritization requires deciding which opportunities justify mobilizing resources.
To do this, it helps to answer four questions: Is it relevant to people? What business outcome could it change? Is it aligned with the strategy? Can the organization make it happen and sustain it?
When an organization has 30 or 40 opportunities and considers all of them important, that assumption is worth testing. Do we know how many customers they affect and with what intensity? What outcome could they change? Do they fit the experience we want to build? What would implementation require? And, finally, do we know who needs to act and what needs to happen next?
In the project used as our reference, the more than 30 opportunities did not simply become the “11 best.” Evidence, decision criteria, constraints, and the grouping of related opportunities allowed us to transform them into 11 solutions that were sufficiently defined to support decision-making.
That is the difference between knowing your customers better and using that knowledge to transform an organization.
Listening better should not serve to generate more initiatives. It should help us make better decisions about which initiatives are worth pursuing.
If you have research, data, journeys, or identified opportunities but still find it difficult to decide where to start, tell us about your challenge and let’s explore how we can help.
