# Design Video Steps Like Media Teams

{% hint style="info" %}
Most training videos don't fail because the content is bad. They fail because of how they're delivered — too long, dropped in the middle of a module with no context, and no interaction to make the learner do anything with what they just watched.
{% endhint %}

***

### Step 1: Is This a Step, or Its Own Training?

Before you build anything, answer one question.

| Video Length             | What to Do                                                                                                                                          |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **15 seconds or less**   | Embed it as a step inside a larger training module                                                                                                  |
| **More than 15 seconds** | Make it a standalone training with its own title, description, and follow-up question                                                               |
| **Multiple concepts**    | Split into separate clips — two 10-second videos that each make one clear point will always outperform a 25-second video that makes two blurry ones |

{% hint style="warning" %}
If you find yourself thinking *"I'll just squeeze two concepts into one video"* — that's a sign to split them.
{% endhint %}

***

### Step 2: Sketch the Sequence Before You Build

Once you know you're building a video step, sketch the surrounding structure before you open the editor.

{% stepper %}
{% step %}
**Context Step**

Tell the learner what this is about and why it matters. One sentence and a clear call to action — like a button that says "Start the video." No paragraphs summarizing the video content. That's what the video is for.
{% endstep %}

{% step %}
**Video Step (Step 2 or 3)**

Place the video within the first three steps. Early in a module, learners are attentive and curious. Deeper in, they've accumulated cognitive load. Put the video where it can land cleanly — before attention starts to drift.
{% endstep %}

{% step %}
**Reinforcement Step**

A quick interaction immediately after the video — a button choice, quiz question, or scenario. One prompt that helps the learner apply what they just watched.
{% endstep %}
{% endstepper %}

***

### Step 3: Structure the Video Step Itself

A strong video step has four elements — nothing more.

| Element         | What to Write                                                          |
| --------------- | ---------------------------------------------------------------------- |
| **Title**       | Name what the video shows — *"Watch: Spotting a fake login page"*      |
| **Instruction** | One line — *"Watch this short video, then choose what you'd do next."* |
| **Asset**       | The video                                                              |
| **Buttons**     | The next action                                                        |

{% hint style="danger" %}
**Avoid:**

* Paragraphs explaining what the video is about before it plays
* Multi-step instructions that mix watching with reading and scrolling

The learner has one job: watch the video and then do something with it. Make that obvious.
{% endhint %}

***

### Step 4: Always Add Buttons

This is where a lot of trainings quietly break down.

{% hint style="warning" %}
**Without buttons:** the platform auto-progresses when the video ends. The learner can't pause, can't rewatch, and doesn't make any choice. You lose the interaction point entirely.
{% endhint %}

Use buttons to do more than just advance the learner:

{% tabs %}
{% tab title="Confirm Completion" %}
*"Got it, next."*

Simple — but it keeps the learner active and gives you a measurable interaction point.
{% endtab %}

{% tab title="Capture a Decision" %}
*"This looks safe"* / *"This looks suspicious"*

Turns passive watching into a judgment call.
{% endtab %}

{% tab title="Branch the Experience" %}
Different buttons lead to different follow-up steps — letting you tailor feedback based on what the learner chose.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Even a single "Continue" button is better than no button. It gives the learner control, which keeps them more engaged.
{% endhint %}

***

### Step 5: Reinforce Immediately After the Video

The step after the video should do one thing: help the learner apply what they just watched.

* One question. One scenario.
* Not a full quiz — not a new concept.
* Something that prompts them to process the video rather than move past it.

{% hint style="success" %}
Watching something activates recognition. Doing something with it builds retention.

*"What would you do if you saw this in your inbox?"* with two or three button choices is enough.
{% endhint %}

***

### Step 6: Keep the Whole Module Tight

Aim to keep your total module to **8–10 steps**. That's the range where most learners can complete a training in a focused sitting.

If you're going over that limit, check whether any steps are doing double duty. A step that tries to explain something, ask a question, and introduce the next topic is really three steps. Break them apart — or cut the least essential one.

***

### The Pattern in Practice

Here's what the full structure looks like assembled:

{% hint style="success" %}
**Step 1 — Context** *"Phishing attacks often look legitimate. Here's a short video showing what to watch for."* Button: *"Start the video"*

***

**Step 2 — Video** Title: *"Watch: Spotting a fake login page"* Body: *"Watch this short video, then choose what you'd do next."* Buttons: *"I'd report this"* / *"I'd ignore it"* / *"I'd enter my password"*

***

**Step 3 — Reinforcement** *"You're about to log into your bank account and the page looks slightly off. What do you do?"* Buttons: scenario choices
{% endhint %}

Three steps. A video that makes one clear point. A decision that puts the learner in the situation. That's the whole structure.

***

### Summary

{% hint style="info" %}
Video steps work when they're **short**, **placed early**, and **paired with something that requires a response**. Without those elements, a video is just something to sit through. With them, it becomes a focused moment that moves the learner from watching → thinking → doing.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://herd-security.gitbook.io/herd-security-docs/how-to-documentation/design-video-steps-like-media-teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.