Loading…
Loading…
For the people who will run these systems after the build: what a model can and cannot do, how to check it, and what to do the first time it is wrong.
Hand a working system to people who cannot tell when it is wrong and it gets switched off within a year. The handover is the point of the whole engagement, so the training is not an add-on to it.
Sessions run from a day for owners and managers to three days of hands-on work for developers, using your own systems and your own documents throughout.
Book a callWhat these systems do, what they cost to keep running, and how to tell a real use from a good demo. No maths.
Executives, Directors, Managers
1 Day
Hands-on work with the techniques and the tooling, on your own data rather than a tutorial dataset.
Data Scientists, Analysts, Engineers
3 Days
Where language models help, where they quietly make things up, and how to tell the difference on your own material.
Product Teams, Marketers, Designers
2 Days
Building a model into an application you already maintain: the APIs, the failure modes, and tests that catch it drifting.
Software Engineers, Developers
3 Days
The examples are your documents, your call recordings, your job records. Generic exercises do not survive contact with a real week.
Most of the time is spent doing the thing rather than watching slides about it.
Notes to keep, and a follow-up session once people have hit the first thing the course did not cover.
Tell me who needs to know what, and I will put a session together on your own systems.
Book a call