This lesson is being recorded
Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.
Bruno Ashford @brunoashfordSubscribeModule 13 · Lesson 13.5 · 10 min
Measuring Adoption
Track usage, results and resistance with a simple weekly scorecard.
Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.
1Track usage per person
Record how many times per week each person runs a company skill or routine. Self-reporting in a two-minute Friday form is fine for a small team. If you use a Team or Enterprise plan, check what usage information your admin console provides.
2Track results per person
Record tasks completed with AI and estimated hours saved, using the same method as Module 12. Usage without results means the skill does not fit the work, which is a Builder problem, not a people problem.
3Track friction and sentiment
Ask two questions every Friday: what slowed you down this week, and how confident do you feel with the tools from 1 to 5. Low confidence with high usage means someone needs pairing. Low usage with high confidence means the tools do not match their tasks.
Here is this week's adoption scorecard (CSV below). Summarize it for me in five lines: overall adoption rate, total hours saved, the two people who need support and why, the most common friction point, and one change to the plugin or training that would help most next week.4Set simple targets
By day 30: at least 80 percent of the rollout group using a skill three or more times a week, average confidence of 3.5 or higher, and rework under 15 percent. These are starting targets, adjust them to your business after the first month.
5Act on the data weekly
Every Monday, pick one action from the scorecard: pair someone, fix a skill, or remove a friction point. Adoption improves through small weekly fixes, not through reminders to "please use the AI".
You cannot manage what you only feel. "People seem to like it" is not a metric. Some of your team will use the tools daily, some weekly, and some will quietly never open them. You need to know which, kindly and early.
Adoption has three layers: are people using it, is it producing results, and what is blocking the rest. A one-page weekly scorecard covers all three.
Key points
- Measure usage, results and friction every week.
- Low usage is usually a fit problem, not a people problem.
- Confidence scores tell you who needs pairing.
- One concrete action per week beats constant reminders.
Avoid
- Using the scorecard to shame people instead of to help them.
- Tracking usage without results.
- Setting targets so high the team games the numbers.
- Collecting data and never acting on it.
An online store rolled its customer service skills out to six agents. The scorecard showed two agents with near zero usage but high confidence. A quick chat revealed they handled wholesale orders, which the skills did not cover. The Builder added a wholesale reply skill, and both agents became the heaviest users within two weeks.