# Use Simulation Results to Decide Your Next Training

{% hint style="info" %}
The most effective approach is simple: **test, measure, train, and reinforce.** Your simulation results show exactly where your organization is vulnerable and who needs help.
{% endhint %}

### 1. Understand Your Metrics

Before making any training decisions, know what your numbers say about user behavior and risk.

| Metric                         | What It Measures                                    |
| ------------------------------ | --------------------------------------------------- |
| **Click-through rate**         | How many users clicked on a phishing link           |
| **Credential submission rate** | How many users entered passwords or other data      |
| **Reporting rate**             | How many users flagged the simulation as suspicious |
| **Repeat offenders**           | How many users have failed multiple simulations     |

**The key question to ask:** Who is struggling the most, and where is risky behavior concentrated?

***

### 2. Identify Who to Prioritize

Focus first on:

* Individuals who have failed more than once
* Teams with higher failure rates or lower reporting rates
* Users who submitted credentials

***

### 3. Act on Results

Check which simulation types had the highest failure rates, then match your training response to the behavior you observed.

{% tabs %}
{% tab title="Individuals Who Failed" %}

* Assign mandatory training on the specific failure type within **48 hours**
* Send a brief reminder about how to spot the relevant red flags
* Re-test with a similar simulation in **1–2 weeks**
* If failures continue, escalate to their manager

{% hint style="info" %}
For everyone who clicks, focus on teachable moments. Send a short 8–10 step training module immediately while the experience is still fresh — just-in-time training is more effective than waiting days or weeks.
{% endhint %}
{% endtab %}

{% tab title="High-Risk Departments" %}

* Share results directly with the department leader
* Maintain regular quarterly training on emerging threats
* Keep simulations varied so users don't become complacent
* Recognize good reporters publicly where it fits your culture
  {% endtab %}
  {% endtabs %}

{% hint style="info" %}
**In Herd:** Link a training module to your simulation so failures automatically trigger enrollment. Use the dashboard or Herd AI to pull click rate, report rate, and credential submission stats by campaign or team.
{% endhint %}

***

### 4. Monitor Trends Over Time

| Trend                              | What to Do                                                                |
| ---------------------------------- | ------------------------------------------------------------------------- |
| **Click rate trending down**       | Keep doing what you're doing                                              |
| **Click rate stuck or rising**     | Shift more training toward the simulation types causing the most failures |
| **Same people failing repeatedly** | Move to direct intervention or involve their manager                      |

***

### Summary

{% hint style="success" %}
Every simulation is a chance to change behavior, strengthen your reporting culture, and steadily reduce real-world phishing risk. The results tell you exactly where to focus — all that's left is acting on them.
{% 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/use-simulation-results-to-decide-your-next-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.