CATEGORIZINGSCENARIOS:A QUIXOTICQUEST? Robert L. Campbell I'm pleased to discover how many HCI practitioners are busy thinking about all this scenario talk. I wish I'd known about some of the work reported in this issue (particularly Jakob Nielsen's contribution, and that of Richard Young and Phil Barnard) before I launched my squib. All in all, the rough-hewn category system that I proposed (i.e., (1) illustrating the system; (2) evaluation; (3) design; and (4) theory-testing) has held up pretty well. Jakob Nielsen (1990), in an independent effort, proposed a taxonomy that covers the same territory as these four categories. But ! part company with Nielsen when he extends the term "scenario" all the way to storyboards and mockups (which I think belong in the prototype family), and even to interactive tutorials. Bonnie Nardi's conception of a scenario is clearly design-oriented; indeed, she claims that when the prototypes are ready, and empirical evaluation begins, her sort of scenario loses its relevance. David Reisner explicitly places his examples in the system demonstration and design categories. I might also mention a report that I received from Gil Ricard of Grumman, which describes a single, highly elaborated airborne early warning scenario, based on a
/lp/association-for-computing-machinery/categorizing-scenarios-a-quixotic-quest-hP6sZ9mm8G