Method
A calm path from release noise to ranked next steps
Engagements follow the same spine whether you book a full Feature Adoption Assessment or a shorter release brief: define success, read evidence, interpret with the people who own the feature, then write what to try next.
1. Scope the feature
We name the feature or release, the accounts that should care, and the repeat behaviour that would count as adoption. Activation and adoption stay separate on purpose.
2. Gather evidence
Usage exports or analytics views, release notes, and support themes from the first weeks after ship. We do not invent metrics that your instrumentation cannot support.
3. Interpret together
Working sessions with product and customer teams turn charts into shared language. Mild disagreement in the room is welcome; the brief records decisions, not consensus theatre.
4. Deliver the brief
You receive a written adoption brief with ranked recommendations, owners suggested where clear, and constraints called out honestly.
What you prepare
Access
Anonymised usage views for the feature, or exports covering reach and return over the agreed window.
People
Time with a product owner and someone close to support or success — usually one hour each at kick-off, plus workshop attendance.
Context
Release notes, intended first-value path, and any known segments (role, plan, region) that should be read separately.
Timing
Features need enough live traffic to observe — typically four weeks for a full assessment, about ten days for a release brief.