Skip to main content
ExperiencePerformanceSystem™

The Experience Performance System

Get the business to act on what customers are telling you.

The Experience Performance System helps CX leaders find the customer problems worth solving, bring the right teams together, and show whether the fix worked.

Follow one customer journey
field jacketView
the customer’s goal
“I want to buy this jacket, get it when you said I would, and feel confident it’ll fit.”

Illustrative example

Find the problem worth solving

Start with the customer view: one first-time shopper, one order, eight moments. Every team sees a piece of it.

  1. 1 · Product page

    They find the jacket.

    Under the price, the page says “Shipping estimate updates at checkout.” The customer can’t tell yet when it would arrive.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  2. 2 · Checkout

    The promo code fails.

    Checkout shows a static “Estimated delivery: 3⁠–⁠5 days.” The customer enters the 20% new-customer code, NEWCUSTOMER20. It’s rejected.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  3. 3 · Cart Abandonment

    They leave checkout.

    A survey intercept catches them on the way out: “Can’t get the promo to apply.”

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  4. 4 · First call

    The customer has to call to get the offer.

    “I can’t get the new customer promo code to apply.” The Care agent applies the offer and the order goes through: a recovery, but a call the customer shouldn’t have needed to make.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  5. 5 · Confirmation

    The email confirmation leaves the delivery date unclear.

    The confirmation email says the order is on its way. Under “Arrives,” it says only “Arriving Soon.”

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  6. 6 · Delivery window passes

    Where’s my order? (WISMO)

    The window goes by. The customer checks the email, then tracking: “Still in transit.” They call Care again to ask where the order is.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  7. 7 · Delivery

    The jacket arrives late.

    The driver drops it off two days after the estimated window.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.
  8. 8 · After the order

    They don’t come back.

    The customer makes no second purchase during the illustrative observation period. Marketing sends “We want you back” emails.

    1Product pageField jacket“Shipping estimateupdates at checkout.”2CheckoutCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20Static delivery estimate.Promo code rejected.3Cart Abandonment“Can’t get the promoto apply.”Leaves checkout.Intercept records why.4First call“I can’t get the newcustomer promocode to apply”Offer Applied. Order placedAn avoidable call,then a recovery.5ConfirmationOrder confirmedArrives: Arriving SoonEmail confirms the order.No delivery date.6Window passesTRACKINGStill in transitcall #2Tracking: in transit.Calls Care again.7DeliveryDELIVERY+2 daysArrives two daysafter the window.8After the orderWe want you backNo second purchase.Win-back emails start.

The company view · Illustrative figures

What the business sees

Meanwhile, inside the company, nobody is looking at this order. Each leader is looking at their own numbers.

Scene 1 · Executive team meeting

The company scorecard is heading the wrong way.

The CEO walks through the quarter. Then each department reports its own numbers, and most of them look good.

CEO

Company scorecard

Quarterly business review · illustrative figures

  • YoY revenuedown
  • Profitabilitydown
  • Net customer growthdown
  • Customer lifetime valuedown
  • Customer acquisition cost (CAC)up

department leaders report their own numbers

  • Marketing

    • eCommerce trafficup
    • Promo code redemptionup
  • eCommerce

    • Page viewsup
    • Trafficup
    • Cart conversionup
  • Fulfillment

    • On-time deliveryimproved
    • 97% of deliveries within SLAmet

    Internal SLA, not the date shown at checkout.

  • Customer Care

    • Digital order callsup
    • “Where’s my order?” callsup
  • CX

    • NPSimproved

SLA ≠ the promise the customer saw. Fulfillment measures delivery against its internal SLA. The customer measures it against the date shown at checkout. The SLA result can improve while some customers still miss the date they were given.

Scene 2 · CX Steering Committee

The CX leader brings the themes. Nothing moves.

The CX leader reports the five most negative eCommerce topics from customer feedback. The room nods.

Top negative eCommerce topics

