Claude training for 400+ employees at a regulated components manufacturer.

What was the challenge?

The manufacturer was rolling Claude out to staff with widely different starting points. Some had never written a prompt; others were ready for technical tools. The company needed one program that could take a first-time user to safe, confident everyday use, and give more technical staff a path beyond that — structured as a progression, with each course building on the one before it, rather than three disconnected sessions.

What constraints shaped the program?

The company makes specialized components for customers in regulated markets, including government-related work. Export-control and controlled-data requirements set a hard boundary: CUI, ITAR, and EAR material never goes into Claude.

The training also had to run in two modes at once: live sessions people attended, and self-paced material hosted on the company’s own SharePoint and Stream environment that learners could revisit between sessions. And it had to teach client-approved data handling and output verification as habits, not as a disclaimer at the end.

What did I design and deliver?

117 hours of live instruction in one month: Beginner, Intermediate, and Advanced courses, each offered multiple times a day, 4 days a week, in 2-week cycles.

• Self-paced materials alongside the live delivery: narrated video produced for SharePoint and Stream, so staff could watch, pause, and revisit material inside the company’s own environment.
• Supporting documentation for each video, simulation, and training course.
• Scenario-based knowledge checks in every session: realistic workplace situations where the learner decides what to do, then sees what good looks like.
• Simulations pairing a learner action with an expected Claude response, so people build an accurate picture of how Claude behaves, including when its output needs human review.
• Provisional reporting on participation, attendance, and exercises while the live delivery ran, so the client had visibility during the month rather than only at the end.
• Synthetic examples throughout. Every prompt, document, and exercise was invented for training, so learners practiced real decisions without using real or controlled data.

What did the curriculum cover?

Each level built on the one before it, combining live instruction, guided practice, simulations, and on-demand resources.

What were the results?

These figures are reported from the training data and attendance for this program.

Confidence reflects what participants reported. For a new rollout I pair that measure with a scenario assessment, so leaders can see what people can do independently, not only how they feel.

What came after: the 90-day readout and Phase 2

Training that ends at delivery leaves adoption to chance. I prepared a 90-day readout with Phase 2 recommendations: a structured review of how the program landed, what learners still needed, and what the next phase of enablement should cover. It gave the client a decision point after the first phase — what to extend, what to adjust, and where to go deeper — instead of a one-off event with no next step.

What can you copy for your own rollout?

• Set the data boundary with IT and Security before the first session.
• Teach in levels so every learner starts at the right place.
• Use scenario checks instead of quizzes to practice judgment.
• Give people self-paced video and reference documents they can use mid-task.
• Use only synthetic examples in training.
• Plan the readout and the next phase before delivery ends.