Last week’s action plan assignment was very helpful in
determining the forms of professional writing in my field. It served a fruitful purpose of giving me a
basis for developing the next assignments on evaluations, press releases, and proposals. But how are these used in computer engineering? I am aware of the prevalence of technical
reports, users' manuals, circuit descriptions, and the like, but when will
someone in my position need to write an evaluation, press release, or proposal? My conclusion: in nearly every stage of the design
or production process. We discussed the
separate connotations of these three modes of writing in class, but I would
propose that they are, in fact, very closely related and may be applied in
unison.
When a project is being defined and refined by a team of
experts, there will be many different propositions. Whether this project is the architecture of a
microprocessor logic unit or the layout of the cooling systems in a server
farm, many large and small decisions must be made. Official documents will need to convey the
process the team used to reach their conclusions (evaluation), the plan of
action for communication with the customer (proposal), and a release of relevant
information to the public (press release).
When a company is releasing a new product, each of these
methods is employed. Whether that
product be a two cent integrated circuit, a thousand dollar laptop, or a
modular industrial fabrication system worth nearly a million dollars, the same
considerations must be made. Teams of
individuals, internal and external to the developer, will examine the product
in question to authenticate its performance and adherence to standards. Proposals may be sent to close affiliates of
the developer, encouraging adoption of the product. Press releases will be composed for the
market of the product to seed interest, enthusiasm, and, ultimately, sales.
In the likely event of a malfunction or catastrophic failure
of a product, all of these approaches are still necessary. Evaluation is a critical stage after a
failure, used to determine the cause and depth of the issue. This stage of the process may take longer
than any other, and it must be the most closely documented as the other two
will reference it recurrently. Press
releases will be formed to quell outcry and assure resolution. Proposals for such resolution will be rapidly
produced and acted upon.
It is important to note that a failure of this magnitude is often
caused by a failure in previous evaluation, proposal, or release. Evaluation may have been completed in
error. Proposals may leave out a
critical component due to eleventh hour adjustments or funding cuts. Releases may communicate inaccurate
information to the public, causing a firestorm that must be snuffed out
quickly. This further emphasizes the
need for close attention to professional writing of all types in every stage of
the process.