Why do people click through our course instead of learning?

You and your team can build the thing now. The slides, the quizzes, the branching paths — that part you solved. Then you watch someone click through it the way they click through anything, eyes forward, mind somewhere else, and you know something did not land. Here is what you are not saying to each other: the problem is not the software. You have that. The problem is you are still building for completion — for the checkmark at the end — instead of building for the moment a person has to think. Those are different work. One finishes alone at a desk. The other asks you to imagine, honestly, what it feels like to not yet understand. No new tool fixes this. A different question does, asked together at every screen: what must this learner produce in their own head before we hand them the answer? Ask it as a team, out loud, on every module, and you will find the clicks that were only decoration.

◆ How this problem reads on the two dials

GuidanceKnowledge

Coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

The team needs the design principle taught plainly, then needs to be pushed to apply it screen by screen — half instruction, half action.

How the two dials adapt to you →

What’s really going on

Engagement is not a feature you add. It is a demand you make on the learner's mind. If someone can finish your course without thinking, you built a slideshow, not a lesson. Stop polishing screens. Start forcing a guess, a struggle, a wrong answer — before you ever show them the right one.

🔒 What you’ll build togetherUnlock by starting

A moveBefore building the next screen, write down what the learner must produce in their own mind — not what they must click.

A moveTake one quiz question and remove the easy option. Make the learner commit to an answer before you reveal anything.

A moveReview a finished screen as a group and ask out loud: could someone pass this without understanding it? If yes, rebuild it.

A moveAssign one person in the pod the job of the skeptical learner — they hunt for shortcuts and patterns that let them cheat the module. Fix what they find.

A moveDelay every correct answer by one extra screen. Force a guess first, always.

PractiseThe Skeptical Learner Pass · a Pod of 4 · 30 min

What changes unlock by starting

Your team can state, in one sentence, the difference between a completion screen and a thinking screen.
You catch and rebuild the clickable-without-thinking moments before launch, not after a learner proves it.
Your pod has a shared test — could someone pass this without understanding it? — to run on every future module.
Learners spend more time hesitating, guessing, and correcting themselves inside the course, and less time coasting.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.