Check out these examples of branching scenarios, and examine the design decisions behind them. Read more.
“Our job is to give the client what they want.” Nope. Our job is to save the client from themselves. We need to learn who they are and what challenges they’re facing, and then help them do the analysis that they probably skipped. Learn more.
“I’ll create whatever you want, even if it will never work!” That’s what the typical training request form promises clients. Set the right expectations by burning that form and replacing it with these ideas. Learn more.
Does that learning objective really want what’s best for you? Conventional objectives aren’t always our friends. These three questions will help you set boundaries with our frenemy. Learn more.
“This thing is new, so of course everyone needs to be trained on it.” Your client is heading toward an information dump. Steer them to a better solution with these tips. Learn more.
How can we make mandatory training actually useful? With some disobedience, questions, and a sneaky workaround to “everyone must be exposed to all the information.” Learn more.
A good job aid can reduce or eliminate the need for training. Here are two examples of interactive job aids created in Twine, a free tool. Learn more.
Here’s an alternative to traditional software training: Create self-contained activities that help people learn by doing, and make the activities available on demand. Learn more.
“How can I design training for new software?” Maybe training isn’t even necessary. Let’s look at some alternatives. Learn more.
“You can’t just throw people into an activity without first teaching them the concepts.” Yes, we can. Check out this simple example. Learn more.