Why we make participants bring their own work

In the joining instructions for most of our courses, there’s a line asking people to bring a real piece of their own work — a report they’re building, a dataset they’re stuck on, a presentation they’re preparing. It’s not optional, and here’s why.

Practice on a demo file doesn’t transfer

When someone learns a technique on the trainer’s tidy example, they’ve learned it in ideal conditions. Their own work is messier: the columns are named strangely, the data has gaps, the requirements keep shifting. The skill they need is applying the technique to that, and the only way to build it is to practise on that, with help in the room.

Engagement takes care of itself

You don’t have to work to keep someone interested in fixing their own problem. The report they’ve been dreading, the spreadsheet that breaks every month — that motivation is already there. Generic exercises have to manufacture it.

People leave with something done

By the end of the day, participants haven’t just learned a skill — they’ve made real progress on an actual task. The report is faster, the dataset is clean, the deck is clearer. That’s a concrete return before anyone applies the skill again.

What we do if someone forgets

We keep a few realistic sample tasks on hand, matched to common roles. They work as a fallback. But the difference in the room between someone on their own work and someone on a sample is obvious within ten minutes.