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.
Hi guys...if anyone remembers this request... I went with "Documentation
Services".
Thanks to everyone who had suggestions.
On Fri, Apr 13, 2018 at 4:46 PM, John Posada <jposada99 -at- gmail -dot- com> wrote:
> Hi, guys....long time.
>
> My department has been expanded and I'll be managing it.
>
> For the org chart (and for other reasons), my manager asked me what I
> wanted to call the department. The my personal title is another issue
> because our group just has never had someone who only does documentation
> and they are still trying to come up with a slot in the hierarchy.
>
> I just don't want to call it "Documentation" because the bank uses that
> term as encompassing anything that isn't code as well as using it as a
> verb.
>
> I'll be responsible for:
>
> - Regulatory submissions
> - Policies
> - Functional, Technical, and Business Requirements Documentation
> - Change Notices
> - Instruction Manuals
> - Methodology documents
> - Procedure documents
> - etc. (The scope is still being defined)
>
> What department titles do you use or have you seen. I'm going to scan Job
> Lists and Linked-In, but that I'd reach out here also.
>
> Thanks
>
--
John Posada
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
