Training and enablement
Hands-on AI enablement for the teams who do the work
A rollout without enablement is a licence bill. Team enablement is practical, function by function, on the tools you have rolled out and the recurring tasks in that function, measured by time saved on real work rather than attendance.
Built around each function's own tasks
Generic AI training does not change behaviour, because nobody's job is generic. Enablement starts by sampling the recurring work in a function: the reports, the drafts, the searches, the summaries, the data reformatting, the correspondence. We configure the assistants and skills for those tasks, then run hands-on sessions where people do their own work with the tools, in the data rules of your policy, and leave with a set of working patterns rather than a slide deck.
Where discovery has run first, the sampling is already done: the divergent workshops captured exactly where each function's time goes.
Three building blocks
Function sessions
Half a day per function, on its own tasks, with its own configured assistants. Typically sales and service, marketing, procurement, operations, finance and engineering, in whatever order the rollout reaches them.
Policy and acceptable use
A short, mandatory session for everyone with access: what may be shared with which tool, how to check AI output, how to recognise and report a problem. The gate before access is opened, and the training the EU AI Act requires.
Champions and follow-up
A champion in each function, a thirty-day review of what is being used and what is not, and a second session on what the first one surfaced.
Time saved on sampled tasks, not seats filled
Before enablement we time a sample of the function's recurring tasks; after it, we time them again, with the tools. That number, alongside usage by role from the platform and the feedback from champions, is what tells you whether the rollout is working and where the next session should go. It is also the number that justifies the licences.
About team enablement
Which tools do you train on?
Whichever you have rolled out: Claude, Microsoft 365 Copilot, ChatGPT Enterprise, and the custom GPTs, skills and projects we configure for each function. For engineers, Claude Code and GitHub Copilot under developer enablement.
Can you use our own documents?
Yes, and we should, within your data classification and policy. Sessions on your own work are what make the patterns stick.
How long does enablement take across a business?
It follows the rollout: usually one function every two to three weeks, so a five-function business is enabled within a quarter, with the policy session first for everyone.
Is the policy session enough for the EU AI Act?
It covers the acceptable-use and literacy basics the Act expects for staff using AI systems; roles with higher-risk uses get additional, specific training in scope.
Make the rollout pay
Enablement is the difference between a licence and a change in how people work.