I’ve written about writing before, but I don’t think I’ve talked about designing a workshop. Yet, that’s what I’m doing right now, and so I’m also reflecting. Which, of course, is very ‘meta’, because reflection is one of the topics of the workshop! Still, I’m pondering what’s different about designing a workshop versus writing, whether book or article or… So here’re some thoughts.
First, as is the case with writing a book (at least for me) is the process of creating the structure. I outline what I’m doing (even both outlined it and separately created a mindmap, to see what overlaps and gaps I found). For instance, I initially saw this as five separate events, spaced out. When I got into it, putting meat onto the bones as the saying goes, I realized that I wanted to combine three and four. So now there are four separate bits.
Then, as is the case with writing, too, I realize I’m alternating between top-down and bottom-up. Which is demonstrably what designers do, but…it’s interesting to break the myth of the waterfall design. I generate low-level elements, which makes me rethink and restructure bits, which means I need to go down into the details some more.
It’s also the case that I can disappear into design for too long (fortunately, the ribs came out ok). I personally go in bursts. I will get going and time will fly by, and then I hit a wall and just have to stop and take a break. It also is mentally taxing, and I find my thoughts become difficult until I take some time off.
And, I recognize it will take several passes. Already I’ve made ‘todo’s for two specific post-hoc passes. First, I’m getting the ideas and the structure right. Then, I want to go back and make sure I’ve put in all the good ideas, hints/tips/tricks, and all that ensures there’s real value in what I’m doing. Finally, I want to make a third pass that ensures I’m helping the audience process the content successfully. That is, getting them to rephrase the ideas into their own words (a form of reflection).
The latter of which is, specifically, what’s at least partly unique to a workshop versus a book. Yes, I’m making it interactive in the first pass by asking an opening question for each section to get folks creating their own thoughts before I present mine, so as to activate and also to generate any improvements that can come from them. While I think I have plenty of relevant background, I’ve not enough hubris to think that there won’t be ideas that are better than mine. I learn when I run workshops, too!
One of the important things here is to develop real new abilities, not just to present ideas. Learning science tells us we need repeated practice, and that’s definitely got to be part of what this workshop does. So, not only do I want some scaffolded practice in the session, but there’s also ‘homework’ where attendees apply the current idea to their own work and share the learnings therefrom in between sessions. (Research emerging from our work at Elevator 9 suggests that when this is done – and it’s hard to do – the results are better.)
The goal is a workshop that delivers real learning, and real value. I don’t want to just make money selling ideas and good feelings. That’s too frequently what we see (*cough* leadership development *cough*), but that’s not what will lead to long term benefit. And I do care about that (perhaps too much! ;). So, there are some thoughts on designing a workshop. What haven’t I made clear? What am I missing?
(And no thanks to Apple for losing my templates and making me create them anew. Ahem.)
