Re: What's in a name?

Subject: Re: What's in a name?
From: Shari Punyon <sharipunyon -at- gmail -dot- com>
To: Suzette Seveny <suzette -dot- seveny -at- gmail -dot- com>
Date: Tue, 10 Aug 2021 09:48:14 -0400

My suggestion is to look around in the marketplace and pick a title that seems to fit with a job you might want in the future.

Documentation jobs are all over the place in description - right now Iâm mostly using Knowledge Manager, because that is an ITIL role that fits some of what I do, and matches search engines well.
Before the discovery of that role (because I was hired for it), I was struggling with things like âContent Architectâ which means nothing to anyone in the job market, as far as I can tell.

Content Strategist seems to skew into marketing, and Specialist might do the same thing. Do some research into about what might be appealing in your future, if your current employers are stupid enough to lose you, and ask for a title that might help you get there.

> On Aug 10, 2021, at 9:14 AM, Suzette Seveny <suzette -dot- seveny -at- gmail -dot- com> wrote:
>
> Captain... it has possibilities!
>
> I'm fortunate that my position resides in the R&D group now, so access to
> information is getting better everyday! I'd love to have documentation
> split up between new initiatives and maintenance of current projects - do
> any companies do that?
>
> Being involved in our user group forums (and sometimes leading them) allows
> me to be right at the forefront of requirement gathering, but it makes it
> difficult to find a suitable title.
>
> Documentation Analyst?
> Information Specialist?
> Content Specialist?
> Technical Content Specialist?
>
>
>
> On Mon, Aug 9, 2021 at 11:02 PM Peter Neilson <neilson -at- windstream -dot- net>
> wrote:
>
>> "Director" is generally a position with legal implications. Tech writers
>> never get even a hint of being considered for "director-level" positions.
>>
>> Technical writing is often a "doesn't fit" compartment of an
>> organization.
>> We get left out and on our own, required to document things that we
>> discovered just weeks or days before the intended shipment date. We are
>> provided "latest" technical details drawn directly from the documentation
>> of three years ago. It's sort of like being a ship at sea, blown about by
>> the winds, or becalmed in muddy waters through no direct fault of our
>> own.
>> I recommend the catch-all title of "Captain."
>>
>> Yes, "Captain" has legal implications when at sea, but one can be captain
>> of a rowboat, a canoe, or a Sunfish sailing dinghy and hardly anyone will
>> complain. It is also the proper title to use for speaking to the skipper
>> aboard a Maine "windjammer" schooner cruise, even though no authority has
>> granted it.
>>
>> To defend the use of "Captain" merely point out that "Your Holiness" (or
>> Her Holiness) seemed a bit too much.
>>
>> On Mon, 09 Aug 2021 22:18:50 -0400, Robert Lauriston
>> <robert -at- lauriston -dot- com> wrote:
>>
>>> Director of technical documentation?
>>>
>>> High-level tech docs roles commonly spill over into other realms. I
>>> don't think that means we need ambiguous titles about "content' or
>>> "information."
>>>
>>> On Mon, Aug 9, 2021 at 4:45 PM Suzette Seveny <suzette -dot- seveny -at- gmail -dot- com>
>>
>>> wrote:
>>>>
>>>> My title (and job description) is currently being reviewed to align more
>>>> with my activities.
>>>>
>>>> I was a Technical Writer.
>>>> Then they called me a Documentation Manager (I managed the process, and
>>>> assumed a lead role).
>>>>
>>>> Now, in addition to "writing the online help and PDF manuals",
>>>>
>>>> I contribute to:
>>>>
>>>> - Online help
>>>> - Video tutorials (more internal at present, but growing to include
>>>> customers)
>>>> - API documentation
>>>> - Knowledgebase
>>>> - FAQs
>>>> - User Group Sessions
>>>> - Almost a SME in Lending and Retail Banking (I had my mortgage agent
>>>> license)
>>>>
>>>>
>>>> I'm not the only person in my department. We also have a technical
>>>> writer
>>>> (more junior) and a UI/UX designer. But I've been here long enough
>> that
>>>> my
>>>> name is synonymous with client documentation.
>>>>
>>>> We have 14 subsystems with 3 add on modules. The work was all originally
>>>> mine (until I had to go on stress leave lol).
>>>>
>>>> PS - Documentation Goddess and Protector of Information was considered
>>>> too
>>>> lengthy.
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> Visit TechWhirl for the latest on content technology, content strategy
>>> and content development | https://techwhirl.com
>>>
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>
>>> You are currently subscribed to TECHWR-L as neilson -at- windstream -dot- net -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
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Visit TechWhirl for the latest on content technology, content strategy and
>> content development | https://techwhirl.com
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> You are currently subscribed to TECHWR-L as suzette -dot- leeming -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
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as sharipunyon -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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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


References:
Re: What's in a name?: From: Peter Neilson
Re: What's in a name?: From: Suzette Seveny

Previous by Author: Re: California AB-2257 (from 2020) - effect on/affected by other contract law ?
Next by Author: Re: What's in a name?
Previous by Thread: Re: What's in a name?
Next by Thread: Re: What's in a name?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads