How I work
On your examples. On anonymised data. No slide-only sessions. On the tools you already pay for. With support after the workshop.
Six principles for a training
- On your examples. The exercises come from the participant survey, not from my drawer. Everyone leaves with 2–3 of their own tasks that they now do faster.
- On anonymised data. We work on real documents without real personal data. I teach anonymisation because it is a daily habit, not a workshop trick.
- No slide-only sessions. There are a dozen or so slides; the rest is work at the keyboard. I move between desks.
- On the tools you already pay for. Claude, ChatGPT, Copilot, Gemini. I do not sell licences or a platform. I say what I would choose and why.
- With the habit of checking. Every exercise ends with the question: how do you know this is true? That matters more than any prompting technique.
- With support after the workshop. 30 days of questions by email, a session after a month and, if needed, building what ended up on the list.
Principles from my developer work that apply here too
- On what you have. I do not rebuild systems from scratch. I fix and extend what works.
- In small steps. Every change checked, with a backup and a way back.
- On a separate account. Named access, only to what is needed. Handed back at the end.
- In plain language. Options with pros and cons instead of one right answer. No jargon unless you want it.
- For time worked. Single jobs, blocks of hours or ongoing support. Quoted per case.
- With notes. I write down what I did and why, so the next person does not start from zero.
These are the principles I work by on clients’ systems. For training they mean: I do not make you switch tools, I take access to data only when the workshop requires it and hand it back afterwards, and the training leaves behind notes, not just an impression.
Data safety during a training
Files
Participants prepare anonymised files following the instructions I send before the training. I do not take the files away with me.
Accounts
We practise on the participants’ own accounts, ideally business ones. If there are none, on test accounts that can be deleted after the workshop.
Access to systems
Only for a workshop on company data: a separate read-only account, sensitive fields excluded, a query log. Switched off after the workshop.
Confidentiality
A confidentiality agreement on request, before I receive any materials. A data processing agreement where the GDPR requires one.
What happens in the week after the training
Materials
Within two business days: prompts for the department, the rules, the list of ideas, the certificates.
First attempts
Participants use AI on the tasks from the workshop. Questions come by email; I reply within a business day.
The list of ideas goes to management
A decision on which “yourselves” items the team takes on straight away, and which “needs a developer” items are worth quoting.
A session after a month
Two hours online: what worked, what did not, what to adjust in the prompts. A decision on whether and what comes next.
A developer or a training company?
For a team that is supposed to start using AI at work, what matters is whether anyone actually works differently afterwards. The rest is detail.
| A developer running the workshop (me) | Training company | Online course | Nothing | |
|---|---|---|---|---|
| What you practise on | Your own tasks from the survey, in your own tools | The trainer’s examples, often the same for every client | The examples in the recording | — |
| Company data and safety | Usage rules ready for management to adopt, anonymisation done live | Usually one slide on GDPR | Usually skipped | Everyone does their own thing on a personal account |
| Reporting and connecting to data | SQL, formulas, MCP, a recurring report: I show it because I do it | Rarely; the trainer is usually not a developer | No | — |
| After the session | 30 days of questions by email, a session after a month, a list of things to build | A feedback form and a certificate | Access to the recording | The tool sits idle, the licence keeps billing |
| Building what came out of the workshop | I can do it myself: a report, an integration, AI in the CRM | You need to find a contractor | You need to find a contractor | — |
| Group size | Up to 12, everyone works on their own tasks | Varies; 30 in a room is common | Unlimited, no contact | — |
Questions about working together
Do we sign a contract?
Yes, a short one: programme, date, headcount, confidentiality, cancellation terms. For a workshop on company data, access rules as well.
How do we pay?
A VAT invoice after the training; for longer series, a deposit before the start. Quoted after a call, depending on format and headcount.
What if the training does not work?
I say so plainly at the session after a month, not in a feedback form at the end of the day. If the team is not using AI after a month, we look for the cause: usually a missing task or a missing business account, not missing knowledge.
Do you run training in English?
Yes, for international teams. I work in English every day for a company in Sweden.
What if we want to build something after the training?
I quote and build it as AI implementation or, for Salesforce, as part of Salesforce support. You can also take it to someone else; the list from the workshop is yours.
Your staff already use AI. Let’s teach them to do it well and safely.
Tell me the department and the headcount. I reply within one business day with a proposed programme.