CX Methods

    Input metrics vs outcome metrics

    Input metrics count motion; outcome metrics count whether the customer won. Steer by outcomes and keep inputs as diagnostics.

    Input metrics such as searches, likes, app opens, and time on page can all rise while the experience gets worse. Outcome metrics measure whether customers actually accomplished what they came to do. The gap between the two is where budgets and trust quietly leak.

    Input metrics count motion: time on page, searches performed, notifications sent, profiles viewed, app opens. Every one of them can rise while the customer experience gets worse. Outcome metrics count whether the customer actually won: task completed, issue resolved, effort reduced, first value reached. A dating app makes it concrete. Profile views and matches sent reward noise; conversations that continue meaningfully reward the thing customers came for. Organizations that optimize inputs create friction by accident. Organizations that optimize outcomes design systems that help customers win.

    Why it matters to the business

    The input-outcome gap is where money leaks. Gartner found 73% of customers use self-service during their journey, yet only 14% of service issues are fully resolved there. Measured by usage, an input, self-service looks like a triumph. Measured by resolution, the outcome, it fails six times out of seven and quietly pushes volume and cost into live channels.

    The gap also predicts churn. Research from CEB, now part of Gartner, found 96% of customers who go through high-effort experiences become more disloyal, versus 9% after low-effort ones. Input metrics can look healthy while customers grind through exactly that kind of effort.

    How to use it

    • Stress-test each headline metric with one question: could this rise while customers fail? If yes, it is an input.
    • Define the outcome each key journey exists to deliver, such as task done, issue resolved, or first value reached, and instrument it.
    • Measure resolution and completion, not just usage and traffic.
    • Demote inputs to diagnostics: useful for explaining why an outcome moved, never as targets in their own right.
    • Rebuild the executive dashboard so outcomes sit on top and inputs sit underneath them.

    Where teams get it wrong

    Optimizing inputs because they are easy to move. A team told to grow sessions will generate sessions: more notifications, more forced steps, more reasons to come back. The activity chart climbs while the customers doing the activity are failing, and the friction was manufactured in-house.

    Ask your team

    • Which of our top five metrics could improve while customers fail?
    • For each key journey, what is the outcome it exists to deliver, and do we measure it?
    • Where do our usage numbers and our resolution numbers tell different stories?

    Input metrics count activity. Outcome metrics count success. Only one tells you whether customers won.

    Apply this

    Reading about input metrics vs outcome metrics is one thing. Seeing where it applies in your journey is the useful part.

    Related signals