Adoption map
A working view of how cloud application adoption actually unfolds — the layers we measure so programmes stop confusing licences with use.
Provisioned access
Identity directories and licence exports show who can enter each cloud application. This layer is necessary — and incomplete. We treat it as the outer ring of the adoption map, never the destination.
First activation
Activation is the first authenticated session that crosses a meaningful threshold — not a password reset. We align activation events with departmental cohorts so silent non-starts become visible early.
First value
First value is the earliest completed job the application was bought for: a synced file, a closed ticket, a submitted report. Without this marker, uptake and readiness metrics invent success later.
Return use
Return visits and recurring workflow completions separate curiosity from habit. We band return use by week and by team so enablement can target dormancy with evidence, not slogans.
Departmental readiness
For migrations and suite expansions, we roll cohorts into readiness bands: trained, dual-running, blocked by integration, or ready to cut over. Steering committees get a map, not a status colour.