This is an archived assignment from English 3764: Technical Writing, taught at Virginia Tech during the Fall 2018 semester. Links may no longer work, and newer versions of some resources may be available.
You will write an informational report for non-experts (a white paper) that presents details on a specific issue related to your company and the work that it does. Your white paper will tie directly to the incubator goal of public outreach and education. Specifically, the incubator founders want to provide a library of documents that inform readers about how science, technology, and engineering work.
As explained in Johnson-Sheehan’s Technical Communication Today (2018):
White papers . . . typically present gathered facts in a straightforward and impartial way. They include the following kinds of information:
- A summary of the facts
- A discussion of the importance of these facts
- A forecast about the importance of these facts in the future (p. 285)
You proposed the topic for your White Paper Project in your Short Proposal. Your Poster Presentation Project will provide an alternate presentation of the information in your White Paper Project.
This week, you received the following memo, accepting your proposal for the Incubator’s December White Paper Publication:
1872 Inventors Way, Blacksburg, Virginia 24060
To: | December White Paper Authors |
---|---|
From: | Traci Gardner, Ut Prosim Director Manolito Reyna Bautista, Manager of the Public Outreach Office |
Subject: | Preparing Your White Paper |
Date: | October 8, 2018 |
Congratulations! We are pleased to accept your proposal for a white paper and research poster for December publication. We look forward to learning more about your topic and working with you to share the information with the public on our website.
Your white paper and poster presentation are due by November 26 [Portfolio 2 due date] and will ultimately be published as PDFs in the December 2018 release on the Incubator website.
Today, we are sharing details on the expectations for your white paper. We will send details on the research poster later this month.
As explained in the call for proposals, your white paper will inform non-expert readers about a technical topic relevant to the work and mission of your company. These documents will share what we do and why we do it with the university, alumni, and local community. Your documents will also contribute directly to our goal of public outreach and education by adding to our growing library of documents that inform website readers about how science, technology, and engineering work.
As an objective white paper, your document will either provide knowledge or information about a subject relevant to your company or provide solutions to a problem or challenge that relates to your company—or even a combination of both goals.
The audience for the white paper is the general public and the university community Readers with no background in your field should be able to fully understand your white paper.
Your report will define or explain your topic with the goal of informing your readers about it fully and with relevant, specific details. You should focus on answering questions such as these:
You should present the information in your report objectively, that is, without letting opinion shape what you have to say. Do not draw conclusions, make recommendations, argue for one side or the other, or in any way take a position on the subject. Its goal is to provide a response to the question "What is [your subject] all about?" This doesn't mean you can't present opinions about it, but those opinions must come from experts in the field. For example, Expert A thinks the subject of your article is a fantastic option for reducing the need to irrigate crops, but Expert B is sure it won't work as planned. You can present these opposing viewpoints, but you must remain objective and let readers make their own decisions.
To ensure that we have time to review and edit your submission, please submit your white paper by 11:59 PM on Monday, November 26. If additional time is necessary, you can take advantage of the grace period, which ends at 11:59 PM on Thursday, November 29.
If you need any help with this project, please let either of us know or contact Traci’s assistant, Leslie Crow <lcrow@utprosimincubator.org>.
Note: These details apply to all of the projects you include in your portfolio.
Your company’s address is [Your Company Name], Ut Prosim Incubator, 1872 Inventors Way, Suite #[you choose a number], Blacksburg, Virginia 24060. Your company’s phone number is 540-555-5555. You may create a fictional Internet domain for your company, and use that domain for a web page address and your email addresses. If you’d like, you may create other information (including a logo) for your company as appropriate. Be sure that you use the information that you create consistently across all of your projects.
Step 1: Review your notes on the topic and audiences, as established in your proposal.
Your proposal should have the basic starting information that you need to begin the research for your white paper. Be sure that you have a strong, well-focused topic before you begin your research.
Step 2: Examine the information about white papers in the readings.
Review the following readings for specific details on the information and details to include in your white paper:
Step 3: Begin your research, taking notes and paying attention to documentation and citation details.
The textbook provides complete details on how to conduct your research and keep track of your notes and sources. Follow the textbook as you work on your project. In particular, be sure that you do the following:
Step 4: Write your white paper.
As you work, also keep the following points in mind:
Step 5: Check your draft against the Writer’s Checklist.
Be sure that you include the required features for your white paper. Review your project, using the Assessment Criteria below.
Step 6: Review your draft for design and basic writing errors.
Everything you write should use accurate/appropriate image editing, grammar, spelling, punctuation, mechanics, linking, and formatting. These are important basic writing skills that you should have developed in high school. Review your project, using the Writer’s Checklist at the end of Markel & Selber, Chapter 10 (on page 242).
You can also consult the information on “Sentence-Level Issues” in Markel & Selber, “Appendix, Part D: Guidelines for Multilingual Writers (ESL)” (on page 683 of Markel & Selber). While the section is labeled for multilingual writers, it is useful for everyone. It includes explanations and examples for many common mistakes writers make.
Step 7: Submit your draft to your Writing Group in Canvas.
Post a rough draft of your technical description to your Writing Group in Canvas in the 10/25 Draft Feedback Discussion in Canvas. Additional instructions are in the Discussion. Post a draft of your technical description by September 20. If you are late submitting a draft, your group may not have time to provide feedback.
Step 8: Provide feedback to your Writing Group in Canvas.
Provide feedback to the members of your writing group in the 10/25 Draft Feedback Discussion in Canvas, by September 24 (end of the grace period). Use the information on the Writing Groups page to provide constructive feedback that will help your group members make concrete improvements to their drafts.
Step 9: Revise your draft.
Use the feedback that you receive from your group members to revise and improve your document. You can share your draft again with your Writing Group, if you desire. As you revise, keep in mind the advice in the steps above, as well as the Assessment Criteria below.
Step 10: Include a polished version of your project in Project Portfolio 2, due November 26.
Have your Technical Description Project finished and ready for submission in your Project Portfolio 2, which is due Monday, November 26. The grace period for Project Portfolio 2 ends at 11:59PM on Thursday, November 29.
All technical writing projects should meet the following general criteria:
Your project should meet the following criteria for effective instructions: