Measure what customers achieve, not what your team does.
It's easy to track how many calls were made or how many emails were sent. But activity volume doesn't correlate with customer success. The framework centers on customer outcomes (value realization, adoption, expansion) because those are the leading indicators of retention and growth. A team that drives 10 outcomes with 5 touches is outperforming one that logs 50 activities with no measurable impact.
"We did 400 QBRs this quarter" is an activity metric. "80% of our top-tier accounts hit their first-year adoption milestone" is an outcome. Activity metrics are comfortable because they are easy to hit: hold the meeting, log the touchpoint, send the email. Outcome metrics are the ones that determine whether retention and expansion happen. A CS team focused on activities ends up busy, measured, and ineffective. One focused on outcomes has to be honest about whether the work is moving the customer toward their stated goal, and adjust when it is not.
The same principle looks different at every stage. Calibrate the expectation to where the team actually is.
Success is measured by what CSMs do: number of calls, emails, QBRs scheduled. The team has no shared definition of what a "successful" customer looks like beyond "not churned yet." Customer goals are mentioned at kickoff but rarely tracked against. Activity dashboards are what CS leaders show during executive reviews.
Each customer segment has a defined success outcome: completed onboarding, reached time-to-value, adopted core features. CSMs track progress toward these outcomes in addition to activities. Review rhythms (QBRs, internal reviews) start with "where is the customer against their stated outcomes" rather than "what did we do this quarter."
Outcome attainment is a primary CS KPI. Compensation, promotion, and team-level planning reference outcome metrics rather than activity counts. Plays are designed around outcomes to move, not boxes to check. Activities are still tracked for capacity planning but are not the scorecard. Account plans at this level anchor on the customer's business outcome as the primary measure: revenue protected, efficiency gained, risk mitigated. A productive quarter means the customer hit their goal, not that the team stayed busy.
Where this principle shows up in the rest of the framework.
Take the five-minute assessment to see how your CS function scores across the eight maturity domains, with priority actions tailored to your stage.