Skip to main content

Training Without PowerPoint

Are you a trainer? Are you a facilitator of any kind? Are you a person who hates being shown slides? (If not, please check out this famous PowerPoint rendering of the Gettysburg Address).


I just attended a very amazing two-day training course given by Luke Hohmann of Innovation Games(R).  The games themselves provide wonderful techniques for doing "qualitative market research" (if you're a marketing person) or "requirements gathering" (if you're a software developer).  You must try them, you must!  Check out the web site, buy the book, license the online tools, and use these techniques.  They are fabulous.

But as veteran qualitative researchers would tell you, the most interesting part of what I learned (and that's saying a lot) was from the medium, not the message.  The course was taught 100% PowerPoint free.  In fact, there was no projector.  It was the most devious and marvelously designed way to coax learning out of an group of adults I've ever seen.  So what did Luke do?
  • Tables covered with paper and strewn with fun office supplies:  each table had pens, sharpies, glitter glue, pipe-cleaners, really high-quality stickers, post-it notes, index cards, and so on, and each table was covered in paper, so if you wanted to illustrate a point to your table-mates, you could sketch it right there on the table.  Visual learning is a powerful thing, and equipping the tables this way set the course up to be non-threatening to participants, appealed to everyone's sense of humor, and (not, of course, an afterthought), put needed materials for later activities ready to hand.
  • Content posters:  core concepts from the course were conveyed on posters which he taped to the wall, and alluded to at appropriate points throughout the two days.  Full disclosure:  I believe PowerPoint might have been involved in the drafting of the posters, since it's WAY easier to use than most other drawing tools, but the slides weren't slapped up, discussed, whisked away, and then brought back in summary later on.
  • A really good in-class workbook for people to use and take home:  the book had a section of "course content" which included portable versions of the posters, a section of "case studies" for class discussion, printed worksheets to support some of the activities, and a bibliography for further reading.
  • Table discussions:  the case studies in the books were used to generate discussions around participant tables.  Once the tables discussed, Luke would facilitate a large-group discussion around findings, adding his own insights (and gestures towards the posters) as appropriate.
  • Discussion posters:  a number of class activities involved participants gathering around a poster with some type of image on it, and brainstorming by putting post-it notes of content onto different areas of the poster.  For example, participants thought of activities which would fit into a set of quadrants defined by "more or less pleasurable" (x axis) and "internally versus externally motivated" (y axis).  Or participants armed with sharpies filled out a whole wall of posters with activities which fit into the categories on those posters.
  • Participant-led discussion:  granted, it was a group of facilitators, but I think this would work with any group--for poster discussions, Luke occasionally drafted a participant to draw conclusions from the poster, rather than sorting the post-its and talking to them himself.
  • Games and simulations:  the course was an introduction to the games, which are facilitated in person and also over the web, so naturally the course involved participants playing the games.  However, in my view, games and simulations are great IN ANY TRAINING COURSE, for participant learning.  Far better than having a moderator try to dryly convey "content packages" in slide-sized chunks directly from her brain to that of the audience.
As a veteran trainer of adults, I can tell you that every time I bring out the slide deck, I know that after ten minutes or so, the tired people in the room are going to literally start falling asleep.  It won't be everyone, but about 5% of any given room has been up late last night, up early this morning, or both.  It's sad to watch as their eyelids flicker, and bam!  they're out.  I'm a goofily interactive instructor, but nobody can save a long slide presentation forever.  I am really challenged and excited by Luke's course design, both for training purposes and for team facilitation purposes in software development discovery and retrospective activities.

Comments

Post a Comment

Popular posts from this blog

How Do You Vote Someone Off of Your Agile Team?

One of the conundrums of agile conversion is that although you are ordered by management to "self-organize," you don't get to pick your own team.  You may not have pictured it this way, but your agile team members are going to be the same people you worked with before, when you were all doing waterfall!   I know I wasn't picturing it that way for my first agile team, so I thought I should warn you.  (I thought I was going to get between six and eight original Agile Manifesto signers.  That didn't happen.). Why "warn" you (as opposed to "reassure" you, say)?  Because the agile process is going to reveal every wart, mole, quirk, goiter, and flatulence issue on the team within a few hours.  In the old days, you could all be eccentric or even unpleasant in your own cube, communicating only by document, wiki, email, and, in extreme situations, by phone.  Now you are suddenly forced to interact in real time, perhaps in person, with written messag...

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1.        Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that: a.    ...

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read. From:  http://www.highestfive.com/mind/how-to-perform-a-successful-interrogation/ Dialogue: WBABA :   ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration! Corporate Standards Guy:   but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actu...