Engagement Is Not Learning. I Look for What Survives the Screen.

Two people can spend the same 30 minutes with the same learning tool and come away with very different things.

One finishes levels, collects points and gets most answers right with the help of hints.

Another closes the tool and can later explain the idea, use it somewhere else or create something from it.

Both were engaged. Only one result tells us much about what actually stayed.

Engagement happens inside the tool. Learning should be able to travel beyond it.

Progress bars measure activity better than understanding

Digital learning tools are very good at making activity visible.

Minutes used. Lessons completed. Correct answers. Streaks. Stars. Levels.

These signals are useful. They tell us that something happened.

They do not tell us whether the learner can still do the important part without the scaffold around them.

Imagine a maths app that gives a hint after every mistake. The learner may finish ten problems successfully.

Now remove the hints and change the numbers.

Can they still solve the problem?

That second question tells us something the progress bar cannot.

The useful question is what survives the interface

Good learning tools are designed to help. They give hints, highlight the next step, break problems into smaller pieces and now increasingly use AI to generate explanations.

That support can be exactly what a learner needs.

But smooth support creates a hidden question:

How much of the successful performance belongs to the learner and how much belongs to the interface?

This is not a reason to remove scaffolding. It is a reason to occasionally test what remains when some of the scaffolding disappears.

I use a simple Explain → Use → Create test

After learning something with a digital tool, I find three checks more interesting than the score inside the app.

• Explain: Can the learner explain one idea without reopening the tool?
• Use: Can they apply the idea in a slightly different situation?
• Create: Can they draw, build, write, demonstrate or ask a new question from what they learned?

You do not need all three.

If someone watches a video about bridges then changes a design after a model collapses, something travelled beyond the screen.

If a vocabulary tool teaches a new word and that word appears naturally later, something travelled.

If a coding tutorial explains loops and the learner later notices repeated code and knows why it can be simplified, something travelled.

That evidence is messier than a score of 92%.

It is also much closer to what I actually care about.

The test becomes useless if every session turns into an exam

There is an obvious failure mode here.

Not every learning session needs a measurable output. Curiosity, exploration and even getting temporarily confused can be useful.

If every interesting video ends with “now prove what you learned”, the tool may survive but the curiosity may not.

So I treat Explain → Use → Create as something to notice, not something to administer constantly.

Transfer often appears on its own. A learner starts drawing a concept, uses a new word, changes how they build something or asks a question that did not exist before.

This changes how I judge learning tools

I am less interested in whether a tool can keep someone busy for 30 minutes.

I am more interested in whether it leaves behind a capability that still works when the tool is gone.

That gives me a simple design and learning question:

What crossed the boundary between the interface and the learner?

A good learning tool should eventually leave the learner with something they can carry away from it.