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 saw a job listed recently that came very close to your original
description. Very interesting. But I haven't been able to find it to
see what it was called.
On Wed, Aug 8, 2012 at 3:35 PM, Steve Janoff (non-Celgene)
<sjanoff -at- celgene -dot- com> wrote:
> Interesting story. Thanks, Debbie.
>
> I think this shows the difficulty of coming up with a good way to describe yourself when the functions are outside the norm of what a Technical Writer/Communicator usually does (or the lack of a reference point, in your case). You do have a varied and interesting assignment. (And a great mission.)
>
> For my part the job title is secondary. I'm trying to identify the niche and process for what I've been doing or see myself as potentially doing going forward. But all of what we're discussing shows that sometimes the totality of the field is very hard to pin down.
>
> Thanks for sharing.
>
> Steve
>
> -----Original Message-----
> From: On Behalf Of Debbie Hemstreet
> Sent: Tuesday, August 07, 2012 11:08 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Update: Data Presentation Architect / Architecture
>
> I'm definitely struggling with this issue these days. Now that I'm working at a hospital in Israel I have the glorious official title of "English Editor" because they didn't know what to do with "Technical Writer." (No official government positions for a technical writer.)
>
> So when I'm given something to "edit" and provide them with a rewritten document, with recommendations for reorganizing information, redone graphics, or a request for the original PPT file to redo the graphics, etc. some are thrilled (like one Director here yesterday), and others have no idea how to respond.
>
> I just explain nicely that the official job titles don't adequately describe what I do... the message is catching on... and at last, I'm getting busier and busier with the kind of work I love! Technical Medical Writing with Medical Marketing thrown in.
>
> I think for some a title is important... to me, I try not to let it bother or influence me. I'm thankful I have a job! But I realize, the importance of a title is not for me, but in helping others understand just what I do, so that they can best utilize my services.
>
> From that perspective, Technical Writer really doesn't work for most of us. Technical Communicator (which I use on my website, for now...) also doesn't get the message across. Because our (or my) definition for "technical" is not exactly correct.
>
> For example, if I'm writing a critical business sensitive letter from the President of the company to a potential business partner, every aspect of my technical writing skills come into play. My letter is going to be much better than the secretary's, and probably not have many changes... so was I playing secretary or technical writer?
>
> Jack-of-all-trades-master-of-none doesn't work, because many of us ARE Jacks and Jills of all trades, and MASTERS of many! Just not necessarily the trade we are documenting. For example, I can edit a medical journal, handle the DTP, check for logic and order, detect when data doesn't match up, point out that the graphics do not convey what the author intended, or that the table could be redesigned to better display the data; because of my medical background from 30 years ago, I even have enough knowledge to know when they have erroneously referred to the liver when they meant the kidney (and I do all this) However, I will never be a master doctor... but I'll always be able to help the doctor write a better paper for publication. (Of course some doctors don't want the help... until their paper is rejected by reviewers who tell them to do everything I told them to do... and more!)
>
> The point, define what I am? Medical Writer? Yes, but not according to the definition of the people hiring medical writers in Michigan, when I was living in the US.
>
> At the end of the day, I find that if people SEE what I do and appreciate what I do, and I am satisfied with the remuneration I receive... the only reason these days I care about what my title is, is because OTHERS simply don't know how to use my services adequately.
>
> So I have an official title in my job description, and when I send emails to people at work, I adjust the title to:
> Editorial Assistant, RMMJ
> and
> English Editor and Writer
>
> It still doesn't come close to what I really DO (because I'm also doing a lot of marketing writing these days).... but it works and no one is complaining.
>
> Just my two cents worth to a discussion that will continue as long as there are "technical writers" and "technical communicators" and "Information Architects" out there.
>
> Deborah
>
> *********************************************************
> THIS ELECTRONIC MAIL MESSAGE AND ANY ATTACHMENT IS
> CONFIDENTIAL AND MAY CONTAIN LEGALLY PRIVILEGED
> INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL
> OR INDIVIDUALS NAMED ABOVE.
> If the reader is not the intended recipient, or the
> employee or agent responsible to deliver it to the
> intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this
> communication is strictly prohibited. If you have
> received this communication in error, please reply to the
> sender to notify us of the error and delete the original
> message. 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.
>
>http://bit.ly/doc-to-help
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as kathleen -dot- eamd -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
--
Kathleen MacDowell
kathleen -dot- eamd -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
