White Paper Redux

Nathaniel's picture

Jeremy and I have now provided feedback on each white paper draft as a comment. Be sure to check yours out.

We noticed that there were common issues that came up for several groups, which inspired the following general list of tips:

  • Provide an executive summary and introduction. The executive summary, which is distinct from the introduction, summarizes the entire white paper. In other words, the executive summary gives away the "ending" of the white paper, summarizing any and all of its key conclusions/points of comparison. The introduction, which introduces the reader to the white paper's purpose (what problem or situation it addresses) and organization, needs to be up front so that it can frame the white paper properly. These sections together provide the necessary framework for the white paper.

  • Allow for multiple ways of reading white papers. Although for most of the white papers the body text is solid, there needs to be sufficient design elements (e.g., bullet lists, captions for images, and tables that compare features) that account for the fact that white papers are rarely read all the way through by every reader. The white paper needs to account for the many readers who raid and skim them, as the readings suggest.

  • Balance your sections. Each option should receive the same care and attention. This is an important way to avoid the appearance of bias. It is also necessary to allow the reader to make an informed decision. Each option should have the same number of sections and the same talking points (e.g., installation, limitations, economic efficiency, etc.). For several white papers, the options are described in different ways, making comparison among them difficult. For instance, one option's section might contain the subsections "Configuration," "Services," and "Compatibility," whereas another contains the subsections "Privacy," "Document Sharing," and "Cost." White papers should contain comparable sections rather independent summaries. This makes comparison and thus selection more effective (which is the purpose of a white paper).

  • Thoroughly and consistently document sources. Documenting sources is required, as the project description states. One of the more unobtrusive ways to document sources is through footnotes. You do not need to adhere to any particular citation format (MLA, APA, Chicago, etc.), but you must be thorough and consistent. You can use the information in your research blogs to produce your citations (this is a main reason why we ask you to do them).

  • Ensure that the white paper has a consistent voice and style. If group members are responsible for separate sections, make sure to review and revise the whole document so that it functions as a single unit rather than a patchwork. You should ensure that the document has consistent terminology, formatting, and design.

By following these tips, you will improve your white papers. As always, feel free to contact your instructor with specific questions about your work.