The documentation gap
Why do SOPs
die in the drawer?
The advice every growing team hears is "write SOPs." So they do. They fire up Trainual, record Loom videos, nominate a documentation owner, and six months later the SOPs are out of date, nobody's consulted them in weeks, and the new hire is still shadowing whoever's willing to tolerate them.
The problem isn't Trainual. Trainual does exactly what it promises: turns content into structured training with quizzes, role assignments, and completion tracking. The problem is upstream. Teams write SOPs for operations that were never actually designed — they're documenting what currently happens, including the workarounds, the tribal knowledge, and the parts that don't work.
Henry runs the design step that SOP advice assumes you've already done. He maps your operation using the AAAERRR methodology from Deliberate Work, specifies each step across three planes, and hands Trainual a designed system to document. Your SOPs describe the operation you actually want — not the chaos you currently have.
This is the pattern consultants with eight years of experience will tell you on Reddit: don't just document what should happen — design it first, document the fixed version, then train the team. Most teams skip the design step. Henry doesn't let you.
Subject structure from step intent
Henry step intents become Trainual subject titles and learning objectives. The SOP opens with the operational purpose — not a wall of screenshots.
Role assignments from execution plane
Every step declares who executes it — human role, AI agent, or hybrid. Trainual role-based delivery inherits those assignments directly.
Tests from the quality bar
Experience Plane quality criteria become Trainual test questions that actually measure operational competence — not recall of a screenshot.