Service model
Pattern atlas
A shared language for the ways people move through your tools—so debates start from observed sequences, not slides about intended journeys.
-
Dormant tools
Features that ship with banners and zero returning sessions. Often an event never fired—or the entry point sits behind a permission users decline. Inventory first; redesign second.
-
Single-shot tools
Opened once during onboarding, never again. Healthy for setup wizards; unhealthy for core editors. Adoption Cohort Study separates intentional one-time use from forgotten panels.
-
Weekly sequences
Edit → export → share, or template → connector → publish. When a middle step goes silent after a release, charts invent abandon that product never caused. Pattern Diagnostic walks the path on device.
-
Plan-gated clusters
Tools only free-tier users never see—or only enterprise admins touch. Measuring them without plan properties mixes audiences and invents false adoption gaps.
-
Cross-device handoffs
Start on web, finish on mobile. Identity resets make completers look like new abandoners. We check stitching rules before blaming the toolbar.
Ready to map your tools?
Most teams begin with a Tool Usage Inventory. If one sequence already argues with reality, tell us which path and we will suggest a Pattern Diagnostic instead.