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.
Re: STC certification: what's in it for tech writers?
Subject:Re: STC certification: what's in it for tech writers? From:Steven Jong <stevefjong -at- comcast -dot- net> To:Keith Hood <klhra -at- yahoo -dot- com>, TECHWR-L Digest <TECHWR-L -at- LISTS -dot- TECHWR-L -dot- COM> Date:Thu, 27 Oct 2011 12:31:45 -0400
On Oct 27, 2011, at 11:50 AM, Keith Hood wrote:
> The first major problem with having a certification process for technical writers is the fact there is no way to test on, and certify a person on, the parts of the job that don't have to do with language or software use. For example, an extremely important part of the job is communicating with SMEs and other people, and being able to get information out of them. How do you test people on their ability to deal with an antisocial software engineer who doesn't like talking to tech writers because he considers them "not techy enough" to be worthy of his consideration? How do you test on the ability to set up a review process that other people will actually use? The human element is always the most variable element in any job, and it is vital to be able to deal with it, and I can't think of any way to sensibly test that ability.
>
> Another major problem is the fact that "technical writing" is not a monolithic career field. There are many different types of technical writing - using Robohelp to create online help systems for a startup is much different from writing business requirements for a huge multinational corporation. And doing anything under a DOD contract is a whole other world. STC certification may be worth something if it were a sheaf of certifications, each adapted to a particular type of technical writing, but developing something like that would take years - and by the time that development is finished, some of the stuff in them would be obsolescent.
With respect, I disagree. I think it can be done, and I think we've doing it. And as Walt Disney said, "It's kind of fun to do the impossible" 8^)
Sub-certifications will be a great addition, though we're looking at at higher levels—not toolsmithing or specific domains, but "writer," editor," trainer," "illustrator, "manager," and such.
-- Steve
--
Steven Jong ("Typo? What tpyo?")
SteveFJong -at- comcast -dot- net
978-413-2553 [C]
Home sweet home page: StevenJong.net
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-