Test first, learn second.

Design · 4 min read

I was designing an education app and we kept getting stuck on the same question: how does the user start? Do we ask them what they already know? Do we give them a quiz to assess their level? Do we show them a menu of topics and let them choose?

Every option added friction. An assessment quiz feels like a test before you've even started. A topic menu means the user has to know what they don't know, which is the whole reason they're here. And "start from the beginning" wastes the time of anyone who already knows the basics.

Then we flipped it. What if the first thing they do is take the real exam?

Failure is the curriculum

The user opens the app and takes the full practice exam. No prep. No study. Just a hundred questions across every topic. They fail. Of course they fail. That's the point.

But now the app knows exactly where the gaps are. Section three, you got 40%. Section seven, you got 20%. Section one, you nailed it. The results become the learning plan. The topics you failed are the topics the app focuses on. No need for an onboarding quiz. No need for a self-assessment. The exam itself is the assessment.

There's a name for this in learning science -- the testing effect. A study published in Psychological Science (Roediger and Karpicke, 2006) found that people who are tested on material remember more of it than people who just keep studying. Trying and failing wires it in better than re-reading ever does.

When we pitched this to the client, he paused and said "that actually ticks a lot of boxes." Because it solves the problem for every type of user at once.

One flow for every user type

The app had three very different audiences. Beginners who needed to learn everything. Experienced professionals brushing up on specific areas. And people from overseas who knew the subject but needed to learn the local standards. Normally, you'd build three onboarding paths. Three sets of questions. Three different starting points.

With the test-first approach, all three users do the same thing. Take the exam. The beginner fails most sections. The professional passes most and fails a few. The overseas user passes the technical stuff and fails the local compliance questions. Same starting action, three completely different learning paths generated automatically.

No branching logic. No onboarding wizard. No "tell us about yourself" form. Just one button: "Start the exam."

Remove the choice to remove the friction

Most apps give users too many choices upfront. Pick your goal. Pick your level. Pick your learning style. Pick your schedule. Every choice feels small, but stacked together they create a wall of decisions before the user has done anything useful. And most users don't know the right answers to those questions anyway.

If your app can figure out what the user needs from their behaviour instead of their answers, skip the questions entirely. Let them use the product. Watch what happens. Then personalise based on real data, not self-reported guesses.

The fastest onboarding is no onboarding at all. Just let them start.

Related blog posts:

Your app should know more than your user →

The default matters more than the option →

Fewer screens forced better thinking →