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.
You have to be careful in the way you label yourself because you will be screened by recruiters who won't understand the differences you mentioned. IMHO, I'd stick with technical writer and then list the type of work that you did. That will make it past any recruiter and the "key words" you use in the description will help you get through to the managers whose eyes you want to view your resume.
If you get too specific, you'll weed yourself out of any selections...
Lin Laurie
206.900.1861
www.linlaurie.com
-----Original Message-----
From: techwr-l-bounces+linlaurie1=hotmail -dot- com -at- lists -dot- techwr-l -dot- com <techwr-l-bounces+linlaurie1=hotmail -dot- com -at- lists -dot- techwr-l -dot- com> On Behalf Of Shari Punyon
Sent: Tuesday, April 21, 2020 9:47 AM
To: TechWhirl (techwr-l -at- lists -dot- techwr-l -dot- com) <techwr-l -at- lists -dot- techwr-l -dot- com>
Subject: What do you call policy/process/procedure structure?
Hi all,
I was just working as a knowledge manager/technical writer at a company, and they let all the contractors go (including me). I'm now updating my resume, and am not sure how to describe the fact that I set up the structure of polices, processes and procedures for their "Enterprise Technology" area. I didn't just write documents within an existing structure- although this was a long running and successful business, they didn't have a basic paradigm.
I did some research, and decided that we would be using Processes & Procedures (rather than Standard Operating Procedures & Work Instructions, for example). I wrote up descriptions of each type of document and when they would be used, created templates and guidelines, and the Enterprise Technology area implemented. We then created a good amount of documentation using the templates I created. I also determined (with management) the release, review and versioning paradigms.
But is "governance document structure" the correct way to describe what I made? I want to capture what I did, but not overstate - this was was limited to a part of their IT department. It did not touch Human Resources, Legal, etc. although it may propagate to those areas, as no other part of the company had a competing structure! I just don't want to imply that I was somehow involved in figuring out, for example, the management structure.
Shari
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
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
