Most companies discover they need training only after they already have the documentation. The SOP exists, it's accurate, and people still get the process wrong — because a reference document and a training course do different jobs.
The good news is the conversion is mostly structural. You rarely need to rewrite the content.
Why an SOP doesn't teach
An SOP is written for someone who already knows they need it. It's optimised for lookup: complete, precise, organised by topic, and indifferent to what the reader already knows. That's exactly right for reference.
It's wrong for learning in three ways. It assumes the reader arrives with a question, so it doesn't motivate anything. It's ordered by structure rather than by what to learn first. And it has no way of establishing whether anything was understood — reading is unverifiable.
What actually has to change
Split it. Use the existing section headings as the joins. Sections in a well-written SOP are usually conceptually complete, so each becomes a module that ends somewhere natural. Aim for pieces that take under ten minutes.
Make each piece stand alone. Check that module four doesn't open by referring to something in module three. If it does, either merge them or add a sentence of context. Independence is what lets someone complete modules in whatever order their week allows.
Add a check at the end of each. Two to four questions, about the substance rather than the phrasing. This is what converts "was sent" into "engaged with", and it's the only part that produces evidence.
Reorder if needed. Reference documents are often organised alphabetically or by system. Training should be ordered by what someone needs first.
Leave the content alone otherwise. The most common mistake is treating this as a rewriting project, which turns a two-hour job into a two-week one and usually makes the SOP and the course drift apart.
Keep the SOP as the source of truth
This matters more than it sounds. If the course becomes a separate copy of the content, you now maintain two things, and within a year they disagree.
The better arrangement is that the SOP stays canonical, and the course is generated from it. When the process changes, you update the SOP and regenerate — rather than updating the SOP and then remembering to update the course.
The failure mode
The single most common outcome is publishing the SOP as one long course with a quiz bolted on the end.
This reproduces the original problem exactly. It's still a twenty-five minute wall of reference material; it now just lives in a different tool and has a test attached. Completion will be poor, and the conclusion drawn will be that the SOP was fine and people are lazy.
The splitting is not an optional refinement. It's the part that does the work.
Doing it automatically
Splitting by hand is tedious, which is why most teams don't and the long-course version persists.
Poplearn does the conversion. /courses new takes the SOP you already have, splits the material into modules, and writes the quizzes as it goes. /assign #support sends it to a person, a channel, or every new hire from that point forward, and /progress gives live completion by team, exportable when someone asks.
Modules arrive as Slack direct messages, so the training reaches people where they already work instead of waiting in a portal. Free under 20 seats, installs in about a minute.
