Pillar 3: Adoption — the lever that stops churn (and what most teams measure wrong)
Adoption is not license utilization. Adoption is operational dependence plus business value delivered through the right features. Teams that confuse them think they're healthy — until the customer tells them they're not renewing.
There's a classic trap in CS: measure adoption by license utilization and conclude the customer is healthy because 80% of seats are filled. The problem is that number can be correct and still predict the renewal wrong. An identity-management company cited by Wayne McCulloch found out, after losing several "healthy" contracts, that the best predictor of churn was not license utilization — it was the use (or non-use) of three specific features that delivered the business outcome the customer had bought.
That's the critical point of Pillar 3 — Adoption: adoption is about the right features used at the right depth, tied to the customer's business outcomes. Not about how many logged in.
The definition that matters
Adoption is achieving operational dependence while simultaneously demonstrating business value by using the right features and functionality of the solution. — McCulloch 2021, ch. 5
The value verb is Value Realized — value materialized. Adoption is where value moves from the plan (Pillar 2) to observable reality in the customer's day to day.
Two halves, both required:
- Operational dependence. The customer's people use the solution every time, by default, instead of alternatives. Not "I remembered to log in this week." Reflex.
- Business value demonstrated. The right features — the ones tied to the outcomes the customer promised to deliver internally — are being used and producing measurable results.
Without the first half, the customer is still experimenting. Without the second, they're using the product but not capturing value. Both scenarios end in churn.
Adoption is ongoing — it never ends
Unlike onboarding, adoption has no endpoint. It continues as long as the customer exists. For three reasons:
- New people arrive. Every new employee has to adopt the product. The customer's retention runs through this continuously.
- New features ship. Every release is a new micro-adoption. If the customer is still on features from 2 years ago, they're losing value they're paying for.
- New versions land. Upgrades, UI changes, flow changes. Each is friction that must be overcome.
Teams that treat adoption as a "phase" miss this dynamic. A customer who adopted well 2 years ago may be adopting poorly today — and nobody noticed because they stopped measuring.
Adoption is not license utilization
The most important point in this pillar, and the most confused:
How many seats are filled tells you little. What matters is whether the customer is using the right features — the ones tied to the outcomes they promised to deliver internally.
Three metrics that sound the same, but say different things:
| Metric | What it measures | Why it can mislead |
|---|---|---|
| License utilization | % of seats logged in this month | Customer can log in, do nothing of value, and the metric goes green |
| Depth of usage | How many distinct features / per user | Customer can use 20 features, none of the 3 that matter |
| Sticky-feature usage | Use of features tied to the business outcome | The only one that correlates with renewal |
The operational question: which 2–5 features, if the customer stops using them, signal imminent churn? Those are the sticky features. Everything else is noise.
What the CSM does in this pillar
McCulloch (ch. 5) lists the specific responsibilities:
Generate operational dependence
Remove operational barriers. Release capabilities in stages — not everything at once. The analogy he uses: Candy Crush unlocks skills level by level. The user doesn't get 50 features at once. They get the next one when they've mastered the previous.
Identify and engage the right stakeholders
Shane Anastasi's test: a person is a real stakeholder if they answer "yes" to two or more of the four questions:
- Are they the budget owner?
- Do they have signatory authority?
- Is their job at risk if this fails?
- Are they the operational owner of the outcome?
Two "yes" answers or more = real stakeholder. One "yes" or none = cosmetic stakeholder. CSMs spend too much time tending to cosmetic stakeholders because they answer the phone — and find out too late that no one with decision power was engaged.
Monitor consumption with depth
Logins aren't enough. Depth, frequency, recurrence. Ride-alongs — sit with the real user and watch them work. That reveals things dashboards don't: where the user gives up, where they improvise outside the product, where they complain under their breath.
Release readiness
Be able to demo a new feature on the day it ships. Without that, releases become noise the customer ignores — and the company keeps paying for R&D the customer never consumes.
Lead organizational change
Bury the FUD (fear, uncertainty, doubt). Evangelize the value. Make the old method easy to leave behind. Adoption is as much about what the customer stops doing as what they start doing.
Show benchmarks
How does this customer compare with peers in the same industry, the same size? That's simultaneously motivational (the customer wants to be above the median) and instructive (the customer sees what's possible).
The "red flag" test during adoption
McCulloch proposes a simple diagnostic trick (ch. 5):
Ask the customer, during adoption, if they'd be willing to be a reference.
The answer matters in two directions:
- "Yes, of course, whenever you need." Positive milestone. The customer is seeing enough value to put their reputation on it.
- "Hmm, let's wait and see." Alert. Not a "no" — a "not convinced yet." Run a survey now. What's missing for the "yes"?
Waiting until the formal QBR to discover that hesitation is late. The customer has already consolidated the opinion — and is probably already talking to a competitor.
Onboarding ≠ Adoption (again, because it matters)
We said this in Pillar 2, but it's worth repeating:
| Onboarding | Adoption | |
|---|---|---|
| Duration | Finite | Ongoing |
| Goal | Value one achieved | Operational dependence + business value |
| End | Defined | Never |
| Key metrics | Time to value, plan completeness | Depth of usage, business outcomes, sentiment |
Teams that mix these produce two symptoms: either onboardings that never end (adoption starts inside "eternal onboarding") or adoptions that never start (the handoff was cosmetic, nobody really took the baton).
The dominant risk: relationship risk
In adoption, the risk that most threatens is relationship risk, in two forms:
- Acute. Sponsor leaves without warning. The replacement is unknown. There's no relationship built with anyone beyond the original sponsor. You find out when the first complaint lands from the replacement.
- Persistent. Small frustrations accumulate. No one is nurturing new champions. The relationship concentrates on one or two people — and if they leave, the customer becomes "orphan account."
Prevention is structural: 3 × 3 relationships — three levels of seniority (operational, managerial, executive), three contacts at each level. It costs time. But it's the only way adoption survives natural turnover on the customer side.
How the toolbox helps
- Moments of truth — map every adoption-phase moment. First adopted release. First new user onboarded. First friction-free week.
- Playbooks — three essentials: no usage, low usage, no business value being realized. Each with clear triggers and actions.
- Health score — six possible categories, but in adoption weight product usage and business outcomes heaviest.
- Customer success plan — the adoption section names stakeholders, milestones, KPIs, and the list of who needs to use what.
- Segmentation — not on who gets a CSM, but on training time and methodology. A 5-day course for an enterprise account can be a half-day for a mid-market one.
What healthy adoption looks like
Five observable signals:
- Operational dependence is visible in the data. Daily/weekly active users on the workflows that matter.
- New features are demoed within days of shipping. Not months.
- New stakeholders emerge continuously — new champions surface, not just legacy ones.
- Business value is being measured and shown back to the customer. Not in a deck. In data.
- The customer accepts being a reference well before formal "go-live." More reliable than any health score.
The diagnostic question
To know if Pillar 3 is healthy on your team, one question resolves 80%:
For each active customer, can I name the 3–5 features that matter for their business outcome, and do I have current usage data on those features?
If the answer is no, you're measuring adoption by the wrong proxy. And you'll be surprised by churn instead of predicting it.
Adoption is the pillar that stops churn when it's well executed. Everything in renewal (Pillar 4) is easier when adoption was solid. Everything in renewal becomes fire when adoption was cosmetic.
Based on McCulloch, Wayne. The Seven Pillars of Customer Success: A Proven Framework to Drive Impactful Client Outcomes for Your Company (2021), ch. 5. Adapted by the Partenero team. This post is part of a series on the 7 Pillars — see also the overview post and the post on Account Health Score.