Running a Workshop at a Developer Conference
Last week I ran a quick video call with some of the amazing humans that are speaking at WordCamp Joburg 2018. It mainly focused on how to run a workshop but these could definitely be applied at normal talks.
First and foremost, workshops are interactive. By their nature, they're designed to show people how to do something. The best way to teach people how to do something, is to get them do it themselves.
Make sure your workshop is designed around getting the attendees to do as much as possible. This also lets them leave with something to show and that's always super rewarding.
Start with the end in mind. Give your attendees a clear picture of what to expect from your workshop so they know what you're working towards. It also really helps them understand why some decisions are being made rather than getting distracted by that.
Explain the why behind the what at each stage. This is similar to the above tip but this really helps people see beyond the practical. Copying what someone else has done is easy but really getting into the detail about how this is going to help them makes them want to take this further.
A good gauge here is to see if people are adding their own little bits to the code you've asked them to do. Don't take it as a negative if they aren't though.
Keep it nice and slow with constant check-ins. I can't actually stress this enough. I've been to so many workshops where the instructor just flies ahead and ends up having two people out of 100 following along.
Like tip #1, this is supposed to be practical so slow down and make sure everyone is up to speed before moving on. If this means less content to get more people involved, then definitely do it.
Don't be afraid to stop your workshop to help someone out. This leads straight on from #4. If someone is stuck, see if you can help them out. If it's going to take too long then it might be better to get them to join up with someone else. If it's a quickish fix then I'd really suggest helping them get going.
Encourage collaboration (this helps out with point 5 as well). Get people to work with others especially if they are more experienced in the topic. You could even ask people that you know could help out before the workshop.
If you can get your attendees helping each other it should mean that a larger part of the audience participates.
Don't try build Rome in a day. This is really important and it will make the difference between a talk that has everyone staring at you with wide eyes or people that walk away with something tangible.
It can be super enticing to give people as much value as possible but sometimes you can give more value by doing less. Actually, I take that back, you can almost always give more value by doing less.
Get your attendees to prep before the workshop. This can be key to a successful workshop especially if there is a technical setup that is required or even a local development environment.
You'd be able to ask the organising team of the workshop / conference to send a mail asking attendees to do a little prep.
Let the organisers know if you have any special requirements. If you need a whiteboard, a flip chart or special equipment, let the organisers know as soon as possible. This allows them to try and organise it for you before the event and remove a very awkward scenario at the event.
Use the PA system especially in larger rooms. If you haven't used a microphone before, it can be a little weird that you don't have to shout to have an entire room hear you (this doesn't mean that you should not speak clearly and confidently).
I'd suggest just checking to see if everyone can hear you OK in a room that doesn't have someone managing the sound.
Have a backup plan if the internet breaks. This is really important as it is super awkward when the internet goes down and there isn't a way for you to continue. A backup could be a screenshot or a video of what you're wanting to do.
Another backup could be using your own device for internet connection or having everything set up locally for you to work off.
Code snippets shared with attendees. This is something that has caught me out in every workshop I've presented before. If you're going to have code that the attendees need to use, create a repo or online resource that you can share with them to get the snippets of code.
This just means you don't have endless typos and also means you can maintain a pretty high velocity if you have a ton of content.