# Training Evaluation Form — Reading the Results

> One rule first: reaction items describe the day; only the day-30 answers describe the work. Report them separately, never averaged together.
> Use with `training-evaluation-form-guide.md`. Reading takes 20 minutes for a cohort of 20.

---

## The 60-second read

1. **Overall item at 4.0 or higher, but relevance under 3.5?** The training was enjoyable and aimed at the wrong work. This is the most common corporate failure and the item means catch it precisely.
2. **Delivery items vs content items.** Logistics and workload under 3.0 while content rides high: fix the program administration, not the course.
3. **Day-30 behavior count above zero?** The training is alive. Zero uses in 30 days — the course was an event, not a change, and no reaction score repairs that.

---

## Item-by-item interpretation

| Item | Construct | Low (≤ 2.5) means | First action |
|---|---|---|---|
| 1 | Relevance | Content missed the actual work | Rewrite the needs intake before the next run |
| 2 | Depth | Correct generalities, no depth | Replace one lecture with one worked case |
| 3 | Instructor | Questions met with slides | Instructor prep session on Q&A handling |
| 4 | Materials | Handouts filed and forgotten | Cut to one page people will reopen |
| 5 | Exercises | Listening outweighed doing | Add one exercise per half-day |
| 6 | Logistics | Sign-up, schedule or room friction | Fix the admin flow — it is dragging the scores |
| 7 | Workload | Course load collided with the job | Reschedule or split the cohort |
| 8 | Overall | The room's honest verdict | Read items 1-7 before reacting to this one |

---

## Level 2: reading the confidence self-reports

The three items (apply without help / explain in two minutes / know where to look when stuck) are deliberate narrow abilities. Read them as a set:

- All three low — the course taught awareness, not capability. Not a failure; but call it awareness training in the report.
- "Apply without help" low, the other two high — people understood and remember, but the doing needs support: schedule a practice session, not a repeat of the course.
- With a baseline: the delta is your Level 2 number. Without: report absolutes plus the words "self-report, no baseline".

---

## The day-30 email (template)

Send 30 days after the last session, from the person the participants know, subject: "30 seconds — did any of it stick?":

> You attended [program name] on [date]. Three questions, 30 seconds, anonymous:
> 1. Since the training, I have used the main method: (never / once / 2-5 times / weekly) — circle one
> 2. What helped or blocked the using? — one sentence
> 3. What support would make it stick? — one sentence
>
> Nothing else. No follow-up will chase you.

The last line is not politeness; it protects the response rate of the next program.

---

## The management one-pager (template)

> **[Program name] — evaluation summary, [date], N=[n], response [r]%**
> - Reaction: overall [x.x]/5; lowest item [name] [x.x]; highest item [name] [x.x]
> - Confidence (self-report[ + delta]): apply [x.x][ (Δ+x.x])], explain [x.x][ (Δ+x.x])], recover [x.x][ (Δ+x.x])]
> - Day-30: [n] of [n] replied; used-it count [n] (never [n] / once [n] / 2-5× [n] / weekly [n])
> - Keep: [one verbatim, permissioned] — Change: [one verbatim, permissioned]
> - Recommended next run: [one sentence, from the keep/change list]

One page. If it does not fit on one page, the program does not fit in a manager's attention — cut until it does.

---

## 3 known failure modes of reading the results

1. **Levels averaged together.** A 4.5 reaction mean next to a zero behavior count is a failed program with a nice cover photo. Rescue: report levels in separate lines — the gap **is** the finding.
2. **The one-pager grows a second page.** Charts, percentile bands, benchmark logos. Rescue: the template above is the ceiling; anything past it goes in an appendix nobody reads.
3. **The day-30 obstacles go unread.** The follow-up's second question (what blocked the using) is free transfer-climate consulting. Rescue: read those sentences first — they are the program's actual to-do list.