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.
Subject:RE: Where does Documentation belong? From:"Karen E. Black" <kblack_text -at- hotmail -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 10 Feb 2004 10:46:18 -0500
1989-1994. Financial Systems (IT) > Training & Documentation. Learned a lot
about mainframe software, policies & procedures, usability, online docs...
1994-1998. Information Technology > Customer Service > Quality Assurance >
Documentation. Worked well, great boss, lots of communication with all
groups.
1998-1999. Information Technology > Customer Service > Customer Support
(i.e., Helpdesk) > Documentation. Could have worked, but lousy boss. No
contact with anyone any more.
2001-present. Information Technology > Relationship Management & Delivery >
Quality Assurance. I am editor of software lifecycle documents, a software
quality analyst, and software release coordinator. Not a writer any more,
but people ask me to review their résumés and cover letters...
Where does documentation ultimately belong? Beats the heck outa me.
Karen Black in Toronto, still trying to persuade mgmt of the ROI of
documentation when we have to roll back the same implementation twice ...
because there was no technical design
