Guide

What does ‘hands-on’ actually mean in AI training?

"Hands-on" in AI training covers four different things: watching a live demo, following a guided exercise, building against a set brief, and building against your own real task. Only the last one reliably changes how you work afterwards. The test is simple - ask what you will personally have running at the end.

Nearly every AI course now describes itself as hands-on, practical or applied. The word has stretched to cover four quite different experiences, and the difference between them is the difference between a good day out and a changed working week.

The four things “hands-on” can mean

1. Watching a live demonstration. Someone builds something in front of you. Genuinely useful for seeing what is possible - and it is still a talk. Your hands are not on anything.

2. Following a guided exercise. You type along with an instructor towards a known destination, usually on prepared material. You finish with the instructor’s example, built through your keyboard. Better; the friction is real but the problem is borrowed.

3. Building against a set brief. You work on a case or a sample dataset with support in the room. Real building, real decisions - but when you get home, the transfer is still yours to do: your work does not look like the brief.

4. Building against your own task. You bring a piece of your actual work - the report, the sift, the weekly assembly job - and build the workflow against that. When the day ends there is nothing to transfer, because the thing you built is already about your job.

Each step up costs more facilitation and caps the room size, which is why most large-format training stops at levels one or two. That is an economic choice, not a dishonest one - but it is worth knowing which one you are buying.

Delivery mode is tangled up in it as well, because the upper two levels are harder to run at a distance: when someone is stuck, the fix is a person walking over. That is the case for doing this in a room.

Three questions that settle it

Course pages rarely say which level they mean, so ask directly:

  • What will I personally have running at the end? The honest answers range from “notes and ideas” to “a working workflow against your own task”. Both are legitimate products; they are different products.
  • Whose problem do I work on? A demo, a script, a case study, or my own work.
  • What happens when I get stuck? A forum, office hours, or a person who walks over. The answer predicts whether you finish.

The checklists you will find elsewhere are written for online courses

Search for how to tell whether a course is genuinely hands-on and most of the advice you will find is built for self-paced video: look for executable notebooks, a GitHub repository, graded projects rather than quizzes, a capstone, a syllabus that lists deliverables, a recent content-update date. All sensible. None of it tells you anything about a day in a room, because a day in a room has no syllabus page to inspect and no repository to open.

Two signals replace them, and both can be checked before you pay.

What you are asked to bring. A day built around your own work has to ask you for something in advance - a task, a document, an account you can sign into. If nothing is required of you beforehand, your material will not be on the screen, whatever the page says. Level four cannot be arranged on the morning.

Whether anyone has mentioned your laptop. Building means installing or signing into something, and corporate and government devices often block tool sign-ups. A provider who expects you to build has usually hit this before and will warn you; a provider who has not raised it is not planning on you installing anything.

For the rest - how many people are in the room, the ratio of talking to building, what happens when you get stuck - there is a fuller list in nine questions to ask before booking AI training.

Why this matters more for senior people

The more senior you are, the scarcer the day and the higher the cost of a format that ends in intentions. An afternoon of demos can be worthwhile for orientation - once. After that, the only training worth a diary slot is the kind measured by what runs afterwards.

For what it is worth, our own format is built deliberately at level four: the Oxford Agentic Bootcamp caps the room small, asks everyone to bring one real task, and treats “what will you use this for next week?” as the closing question of the day. No coding, and no stretch of anyone talking at you for more than twenty-five minutes.

The Oxford Second Brain Bootcamp sits at the same level for the same reason. You are asked to bring your own documents and notes, and the day is spent building a second brain out of them rather than out of a supplied example, so what exists at the end is yours and already populated. Level four is not a property of the subject. It is a property of whose material is on the screen.