# Create the Best Video Training

### 1. Build Order

{% stepper %}
{% step %}
**Decide if the video is a step or its own training**

If the video is longer than 15 seconds, make it its own standalone training.
{% endstep %}

{% step %}
**Sketch the step sequence**

Plan your full step order and place the video step within the first three steps.
{% endstep %}

{% step %}
**Add a pre-video step with a button**

One sentence of context plus a button — for example, "Start the video."
{% endstep %}

{% step %}
**Add the video step**

Short title, one-line instruction, the video asset, and buttons to continue.
{% endstep %}

{% step %}
**Add a post-video step**

One question or scenario to reinforce what they just watched — use buttons or a quiz.
{% endstep %}

{% step %}
**Review total length**

Aim to keep the overall module to **8–10 steps**.
{% endstep %}
{% endstepper %}

***

### 2. When to Make a Video Its Own Training

| Video Length             | What to Do                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------- |
| **15 seconds or less**   | Embed it as a step inside another training                                            |
| **More than 15 seconds** | Make it a standalone training with its own title, description, and follow-up question |
| **Multiple concepts**    | Split into multiple short videos instead of one long clip                             |

***

### 3. Where to Place a Video Step

Place the video step within the **first three steps** of a training. A simple pattern:

1. **Step 1** — Set the context: what this is about and why it matters
2. **Step 2 or 3** — Video step
3. **Next step** — Quick interaction (button, quiz, or scenario question) to reinforce what they just watched

***

### 4. How to Structure the Video Step

| Element     | What to Write                                                                |
| ----------- | ---------------------------------------------------------------------------- |
| **Title**   | "Watch this short video"                                                     |
| **Body**    | One-line instruction: *"Click play, then use the buttons below to move on."* |
| **Asset**   | The video                                                                    |
| **Buttons** | Action to advance or capture a decision                                      |

{% hint style="success" %}
**Example video step:**

* **Title:** "Watch: Spotting a fake login page"
* **Body:** "Watch this short video, then choose what you'd do next."
* **Buttons:** "I'd report this as phishing" / "I'd ignore it" / "I'd enter my password"
  {% endhint %}

***

### 5. Buttons and Progression

Always add buttons to every step — including the video step.

{% hint style="warning" %}
**Without buttons:**

* The platform auto-progresses when the video ends
* Learners can't pause, rewatch, or make a choice
* You lose an interaction point for measuring understanding
  {% endhint %}

**Use buttons to:**

* Confirm completion — *"Got it, next."*
* Capture a decision — *"This looks safe / This looks suspicious."*
* Branch to different follow-up steps (if your flows support branching)

***

### 6. What to Write for the Video Step

{% tabs %}
{% tab title="Do" %}

* *"Watch this short video, then pick the best response."*
* *"Play the video, then click the button that matches what you'd do."*
  {% endtab %}

{% tab title="Avoid" %}

* Long paragraphs explaining the video content before it plays
* Instructions that mix multiple actions — *"Read all the text, then watch, then scroll, then click…"*
  {% endtab %}
  {% endtabs %}

{% hint style="info" %}
Keep videos short, place them early, and always pair them with buttons. This turns each video into a focused learning moment instead of background noise — and makes your training faster to build and easier to complete.
{% 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/create-the-best-video-training.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.