AI Training and Workforce Enablement
Role specific AI training built on your own tools and policies, with practical exercises rather than a lecture.
Generic AI training produces a room of people who can define a large language model and cannot use one competently on Monday. The gap is not conceptual. It is that the training used somebody else's examples, somebody else's tools, and ignored the policy constraints the attendees actually work under.
Tracks by role
| Track | Audience | Focus |
|---|---|---|
| Executive | Board, C-suite, senior leadership | Where value is real and where it is not, what governance obligations attach, how to read a vendor claim, how to interrogate a business case. Half day. |
| Practitioner | Analysts, marketers, operations, support | Daily use inside approved tools. Prompt structure, verification habits, what must never be pasted into a model, and where the policy line sits. One to two days. |
| Engineering | Developers, data and platform engineers | Retrieval design, evaluation harnesses, agent patterns, tool calling, cost control, failure handling. Three to five days, hands on. |
| Legal and risk | Legal, compliance, risk, procurement | EU AI Act classification, data protection interaction, vendor contract terms, what to ask before approving a system. One day. |
| Product | Product managers, designers | Scoping AI features, writing acceptance criteria for probabilistic systems, human in the loop design, managing user expectations. Two days. |
Built on your material
Every exercise uses your documents, your systems and your policies. If your organisation has approved one assistant and prohibits others, the training teaches the approved one and explains the prohibition rather than pretending the constraint does not exist. If your data classification rules forbid certain content leaving your tenancy, that rule is the spine of the practitioner session rather than a footnote.
Preparation takes one to two weeks before delivery. We review your policies, collect representative work samples, and adapt exercises. Sessions delivered without this step are noticeably worse and we do not offer them.
Format and retention
Sessions are majority hands on. Attendees work on their own tasks with support in the room rather than watching a demonstration. Cohorts are capped at sixteen for practitioner and engineering tracks, because beyond that number the practical portion stops functioning.
Retention is the weak point of all corporate training, so each programme ends with material that survives the session: a short internal reference written for your context, a set of worked examples using your data, and a suggested follow-up structure. We recommend a shorter reinforcement session six to eight weeks later, when real questions have surfaced.
Programme option
For larger rollouts we run a six week programme rather than isolated sessions: a baseline skills assessment, weekly cohort sessions, practical assignments drawn from live work, an internal champions group, and a closing measurement against the baseline. This costs more and works considerably better than a single day for everyone.
We will tell you if training is not the answer
When adoption is failing because the tool does not fit the workflow, or because nobody removed the old process, training will not fix it. That is a change management problem and more sessions make it worse by adding frustration to confusion.
Output
Delivered sessions, exercises, internal reference material. Delivered in editable formats. Full IP transfers to you on final payment.
FAQ
Can training be delivered remotely?
Yes, with cohorts capped lower, around twelve, and sessions split into shorter blocks. Engineering tracks work well remotely. Executive sessions consistently work better in person, largely because the valuable part is the unguarded discussion.
Do you certify attendees?
We issue a completion record and, for the engineering track, an assessed exercise. We do not offer a certification with an accreditation claim behind it, because we are not an accrediting body and pretending otherwise would be dishonest.
How do you handle attendees at very different skill levels?
A short pre-assessment before the cohort is formed, then grouping by level. Mixing a first time user with an experienced practitioner in the same hands on session serves neither of them.
Can you train our team on a system you built for us?
Yes, and handover training is included in build engagements rather than sold separately. This service covers broader capability building beyond a single system.
Often paired with
AI Adoption and Change Management
The organisational side of an AI rollout, from workflow redesign to communication and measured adoption.
Read moreAI Center of Excellence Setup
Design and launch an internal AI function with a working operating model, not an org chart and a mission statement.
Read moreFractional Chief AI Officer
Senior AI leadership on retainer, typically two to four days a month, for organisations not ready to hire a full time executive.
Read moreIs this the right engagement?
Tell us what you are trying to decide. If a different service fits better, or if you do not need us at all, we will say so.