MEMORANDUM
|
Document Title
- Include “Memo” or “Memorandum” as the document title.
- Do not include any other title.
- Do not include the assignment name as the document title.
|
To: |
Traci Gardner |
From: |
Full Names of Group Members |
Date: |
March 28, 2025 |
Subject: |
Improving the Usability of the Simple Sabotage Field Manual |
|
Memo Headers
- Every memo begins with a memo headers: To, From, Date, and Subject.
- Follow each header with the pertinent information.
- Align the memo headers align vertically.
- Use the same size and style for all the Memo Headers.
- Double space (leave 1 blank line) between headers.
|
Follow these instructions for the Introduction:
- Draw the reader in by providing facts, telling a story, or another strategy.
- Persuade the reader(s) to read the rest of the proposal and ultimately to approve the project.
- Introduce the subject of your team management project, providing the name of the website and linking to it.
- End the introduction with a purpose statement that indicates the following:
- Why you are writing, touching on your overall evaluation of the original website’s usability.
- What is included in the rest of the proposal as an Advance Organizer.
- How accepting the proposal will effect the website’s rhetorical success and overall usability.
|
Memo Body
- Do not indent paragraphs
- Use hierarchical headings, in bold. Your title should be the largest and then work down from there.
Memo Introduction
- This is the intro section. There is no need to give an introduction a heading, as it’s obvious it’s the intro.
- The section is typically two to three paragraphs. It can be longer for more complex proposals and bigger projects.
- Find help on Introductions in Tech Writing.
|
Project Overview and Rationale
Follow these instructions for the Project Overview and Rationale section:
- Reintroduce and provide information about the intended subject of your Recommendation Report.
- Explain the following details of your proposal (improving the website you’ve chosen):
- Define the subject of your project.
- Indicate what the project involves
- Explain why the project is important.
- If desired, use screenshots from the website to demonstrate places that need improvement.
|
Project Overview and Rationale Section
- Begin all main sections with a First-level Heading (using the same size and style).
- Can also use the heading Justification.
- Include your section content in paragraphs under the heading.
- NOTE: This will be the longest section of the proposal.
- Find help on writing about the background of the situation in Tech Writing.
|
Project Methodology and Resources
Follow these instructions for the Project Methodology and Resources section:
- Indicate the methods your group plans to use to conduct research into the projected subject (interviews, online research, questionnaires, surveys, traditional research methods).
- Describe any key information (i.e., articles, books, videos) that you know you will be using and provide a brief summary of each.
|
Project Methodology and Resources Section
- Add another main section with a First-level Heading (using the same size and style).
- Add footnotes with bibliographic details on the key information you plan to use in your Recommendation Report.
- Find help on writing about the methods you propose using in Tech Writing.
|
Project Audience
Follow these instructions for the Project Audience section:
- Identify the specific audience(s) to whom the Recommendation Report will be addressed.
Tip: The audience is not me (Traci). It is the person who can decide to implement the ideas in your Recommendation Report.
- Indicate what considerations you must make for this audience (such as language, visuals, and so on).
|
Project Audience Section
|
Project Personnel
Follow these instructions for the Project Personnel section:
- Provide brief bios of your group members with their names.
- Indicate the roles each team member will fulfill for the Recommendation Report.
- Emphasize how each of you is qualified to pursue this subject.
|
Project Personnel Section
- Add another main section with a First-level Heading (using the same size and style).
- Return to your group’s Professional Bios in the Introduce Yourself Discussion to get started. Focus on the professional details in the bios.
|
Project Timetable
Follow these instructions for the Project Timetable:
- Introduce your schedule with some general details on the most significant dates.
- Establish a rough deadline for each major stage of the project.
- Include a Gantt chart.
Tip: Be sure that your Gantt chart is large enough to be read easily. If necessary, include the chart on a separate page and turn that page only to Landscape Orientation.
|
Project Timetable Section
- Add another main section with a First-level Heading (using the same size and style).
- Find help on writing about the schedule in Tech Writing.
|
Conclusion
Follow these instructions for the Conclusion:
- Reiterate your subject and the reasons it’s important.
- Provide contact info for the team leader so that the reader can follow up with questions and let you know if your proposal is approved.
|
Conclusion Section
- Add another main section with a First-level Heading (using the same size and style).
- Keep it simple.
- Do not sign your name at the end or add a signature block.
- Find help on writing about the Conclusion in Tech Writing.
|