Impact ScoreIllustrative scores

  1. 1Promo Codes−6.5
  2. 2Delivery Date Estimates−4.7
  3. 3Late Deliveries−3.2
  4. 4Merchandise Availability−1.7
  5. 5Delivery Communication−0.7

Department leaders:

“Great insights. Let’s keep monitoring.”

the CX leader
“Why can’t I get the organization to take action?!”
the CEO, looking at the scorecard
“Why is the business not performing?”

Same company. Same data. What if the CX leader worked it differently?

Green marks a good result, red marks a bad one.

The Experience Operator · Illustrative example

Bring the right teams together

Same company, same data. This time the CX practitioner works it like an operator: connect the evidence, earn 15 minutes, build the case with the owner, and get a decision.

  1. Which issue first?

    Which issue do we look at first?

    Looking across the whole order, the practitioner circles the failed promo code and the cart abandonment it caused. That’s the first issue to address: it sits on a goal eCommerce already owns. Delivery estimates and post-purchase updates stay on the board for later.

    first issue to addressCHECKOUTEstimated delivery:3–5 daysNEWCUSTOMER20“Can’t get the promoto apply.”next in the queue1. Delivery estimates2. Post-purchase updates
  2. A · Problem statement

    Draft a specific problem statement.

    The practitioner pulls evidence from five places and puts numbers on the problem: how many shoppers hit it, what’s left in their carts, what it costs Care, and what it puts at risk. It’s a starting point for a conversation with the owner, not a verdict.

    Problem statement · draft

    Synthetic example

    Every week, 1,200 first-time digital shoppers encounter an error when they try to apply the new-customer promo code at checkout. Of those shoppers, 76% abandon checkout, leaving $77,638 in their carts.

    The issue also generates 220 calls a week to Customer Care from shoppers who need help applying the code. At an average cost of $11.07 per contact, those calls cost about $2,435 a week. If we don’t fix the issue by Q4, we project a shortfall of 1.2 percentage points against our cart conversion goal and $440,000 against our eCommerce revenue goal.

    where the evidence comes from

    • Promo error events
    • Eligibility rules
    • Checkout behavior
    • Survey intercept
    • Care contact reasons
    Average order value (AOV)
    $85.13
    Value left in abandoned carts
    $77,638
    Average cost per contact
    $11.07

    Three different figures: value left in carts (not realized revenue loss), the weekly cost of Care calls, and the projected revenue shortfall. They aren’t added together.

  3. B · 15 minutes

    Get 15 minutes with the right person.

    Doug, VP of eCommerce, is accountable for two numbers: cart conversion and the year-over-year digital revenue commitment. Both are projected to miss. The promo error sits right on his goals, so the ask is short and speaks to them.

    What Doug owns

    Synthetic example
    • Improve cart conversionProjected 1.2 percentage point gap to goal
    • Meet the YoY digital revenue commitmentProjected $440,000 shortfall
    To
    Doug, VP of eCommerce
    Subject
    Something that may be blocking checkout conversion

    Hi Doug, I know your team is focused on reducing cart abandonment %, I may have found an issue that is blocking conversion. Worth 15-minutes to discuss?

    short, specific, and about his goal

  4. C · The business case

    Build the business case together.

    Doug brings the checkout goal and who owns what. The practitioner connects the customer comment with checkout behavior and Care contacts. Together they agree on the change to propose and the one measure that will show whether it helped.

    CX Case Maker · one page

    built togetherSynthetic example
    Headline
    Fix the new-customer promo code at checkout.
    Problem
    1,200 first-time shoppers a week hit a promo code error; 76% abandon checkout, leaving $77,638 in their carts.
    Approach
    Correct the eligibility or application rule, reproduce the issue, and verify that an eligible shopper can complete checkout with the offer.
    Payoff
    Improve cart conversion for eligible first-time shoppers and reduce the 220 promo-related Care calls a week (about $2,435).
    Investment
    eCommerce engineering and QA time, plus validation with Marketing and Care.
    Compelling Event
    Fix it before Q4, when the conversion and revenue goals are measured.
    Cost of Inaction
    A projected 1.2-point gap to the cart conversion goal and a $440,000 shortfall against the eCommerce revenue goal.
    Doug bringsgoal: close the cart conversion gapowns checkout + promo rulesPractitioner bringsthe customer commentcheckout behaviorCare contact reasonsWE AGREEchange: fix the promo rulemeasure: eligible checkout completionDougVP of eCommerceCX practitionersame whiteboard, same customer
    • Doug brings: the goal (cut cart abandonment %) and ownership of checkout and promo rules
    • The practitioner brings: the customer comment, checkout behavior, and Care contact reasons
    • They agree: change: fix the promo rule · measure: eligible checkout completion
  5. D · The decision

    Get a decision and an owner.

    At the prioritization session, Doug presents and champions the case. It’s approved, and the Director of eCommerce is assigned to own delivery of the fix.

    prioritization sessionCX CASE MAKERFix the new-customerpromo code at checkoutAPPROVEDMarketingFulfillmentCustomer CareDougchampions the caseOWNERDirector ofeCommercedelivers the fixbrought the evidence
    • Doug, VP of eCommerce: presents and champions the case
    • Decision: approved
    • Owner: Director of eCommerce, who delivers the fix
    • CX practitioner: brought the evidence
  6. E · Separate teams

    Five teams, five pieces of the same order.

    eCommerce, Marketing, Fulfillment, Customer Care, and CX each see part of this customer’s experience in their own numbers.

    Before · separate views

    • eCommerce

      own numbers:

      • Cart conversion ↑
      • Page views ↑
    • Marketing

      own numbers:

      • Promo redemption ↑
      • Traffic ↑
    • Fulfillment

      own numbers:

      • 97% within SLA
      • On-time ↑
    • Customer Care

      own numbers:

      • WISMO calls ↑
      • Order calls ↑
    • CX

      own numbers:

      • NPS ↑
      • 5 negative topics

    Local fixes. More friction.

  7. E · The Journey Pod

    Form the Journey Pod.

    The teams move into one shared workspace around the same journey. The VP of eCommerce sponsors it, the Director of eCommerce owns the first fix, and the pod coordinates the work and the measurement.

    Journey Pod: a team from across the business with the authority to fix a shared customer problem.

    After · shared workspace

    Journey Pod

    VP of eCommerce

    sponsors the work

    Director of eCommerce

    owns the first fix

    Shared outcome · longer term

    Increase repeat purchase among first-time digital buyers.

    First intervention: Fix the promo code. Measure cart conversion for the eligible checkout group.

    • eCommerce

      Cart conversion ↑ · Page views ↑

    • Marketing

      Promo redemption ↑ · Traffic ↑

    • Fulfillment

      97% within SLA · On-time ↑

    • Customer Care

      WISMO calls ↑ · Order calls ↑

    • CX

      NPS ↑ · 5 negative topics

    the same order

    1. Product
    2. Checkout
    3. Cart abandon
    4. Call
    5. Email
    6. WISMO call
    7. Late
    8. Win-back

    next in the pod’s queue

    1. Estimated delivery dates
    2. Post-purchase communications

