By the TopicLearn teamA reflect and write exercise asks you to put an idea you just learned into your own words and connect it to something you already know. There's no answer key to match, and that's deliberate: the value is in the writing itself. It's the step where the material stops being something you read and starts being something you can say.
What the exercise looks like
The prompt is specific and personal rather than "summarize this section." Something closer to: how would you explain superposition to your younger self? Below it, an empty text box. No grade, no model answer sitting there to measure yourself against.
That phrasing does two jobs. It pulls you out of the source's vocabulary, so you have to pick words yourself. And it demands a link to something already in your head: the kid you used to be, a job you've held, a field you genuinely understand.
Compare that with "summarize this section," which you can finish by rearranging sentences you read ninety seconds ago. A prompt aimed at one particular person can't be closed that way. You have to decide what they already know, what to leave out, and which word will land wrong with them. Every one of those decisions needs you to be holding the idea, not the page.
Why writing it out finds the holes
A good explanation reads smoothly, and that smoothness is misleading. It's easy to mistake the author's command of the subject for your own. The moment you start writing, the author isn't there to arrange the sentence for you.
To write an explanation you have to choose words, choose an order, and choose an example. When any one of those stalls, you've got the exact address of the gap.
Here's how that plays out. You can write "superposition means a particle is in two states at once" without effort, then stall completely when you try to say what "at once" means and what happens when someone measures it. The stall is the finding.
Saying it in your head doesn't count
The feeling of "sure, I could explain this" isn't the same test. Thought runs fast and skips the joins without telling you it skipped them. Writing is slow enough that you can't: you commit to one word instead of a cloud of nearly-right ones, and you're left with a text you can go back and read. That text is most of the value, because a vague sentence looks vague on the page in a way it never does inside your head.
Connecting it to what you already know isn't decoration
Elaboration works by hanging new material on a structure that's already there. A fact with one link to something familiar has a route back to it. A fact floating on its own doesn't. That's why the prompt asks for the connection outright instead of leaving it to chance.
Where it sits in a lesson
The writing step comes after the explanation, and usually after a recall check too, not before either. You need something to reflect on first. Each format in a lesson asks a different question:
- A recall check asks whether the fact is retrievable at all.
- A drag and match asks whether you can tell near neighbors apart.
- A reflect and write asks whether you can produce the explanation yourself, in a form nobody handed you.
Active recall and spaced review are planned into a course's lesson sequence from the start, so a concept you wrote about early tends to resurface later in a form that asks you to use it again rather than recognize it.
How to get more out of it
- Write it for a specific person. A blurry audience produces blurry writing. Your younger self, or a colleague from a different field, both work.
- Use an example that wasn't in the lesson. A ready-made example lets you reproduce the shape of an explanation without understanding it.
- Don't smooth over the part you're unsure about. Write the sentence that feels uncomfortable to write, and watch where it breaks.
- Keep it short. Four or five lines. Long answers drift back into restating the text you just read.
What to do with the answer afterward
Most people write the answer and move straight on. It's worth more than that, and using it costs almost nothing.
- Reread it immediately and mark any sentence you'd struggle to defend if someone asked "why, though?"
- Come back to it before the next lesson in the course. Whatever reads as fuzzy a day later is the part to revisit, and it's usually not the part you expected it to be.
- Set it next to the lesson's own explanation and look for what you left out, not what you got wrong. Omissions are where the understanding is thin.
When it's the wrong format
At the very start of a subject, when there's nothing yet to connect to, the prompt produces a paraphrase instead of understanding. It's also a poor fit for skills that are mostly execution: running code, drilling keyboard shortcuts, working through a calculation. Doing beats describing there. TopicLearn picks the exercise format to fit the subject, so a code-heavy lesson leans on the code runner while a concept-heavy one leans on writing.
If the answer came out easily, you knew the material. If it came out awkward and half-finished, you found the sentence worth going back to. Either way those three minutes returned information that rereading never does.