Post History
In a technical tutorial it is helpful for a user to be able to check their progress often. Veryfing that the steps have produced a result is good because the user: has a feeling of progress can c...
Question
technical-writing
#3: Attribution notice added
by
System
·
2019-12-08T09:25:42Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/37728 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
System
·
2019-12-08T09:25:42Z (almost 5 years ago)
In a technical tutorial it is helpful for a user to be able to check their progress often. Veryfing that the steps have produced a result is good because the user: - has a feeling of progress - can check for any mistakes they've made However, I'm working with advanced tutorials aimed at developers who are extending a complex product. Sometimes the tutorials require adding and modifying code in multiple files, before any effect can be previewed. **How can I design a tutorial when it is impossible to check the progress in the meantime?** What methods can I use to ensure 1) that the user stays motivated to finish all steps and 2) to minimize the risk of the user making small mistakes that will be hard to trace at the end?
#1: Imported from external source
by
System
·
2018-07-18T11:41:03Z (over 6 years ago)
Original score: 28