Which customer problem is worth fixing first at your organization?

Build your problem statement

Or keep scrolling to see whether the fix worked

The payoff · Illustrative example

Show whether the fix worked

Replay the same order with the promo fix in place. Then pull back to what the pod measures.

  1. Replay · Before

    Replay the same order.

    Same jacket, same customer, same journey. Before the fix: the code is rejected, the customer abandons checkout, and Care has to help them finish the order.

  2. Replay · After

    Now with the promo fix in place.

    NEWCUSTOMER20 applies for the eligible shopper, and they complete checkout without calling for help. The delivery estimate and the post-purchase updates haven’t changed yet. They’re next in the pod’s queue.

    Replay the same order

    Illustrative replay · Before the fix

    1. 1. Checkout

      NEWCUSTOMER20 is rejected.

    2. 2. Cart

      Leaves checkout. Survey: “Can’t get the promo to apply.”

    3. 3. Customer Care

      An avoidable call. The agent applies the offer and the order goes through.

    4. 4. Confirmation

      “Arrives: Arriving Soon.” No delivery date.

      Then: post-purchase communication

    5. 5. Tracking

      The window passes. “Still in transit.” A second call.

      Then: post-purchase communication

    6. 6. Delivery

      Arrives two days after the static estimate.

      Next in the queue: delivery estimates

  3. The measurement board

    Pull back to what the pod measures.

    One measure for the first intervention, two things to keep an eye on, and the longer-term outcome the pod is working toward.

    The payoff that matters

    Synthetic example

    First intervention · the measure

    Eligible checkout completion

    +6 percentage points

    Definition: Completed orders ÷ eligible checkout sessions, using the same eligibility rules in each period.

    An illustrative observed change for this example. Not a real client result, and not proof of causation on its own.

    This pilot measure doesn’t show that the projected $440,000 revenue gap has closed. Revenue impact needs its own comparison over time.

    Also monitor

    • Promo code rejectionsto check
    • Promo-related Care contactsto check

    Longer-term outcome

    Second purchase rate among first-time digital buyers

    The longer-term outcome. Before drawing a conclusion, compare with a comparable group and give both the same full follow-up window.

  4. What’s next

    Move to the next item in the queue.

    With the promo fix in place and being measured, the pod turns to delivery estimates, then post-purchase communication.

    The pod’s queue

    1. Promo code fix

      In place. Being measured.

    2. 1

      Estimated delivery dates

      upcoming work · next

    3. 2

      Post-purchase communications

      upcoming work · after that

