How to Prioritize a Portfolio of CX Initiatives, Not a Backlog

Most CX prioritization exercises fail before the workshop starts, because the room agrees to rank a list when it should be designing a system. Everyone scores initiatives on impact and effort, sorts the spreadsheet, and calls the top ten "the roadmap." Then, eighteen months later, satisfaction hasn't moved, and nobody can explain why — the highest-scoring initiatives got funded, after all.

They got funded. They just weren't the right ones, in the right order, for the way customers actually experience the journey. A portfolio of CX initiatives should be prioritized by where an initiative sits on the customer's emotional arc and what it unlocks downstream — not by a standalone impact/effort score. Two initiatives can carry identical scores and deliver wildly different returns, because one closes a moment of truth near the end of the journey and the other patches a step nobody remembers. Score them the same way and you'll fund the wrong one every time.

Why do standard prioritization matrices fail for CX portfolios?

They fail because they treat every initiative as an independent bet, when a CX portfolio behaves like a system with dependencies, sequencing constraints, and a memory. The classic 2x2 — impact on one axis, effort on the other — was built for product backlogs, where features genuinely can ship in almost any order. Journeys don't work like that. Fixing the checkout step before the onboarding step that causes half the checkout abandonment is a wasted quarter, no matter how high checkout scored on its own.

Frameworks like RICE — reach, impact, confidence, effort, popularised by Intercom in a widely cited product-management framework (Intercom, "RICE: Simple prioritization for product managers," 2016) — are a genuine improvement over gut-feel roadmaps. But they were designed for feature portfolios, not experience portfolios. They score initiatives in isolation and assume effort and impact are independent of what else is in flight. In a CX programme, they rarely are: a new complaints workflow only pays off once the escalation policy behind it has been redesigned, and a personalization initiative is worthless until the data model it depends on exists.

The deeper problem is that impact/effort scoring answers "is this worth doing?" when the real portfolio question is "worth doing before what?" A backlog is not a portfolio until someone has decided what it's for.

What should sit on the axes instead of "impact" and "effort"?

Replace the generic impact score with three components that actually predict return in a service context: journey position, behavioral leverage, and operational drag.

• Journey position — where the touchpoint sits relative to the moments customers actually remember and recount: the emotional peaks, the troughs, and the very end of the interaction.
• Behavioral leverage — whether fixing it changes a decision, not just a feeling. A friction point that stops someone completing an application scores differently from one that merely irritates them without altering the outcome.
• Operational drag — the ongoing cost of leaving it unfixed: repeat contacts, escalations, agent time, churn risk. This is what turns a "nice to have" into a line the finance director will actually defend.

Effort still matters, but split it into build effort and organisational effort — the latter being change management, training, and policy rewrites, which is usually the bigger number and the one teams forget to score. An initiative that requires no new technology but does require three departments to change how they hand off a case is not "low effort" just because there's no development ticket attached to it.

How does the peak-end rule change your priority order?

It changes it substantially, because customers don't average their experience — they remember its emotional high points, its lowest point, and how it ended, and judge the whole journey by those few moments. This is the peak-end rule, demonstrated by Daniel Kahneman, Barbara Fredrickson, Donald Redelmeier and colleagues in a 1993 study published in Psychological Science, "When More Pain Is Preferred to Less: Adding a Better End," in which participants who endured a longer but improving discomfort remembered the experience more favourably than those who had a shorter one that ended badly.

Applied to a CX portfolio, this means a mediocre fix to the final step of a journey — the delivery confirmation, the resolution message, the account closure — can outperform a brilliant fix to a middle step that nobody dwells on afterwards. Teams routinely underweight "boring" endings and overweight flashy middle-of-journey redesigns because the latter look better in a steering-committee deck. The scoring model has to correct for this bias deliberately, or the organisation's own presentation habits will sabotage the sequencing.

Loss aversion, from Daniel Kahneman and Amos Tversky's 1979 prospect theory (Econometrica, "Prospect Theory: An Analysis of Decision under Risk"), does similar damage from the other direction. A touchpoint where customers feel they are losing something — a fee they didn't expect, a benefit that silently expires, a status they might drop — generates outsized dissatisfaction relative to an equivalent gain elsewhere. Portfolios that only chase "delight" initiatives and leave loss-framed moments unaddressed are optimising the wrong side of the ledger; the downside moments are usually cheaper to fix and carry more weight in memory than the upside ones.

How do you handle dependencies between initiatives?

You map them explicitly, before you score anything, because sequencing errors are the single most common reason a well-scored portfolio underdelivers. Three dependency types show up in almost every CX programme:

