A Critical Assessment of the Minimalist Approach to Documentation  

Carroll's (1991) minimal manual has been considered an important advance in teaching first-time users the basics of computer programs. Unfortunately, it is not very clear what minimalism really means. Practitioners, for example, will find it difficult to create their own minimal manual because the principles of minimalism have not been described in enough detail (see Horn, 1992; Tripp, 1990). It is also not yet settled that a minimalist approach is the most effective one because critical experiments have hardly been conducted. This study therefore closely examines the minimalist principles and claims. This paper describes the basic ideas of minimalism, its design principles and how they can be operationalized. A parallel is drawn between a minimalist and constructivist perspective on learning and instruction. Like minimalism, constructivism places a high value on experience-based learning in context-rich environments. Like minimalism, it stresses the need to capitalize on the learner's prior knowledge as much as possible. And like minimalism, constructivists urge learners to follow their own plans and goals, to make inferences, and to abstract principles from what they experience (see Duffy & Jonassen, 1991, 1992). An experiment is reported that examines the claims of minimalism. Strong and significant gains on several factors were found, all favoring the minimal manual over a control (conventional) manual. The discussion points to several issues that minimalism has yet to address.

van der Meij, Hans. ACM SIGDOC (1998). Articles>Documentation>Technical Writing>Minimalism

Effects of Pictures, Age, and Experience on Learning to Use a Computer Program    

Research indicates that older people generally do not process information differently than younger people do. Instead, 'the main difference ... seems to be that elderly users are less capable in dealing with any shortcomings in the manuals than younger users. The impact of badly designed manuals is usually greater for elderly people,' (van Hees 1996, p. 531). In line with this view, Hartley (1994) suggests that 'text will be easier for older people to use when their perceptual and memory processing loads are reduced' (p. 171). Although the criteria for good design remain a bit unclear, we can accept the general idea that designing well will help the elderly.

van der Meij, Hans and Mark Gellevij. Technical Communication Online (2002). Design>Accessibility>Software>Elderly

Examining the Relationship Between Quality Writing and Quality Reading    

This article introduces the ISTE approach as a way to measure the relationship between the design of a document and the way that users handle it. ISTE is an acronym for Information SubTypes and Effects. The article describes the classification of information into a general typology as well as into a specific one, to illustrate how the approach can be adapted to specific usability questions. ISTE also requires a typology for categorizing possible user reactions. This article first positions ISTE within the broader context of usability testing and then describes its basic approach and some recent applications. Unlike most formal research methods, ISTE does not require an inordinate amount of time and effort for analyzing high-fidelity data. Electronic versions such as the ERR instrument allow for the creation of a complete and detailed profile of the use of a document 10 minutes after task completion. These characteristics make ISTE a viable instrument for gathering usability metrics in industrial settings.

van der Meij, Hans. Technical Communication Online (2000). Articles>Usability>Testing>Assessment

Screen Captures in Software Documentation    

While screen captures are the most widely used illustrations in manuals, there is almost no literature on their role and design. In this paper we draw together practice, theory and empirical research to advance a taxonomy that identifies these roles and designs. We suggest that screen captures in software documentation can help the user to switch attention, develop a mental model of the program, verify screen states, and identify and locate window elements and objects. Four important design areas (coverage, positioning, size, and cueing) are distinguished and empirical findings discussed. Research has substantiated the claim that screen captures speed up task completion, but others have yet to be proven. We believe that a more refined approach, afforded by the taxonomy, is likely to improve practice and research, and yield strong evidence supporting the use of screen captures in software documentation.

van der Meij, Hans and Mark Gellevij. Technical Communication Online (1998). Articles>Software>Documentation>Screen Captures

Three Decades of Research and Professional Practice on Printed Software Tutorials for Novices    

Provides a historic overview of research on printed software tutorials. Describes developments in design approaches, refinements in design, and user experience.

van der Meij, Hans, Joyce Karreman and Michaël Steehouder. Technical Communication Online (2009). Articles>Documentation>Help>User Experience