Passive Aggressive Videos in Storyline

Not that passive-aggressive. I was just looking for the opposite of passive but aggressive sounded better.

Business Case

Have you ever had a video clip in your course that people watched “passively,” and maybe at the end, you asked some questions about it? Let’s say the clip shows a 5 step process. Or 5 top features. Or whatever topic/sections. What if you would like to know which sections your audience liked/understood/found complicated/got lost in, etc?

Here’s a rough prototype interaction to attempt to achieve that. In this example, you’re going to watch a video. While you’re watching the clip, you can adjust a slider showing how much you like the content. There’s no right or wrong here. You can adjust the slider any time. (For this example, it’s limited to 100 sliding.) It’s like instant polling.


At the end, the course checks 5 sections of the clip and averages your “liking” you did during each section.


What is this good for?

To be passive aggressive: maybe for nothing. But maybe you want to present 5 topics that is covered in high level in the clip. Everybody should go through the high level overview, but then they could explore one in details. You can “monitor” their reaction based on the slider, and jump straight into the most interesting topic at the end.

Or, you may want to know if they have any questions on a process. You play the animation of the process, and your audience can adjust the slider based on how clear the steps of the process are to them. You can then create a personalized cheat sheet with tips on some of the murkier steps.


This rough prototype won’t allow you to pause the video. If you want to allow the user to pause the video, you would need to add a feature that stops the “ticking” time as well. If you want to be more sophisticated and you can use a YouTube video, you can have full control over pause/stop/jump to section. Here’s an example.


1 thought on “Passive Aggressive Videos in Storyline

Leave a Reply

Your email address will not be published. Required fields are marked *