Reporting to the Team

The rollout team needs operational data: adoption by segment, blocker list, champion activity, support ticket volume, and training gap indicators. Not the transformation scorecard — that is the sponsor's document. Not the board slide — that is the governance document. The team dashboard is the operational intelligence tool that tells the rollout team where to direct their attention this week. It should surface the right signals at the right frequency without creating reporting overhead that takes the team away from doing the work.

1. Adoption by Segment Break adoption data down by team, region, role, and cohort. The aggregate adoption rate tells the team very little. Adoption by segment tells them where the initiative is ahead of plan (amplify and learn), where it is behind (investigate and intervene), and whether the pattern of behind-plan performance points to a systemic issue or an isolated one.
2. Blocker List A living list of active blockers: what the blocker is, who owns resolving it, what is needed to resolve it, and how long it has been open. Blockers that have been open for more than two weeks without progress are candidates for sponsor escalation. The blocker list makes the initiative's friction visible and creates accountability for resolution.
3. Champion Activity Which champions are active (supporting peer questions, attended last champion sync, visible in the adoption data of their teams) and which are inactive. Champion inactivity is a leading indicator of the adoption problem that will appear in their teams two to four weeks later. The team dashboard should surface inactive champions weekly so the rollout lead can re-engage them before the adoption gap appears.