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.
The SMEs like me, because I always try to figure out how the software works myself and usually only get with them if I have specific questions. I am occasionally wrong about how something works, but most of the time I get it right. Of course technical writers decide how to use the software. They might ask SMEs about best practices, but a technical writer that can't figure anything out for himself or herself is going to get short shrift from most of the SMEs I've known.
-----Original Message-----
From: techwr-l-bounces+kay -dot- robart=tea -dot- state -dot- tx -dot- us -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+kay -dot- robart=tea -dot- state -dot- tx -dot- us -at- lists -dot- techwr-l -dot- com] On Behalf Of Steven Jong
Sent: Saturday, June 12, 2010 1:20 PM
To: TECHWR-L Digest
Cc: Steven Jong
Subject: Resolved: Technical communicators can create information
I recently wrote an article for the STC Carolina chapter's newsletter, the Carolina Communiqué. In it I wrote:
> At the high end of the [technical communication] scale are people who can not only write the procedures but design entire information product offerings, as well as people who can not just describe what a product does, but explain how to use it effectively: not just how to get to the screen or page, but what to do once you're there, and why.
In response, a reader (who gave me permission to quote him) commented:
> You should make certain that young tech writers don't begin to think of themselves as the sources of anything other than effective communication. It is the SME who is to provide the explanation of how to use a product (in his opinion) effectively or what should be done when reaching a screen or a page. It is the tech writer who should seek out the opinion of the SME and perhaps the balancing opinions of other SMEs and communicate those opinions (with credit) to the audience, assuming, of course, that tech writers actually have time to do that in the real world.
I did not say, or intend to say, that technical communicators can dispense with SMEs. But I do think that we can create information, not just serve as amanuenses. I think this goes to the heart of what a technical communicator does. If I am correctly paraphrasing the reader's opinion, a technical communicator can collect information ("here's what folks say"), and curate information ("here's what the SMEs say"), but not CREATE information. I disagree. What do you think?
-- Steve
Steven Jong ("Typo? What tpyo?")
SteveFJong -at- comcast -dot- net
978-413-2553 [C]
Home sweet home page: StevenJong.net
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as kay -dot- robart -at- tea -dot- state -dot- tx -dot- us -dot-
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
