Professional Documents
Culture Documents
INTRODUCTION
Through this report memo project, I gathered information and analyzed writing samples for a
potential career field of interest: technical writing. My subsequent research compiled detailed
insight about the general workplace routines of a technical writer as well as the expectations and
strategies related to the written products produced by technical writers.
RESEARCH METHODS
I conducted primary and secondary research to learn about the work of a technical writer.
RESULTS
This section includes the information gathered through my research.
Technical Writing: User Guides Vero 2
Adobe FrameMaker
My interviewee Ms. Crain regularly uses FrameMaker software as a means of organizing long
documents. This tool provides a range of settings for writers to filter and search their content by
different heading levels, spacing, and overall formatting across pages. I learned from Ms. Crain
that in terms of the upkeep of technical documents, design changes more often than content, thus
FrameMaker allows convenient updates to be made. The software also ensures usable formatting
between print and digital copies of technical writing (“Adobe FrameMaker-Intelligent, Modern,
Superfast”).
User Guides
My focal genre is user guides because this is the most central type of writing to the work of my
interviewee, Ms. Crain. This type of document is used by readers seeking understanding of any
given product, including physical equipment and software alike. While user guides are needed
across industries, Ms. Crain has experience working for Thermo Fisher Scientific Inc. and their
products related to scientific laboratory equipment. She currently works for Eagle Eye Networks,
largely writing user guides for software of the video surveillance company, which notably offers
uploading of security videos to the cloud via company-owned servers and encryption. From Ms.
Crain’s professional experience, her primary audience for Thermo Fisher Scientific Inc. included
scientists and engineers; her audience for Eagle Eye Networks is more broad to include “all end
users of the Eagle Cloud VMS” – Video Management System (see Appendix B). Overall, Ms.
Crain explained the constant importance of writing to meet “user-level understanding,” meaning
that she writes user guides on the premise of a knowledge base a reader would have to be using
the given product. Once writing, the following textual patterns are practiced by technical writers
to create user guides:
power source quality in your laboratory [...]” and phrases sentences to start with an infinitive
verb (see Appendix A). She practices consistent language in this structure to ensure clarity and
ease of reading. Headings and lists of information are written in parallel grammatical structure,
and content is concise.
DISCUSSION
This section describes how the features of my focal genre of technical writing, user guides,
reveal the values and significance of technical writing.
Learning Continuously
Technical writers must have a strong understanding of the given product or application basis of
each user guide they compose in order to write clearly for readers. Even for senior technical
writers such as my interviewee, research and learning are ongoing processes. Technical writers
research content independently and consult SMEs – subject-matter experts – with essential
questions thereafter. Successful technical writers seek and take note of new information on a
regular basis in order to meet the needs of their readers.
CONCLUSION
After interviewing a technical writer and learning more about the field, I gained valuable
takeaways for the workplace. Ms. Crain explained that the first half of her day is spent in project
and software meetings, where she observes and while taking audio recordings and notes for her
own learning and reference. Her writing follows in the afternoons since her company has global
offices, whereby her European colleagues end their workday once she starts writing. Ms. Crain
emphasized the value of “polite persistence” in order to get her writing reviewed by colleagues
and to consult with SMEs – subject matter specialists – in a timely manner. She sends her work
e.g., user guides in segments to break-up lengthy documents for review in smaller sections at a
time. Most importantly, technical writers must exercise initiative to complete independent
research and to constantly learn.
While Ms. Crain integrates her writing skills with science-related content, she clarified that many
technical writers primarily have a background in writing and supplement their content
knowledge as they go. She encouraged me to learn new software, to thoroughly grasp any
content I write about, and to even explore programming languages such as Markdown. Her quote
that technical writing is less about “can you do it” and more about “will you do it” serves as the
thesis of my regard of the professional field of technical writing. In my future career, I hope to
use my writing skills as a tool for producing documents and synthesizing new information, be
that in my interest of science or any discipline I encounter in the workplace.
Technical Writing: User Guides Vero 5
REFERENCES
www.adobe.com/products/framemaker.html.
“Eagle Eye Cloud VMS App Notes.” Eagle Eye Networks, 13 July 2022,
www.een.com/docs/app-notes/.
“Eagle Eye Networks Cloud Video Surveillance for School Campuses.” YouTube, Eagle Eye
“How to Become a Technical Writer: ASU Online.” How to Become a Technical Writer | ASU
ow-to-become-technical-writer/.
Knott, Ryan. “How to Build the Best User Manual.” The TechSmith Blog, TechSmith
“Simplified Technical English and Clearer Documentation through the Thumbs up Technique
procomm.ieee.org/simplified-technical-english-and-clearer-documentation-through-the-
thumbs-up-technique-33/.
“Technical Writers : Occupational Outlook Handbook.” U.S. Bureau of Labor Statistics, U.S.
ation/technical-writers.htm.
Technical Writing: User Guides Vero 6
APPENDICES