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.4 · 12 min
Training Your Team in 30 Days
Run a practical 30-day internal training plan built around real work, not theory.
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.
1Week 1: set up and first win
Install Claude Code, add the company marketplace and install the plugin. Each person completes one real task with one proven skill on day two, not day ten. The first win must happen fast, while motivation is high.
2Week 2: their own work
Each person picks two recurring tasks from their own week and runs them through the plugin skills. Hold a 20 minute check-in on Friday to share what worked and what broke. Collect every issue for the Builder.
3Week 3: habits and verification
Teach the verification habit: check outputs against the source, use plan mode (Shift+Tab) for bigger tasks, and use /clear between unrelated jobs. Pair a confident user with a hesitant one for two sessions.
I am training my team on our acme-ops plugin. Using the skills in the plugin and the tasks listed below for each role, create a 30-day training plan with 15 minutes of practice per day. Every day must use a real task from that person's job, name the skill to use, and say what good output looks like. Add a Friday check-in agenda for each week.4Week 4: contribute back
Each person suggests one improvement to a skill or one new use case, using the prioritization sheet from Module 12. The Builder ships the best two as a new plugin version. When people see their idea in the tool, they own it.
5Certify simply
At day 30, each person demonstrates two tasks end to end, including verification, to their manager. No exam, just real work done safely. Record who passed in the adoption scorecard.
Most AI training is a two-hour webinar followed by nothing. People nod, go back to their desks, and do the work the old way because the old way is familiar and Friday is busy.
People learn tools by using them on their own tasks with someone nearby to help. Thirty days, fifteen minutes a day, on real work, beats any workshop.
Key points
- First win by day two, on a real task.
- Fifteen minutes a day on real work beats a long workshop.
- Friday check-ins collect issues and share wins.
- People who improve a skill become its champions.
Avoid
- Training on generic examples instead of the person's actual job.
- Running one big session and calling it done.
- Skipping verification training, which leads to the first embarrassing error.
- Ignoring suggestions from the team, which kills ownership.
A roofing contractor trained its office team of five over 30 days: the estimator on quotes, the scheduler on crew plans and the office manager on supplier chasing. Each did 15 minutes a day on live jobs. By week four, the scheduler suggested a weather-check step for the crew planning skill, which the Builder added. That idea alone prevented two wasted crew call-outs the following month.