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.
Subject:Re: ROI on hiring tech comms vs. SMEs From:Gene Kim-Eng <techwr -at- genek -dot- com> To:William Sherman <bsherman77 -at- embarqmail -dot- com> Date:Tue, 12 Jun 2012 14:31:57 -0700
This is inevitably going to vary. Most of my experience has been in small,
"bleeding edge" startups, where the engineer was all of these people.
However, in those environments, the tech writer is often one of the testers
and the closest thing there is to QA, at least until the company goes from
an R&D shop to actual production.
On Tue, Jun 12, 2012 at 1:59 PM, William Sherman
<bsherman77 -at- embarqmail -dot- com>wrote:
> As SME is a sore spot with me, I'll have to say that at most places I have
> been, the technical writer was the subject matter expert.
> However, I think you are referring to the engineer who in most cases I
> is NOT the subject matter expert. They may be the expert on the design but
> you find the assembly line person is the expert on how it goes together
> (thus you can figure how it comes apart), the tech is the expert on what
> makes it work and what makes it work again when it doesn't, and the
> programmer is the expert on what makes it think and function.
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.