Why login volume is a poor proxy for platform adoption

Platform teams often inherit a single chart: users who signed in this week. It feels reassuring until someone asks whether the new billing module, the API console, or the shared workflow engine is earning its keep.

Adoption needs a narrower definition. Pick the first meaningful action inside each module—creating a resource, connecting an integration, publishing a workflow—and measure how many eligible users reach it within a fixed window after access is granted. Separately track return use at seven and thirty days. Those two numbers tell you more than a rising login curve.

For multi-tenant platforms, slice by tenant maturity. A brand-new workspace that never opens advanced modules is expected; a two-year tenant still living in one surface is a product and enablement problem. Login volume hides both stories.

Start with five modules max. Instrument those thoroughly before expanding the dictionary. Broad, shallow tagging produces dashboards nobody trusts.