When I plan a workshop, I try to think beyond the moment when a demonstration works. I want to know whether a colleague will be able to use the approach again in their own setting.
That question connects my work with teachers in international schools, my autism advisory experience and my current staff development at Queen’s University Belfast.
Begin with something people recognise
A specific task gives people a reason to try a tool and a basis for judging the result. In the October 2026 Copilot in 30 flashcards session, the work connected learning material with recall activities and an interactive HTML resource.
The useful discussion is about the choices: what to include, what to check, how the output fits the learner and when to change the approach.
Make practice part of the session
People need time to try, make mistakes and ask questions. A good question can reveal that an instruction is unclear, an assumed permission is missing or a workflow creates too many steps.
Those observations belong in the design of the support. A reusable guide should reflect the difficulties people actually encounter.
Keep a route back
A workshop is one point in a longer process. Colleagues need guidance they can revisit and a clear place to ask for help. At Manila, teacher coaching, parent engagement and staff clinics were part of that work. At Queen’s, workshops sit alongside individual support and published resources.
Ask what changed
Attendance tells us that someone came. A completed task can show what they did during a supported session. Neither automatically tells us what they can do independently later.
I want follow-up to focus on that practical use: whether someone could repeat the approach, what barriers remained and whether it was worth their time. Those are questions to investigate, rather than outcomes to assume.
Read more about my staff learning work or explore the presentation resources.