I’ve written about all the steps in the Designing Predicaments job aid in detail now, with a video talk about each.
I just want to remind you of how I recommend using Designing Predicaments. It works best, I think, in a small group or pair – maybe a designer and an SME – who’ve already made the decision to build a scenario, have a fairly clear idea of the learning point and the situation it’ll be based around.
It’s supposed to be a working document on which you scribble ideas as you go through each step. The steps don’t translate directly into elearning screens – they’re not supposed to. They help you build up the story in a way that adds drama and interest and at the same time holds true to the learning points. I’ve watched it used that way at the Good Things Foundation (formerly Tinder Foundation) and it really worked.
Here’s the entire series:
Designing Predicaments, a job aid for scenarios
Step 3: the situation in detail
Steps 12 & 14: sense-check and the call to action
I’m now considering ‘what next?’ – two suggestions have been to add more to it about complex scenario paths and to write specifically about Storyline scenarios. What’s your experience of using the tool and how could I improve it?