Professional Documents
Culture Documents
Overview
Technical writing is performed by a
technical writer (or technical author) and is
the process of writing and sharing
information in a professional setting.[3]:4 A
technical writer's primary task is to convey
information to another person or party in
the most clear and effective manner
possible.[3]:4 The information that
technical writers convey is often complex,
and it is one of their main tasks to analyze
the information and present it in a format
that is easy to read and
understand.[3]:12–14A good technical writer
needs strong writing and communication
skills. They do not only convey information
through text, and must be proficient with
computers as well. They use a wide range
of programs to create and edit
illustrations, diagramming programs to
create visual aids, and document
processors to design, create, and format
documents.[4]
History
While technical writing has only been
recognized as a profession since World
War II,[6]:2 its roots can be traced to
classical antiquity.[7]:233 Critics cite the
works of writers like Aristotle as the
earliest forms of technical writing.[7]:234
Geoffrey Chaucer's work, Treatise on the
Astrolabe, is an early example of a
technical document and is considered to
be the first technical document published
in English.[8]
With the invention of the mechanical
printing press, the onset of the
Renaissance and the rise of the Age of
Reason, the need to document findings
became a necessity, and inventors and
scientists like Isaac Newton and Leonardo
da Vinci prepared documents that
chronicled their inventions and
findings.[6]:1 While never called technical
documents during their period of
publication, these documents played a
crucial role in developing modern forms of
technical communication and writing.[6]
Techniques
Good technical writing is concise, focused,
easy to understand, free of errors, and is
audience-based.[11]:7 Technical writers
focus on making their documents as clear
as possible, avoiding overly technical
phrases and stylistic choices like passive
voice and nominalizations.[3]:236–245
Because technical documents are used in
real-world situations, it should always be
explicitly clear what the subject matter of
a technical document is and what should
be done with the presented information. It
would be disastrous if, for example, a
technical writer's instructions on how to
use a high-powered X-ray machine were
difficult to decipher.
Technical documents
Technical writing covers many genres and
writing styles depending on the
information and audience.[3]:84–114
Technical documents are not solely
produced by technical writers. Almost
anyone who works in a professional
setting produces technical documents of
some variety. Some examples of technical
writing include:
Instructions and procedures are
documents that help either developers
or end users operate or configure a
device or program.[11]:226 Examples of
instructional documents include user
manuals and troubleshooting guides for
computer programs, computer
hardware, household products, medical
equipment, mechanical products and
automobiles.
Proposals. Most projects begin with a
proposal—a document that describes
the purpose of a project, the tasks that
will be performed in the project, the
methods used to complete the project,
and finally the cost of the project.[11]:191
Proposals cover a wide range of
subjects. For example, a technical writer
may author a proposal that outlines how
much it will cost to install a new
computer system, a marketing
professional may write a proposal with
the product offerings and a teacher may
write a proposal that outlines how a new
biology class will be structured.
Emails, letters, and memoranda are
some of the most frequently written
documents in a business.[11]:117 Letters
and emails can be constructed with a
variety of goals—some are usually
aimed at simply communicating
information while others are designed to
persuade the recipient to accomplish a
certain task. While letters are usually
written to people outside of a company,
memoranda (memos) are documents
written to other employees within the
business.[11]:118
Press releases. When a company wants
to publicly reveal a new product or
service, they will have a technical writer
author a press release, a document that
describes the product's functions and
value to the public.[14]
Specifications are design outlines that
describe the structure, parts, packaging,
and delivery of an object or process in
enough detail that another party can
reconstruct it.[15] For example, a
technical writer might diagram and write
the specifications for a smartphone or
bicycle so that a manufacturer can
produce the object.
Descriptions are shorter explanations of
procedures and processes that help
readers understand how something
works.[3]:564 For example, a technical
writer might author a document that
shows the effects of greenhouse gases
or demonstrates how the braking
system on a bike functions.
Résumés and job applications are
another example of technical
documents.[11]:284–285 They are
documents that are used in a
professional setting to inform readers of
the author's credentials.
Technical reports are written to provide
readers with information, instructions,
and analysis on tasks.[11]:141–143
Reports come in many forms. For
example, a technical writer might
evaluate a building that is for sale and
produce a trip report that highlights his
or her findings and whether or not he or
she believes the building should be
purchased. Another writer who works
for a non-profit company may publish an
evaluation report that shows the
findings of the company's research into
air pollution.
Case study is a published report about a
person, group, or situation that has been
studied over time; also : a situation in
real life that can be looked at or studied
to learn about something.[16] For
example, an individual's challenging
situation at his or her workplace and
how he or she resolved it is a case
study.
White papers are documents that are
written for experts in a field and typically
describe a solution to a technological or
business challenge or problem.[11]:644
Examples of white papers include a
piece that details how to make a
business stand out in the market or a
piece explaining how to prevent cyber-
attacks on businesses.
Websites. The advent of hypertext has
changed the way documents are read,
organized, and accessed. Technical
writers of today are often responsible
for authoring pages on websites like
"About Us" pages or product pages and
are expected to be proficient in web
development tools.[17]:484–504
Datasheets are the document that
summarize the features, key
specifications, technical characteristics,
application circuits and some other
important information about the
product, machine, equipment, software,
application, system in brief.
API guides are written for the developer
community and are used to explain the
application programming interfaces.
Help systems are online help centres
that provide users with technical
information about products and
services. They provide content as web
pages that are viewed in a browser. The
content may be created in help centre
software, such as Zendesk, or in help
authoring tools or component content
management systems that can create a
help centre as an HTML output.
Tools
The following tools are used by technical
writers to author and present documents:
List of associations
Association for Business
Communication
Czech Society for Technical
Communication
European Association for Technical
Communication
IEEE Professional Communication
Society
Institute of Scientific and Technical
Communicators
International Association of Business
Communicators
SIGDOC
Society for Technical Communication
References
1. What is Technical Communications?
TechWhirl. Accessed December 9,
2014.
2. "Defining Technical Communication" .
Society for Technical Communication.
Retrieved February 10, 2019.
3. Mike Markel (2012). Technical
Communication 10th Edition.
Bedford/St. Martins.
4. Johnson, Tom (December 19, 2011).
"What Tools Do Technical Writers
Use" . I'd Rather Be Writing. Retrieved
May 4, 2014.
5. Perelman, Leslie C.; Barrett, Edward;
Paradis James. "Document Types" .
The Mayfield Handbook of Technical &
Scientific Writing. Retrieved May 4,
2014.
6. O'Hara, Fredrick M. Jr. "A Brief History
of Technical Communication" (PDF).
Montana State University Billings.
Retrieved April 22, 2014.
7. Doody, Aude; Follinger, Sabine; Taub,
Liba (February 8, 2012). "Structures
and Strategies in Ancient Greek and
Roman Technical Writing: An
Introduction" (PDF). Studies in History
and Philosophy of Science. University
Of Cambridge. 43 (2). Archived from
the original (PDF) on August 3, 2012.
Retrieved April 22, 2014.
8. "The Way to the Stars: Build Your Own
Astrolabe" . Saint John's College.
Retrieved April 22, 2014.
9. Crabbe, Stephen (2012). "Constructing
a Contextual History of English
Language Technical Writing" (PDF).
University of Portsmouth. Archived
from the original (PDF) on May 12,
2014. Retrieved April 30, 2014.
10. "History of Technical Writing" . Proedit.
Retrieved May 9, 2014.
11. Tebeaux, Elizabeth; Dragga, Sam
(2010). The Essentials of Technical
Communication. Oxford University
Press.
12. Diane Martinez, et. al., "Technical
Writing: A Comprehensive Resource of
Technical Writers at All Levels."
13. Waller, Rob (April 2011). "What Makes
a Good Document? The Criteria we
use" (PDF). The University of Reading:
16–19. Retrieved May 4, 2014.
14. Perelman, Leslie C., Barrett, Edward,
and Paradis James. "Press jaylan
peregrino". The Mayfield grave naba
Handbook of Technical & Scientific
Writing. Retrieved May 4, 2014.
15. Perelman, Leslie C., Barrett, Edward,
and Paradis James. "Specifications."
The Mayfield Handbook of Technical &
Scientific Writing. Retrieved May 4,
2014.
16. "Dictionary and Thesaurus | Merriam-
Webster" . www.merriam-
webster.com. Retrieved 2016-01-22.
17. Anderson, Paul V. (2007). Technical
Communication [A Reader-Centered
Approach] 6th Edition. Thompson
Wadsworth.
18. Johnson, Tom "What Tools Do
Technical Writers Use". I'd Rather Be
Writing. December 19, 2011. Retrieved
May 4, 2014.
19. "What is LyX" . LyX. Retrieved May 9,
2014.
20. Hewitt, John (January 18, 2005). "How
Technical Writer's use Microsoft
Visio" . Poe War. Archived from the
original on May 12, 2014. Retrieved
May 9, 2014.
21. Brierley, Sean (2002). Screen Captures
102 (PDF). STC Carolina (Report).
pp. 5–8. Retrieved May 9, 2014.
22. Johnson, Tom (December 19, 2011).
"What Tools Do Technical Writers
Use" . I'd Rather Be Writing. Retrieved
May 4, 2014.
External links
Technical writing at Curlie
IEEE Transactions on Professional
Communication
Technical writing courses from
Wikiversity
Retrieved from
"https://en.wikipedia.org/w/index.php?
title=Technical_writing&oldid=896971051"