Teams sometimes delay an assessment until instrumentation feels perfect. That wait is rarely necessary. What helps most is a bounded export: a few weeks of events or session summaries for the surfaces under review, with personal identifiers removed and role labels retained where possible.
Include a short glossary. Event names that made sense to the engineer who added them six releases ago may not survive a new reader. A one-page dictionary—name, meaning, when it fires—cuts days of back-and-forth.
Add qualitative anchors: five recent support threads, a list of features leadership considers strategic, and any known outages in the window. Utilization patterns during an incident week look different from ordinary weeks; labeling those days prevents false conclusions.
If exports are thin, say so early. An instrumentation readiness audit can run first, then a full feature utilization assessment once the signal is trustworthy. Sequencing the work honestly is better than pretending sparse logs can answer precise adoption questions.