Advertisement
Advertisement
Office colleagues congratulating happy woman excited by good new
ATD Blog

Dry, Boring, or Technical Content Can Still Be Engaging

Wednesday, May 27, 2020
Advertisement

A recent survey showed that 67 percent of employees admit they plan to multitask at their next virtual training session. And 100 percent admit to actually doing it.

Virtual or in-person training must engage participants for learning transfer to occur and for people to feel that their time has been well-spent. We want our participants to be wide-awake and learning, so at a previous ATD International Conference & Exposition, I presented a session on how to add caffeine to your training design and implementation.

While I had rave reviews, I had a few people ask me how to add some energy even when working with dry, boring, or technical content. Another participant asked me for some advice about ways to engage accountants and engineers. Sound familiar?

Advertisement

Different subjects and audiences require different approaches and options for interactive strategies, but there are some activities that work for most content and learners. For instance, “Fill It In” is a simple strategy you can try. The title is self-explanatory: instead of showing your learners a completed flowchart, list, or graph, let them engage their brains to make predictions about the missing text. And depending on your audience, you can opt for more serious, intellectual, or creative slide design.

For more tips on how to liven up your content, join me during ATD Virtual Conference.

About the Author

Anne Beninghof is founder of Caffeinated Learning, whose mission is to improve the quality of instruction for learners of all ages and in every field. Known for her dynamic, interactive virtual training as well as in-person sessions, Beninghof has worked in all 50 states and several countries. Her most recent book is Caffeinated Training Design: An Engagement-Centered Process.

Be the first to comment
Sign In to Post a Comment
Sorry! Something went wrong on our end. Please try again later.