Preparation is the key to a good workshop, and it also helps you to be more confident. An agenda, or workshop plan, is a good way to make sure you're adequately prepared, and that you are being sensible about what you can cover in the time you have. It's always tempting to try to cram in too much, so be realistic about how much time you gives to activities, and be brutal about taking stuff out!
First of all work out your aims for the workshop - you may find it helps to write them out at the top of the agenda when you're working on it. Come back to these as you plan each activity. Does what you are planning to do help you achieve your workshop aims, or help the group relax and get to know each other? If not, you probably don't need the activity.
If your workshop is about producing practical outputs (like how to do a news release or code an HTML page) then make sure to add enough time for people to try out their new skills. This helps build people's confidence and means they're more likely to remember what they've learned, especially if they get the chance to try things out several times, not just the once.
When designing a workshop it's easy to forget the breaks - there always seems to be more to fit in than time will allow! But we're all human, both facilitators and participants, and when we're tired we don't function too well - and that includes understanding and remembering what the workshop is about.
If your workshop is two hours or less it's usually enough to make sure there is a possibility to get tea or coffee (or a trip to the pub) at the end. But if your workshop is longer than two hours then it's a good idea to schedule in a break every two to three hours, with an energiser in between.
Whenever possible, it is advisable to engage participants 1-on-1 before events, and ask them about what they want to get out of the event.
Ask them to help shape the Agenda
More pre-engagement questions.
It can be really fun to work with audio recordings to make a real or spoof news report. I offered to run this workshop as part of a series on using Free Software.
Prepare and test your equipment. Just because the software is on the machine doesn't mean it will do what you want it to. A test showed that out of the 5 computers only 3 could record a 'line in' signal. So we brought 2 laptops to fill the gap.
For the examples above, ask yourself:
There has been error in communication with Booktype server. Not sure right now where is the problem.
You should refresh this page.