The training never gets built, and everyone knows why, and nobody says it out loud: the blank page. The manager who actually knows how to onboard a new rep, or run the safe-lift procedure, or close a support ticket the right way — that person has the content in their head and no time and no idea how to shape it into a course. So the training request lands on someone's plate as "we should build a course on this," and it sits there, quarter after quarter, because "build a course" from nothing is a project, and nobody at a small company has a project's worth of slack.

This is the real bottleneck in SMB training, and it's almost never a knowledge problem. The knowledge exists — it's in the head of the person who does the job well. It's a starting problem. Facing an empty document, the person who could teach the thing freezes, because the distance between "I know how to do this" and "here is a structured course that teaches it" is exactly the distance a professional instructional designer spends years learning to close. At an enterprise, you hire that person. At a 60-person company, you are that person, part-time, on top of your actual job.

The instinct is to lower the bar: throw some slides together, record a screen-share, call it training. Sometimes that's fine. Often it produces the thing everyone quietly ignores — no structure, no clear objective, no way to tell if anyone learned anything — because slapping content on slides isn't instructional design, and the gap shows.

There's a better move than either freezing or lowering the bar, and it's a change in where you start. Don't start by writing. Start by describing. Then let AI turn the description into a draft structure, and spend your scarce attention editing it instead of birthing it. The blank page was never the valuable part of the work. Your judgment about what's true and what matters is — and describe-then-edit puts it exactly where it belongs.

Why the blank page is the actual enemy

It's worth being precise about what's hard here, because the fix follows from it. Building a course from scratch demands two very different things at once, and the collision is what kills it. The first is subject-matter knowledge — what the job requires, what good looks like, where people go wrong; the manager has this in abundance. The second is instructional structure — how to sequence it, what the objective is, what the modules should be, how you'd know someone learned it. That's a craft the manager doesn't have, and acquiring it is not a reasonable ask on top of a full-time role.

The blank page forces you to supply both simultaneously, and that's the freeze. You can't structure knowledge into a course while you're also trying to recall and articulate the knowledge itself. The work stalls not because anyone lacks content but because the two demands jam each other. The entire value of describe-then-edit is that it splits them: you supply the knowledge in plain language first, and let something else propose the structure, so you're never doing both at once.

The describe-then-edit method

You can run this pattern with any capable AI assistant, no special tooling required, and it's worth understanding as a method before it's a product. Four moves.

  1. Describe in one plain sentence, out loud if it helps. Not a course outline — a sentence. "New support reps need to learn how to handle an angry customer without escalating and without giving away the store." That's the seed. If you can say what the training is for in a sentence a colleague would understand, you have enough to start. The precision comes later.
  2. Let AI draft the scaffolding. From that sentence, AI can propose the structure a professional would build toward: who the learner is and what they need (the needs analysis), a plan for getting them there, an outline, and the modules underneath it. This is the instructional-structure half — the part the manager couldn't supply — generated as a starting draft, not a finished course.
  3. Apply subject-matter judgment ruthlessly. Now you're the expert reviewing a competent-but-generic first pass — a role you can actually play. The AI doesn't know your customers, your policy, your product's edge cases. You do. So you cut the module that's wrong for your context, add the scenario that actually happens on your floor, fix the objective aimed at the wrong behavior. The draft is a foil to react against, and reacting is far easier than creating.
  4. Anchor it to a real outcome before you ship. Ask the one question that separates training from content: how will we know it worked — what should the learner do differently on Monday? If a module doesn't move toward that, cut it. The AI won't ask this for you; it's the judgment call that stays human.

Notice the division of labor. AI supplies structure and a fast first draft. You supply truth, context, and the outcome. The blank page — the thing that stalled the whole enterprise — never appears, because you always start from something to edit rather than nothing to write.

Edit like an expert, not a proofreader

The quality of what ships lives entirely in step three, so be honest about what "editing" means here. It is not fixing typos. A generated draft that reads smoothly can still teach the wrong thing, and polishing it just makes a more convincing version of wrong.

Edit for the things only you can see:

Done this way, the edit is where your craft lives and the AI is a multiplier of it, not a replacement. A generator with no expert editing it produces plausible filler; your editing turns the draft into training.

Where the tool fits

Most of the method above runs on judgment and any decent AI assistant. Where a purpose-built tool helps is in producing the right scaffolding — the instructional structure an SMB manager doesn't have — rather than a generic essay.

LearningByDesign's AI course generator takes exactly the seed this method starts with: one sentence, or a short description, of what the training is for. From that, it drafts the pieces a professional would build toward — a needs analysis, a training plan, a course outline, and the modules underneath — all of it editable. So you're not handed a wall of text to reshape; you're handed the structured bones of a course, in the shape instructional design says they should take, ready for you to apply the subject-matter judgment that's yours to apply.

That's the whole role of the software. It closes the gap between "I know how to do this" and "here is a structured course," so the manager who has the knowledge can finally get past the blank page. The truth, the context, and the outcome still come from you — the tool just makes sure you never start from nothing.

The bottom line

SMB training doesn't fail for lack of knowledge — it fails at the blank page, where the person who knows the content is asked to also be an instructional designer, and freezes. The fix isn't lowering the bar to slapped-together slides, and it isn't hiring a department you can't afford. It's changing where you start: describe the training in a plain sentence, let AI draft the structure you don't have, and spend your scarce attention editing for truth, context, and outcome instead of creating from nothing. The blank page was never the valuable work. Your judgment is — and describe-then-edit finally lets you spend all of it there.

Turn one sentence into a course draft — free

The free Course Outliner takes a topic and an audience and gives you modules, measurable objectives, and an assessment — the scaffolding, ready to edit. No signup.

Try the free Course Outliner →

About the author

Tom Christian is the founder of LearningByDesign, an AI-native learning platform that builds real training — needs analysis to course to evaluation — without hiring a Director of L&D.

He has spent twenty years inside training, learning, and quality at scale — building and running programs at Guardian Life, ConnectiveRx, and Horizon Blue Cross Blue Shield. He writes about course design that changes behavior, the discipline of starting with outcomes, and running an L&D function without a department behind you.