Basic Principles of Good Technical Writing
Basic Principles of Good Technical Writing
TECHNICAL WRITING
Content
There are five basic questions a technical writer has to ask
themselves when starting a new project who, why, what,
how and when. Answering these questions will allow the
technical writer to be able to develop the content for any
type of technical documentation.
Styleguide
Technical writers will more than likely use a company
styleguide (if there is one) to ensure that their
documentation has a structured and organized pattern so
that it gives consistency to their writing. A styleguide will
provide the document with continuity so that the audience
can comprehend the information. For example, technical
writers need to organise their ideas in a specific
chronological format because without a specific layout and
structure to the documentation it will be very confusing for
the reader to understand.
Writing Style
Technical writers will need to change their writing
style depending on the audience and situation they
are writing about. If they are writing technical
documentation then it needs to be formal and devoid
of any emotion as you get with creative writing.
Whereas, if say they were an email to one of the
senior managers involved in the project then their
approach would more casual than formal.
Grammar
A technical writer must adhere to all the rules of
conventional grammar. Also it is the technical writers
responsibility to proofread and edit their documentation to
detect and correct any errors in the writing, graphics,
typography and layout.
KINDS OF TECHNICAL
WRITING
Marketing Materials
Companies use technical writers to compose promotional
materials to market and sell their products. They rely on
these writers' expertise to describe products or services in
an appealing manner while incorporating facts into the
narratives. This category includes home pages for
websites, press releases, brochures, advertising copy for
audio, visual and written communications and product
descriptions for catalogs and online retail websites.
Report Writing
Although the original definition of technical writing
only included the aforementioned formats, in recent
years technical writers have found a niche in report
and policy writing. Organizations frequently gather
information from several departments or executives
that require organization and editing before it can
be published or distributed. Technical writers
perform these tasks in several categories.
Technical Reports
In addition to instructions and guidelines, many technical
products include information on the products' history,
evolution or structural or operational revisions. Technical
writers organize the information and edit it for brevity and
accuracy.
Research Results
Products such as pharmaceuticals or medical devices are
required to include information on findings and
interpretations based on laboratory testing or field
research. Exemplary attention to detail is important in this
type of writing as it frequently includes facts on drug
interactions, side effects and other health-related issues
that could be life threatening.
Business Plans
Before lending institutions consider extending loans
to new or established businesses, they require a
detailed business plan. These documents require
research of economic trends and include projections
on expenditures, possible losses and profit margins
along with detailed background information on the
business owners' professional background and
financial stability.
PROPERTIES OF
TECHNICAL WRITING
1. Accuracy
Unclear writing can cause many problems and even accuracy in the
report.
2. Brevity
Its easier to grasp the main idea of the report written if you have a
brief report.
3. Coherence
Logical togetherness of the material; use of traditional devices.
4. Confidence
The modest sureness on your part as the report writer.
5. Dignity
Formality with respect to words and the way words are used. Avoid
contracted word such as cant, havent, doesnt because it might give
other meaning.
6. Emphasis
Main point; separates major from minor issues.
1 Introduction
A technical report is a formal report designed to
convey technical information in a clear and easily
accessible format. It is divided into sections which
allow different readers to access different levels
of information. This guide explains the commonly
accepted format for a technical report; explains
the purposes of the individual sections; and gives
hints on how to go about drafting and refining a
report in order to produce an accurate,
professional document
2 Structure
A technical report should contain the following sections;
3 Presentation
For technical reports required as part of an assessment, the following presentation guidelines
are recommended;
Journal article:
Journal article:
author(s)
author(s)
title of article
title of article
name of journal (italic or
name of journal (italic or
underlined)
underlined)
year of publication
year of publication
volume number (bold)
volume number (bold)
issue number, if provided
issue number, if provided
(in brackets)
(in brackets)
page numbers
page numbers
Book:
Book:
author(s)
author(s)
title of book (italic or
title of book (italic or
underlined)
underlined)
edition, if
edition, if
appropriate
appropriate
publisher
publisher
year of publication
year of publication
During year 1, term 1 you will be learning how to write formal English for
technical communication. This includes examples of the most common pitfalls in
the use of English and how to avoid them. Use what you learn and the
recommended books to guide you. Most importantly, when you read through
what you have written, you must ask yourself these questions;
9 Headings
Use heading and sub-headings to break up the text and to guide the
reader. They should be based on the logical sequence which you
identified at the planning stage but with enough sub-headings to
break up the material into manageable chunks. The use of
numbering and type size and style can clarify the structure as
follows;
13 The Summary
The summary, with the title, should indicate the
scope of the report and give the main results and
conclusions. It must be intelligible without the rest
of the report. Many people may read, and refer to, a
report summary but only a few may read the full
report, as often happens in a professional
organisation.
Purpose - a short version of the report and a guide
to the report.
Length - short, typically not more than 100-300
words
Content - provide information, not just a description
14 Proofreading
This refers to the checking of every aspect of a piece
of written work from the content to the layout and is
an absolutely necessary part of the writing process.
You should acquire the habit of never sending or
submitting any piece of written work, from email to
course work, without at least one and preferably
several processes of proofreading. In addition, it is
not possible for you, as the author of a long piece of
writing, to proofread accurately yourself; you are too
familiar with what you have written and will not spot
all the mistakes.