Remote workshops need shorter blocks, smaller groups, labs tested on attendees' own machines in advance, and a second person watching the chat. Keep talks under ten minutes, put people in pairs for the hands-on work, and plan for the stuck few before the session starts.
Why remote is different
In a room you can see who is lost. On video you cannot, and a silent participant may be stuck, distracted or gone. Setup problems also multiply, since every laptop is different. The fix is structure: frequent small checkpoints and a way to ask for help without speaking up in front of everyone.
Before the session
- Send setup instructions a week ahead, and ask everyone to run a smoke test that prints a success message.
- Offer a hosted fallback for people whose machines fail. If it is a shared environment, keep it isolated, as in our lab safety guide.
- Share a single document with the agenda, lab links, hints and a place for questions.
- Cap the group. About 12 people per facilitator is a workable limit when labs are hands-on.
During the session
Short blocks. Alternate talk and lab in chunks of ten and twenty-five minutes. Long lectures on video lose people quickly.
Pairs in breakout rooms. Two people can talk through a problem, and shy attendees speak more easily. Drop in to each room and leave a short hint card in the shared document.
A chat helper. Assign a second facilitator to answer questions in the chat, so the lead can keep going. Ask people to type "stuck" with the step number.
Checkpoint polls. After each lab step, ask for a thumbs up or a number: "Who has reproduced the exploit?" Use the answers to decide whether to wait.
Camera norms. Make cameras optional but encourage them for pairs. Share screens during labs so the partner can follow.
Handling the stuck few
Have a one-to-one breakout room with a facilitator open throughout. Offer to pair a stuck attendee with someone who finished. Keep the tone relaxed, since people who feel judged hide.
Time zones and recordings
If the team spans regions, run the same workshop twice rather than at an awkward hour. Record only the framing and debrief, not labs where people may type credentials by mistake. Provide the lab for self-paced replay.
Closing
Ask each person to write their one commitment in the shared document. Send the list within a day, with links to redo the lab. For the agenda, see the 90-minute workshop plan, and stretch breaks if you run over a longer window.
Quick check
How long can a remote workshop be?
Keep sessions to about two hours with a break. For longer topics, split into two sessions on different days.
What if someone cannot run the lab locally?
Provide an isolated hosted instance or pair them with a participant who has it working.
Last reviewed: 19 October 2026.
