Two tutorials can reach the same result while demanding very different amounts of background knowledge. A useful comparison is not simply which one is shorter. Ask what a beginner must already know to follow each explanation.
Consider these invented instructions: “Export the file,” and “Use Export, choose the requested format, then open the saved file to check it.” The second gives a clearer endpoint, but may still leave the save location unexplained.
Try marking three kinds of information in a tutorial: the action, the reason for it, and the evidence that it worked. Missing information is not always a flaw; an advanced guide may reasonably assume knowledge that a beginner guide needs to provide.
Turn one gap into a question
Instead of writing “this tutorial is confusing,” identify the gap: “I do not know whether Export changes the original or creates another file.” That question can be checked against the tool’s official documentation before practising.
Do not combine instructions from different versions without noticing their differences. A menu name or feature may have changed. Record the product and version when they matter to the task.
The aim is not to produce the longest possible tutorial. It is to make the necessary decisions visible. When evaluating your own instructions, ask another reader to identify the next action and the expected result; the point where they must guess is a useful place to revise.

