ME Sr. Design Project Executive Summary (2007)
(Each Student Must Complete an Independent Executive Summary)

Follow the general Executive Summary Guidelines* with respect to writing style.

· Remember that an executive summary should be written to be influential and persuasive, not merely informative.

· Remember to clearly state what the decision maker is expected to do in response to your summary

In this executive summary you should briefly explain your design solution, it’s strengths and weaknesses, what you did to validate and demonstrate its performance, and your recommendations

· Consider the overall purpose of the project as well as the detailed specifications.

· The report should be short (probably 3-5 pages, including pictures and tables) and targeted to a non-technical decision maker. It must not be an edited version of content from your group's design report, but must be completely independent work. If you use images or tables from the design report, please give proper citations.

The goal is not to summarize the Final Design Report, but to evaluate the entire Design Project (based on your improved understanding of the market, the production costs, and the overall impact that producing this design is likely to have relative to addressing the original needs statement) with the purpose of making a persuasive argument (with justification) that:

a) your design should be continued into production (do not compare to other projects but justify it on its own merits)

b) your design is a good solution but needs additional testing and should receive continued development funding for additional tests (define them, being as specific as possible with the recommendations of what should be done, in what priority, and who is responsible)

c) your project is an incomplete solution that needs more design work, but is a good enough idea that it should receive continued funding for development and improvement (define the work needed to get to the production decision, being as specific as possible with the recommendations of what should be done, in what priority, and who is responsible)

d) your project is an inappropriate solution or flawed in some way so the project should be terminated and no more money should be spent on it.

Note: This is a technical report, not a sales brochure, so make sure to be brutally honest in your appraisal of the overall design and its state of readiness for production.

* When writing the Executive Summary it is best to keep the writing and style simple and concise.
Following are a few reminders for good communications: [Whrp.org]

· Use simple short words unless only the long words fit your needs. Weed out unnecessary words, clichés and overused buzzwords.

· Keep sentences short (15-20 words).

· Avoid technical jargon and acronyms. If a technical word is absolutely necessary, define it for the reader. For instance if the research involves rubblization explain it.

· Keep numbers simple. Round them off when possible ($8.4 million instead of $8,421,500). Use charts to show comparisons or trends.

· Substitute active verbs for "to be" verbs. For instance, "the program achieved its goals" instead of "program goals were achieved."

· Write as you talk, use everyday language. Avoid stuffy, halting sentences.

· Read it aloud and make sure it flows well and sounds good.

· Keep the tone friendly, informal, matter-of-fact.

· Use examples that are familiar to the reader.

· Remember to spell-check and proofread. Don't trust the Spellchecker alone.