Use caseImprove onboarding
Hear new customers describe their first weeks, with the admin who set things up and the people meant to use the product each interviewed apart, and give customer success a watch list of the snags that stall accounts.
Onboarding is promised in the sales conversation and delivered by the product, and the first weeks show whether the two matched.
Choose accounts that signed recently, some that reached first value and some that stalled, so the study can set the paths side by side and see which steps separate a settled account from a drifting one.
The admin who configured the product and the colleagues expected to use it get separate interviews, since each meets different steps, and an account only settles when both groups get somewhere.
Customers describe what they thought would happen after signing, drawn from the sales conversation, the website and the kickoff call, which exposes the gap between what was promised and what the first week delivered.
The world's most ambitious teams research with Pulse.
GrowwA snag costs most when nobody notices it until renewal, so the output is arranged around when a snag appears and who can clear it.
The problems customers described are grouped by the week they hit them, from connecting data in week one to inviting colleagues in week three, each group with the quotes that describe it.
Every interview is available as a transcript and a recording, so the admin's interview and a user's interview from the same account can be read one after the other to see what would have got both to value sooner.
The snags that stalled accounts become signals customer success watches for in new ones, such as an admin who has invited nobody by the second week, with the help that worked written beside each.
Between signing and first value, the point often called activation, a new account either settles or drifts, and that stretch is where onboarding work concentrates. Product analytics show where new accounts stop moving, and interviews explain why. Talking to recent customers, some who reached value and some who stalled, reconstructs what they tried, what confused them and what they expected from the sales process. For business products several roles are involved, from the admin who configures the product to the colleagues who must adopt it, and each meets different obstacles, so they are best heard separately. Diary studies can follow a cohort through its first weeks and catch moments a single interview would miss. Programs that improve activation define the event that counts as first value and measure the share of accounts reaching it. Usability testing then takes the setup screens that new admins named most often and checks each one before the next cohort signs up.
Accounts onboarded by an implementation partner and those set up by the company's own team take different paths. One study recruits the two as separate groups, each screened for the way its account was set up, so the partner manager sees whether partner-led accounts stall at different steps.
New admins often mention the help article or training video they tried before asking for help. Reading the transcripts for those mentions shows the education team which content new admins open, and which sent them the wrong way.
Accounts below a size threshold get no named success manager and onboard alone. Recruited from that segment of the customer list, they point the product team to the steps a self-serve account cannot get past without a person.