TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I have heard the term "domain knowledge" and understand it to mean "the
knowledge that we as technical communicators have of the product/industry we
are writing about." I have three questions:
1. Is this the correct definition?
2. How do we acquire such knowledge?
3. Can a technical writer always acquire such knowledge (through asking
a million questions) or does a writer have to have an aptitude for and
interest in the domain?
I'm asking because I'm in a situation in which the "domain knowledge"
required of me when I was hired was, I felt, much less than that which is
required of me now, and VERY much less than what will be required of me in
the near future. I'm concerned that I may be in over my head, and seek
advice on how to deal with the situation.
Kathy Stanzler
Technical Writer
Brooktrout Technology Inc.
Southborough, MA
(508) 786-9182
kstanzler -at- brooksoft -dot- com <mailto:kstanzler -at- brooksoft -dot- com>
