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.
I am a Business Systems Analyst in the IT dept of our organization. We have recently had a change o
Subject:I am a Business Systems Analyst in the IT dept of our organization. We have recently had a change o From:"Brenda Duncanson" <Brenda_Duncanson -at- mtha -dot- gov -dot- on -dot- ca> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 30 May 2000 09:00:21 -0400
I am a Business Systems Analyst in the IT dept of our organization. We have recently had a change of top management and now I need to justify why our programmers can't and shouldn't write the documentation [we are years out of date].
I have been asked to write a justification for hiring a tech writer to document our systems - we are in dire need but have to convince the higher ups of this need.
I feel frustrated and too close to the situation and am asking for some objective explanations.
Any brilliant suggestions? Any solid reasons as to why we cannot go another minute with out having our systems documented? Our IT department reports to Finance and our CFO is a very demanding task master. It is he I need to sell the idea to.
Thanks in advance for your help,
Brenda Duncanson
Business Systems Analyst
MTHA
416-969-6127
Brenda_Duncanson -at- MTHA -dot- gov -dot- on -dot- ca
