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: Should the Doc Manager be equal to the Dev Manager? (LONG)
Subject:RE: Should the Doc Manager be equal to the Dev Manager? (LONG) From:"Glenn Maxey" <glenn -dot- maxey -at- voyanttech -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 7 Aug 2001 08:41:47 -0600
Based on the persuasive arguments that you have provided (Arguments for
a doc mgr, Arugments against a doc mgr, and Arguments for reporting to
dev mgr), 2 against 1 you have convinced me that you should keep the
current chain of command. Your company isn't big enough to support lots
of chiefs and few indians.
The syncher for me was that the dev mgr is also QA mgr, product mgr,
proj mgr, and doc mgr. If any position screams to be broken out from
under this umbrella and needing equal footing and voicing when reporting
to the VP of Operations, its the QA mgr and not the doc mgr.
QA needs to be able to say "No, this product isn't ready for prime time,
because it doesn't work. Fix it, or we don't release it." How can you,
as an equal doc mgr, provide more benefit to the quality of the release
than this? "No, this product isn't ready for prime time, because the
documentation (a) sucks, (b) is incomplete, (c) is a sauve for a shoddy
design?" Methinks thou seekest too much honour and glory when there is
none.
I, personally, wouldn't want to be shot up the flag pool to this guy's
level. If he were to become a Director and spin off his many hats to
others, I would say "go for it and become that doc mgr" reporting to him
(and not the VP). Until that time, don't let your ego overshadow the
realities of your company.
> -----Original Message-----
> From: Teemu S. [mailto:tselane -at- home -dot- com]
> Sent: Monday, August 06, 2001 6:22 PM
> To: TECHWR-L
> Subject: Should the Doc Manager be equal to the Dev Manager? (LONG)
>
>
> Do you think the Documentation Manager should be equal to --
> or report to -- the Development Manager?
> 2. The Dev. Mgr has "too much" authority.
> Development Manager also acts QA manager, product manager,
> project manager,
> and doc manager. There is no one equal to him. (There is no
> support manager;
> support staff operating relatively independently.) The only
> people higher
> than him are his boss (VP of Operations), the VP of
> Marketing, and the Pres.
> I think having someone equal to the Dev. Mgr would provide some
> accountability and balance.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
A landmark hotel, one of America's most beautiful cities, and
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe. http://ieeepcs.org/2001/
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
