Using Basic Organizational Patterns

Every document calls for its own organizational pattern. You should begin by asking yourself whether a conventional pattern for presenting your information already exists. A conventional pattern makes things easier for you as a writer because it serves as a template or checklist, helping you remember which information to include in your document and where to put it. For your audience, a conventional pattern makes your document easier to read and understand because the organization of information meets readers’ expectations. When you write a proposal, for example, readers who are familiar with proposals can find the information they want in your document if you put it where others have put similar information. This Choices and Strategies box explains the relationship between organizational patterns and the kinds of information you want to present.

Does this mean that technical communication is merely the process of filling in the blanks? No. You need to assess the writing situation continuously as you work. If you think you can communicate your ideas better by modifying a conventional pattern or by devising a new pattern, do so. Long, complex arguments often require several organizational patterns. For instance, one part of a document might be a causal analysis of a problem, and another might be a comparison and contrast of two options for solving that problem.