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: What do you call policy/process/procedure structure?
Subject:Re: What do you call policy/process/procedure structure? From:Shari Punyon <sharipunyon -at- gmail -dot- com> To:Monique Semp <monique -dot- semp -at- earthlink -dot- net> Date:Tue, 21 Apr 2020 20:21:10 -0400
Yeah, I've often put that together for the actual documentation, but I
think of the "Process/Procedure" world as separate I guess, because it is
generally part of an overarching "the way we run our company" type of
thing. I've never been anywhere before where at least a *basic* structure
hasn't been in place, and you just fill in which actual documents you need.
I think of that type of thing being something where people pay way too much
money to have some outside firm tell them what to do.
On Tue, Apr 21, 2020 at 7:03 PM Monique Semp <monique -dot- semp -at- earthlink -dot- net>
wrote:
> Hmm... Decades ago, when we wrote 20-page doc plans for projects, we
> included those things that you've mentioned: doc types, structure of them,
> format/header/footer requirements, reviewer rules, and much, much more. So
> I do not think of any of that as "way outside standard tech writing stuff."
> Now given today's "agile" world and the fact that we largely work from
> checklists these days, especially in docs-as-code environments where our
> "doc plans" are basically JIRA tickets, GitHub issues, Trello cards and the
> like, yeah -- that sort of thing does often fall through the cracks. But
> that doesn't mean that it's not regular tech writing.
>
>
> On 4/21/20 2:39 PM, Shari Punyon wrote:
>
> Way outside standard "tech writing stuff"
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com