You weren’t meant to just manage experience.You were meant to change it.

That’s what it looks like to operate the Experience Performance System inside your organization.

one friction off the journey

wins stack up

Promo code works
  • up nextClear delivery estimate
  • up nextTimely order updates

What would you change about your customers’ first experience?

Build your own problem statement with the CX Case Maker template. Fill in what you know, leave the rest open, and copy it into your next conversation.

Fill in what you know. Tick Leave open for anything you still need evidence for.

your problem statement

Every [ frequency ], at least [ reach ] of our [ customers / employees / stakeholders ] experience [ pain point ], resulting in [ measurable CX loss ].

This leads to [ implication #1 ]. If this is not resolved by [ timeline ], we risk [ implication #2 ].

See the full original template

Every [ frequency ], at least [ reach ] of our [ customers / employees / stakeholders ] experience [ pain point tied to CX, e.g., delivery delays, inconsistent support, poor communication ], resulting in [ measurable CX loss, e.g., lapsed customers, increased churn, or loss revenue ].

This leads to [ implication #1, e.g., loss of repeat purchases, higher acquisition costs to replace churned customers, etc ]. If this is not resolved by [ timeline, e.g., Q2 ], we risk [ implication #2, e.g., further erosion of brand loyalty, compounding operational inefficiencies, or falling behind revenue target by $$].

Your draft stays in your browser. Builder privacy

Free CX Case Maker toolkit

You’ve written the problem statement. Now build the case for fixing it.

The free CX Case Maker toolkit gives you a practitioner’s guide and a one-page business case template, the same one Doug and the practitioner filled in above.

Free through Experience Performance Academy.

Practitioner’s guide

CX Case Maker

Experience Performance Academy

One-page business case

  • Headline

  • Problem

  • Approach

  • Payoff

  • Investment

  • Compelling Event

  • Cost of Inaction

Problem statement builder privacy

The problem statement builder processes what you type in your browser. Typing in the builder or using Copy problem statement does not send your draft to EPS. Optional sharing is currently off. Please leave out names, customer identifiers, and confidential company information.