When technical communicators sit down to draft a manual, the instinct is often to document every feature, edge case, and configuration. “Completeness” becomes the metric of success. However, academic research in instructional design and technical communication suggests this comprehensive approach often backfires. To create truly effective documentation, you must prioritise functionality and structure over exhaustive coverage. The goal is not to document the system but to resolve the majority of user issues. Specifically, the “vital few” that cause the most friction.

The Science of “Less is More”

The argument for completeness typically relies on the assumption that more information leads to better understanding. However, empirical evidence contradicts this. A landmark meta-analysis by Ginns et al. (2006) reviewed the effectiveness of “minimalist” instruction—a paradigm that slashes excessive wordiness and focuses on real tasks. The results were striking: minimalist documentation produced a large positive effect on learning outcomes (d = 1.12) compared to traditional, system-centred manuals.

This superiority stems from the “paradox of sense-making” identified by Carroll (1990). Users are often too busy trying to accomplish a task to read long explanations. When manuals attempt to be complete, they bury critical information under layers of “nice-to-know” detail, increasing cognitive load and making it harder for users to find the specific guidance they need to act (van der Meij & Carroll, 1995).

Applying the Pareto Principle

To resolve 80% of user cases, you do not need 80% of the possible information. You need the right 20%. This is an application of the Pareto Principle (80/20 rule), which states that roughly 80% of effects come from 20% of causes. In the context of error analysis, O’Neill (2018) demonstrated that focusing on the “critical few” errors—the top frequent issues—can resolve the vast majority of problems.

For a manual, this means:

  1. Identify the Vital Few: Analyse support tickets or user observations to find the top 20% of tasks that users perform 80% of the time.
  2. Prioritise Recovery: Instead of documenting every setting, focus on “error recognition and recovery” (van der Meij & Carroll, 1995). Users don’t open manuals when things work; they open them when things break.
  3. Relegate the exceptions: If a scenario affects only 1% of users, documenting it in the main workflow degrades the experience for the other 99%. Relegate these exceptions to a searchable appendix or knowledge base, keeping the core manual lean.

Structure as the solution

If you strip away the “completeness”, what remains must be highly structured. Horn (1993) argued for “structured writing”, where information is chunked into discrete, labelled blocks based on relevance. This approach ensures that every paragraph has a specific purpose, whether it is a concept, a procedure, or a principle.

Redish (2012) reinforces this with her mantra of “letting go of the words.” The modern user starts as a scanner and then may become a reader if they are interested in the topic. A manual designed for functionality uses clear headings, bulleted lists, and “information maps” to help users locate their specific problem immediately. This structural clarity allows a smaller, focused manual to outperform a larger, comprehensive one because the user can actually find the solution.

Conclusion

Striving for 100% completeness is a futile pursuit that leads to unusable “bloatware” documentation. This stems from the writer’s fear of accountability and the potential accusation of omitting information. By focusing on the vast majority of common cases through a strict application of the Pareto Principle and minimalist design, you create a tool that respects user time. Prioritise functionality and structure, leaving exceptions for the appendix.

Selected references

Carroll, J. M. (1990). The Nurnberg funnel: Designing minimalist instruction for practical computer skill. MIT Press.

Ginns, P., Hollender, N., & Reimann, P. (2006). Meta-Analysis of the Minimalist Training Model. https://files.eric.ed.gov/fulltext/ED491708.pdf

Horn, R. E. (1993). Structured writing as a paradigm. In Instructional designs: The state of the art (pp. 341–378). Educational Technology Publications.

O’Neill, K. S. (2018). Applying the Pareto Principle to the analysis of students’ business communication errors. Journal of Instructional Pedagogies, 20. https://files.eric.ed.gov/fulltext/EJ1178476.pdf

Redish, J. (2012). Letting go of the words: Writing web content that works (2nd ed.). Morgan Kaufmann.

van der Meij, H., & Carroll, J. M. (1995). Principles and Heuristics for Designing Minimalist Instruction. Technical Communication, 42(2), 243–261. http://www.jstor.org/stable/43087895