Making sense of step-by-step procedures

Procedural instructions that consist of only a sequence of steps will probably be executable, but nevertheless "meaningless" to users of technical devices. The paper discusses three features that can make procedural instructions more meaningful: adding functional coordinating information, adding information about the use of the technical device in real life, and adding operational information about how the device works. The research literature supports the effectiveness of the first feature, but offers little evidence that real life elements enhance understanding of instructions. As for operational information, the research suggests that users are willing to read it, and that it contributes to better understanding and performance in the long term, but only if it is closely related to the procedure. As a conclusion, we propose a theoretical framework that assumes three levels of mental representation of instructions: syntactical, semantic, and situational.

[1]  Nicole Ummelen Procedural And Declarative Information In Software Manuals. , 1997 .

[2]  Jo-Anne LeFevre,et al.  Processing instructional texts and examples. , 1987 .

[3]  Ben Shneiderman,et al.  Designing The User Interface , 2013 .

[4]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[5]  R. F. Lorch,et al.  Text-signaling devices and their effects on reading and memory processes , 1989 .

[6]  P. Dixon Actions and procedural directions , 1987 .

[7]  M. Just,et al.  The psychology of reading and language comprehension , 1986 .

[8]  David K. Farkas The Logical and Rhetorical Construction of Procedural Discourse , 1999 .

[9]  Russell S. Tomlin,et al.  Coherence and Grounding in Discourse: Outcome of a Symposium, Eugene, Oregon, June 1984 , 1987 .

[10]  Alan Cooper,et al.  The Inmates are Running the Asylum , 1999, Software-Ergonomie.

[11]  Barbara Mirel,et al.  Analyzing audiences for software manuals: A survey of instructional needs for “real world tasks” , 1992 .

[12]  William Horton Secrets of User-Seductive Documents: Wooing and Winning the Reluctant Reader , 1997 .

[13]  Nicole Ummelen Declarative information in software manuals: what's the use? , 1997, SIGDOC '97.

[14]  Peter Dixon,et al.  Learning to Operate Complex Devices: Effects of Conceptual and Operational Similarity , 1991 .

[15]  J. LeFevre,et al.  Do Written Instructions Need Examples , 1986 .

[16]  John M. Carroll,et al.  Learning to use a word processor: by doing, by thinking, and by knowing , 1984 .

[17]  Jm Noyes Review of Procedural and declarative information in software manuals: Effects on information use, task performance and knowledge by Ummelen, N , 1998 .

[18]  P. Dixon The processing of organizational and component step information in written directions , 1987 .

[19]  Edward E. Smith,et al.  Understanding Written Instructions: The Role of an Explanatory Schema , 1984 .