← Selected work
Work
Enterprise Customer Success
Portfolio of enterprise accounts

Adoption & Engagement Analysis

Downloads flatter everyone. Usage rate tells you whether anything actually happened.

AdoptionRetentionBehavioral Analysis

Sanitized for publication. Company names, customer identities, and proprietary figures have been removed.

01

Purpose

Accounts wanted to know whether their program was working. The honest answer required separating the numbers that sound like success from the numbers that are success, then saying which levers would move the second set.

02

The problem

Every account had access to the same dashboards and reached different conclusions. Adoption was being reported as installs, retention as a single blended percentage, and referral as a count of invites sent. None of those measures told anyone what to do differently on Monday.

03

The thinking

  • Separate registration, install, sign in, and active use. They are four different problems with four different owners.
  • Read retention as weekly cohorts. An average hides the fact that one cohort collapsed and another held.
  • Instrument growth as a loop with stages, not as a single number. Invites sent means nothing without activation and conversion behind it.
  • Watch which screens people actually use. The event mix tells you what the product is for, which is often not what it was designed for.
  • Compare against a known standard. Telling an account they are at a certain usage rate is information. Telling them the standard is higher, and here is the plan to close it, is a decision.
  • Time-bound campaigns and challenges are the cleanest natural experiments available. Measure them properly and they answer questions no dashboard will.
04

What was created

  1. 01

    An adoption funnel definition

    A shared set of stages from registered through weekly active, applied identically across accounts so results were comparable.

  2. 02

    A cohort retention read

    Weekly joining cohorts tracked across their first several weeks, replacing a single blended retention figure.

  3. 03

    A growth loop model

    Referral and trial pass activity measured as a staged loop from invite through activation, visit, and conversion, with an owner at each stage.

  4. 04

    An engagement program read

    Challenges, campaigns, and notification activity evaluated on participation and follow-through rather than on send volume.

  5. 05

    A recommendation set per account

    Each analysis closed with specific moves: signage, staff training, notification cadence, or program design, matched to whichever stage of the funnel was actually leaking.

05

Selected artifacts

Figure 01 — Adoption is not engagement
ADOPTION IS NOT ENGAGEMENTRegisteredEveryone on the listDownloadedInstalled the thingSigned inCleared setupActive in periodThe honest numberActive weeklyHabit formingREPORT THE NARROW END. THE WIDE END FLATTERS EVERYONE AND CHANGES NOTHING.
The stages that get conflated. Reporting the narrow end changes behavior. Reporting the wide end changes nothing.

Shared framework · The same structure also supports Product & Dashboard Training.

Figure 02 — Retention by cohort
WEEKLY COHORTS · WEEK 0 THROUGH WEEK 5W0W1W2W3W4W5Cohort 1Cohort 2Cohort 3Cohort 4Cohort 5Cohort 6SHAPE IS ILLUSTRATIVE. THE POINT IS READING DECAY BY COHORT, NOT ONE AVERAGE.
Weekly cohorts read across their first weeks. Shape is illustrative. The method is the point.
Figure 03 — Referral as a measured loop
REFERRAL AS A MEASURED LOOPInvite sentPass createdPass activatedVisitedConvertedA converted member becomes the next inviterEVERY STAGE HAS AN OWNER. A LOOP WITH NO OWNER IS A CAMPAIGN.
Each stage has an owner. A loop without owners is a campaign that runs once.
06

Key decisions

  1. 01

    Report the usage rate, always

    It was the least flattering number available and the only one that consistently produced action.

  2. 02

    Attribute the gap to a stage

    Saying engagement is low is a complaint. Saying sign-in completion is where the drop happens is an assignment.

07

What it informed

  • Gave a portfolio of accounts a comparable read on performance rather than account-specific storytelling.
  • Shifted conversations from install counts to habit formation.
  • Directly shaped the later customer health work, which is the same idea applied to individual customers instead of populations.
08

Reflection

Reading behavior at population scale taught me most of what I later applied to individual customer health. The mistake I made early was presenting more analysis when an account resisted a conclusion. More analysis rarely wins that argument. A single clear stage-level gap, with an owner, usually does.

See the same thinking applied to individual customers
Creating Customer Health & Retention Visibility →
09

Related work