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: Technical Communication Poll: Best Career Prospects
Subject:RE: Technical Communication Poll: Best Career Prospects From:"Dan Goldstein" <DGoldstein -at- riveraintech -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 31 Aug 2012 14:31:36 -0400
No, actually, I was talking about tech writing for internal use within
an organization. This doesn't always depend on whether there's a
customer to be marketed to.
As Milan pointed out, some writers think of their colleagues as internal
customers to whom they have to market their work. If you want to call
that Marcom, okay by me!
-----Original Message-----
From: Tony Chung
Sent: Friday, August 31, 2012 2:12 PM
To: Dan Goldstein
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Technical Communication Poll: Best Career Prospects
Dan, if I read you correctly, I think you're comparing companies who
treat content as an asset as opposed to a commodity. I prefer working
for companies who believe in the tech writer's responsibility to ensure
the content has value, and isn't produced just to maintain the ISO
certification.
A lot of companies just pump out "a document" because that's what they
know to do. Then they repeat the work every time a new version comes
out. But what if the user's work environment would be more efficient if
the documentation were provided by different means, which may or may not
involve "a document"?
I think marketing writers have grasped the fluidity of social media
tools more than technical writers. Technical writers who embrace these
intuitive tools spend most of their time in embedded user interface and
user experience tasks. Generalization. Yes.
-Tony
On Fri, Aug 31, 2012 at 9:59 AM, Dan Goldstein wrote:
An offline discussion alerted me that my post below wasn't clear enough.
I wasn't talking about businesses that are starving for customers. I was
talking about tech writing jobs in organizations that don't *need*
customers.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
