Pattern atlas
Usage pattern analysis for SaaS apps is the core of app analytics at this desk. The atlas is the artefact: twenty or fewer labelled paths, each with a grain, a quiet-week note, and an owner.
Every journey in the atlas has a name a PM can say out loud, a start trigger, an end condition, and the grain (tenant, seat, or session). If you cannot say who the actor is, it is not a path yet.
We also record one counter-example: the similar-looking clickstream that is actually a tourist, a shared login, or a tooltip experiment.
Composite “health scores,” unexplained clusters, and n-gram dumps longer than a page. Those objects impress a slide and fail a hallway conversation.
If a journey only appears during a campaign week, it goes in an appendix, not the living atlas.
The events on the card must exist in the contract. Unnamed clicks do not get a path. This is slow on purpose.
Each card notes what silence looks like between day 8 and 14. Silence that still pays is not treated as failure.
We write where pattern work ends. If the product has no reason to return, the atlas shows an empty room. That is the finding.
Sequence Atlas is where you build your first library. If you already know the question is gravity or silence, start with a short desk instead.