Trainer dependency

Atlas

The constraint created when delivery requires a scheduled person, which limits how fast a network can be reached.

What is trainer dependency?

Trainer dependency is the constraint created when delivery requires a scheduled person. Reach is then limited by the number of trainers and the days they can travel, which is a hard ceiling rather than a budget line. It appears in any network large enough that a policy change has to arrive everywhere within one quarter.

Why the arithmetic of a network settles this before anyone debates it

Trainer dependency shows itself in the arithmetic long before anyone names it as a problem. A network of several hundred branches and a handful of qualified trainers produce a schedule that cannot close, so the locations at the end of the sequence are always a quarter behind the first. The trainers themselves are usually the most capable people in the function, spending their weeks repeating one session. Removing the dependency does not mean removing them, since their judgement is what the content needs; it means separating delivery from the diary.

  • Reach is bounded by trainer availability, which no budget increase resolves quickly.
  • The last location trained is always materially behind the first on a changed policy.
  • Scarce expertise is consumed by repetition rather than by designing the material.
  • A single trainer's absence removes a quarter of delivery for a whole region.

How trainer dependency works

  • Current delivery is mapped against locations, with the cycle time per region recorded.
  • The trainer's session is captured as source material rather than as a recording to watch.
  • Content is generated so the explanation survives without the person present.
  • Assessment replaces the trainer's informal judgement of whether the room understood.
  • Trainers are redeployed onto content review and onto the cases that need a person.
  • Delivery coverage is then reported by location instead of by session delivered.

How trainer dependency is evaluated

Trainer dependency is measured by how long a change takes to reach the furthest location. Examine the following across a full delivery cycle:

  • elapsed days from policy approval to the last location trained
  • trainer days consumed per thousand people trained
  • variance in assessment results between locations
  • share of delivery requiring a scheduled attendance
  • coverage reached without a trainer present

Limitations, risks and common failure modes

  • Recorded sessions are treated as a substitute and completion collapses within weeks.
  • The trainer's informal reading of the room disappears with nothing replacing it.
  • Regions with the weakest performance are the ones a trainer reached last.
  • Removing trainers from delivery also removes the only channel for upward feedback.

All 315 terms