A training program is a set of modules and a set of decisions about the order those modules run in. Most of the attention goes to the modules. The order is treated as a scheduling problem, settled late, and rearranged whenever a deadline moves. This is backwards. Sequence is where a program holds together or comes apart, and it is decided before a single module is written.
We map sequence first. Before we storyboard a screen, we know which module depends on which, what each one assumes the learner already knows, and where the material that governs everything else has to sit. The build follows that map. When it does, each module lands on ground the previous module prepared.
Start with the dependencies
Every module rests on something. A competitive-positioning module assumes the learner understands the mechanism it is positioning against. An objection-handling module assumes the learner already holds the evidence being challenged. Teach the second before the first and you have asked the learner to reason with material they have not been given.
Dependency mapping makes those relationships explicit. We list each module, then draw the arrows: what has to be known before this one makes sense. The result is not a preference for one order over another. It is a constraint. Some modules can run in parallel because they share no dependency. Others have a fixed position because everything downstream needs them. The map tells us which is which, and most of the sequence falls out of it.
Sequence is not the schedule. It is the argument the program makes, one module at a time.
Compliance before the customer-facing work
The most common sequencing mistake is filing compliance content at the end. It reads as tidy: teach the product, teach the selling, then cover the rules. In practice it inverts the dependency. The rules govern the customer-facing material. A representative cannot position a product correctly if they learn what they are allowed to claim only after they have learned how to make the claim.
We put compliance ahead of the material it governs. Regulatory framing, substantiation limits, and the boundaries of a claim come before the module that teaches the claim. The customer-facing content is then taught inside the constraints from the first minute, rather than taught freely and corrected later. Corrected-later rarely lands. What a learner practices first is what a learner keeps.
Prerequisites as design, not assumption
Prerequisites are usually implicit. A module is written as though the learner arrives with certain knowledge, and whether they actually do is left to chance. We make prerequisites explicit and design for them. Each module states what it assumes. If an earlier module does not supply that assumption, either the earlier module moves ahead of it or the prerequisite becomes part of the module itself. Nothing is left to hope.
Role-gating is the same principle applied to audience. Not every learner needs every module, and pushing a full field team through material meant for one role wastes time and dilutes attention. We gate modules by role, so each learner follows the path built for them. A prerequisite for one role can be a given for another. Sequence and audience are decided together, because a module's position depends on who is taking it and what they were shown before.
Why the capstone comes last
A capstone — the scenario, the certification, the decision made under pressure — belongs at the end. This is not a matter of taste. A capstone works by requiring the learner to combine everything that came before it. It has, by definition, the most prerequisites in the program. Place it earlier and it tests knowledge the learner has not yet been given, which measures nothing and teaches frustration.
Last is where its dependencies are finally satisfied. The capstone is the clearest case of a general rule: position follows dependency. Once the dependencies are mapped, most of the sequence stops being a choice. The order is doing instructional work of its own, and getting it right costs nothing that getting it wrong does not cost more.