Process and Pitfalls in Writing Information Visualization Research Papers - Information Visualization: Human-Centered Issues and Perspectives - page 134

Process and Pitfalls in Writing
Information Visualization Research Papers

Tamara Munzner

Department of Computer Science,University of British Columbia
201-2366 Main Mall, Vancouver BC V6T 1Z4 Canada,
[e-mail] ,
http://www.cs.ubc.ca/ ~ tmm

Abstract. The goal of this paper is to help authors recognize and avoid
a set of pitfalls that recur in many rejected information visualization
papers, using a chronological model of the research process. Selecting a
target paper type in the initial stage can avert an inappropriate choice
of validation methods. Pitfalls involving the design of a visual encoding
may occur during the middle stages of a project. In a later stage when
the bulk of the research is finished and the paper writeup begins, the
possible pitfalls are strategic choices for the content and structure of the
paper as a whole, tactical problems localized to specific sections, and
unconvincing ways to present the results. Final-stage pitfalls of writing
style can be checked after a full paper draft exists, and the last set of
problems pertain to submission.

1 Introduction

Many rejected information visualization research papers have similar flaws. In
this paper, I categorize these common pitfalls in the context of stages of the
research process. My main goal is to help authors escape these pitfalls, espe-
cially graduate students or those new to the field of information visualization.
Reviewers might also find these pitfalls an interesting point of departure when
considering the merits of a paper.
This paper is structured around a chronological model of the information
visualization research process. I argue that a project should begin with a careful
consideration of the type of paper that is the desired outcome, in order to avoid
the pitfalls of unconvincing validation approaches. Research projects that involve
the design of a new visual encoding would benefit from checking for several
middle-stage pitfalls in unjustified or inappropriate encoding choices. Another
critical checkpoint is the late stage of the project, after the bulk of the work is
done, but before diving in to writing up results. At this point, you should consider
both strategic pitfalls about the high-level structure of the entire paper, tactical
pitfalls that affect one or a few sections, and possible pitfalls in the specifics of
your approach to the results section. At a final stage, when there is a complete
paper draft, you can check for lower-level pitfalls of writing style, and avoid
submission-time pitfalls.