Methodology
How an assessment moves from question to readout
This page outlines the rhythm we use for feature utilization and workspace activity work—so you know what happens between kickoff and recommendations.
-
1. Scope the question
We agree on the product surface, the time window, and the utilization questions that must be answered. Out-of-scope surfaces are named explicitly so the matrix stays honest.
-
2. Gather what you already hold
Anonymized exports, event dictionaries, support themes, and role definitions arrive through a shared channel. We do not require production access; read-only extracts are enough for most assessments.
-
3. Analyze reach, depth, and friction
Features are scored for reach and return use, then annotated with friction hypotheses. Idle gaps are interpreted with role context so waits are not mistaken for abandonment.
-
4. Pressure-test with stakeholders
Two working sessions surface disagreements early. Product and engineering can challenge findings before the written report locks.
-
5. Deliver recommendations and readout
You receive a written assessment and a ninety-minute live readout. Recommendations separate promote, simplify, relocate, and retire—with effort notes attached.
What you prepare
A short glossary of events, a list of strategic features, and any known outage days in the window. If measurement is too thin to answer the questions, we may suggest an Instrumentation Readiness Audit first.