What a good workshop day actually looks like, hour by hour

Here is roughly how we run a one-day, hands-on workshop. The shape matters more than the exact timings.

9:00 – 9:20 · Why we’re here

Context, not content. Where this skill fits, what good looks like, what people will be able to do by the end. Short. If it runs past twenty minutes, we’ve turned it into a lecture.

9:20 – 10:30 · First skill, then practice

We demo one thing briefly, then everyone tries it on their own work. The trainer moves around the room. This is the pattern for the whole day: small input, then hands on keyboards.

10:30 – 10:45 · Break

10:45 – 12:30 · Build the core capability

The main block. Participants work through the real task the course exists for, with the trainer helping individually. We stop once mid-morning to ask what isn’t landing and adjust.

12:30 – 1:30 · Lunch

1:30 – 3:30 · Apply it to something harder

Now people take what they’ve learned and use it on a messier, more realistic version of their own work. Fewer instructions, more problem-solving.

3:30 – 3:45 · Break

3:45 – 4:30 · Monday

Not a recap. Each person writes down what they’ll do differently next week, what they need to make that happen, and who will check in with them. We collect these so the follow-up two weeks later has something to reference.

The principle

Front-load the “why”, then get out of the way. The day belongs to the participants doing the work, not the trainer performing.