Why employees hate async courses (and why async is not the problem)

Asynchronous education is already ordinary technology. We stream instructions, search for explanations, and learn from digital tools every day. Yet inside many organisations, a self-paced course is still treated as a progressive—and slightly suspicious—alternative to a classroom, live course, or webinar.

Why? Here is the argument we keep hearing, presented as a debate.

TL;DR

• Employees rarely hate learning on their own schedule; they hate being left alone with poorly repackaged material.
• A recorded lecture, a 20-page PDF, and a quiz are not automatically a course.
• Completion percentages and passing scores can document activity without demonstrating useful learning.
• Short explanations, frequent low-pressure interaction, varied formats, and visible progress respect attention.
• Async production requires more decisions before launch, but produces a consistent foundation that can improve over time.

The debate

The enterprise voice: “Our people prefer live training”

Enterprise: We tried asynchronous learning. Employees disliked it, completion was difficult, and everyone asked for a live session instead. Async may work in the future, but our culture is not ready for it.

Learning designer: What did the course ask people to do?

Enterprise: Watch several 30-minute videos, reach the required viewing percentage, read a PDF, and answer questions. That is how we verify participation.

Learning designer: Then you did not test whether people reject async learning. You tested whether they tolerate recorded lectures, document dumps, and surveillance.

That distinction is provocative, but important.

“But all the information was there”

Enterprise: The videos contained the complete lecture. The PDF contained everything employees needed. Nothing was missing.

Learning designer: Completeness is not the same as teachability.

Uploading a one-hour presentation transfers the burden of production to the learner. They must find the important passage, create their own structure, decide what to remember, recover after an interruption, and work out how one point relates to their job. A quiz at the end does not repair that experience. It only checks what survived it.

In professional education, the goal is not to preserve every sentence an expert wants to say. It is to identify what somebody needs to understand, remember, and do.

“We need proof that they watched it”

Enterprise: We have compliance and reporting requirements. We need a viewing threshold and a passing score.

Learning designer: Track what you genuinely need to track—but do not confuse a metric with learning.

A person can let a video run without paying attention. Another can understand a three-minute explanation, apply it correctly, and still fail a viewing-percentage rule. Completion data is useful operational evidence; it is not, by itself, evidence of retention or changed behaviour.

Assessment matters when the risk demands it. But every interaction does not need to feel like an exam. A simple question can ask the learner to choose an example, predict the next step, recall one key point, or connect an idea to their role. These small moments restore attention and help the learner rehearse the meaning before high-stakes assessment begins.

“Short lessons make serious topics superficial”

Enterprise: Our material is complex. We cannot reduce it to social-media clips.

Learning designer: Short is not the same as shallow.

A three-to-five-minute video should answer one clear question. The next lesson can answer the next one. Together, those lessons can contain the full subject with more useful signposts, easier recaps, and fewer places to get lost.

Long-form video can be valuable when an uninterrupted demonstration or argument genuinely needs time. It should not be the default simply because recording one lecture was easier for the producer. As we explain in Why short lessons beat long videos in professional education, the unit of content should follow the learner’s task, not the recording session.

“Interaction means a live instructor”

Enterprise: A digital course cannot notice the room, answer a raised hand, or create a human connection.

Learning designer: Correct. Async should not impersonate a live room. It should do what preparation can do better.

It can provide the clearest reviewed explanation to every learner. It can pause for a decision at exactly the right moment. It can offer a diagram, demonstration, download, optional explanation, short recap, and active-recall prompt without rushing the group. It lets a learner stop after an interruption and return to a meaningful boundary instead of searching through an hour-long recording.

Human support can remain. Questions, feedback, office hours, workshops, and expert discussions can sit around the reusable foundation. Async is not always best; live time is especially valuable for ambiguity, practice, sensitive discussion, and judgement.

What respectful async feels like

A learner should feel movement without losing the whole subject. That usually means:

1. One clear purpose per lesson. The learner knows why this part matters.
2. Brief, direct explanation. Video is used when seeing or hearing improves understanding—not merely because a camera was available.
3. Frequent, simple participation. Prompts and questions help the learner think without turning every screen into a test.
4. A change of format when the task changes. Video, text, diagrams, examples, downloads, and exercises each do different jobs.
5. Visible progress and easy return points. Interruption does not destroy the learning session.
6. Assessment proportional to the stakes. Practice supports learning; formal testing verifies only what must be verified.
7. A route to a person. Learners know where to ask a real question when the prepared path is not enough.

This is not “adding engagement” as decoration. It is doing more of the teaching work during production so the student does not have to reconstruct the course alone.

“That sounds like more work”

Enterprise: It is much quicker to upload the lecture and attach five questions.

Learning designer: It is quicker to publish. It is not necessarily quicker to teach.

The cost appears later as resistance, repeated questions, weak recall, support requests, and another live explanation. A designed course moves that effort forward: clarify the outcome, divide the knowledge, choose the right medium, build memory cues, test the path, and revise weak lessons.

That preparation creates a reusable and maintainable learning asset. Our article on granular updates explains why modular content is also easier to correct when a process, law, or product changes.

What our learners told us

Across our work with well over 1,000 learners, we have received more than 400 learner reviews. The response has been consistently positive, and a recurring comment is that this approach fits professional learning well.

We do not read that as proof that every subject belongs online or that one format guarantees an outcome. We read it as strong practical evidence against a common assumption: professionals do not inherently resist asynchronous learning. When content is concise, varied, interactive, and built around their reality, many value precisely the autonomy and focus it gives them.

Closing statements

Enterprise: So employees do not hate async?

Learning designer: They may hate your async course. Listen to that reaction. But diagnose the course before blaming the medium.

Asynchronous learning is not futuristic, and it is not an automatic improvement. It is a production choice. Used lazily, it turns lectures and documents into individual homework. Used thoughtfully, it gives professionals a clear path through exactly what they need to learn—and saves live human attention for the moments that truly need it.