Cut the Course Bloat with the Five Moments of Need

Priya Nair

Thirty two. Thirty two separate, hyper specific refund rules for edge cases that happen maybe, uh, once every six months. And the support manager was just... adamant. Absolutely insisted they all had to be jammed into a forty five minute mandatory onboarding deck.

Jordan Avery

Thirty two edge cases in forty five minutes? What was the, uh, what was the actual completion rate on that?

Priya Nair

A dismal forty percent. Forty percent. And escalation tickets? Didn't budge. Not even a single percentage point.

Jordan Avery

It is the classic subject matter expert trap, right? We think if it's important to know, it has to be memorized in a classroom or a SCORM module. But, um, but Conrad Gottfredson and Bob Mosher actually built a whole framework around this. It's called the Five Moments of Need framework. And it, it, it delineates five specific conditions or situations in which people require instruction or assistance.

Priya Nair

Five conditions. Okay, walk me through them, because usually people just dump everything into a single slide deck.

Jordan Avery

So the first two are Learning New and Learning More. That's your formal instruction. That is when you're conceptualizing a new framework or building foundational skills from scratch. But the other three? That's workflow support. That's when you need to Apply something on the job, when things Change, or when you need to Solve a problem when something breaks.

Priya Nair

Apply, Change, and Solve. Right, okay, so when someone is actually staring at a customer ticket at two in the afternoon, they're not trying to Learn New. They're trying to Apply or Solve.

Jordan Avery

Exactly! And trying to make people memorize Apply or Solve details during a Learn New event is why modules balloon to eighty slides.

Priya Nair

I, I actually had to fight this exact battle last year with an anxious compliance stakeholder. She wanted a twenty slide presentation on regional trade policy. People were making so many errors on frontline processing. I managed to convince her to put the presentation away and just build a simple, one page decision tree.

Jordan Avery

A one page decision tree? Did it actually work?

Priya Nair

It cut frontline processing errors by thirty five percent in the first month. Thirty five percent! Because they didn't have to recall slide fourteen from three weeks ago. It was right there in front of them.

Jordan Avery

That comes down to two variables every instructional designer needs to weigh: task frequency and consequence of error. If a task is low frequency and high consequence, like those thirty two refund edge cases, pushing it into human memory is a recipe for failure. It belongs in a searchable job aid, not a training module.

Jordan Avery

So how do you actually take a massive, bloated deck and strip it down without causing a stakeholder panic attack? You use a simple Three Column Moment Audit.

Priya Nair

A Three Column Moment Audit. How do you set that up?

Jordan Avery

Column one is your original slide content or topic. Column two is the designated Moment of Need, chosen from those five conditions. And column three is the final home for the content, whether that's the live session or a performance support tool.

Priya Nair

Let's test this right now. Pretend I am an enablement lead, and I have a twelve step contract approval sequence inside our quarterly sales enablement deck.

Jordan Avery

Okay, twelve steps. First question: are reps executing contract approvals every single day, or once a month?

Priya Nair

Maybe twice a quarter when a big deal closes.

Jordan Avery

Right, so that is an Apply moment for a low frequency task. Putting twelve steps on slide twenty two means they will forget step seven by the time they actually land a deal. That shouldn't be an interactive module at all. That should be a pinned Slack workflow prompt or a one page lookup guide.

Priya Nair

Okay, but let me push back on that, Jordan. Because I see a real world risk here. If we pull everything out of training modules and scatter it into job aids, Slack prompts, and wikis, what happens when the policy changes? Unmaintained job aids create massive compliance hazards. At least a training module forces an annual review cycle.

Jordan Avery

That is a totally fair point. Performance support only works if there is clear content ownership. If nobody owns the wiki or the job aid, it rots. But the solution isn't to force people to memorize outdated slides instead. The solution is assigning an explicit owner to every performance tool you create.

Priya Nair

Fair enough. Clear ownership keeps the tool alive, and keeping it out of the module keeps the learner sane.

Jordan Avery

So here is a forty eight hour experiment for anyone listening. Grab ten slides from your organization's absolute longest, most painful training deck. Run a Moment Audit on those ten slides. Identify three concepts that are purely Apply or Solve, and convert them into single screen lookup guides before your next team check in.

Priya Nair

Just three concepts. Try it out, see how much friction disappears. Alright, good chatting, Jordan.

Jordan Avery

Talk soon, Priya.