DiwaX: pause a tutorial at the moment before, during and after an action

Use three pauses to understand a DiwaX tutorial: inspect the starting state, identify the actual input and compare the resulting state carefully.

The cursor moves, a panel changes and the narrator says, “Now continue.” A beginner replays the clip but still cannot explain what caused the change. Watching it more often may not solve the problem if every replay skips over the same missing action. For DiwaX readers, we use three deliberate pauses: just before the input, at the input and after the result. Each pause answers a different question about the demonstration.

Before the movement

Our invented tutorial shows a web-based shape exercise. Initially, a square is outlined, a circle is unselected and a button reads Apply. The exercise's teaching rule says selecting a shape previews it, while Apply commits that selection. No actual product interface is being described. At the first pause, record exactly this starting state: square previewed, circle not selected, Apply available. Without that baseline, later changes are easy to misremember.

Ask what you can observe before asking what it means. An outline around a square is visible. Calling that square “submitted” would be an interpretation requiring the rule's support. Here the teaching rule calls it a preview. Keep that vocabulary consistent. A narrator may casually say chosen, selected or ready, but those words can refer to different stages. The learner benefits from one precise label tied to the stated operation rather than a succession of loose synonyms.

At the actual input

In the second pause, the cursor is over the circle and the tutorial shows a click. Immediately afterwards the circle gains an outline. That explains the preview change, not the final submission. Continue slowly enough to inspect whether the cursor later reaches Apply and whether a second input is shown there. The point is to identify actions, not infer them from the eventual appearance. One visible click and two visible clicks describe different demonstrations.

Now suppose the video jumps from the outlined circle to a result panel without showing Apply. The missing interval matters because our stated rule includes a commitment step. We cannot tell from the cut alone whether the creator clicked Apply, used another permitted input or omitted part of the demonstration. Label the action as not shown. A useful tutorial can repair this by retaining the relevant input or adding a clear annotation explaining the omitted step.

After the response

At the third pause, a result panel says “Circle recorded”, and the next exercise appears. Compare it with the first state: the square preview has been replaced by a recorded circle, and the task has advanced. That is stronger information than merely saying the screen changed. However, the result does not retrospectively show the missing input. The final state tells us what is displayed now; the action record explains how the tutorial demonstrates reaching it.

Use a compact three-part transcript: before, square preview; input, circle clicked and Apply clicked; after, circle recorded. When Apply is absent from the clip, write “commitment input not shown” in the middle instead of completing the transcript from memory. This is especially helpful when comparing two DiwaX demonstrations. Their results might agree while one is much easier to learn from because it preserves the causal steps the other edits away.

A slow animation can create a different confusion. If the narrator starts describing the next task while the previous result is still appearing, the viewer may associate the spoken instruction with the wrong screen. Pause using visible state changes rather than sentence boundaries alone. We ask learners to point out which task the words concern. A short label such as “still completing task one” can restore the connection without requiring the whole video to be narrated again.

After the three pauses, attempt a verbal replay with the video stopped. Say what is initially selected, which input changes the preview, which input commits it and what confirms completion. If one link remains unknown, identify that link. Do not replace it with “probably”. The exercise distinguishes following a movement from understanding a state transition. It also gives a tutorial creator a concrete improvement: retain the one missing input instead of adding unrelated explanation around it.

Imagine the repaired clip now keeps both clicks. The learner sees square previewed, circle clicked, Apply clicked and circle recorded. They can explain the same sequence without the narrator. The DiwaX viewing task has achieved its purpose: three pauses have turned an impression of activity into an intelligible chain of states and inputs. On the next tutorial, start with the moment before the change; that is often where the detail needed to understand the action is waiting.