Licences purchased are not the same as software adopted
A seat count can look healthy while feature use never crossed the threshold leadership thinks they bought.
On software cloud programmes, procurement tracks seats; product tracks feature flags; analytics tracks sessions. When those three never share a definition of adopted, the programme review invents a story each month.
Before rewriting the rollout plan, walk one wave while watching live events and error rates. Note client-only retries versus confirmed first-use. Check whether staging shares production cohort identifiers.
Rollout Friction Mapping stays narrow on purpose: one window, deep reconciliation, a checklist you can rerun after every wave so the seat-vs-use cliff does not return unnoticed.