Skip to lesson
Exit
Enterprise Rollout & Adoption Playbook1 / 3

1 min lesson

Train on real repositories and real tasks

Say what this means in practice: "Training that uses a sample project teaches a skill that evaporates the moment the engineer opens their actual work."

Step 1 of 3

Train on real repositories and real taskstransfer beats theory

Training that uses a sample project teaches a skill that evaporates the moment the engineer opens their actual work. Anchor every session in the customer's repositories and the team's live backlog, so what they learn transfers to Monday morning with zero translation.

Learn more

Full explanation

Pair enablement with measurement

Pair enablement with measurementconfirm behavior actually changed

A session attended is not a habit formed. Close the loop: after a team is trained, check whether their activation and usage depth actually moved over the next two weeks. If they didn't, the training failed regardless of how good the room felt.

  1. 1Baseline the team's usage before the session so you have a before.
  2. 2Run the tiered session on their repo and live tasks.
  3. 3Watch the two-week window for a real lift in weekly-active and agent/Tab usage.
  4. 4Re-intervene if flat. No lift means a wrong path, a missing champion or an unresolved blocker - diagnose, don't repeat the same session louder.
Trained is not adopted

Always verify that a trained team's numbers moved. The fastest way to fool yourself in this role is to count enablement sessions delivered as if they were adoption. The only proof is a usage curve that bent upward in the weeks after.

Learn more

Optional practice

Practice: Train on real repositories and real tasks

QYou ran a polished enablement session and the room loved it. Two weeks later the team's weekly-active usage is flat. What does this tell you and what do you do?