Documenting What Made It Work

The playbook is built during the pilot, not after. This is the discipline that most organizations skip because during the pilot, there is no bandwidth to document — everyone is focused on running the pilot. The consequence: at the end of the pilot, the team has results but cannot articulate specifically what produced them. Was it the training approach? The manager who actively reinforced adoption? The workflow design? The specific champion who drove enthusiasm on their team? Documentation during the pilot is the difference between a replicable playbook and a collection of results that cannot be reproduced at scale.

1. Document Champions Weekly For every pilot participant who exhibits champion behavior — voluntary advocacy, extended usage, peer coaching — document: who they are, what role they play, what specifically they did, and what conditions seem to have enabled their behavior. The champion profile built during the pilot is the recruiting tool for the expanded rollout's champion network.
2. Document Training Effectiveness Track which training approaches produced adoption and which did not. Live training for complex features? Asynchronous video for basic usage? Peer coaching for workflow-specific application? The training that worked in the pilot will work in the rollout if it is documented precisely enough to be replicated. "Training seemed effective" is not a replicable finding.
3. Document Objections and Responses Every objection raised during the pilot and every response that addressed it is rollout preparation. The question that came up in week 3 of the pilot will come up in week 1 of the rollout, at 10x the scale. The FAQ built from pilot objections is the change manager's most valuable rollout tool.