Chapter 4: Document Design

4.7: Tables, Charts, and Graphs

By: David McMurrey and Tamara Powell

Objectives


Upon completion of this chapter, readers will be able to do the following:

  1. Distinguish between tables, charts, and graphs.
  2. Identify chief characteristics of tables, charts, and graphs.
  3. Identify and apply best practices in creating tables, charts, and graphs in technical communication.

Introduction to Tables, Charts, and Graphs

One of the nice things about technical writing courses is that most of the papers have graphics in them—or at least they should. A lot of professional, technical writing contains graphics—drawings, diagrams, photographs, illustrations of all sorts, tables, pie charts, bar charts, line graphs, flow charts, and so on. Graphics are important in technical communication. We learn more from a document when graphics are included (Gatlin, 1988). In fact, people learn about 1/3 more from a document with graphics than without (Levie and Lentz, 1982). A recent study found that readers learn faster and are better able to use the information they learn when the text includes graphics (Große,Jungmann, and Drechsler, 2015). That does not, of course, mean that one should place graphics willy-nilly into every spot possible. On the contrary, graphics should be used carefully and correctly. The information below will help you to make informed decisions regarding graphic creation and placement that will help to make your documents more effective for your readers.

Tables

Tables, of course, are those rows and columns of numbers and words, mostly numbers. They permit rapid access to and relatively easy comparison of information. If the data is arranged chronologically (for example, sales figures over a ten-year period), the table can show trends—patterns of rising or falling activity. Of course, tables are not necessarily the most vivid or dramatic means of showing such trends or relationships between data—that's why we have charts and graphs (discussed in the next section).

Uses for Tables

The biggest use of tables is for numerical data. Imagine that you are comparing different models of laser printers in terms of physical characteristics such as height, depth, length, weight, and so on. Perfect for a table.

However, don't get locked into the notion that tables are strictly for numerical data. Whenever you have situations where you discuss several things about which you provide the same categories of detail, you've got a possibility for a table. For example, imagine that you were comparing several models of a laser printer: you'd be saying the same category of thing about each printer (its cost, print speed, supply costs, warranty terms, and so on). This is ideal stuff for a table, and it would be mostly words rather than numbers (and in this case, you'd probably want to leave the textual discussion where it is and "re-present" the information in table form).

Table Format

In its simplest form, a table is a group of rows and columns of data. At the top of each column is a column heading, which defines or identifies the contents of that column (and often it indicates the unit of measurement). On the left edge of the table may be row headings, which define or identify the contents of that row. Things get tricky when rows or columns must be grouped or subdivided. In such cases, you have to create row or column subheadings. This situation is illustrated here:

Figure 1

Figure 1: Format for tables with grouped or subdivided rows and columns. Notice that the table title goes above the table.

Traditionally, the title of a table is placed on top of the table or is the first row of the table. If the contents of the table are obvious and there is no need to cross-reference the table from anywhere else in the report, you can omit the title.

As for specific style and formatting guidelines for tables, keep these in mind:

Producing Tables

Normally, you'll be borrowing information in which a good table occurs. If it's a simple table without too many rows and columns, retype it yourself into your own document (but remember to document where you borrowed it from in the figure title). However, if it is a big table with lots of data, you're justified in scanning, screen-capturing, or photocopying it and bringing it into your report that way.

If you use OpenOffice, Word, or WordPerfect, get used to using the table-generating tools. You don't have to draw the lines and other formatting details.

Occasionally, in rough-draft technical reports, information is presented in regular running-text form that could be better presented in table (or tabular) form. Be sure and look back over your rough drafts for material that can transformed into tables.

Figure 2

Figure 2: Example of information included in text that would be better represented in a table.

Charts and Graphs

Charts and graphs are actually just another way of presenting the same data that is presented in tables—although a more dramatic and interesting one. At the same time, however, you get less detail or less precision in a chart or graph than you do in the table. Imagine the difference between a table of sales figures for a ten-year period and a line graph for that same data. You get a better sense of the overall trend in the graph but not the precise dollar amount.

More information on creating charts in MS Word

Formatting Requirements

When you create charts and graphs, keep these requirements in mind (most of these elements are illustrated below):

Figure 3

Figure 3: Example of a line graph.

Example of a Graph

Notice that a figure title is placed beneath the graph.

Producing Charts and Graphs

As with illustrations, you have these options for creating charts and graphs: screen-capturing, scanning, photocopying, generating your own with software, and drawing your own.

Helpful downloads to jumpstart your graph creation

Documenting Tables, Charts, and Graphs: Indicating Sources

As mentioned earlier, it's perfectly legal to borrow tables—to copy, photocopy, scan, or extract subsets of data from them. But you're obligated to cite your sources for tables, charts, and graphs just as you are for the words you borrow. Normally, this is done in either the table title or in a footnote just below the table. Check the example in the table shown previously.

General Guidelines for Tables, Charts, and Graphs

The preceding sections state a number of common guidelines that need to be stated all in one place. These are important!

Best Practices for Creating Graphics in Technical Writing: Examples

What are best practices for creating graphics? How can one mess up when adding a graphic to technical communication? This video will show you how to do things correctly and incorrectly.

Graphics in Technical Writing

For more information and examples on how NOT to create graphs, please look at C.J. Schwarz' "A Short Tour of Bad Graphs." Shared with permission.

References

Gatlin, P. L. (1988). Visuals and prose in manuals: The effective combination. In Proceedings of the 35th International Technical Communication Conference (pp. RET 113-115). Arlington, VA: Society for Technical Communication.

Große, C. S., Jungmann, L., & Drechsler, R. (2015). Benefits of illustrations and videos for technical documentations. Computers In Human Behavior, 45109-120. doi:10.1016/j.chb.2014.11.095

Levie, W.H., and Lentz, R. (1982). Effects of text illustrations: A review of research. Journal of Educational Psychology, 73, 195-232.