AI training for business teams and managers.

The usual shape: a morning of slides, a few demos, examples from somebody else's industry — afterwards everyone carries on as before, because nobody built the bridge to their own work.

The difference is not the tool, it is the material: someone working on their own quote and their own meeting notes leaves with something that is still true the next day. So you bring the tasks.

For the people who work with text, documents and decisions all day: administration, assistants, sales, project management, leadership — in other words most of a company, not the IT department.

Developers are explicitly not the audience: in a mixed group half the room is bored while the other half is left behind.

• Workshops for business teams, assistants and leadership
• Exercises on your own work, not on sample data
• Clear rules about what may go in and what may not
• Follow-up until it sticks in day-to-day work

Since February 2025 the EU AI Act expects companies that use AI to make sure their people have a sufficient level of AI literacy — Article 4, if you want to look it up. What "sufficient" means is not prescribed: no mandatory certificate, no fixed format, no authority collecting attendance lists.

So anyone threatening you with fines for missing training is exaggerating. The obligation is still a good occasion: a workshop that works on real tasks and settles the data rules covers it along the way — documented, too. A click-through course covers it formally as well; it just changes nothing about how anyone works the next day.

A round runs half a day to a full day, and the lecture portion is deliberately small: a brief, honest framing of what tools like ChatGPT, Microsoft Copilot or Claude do well and where they reliably fall over. We work with the tools you have and are allowed to keep — not with whichever one has the best advertising right now.

The rest is work on your own cases — the quote that looks much the same every week, the meeting notes nobody enjoys writing. We keep going until the output is good enough for real use, not just until the demo worked. You leave with a short page written together, which goes up in the team afterwards.

The most important half hour is the one about data: what may be typed into a tool that runs outside the company, and what absolutely may not?

Without clear rules, either nobody uses the tools for fear of getting it wrong, or everybody uses them without thinking about it. Both are worse than a line that fits on one page.

The weeks after a workshop are where most of the value leaks away. It helps if someone follows up: what made it into daily work, and where is it stuck?

Often that reveals that some of the daily handwork could be automated properly, once. At which point the training turns into an automation question — and the other way round.