• Technical dependencies — initiative B needs the data, API, or platform that initiative A builds.
• Process dependencies — a policy or escalation rule has to change before a frontline fix can hold; retraining agents on a new complaints script before the underlying resolution authority has shifted just produces frustrated agents repeating an old promise.
• Perceptual dependencies — customers won't believe a new initiative if an unresolved, higher-visibility pain point is still active. Launching a loyalty upgrade while the contact centre wait time is still notorious will get read as tone-deaf, not generous.

A dependency map turns a ranked list into a sequenced implementation roadmap, and this is where a lot of prioritization work actually earns its budget — not in the scoring workshop, but in deciding what has to be true before something else can succeed.

What does a working prioritization framework look like end to end?

The mechanics matter less than the discipline of running them in order. This sequence works because each step corrects a bias the previous step introduces:

1. Map the full journey and place every candidate initiative on it. Use existing journey mapping work rather than starting from a blank backlog; if the map doesn't exist yet, this step is where the portfolio conversation should actually begin.
2. Score behavioral leverage and operational drag for each initiative, not just a single "impact" number. Pull operational drag from real data — repeat-contact rates, escalation volumes, churn correlation — rather than opinion.
3. Apply a peak-end weighting that boosts initiatives at emotional peaks, troughs, and journey endings relative to their raw score, and flag any initiative addressing a loss-framed moment for the same reason.
4. Map dependencies across technical, process, and perceptual layers, and demote any initiative that depends on something not yet funded, regardless of how well it scored on its own.
5. Stress-test against delivery capacity. A portfolio that looks affordable on budget can still be undeliverable on people; sizing the actual team required — often via a structured CX ROI Calculator to quantify projected returns against cost — keeps the shortlist honest before it reaches committee.
6. Set a reprioritization cadence, typically quarterly, so the portfolio can absorb new voice-of-customer data or a shifted regulatory deadline without a full re-litigation of every decision.

Skipping step three is the single most common shortcut, because it's the one step that has no obvious spreadsheet column. Teams that skip it end up with technically well-scored portfolios that customers still describe as disappointing, because the fixes landed in the middle of the journey where nobody was going to notice them.

Who should actually own the trade-off decisions?

A single accountable body should own it — call it a CX steering group or investment committee — because prioritization is a resource-allocation decision with political consequences, and consensus-by-committee is how mediocre initiatives survive. The alternative, where every department head defends their own initiative in a shared meeting, reliably produces a portfolio shaped by who argues loudest rather than what the journey needs.

This is a CX governance question as much as a scoring one. The committee needs three things to function: a mandate to say no to a business unit's pet project, visibility into the dependency map so it isn't re-litigating sequencing every meeting, and a standing seat for whoever owns change management, because the organisational-effort score from earlier is only credible if the person who has to deliver the retraining or the policy rewrite is in the room when it's scored.

Bain & Company's 2005 report Closing the Delivery Gap, published on bain.com, found that the large majority of companies in its study believed they delivered superior customer experience while only a small fraction of their customers agreed — a gap the report attributed largely to leadership overestimating the quality of what they'd already funded (Bain & Company, "Closing the Delivery Gap," 2005). A governance body that reviews outcomes against the original journey diagnosis, not against internal opinion, is the mechanism that keeps that gap from reopening.

What breaks in practice, even with a good framework?

Three failure modes recur across almost every CX programme, regardless of how well the scoring model was designed:

• Sunk-cost capture. An initiative that's already 60% built gets re-prioritized upward not because it still scores well, but because nobody wants to write off the spend. The committee's job is to score it as if starting today, every quarter, without exception.
• The HiPPO override. A senior executive's pet initiative jumps the queue after the scoring is done. This is less a scoring failure than a governance failure — it means the committee's mandate wasn't real in the first place, and the fix is structural, not analytical.
• False precision. Teams argue for forty-five minutes about whether an initiative is a 7 or an 8 on a ten-point impact scale, as if the model were more accurate than the underlying data. The scoring exists to force a conversation and create defensible sequencing, not to produce a number worth arguing over to the decimal point.

None of these are solved by a better spreadsheet. They're solved by a committee with a real mandate, a dependency map that makes shortcuts visible, and a habit of re-scoring rather than re-arguing every quarter.

Where does this leave the CX programme office?

Somewhere less comfortable than "we ranked the backlog and funded the top ten," and considerably more honest. A portfolio built on journey position, behavioral leverage, and mapped dependencies will occasionally tell you to fund the unglamorous fix to a resolution email over the flashy app redesign everyone wanted to show the board — and that's the point. Customers don't remember your roadmap. They remember the peak, the trough, and the end, and they judge you on whether the sequence made sense, not on how many initiatives shipped this quarter.

Building that discipline into how a team scores, sequences, and governs its portfolio — rather than into a one-off workshop — is what separates a CX function that compounds credibility over time from one that re-explains itself every budget cycle. If your organisation is still ranking initiatives on a single impact/effort axis, an honest customer experience strategy review is usually the faster fix than another scoring template.