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.
Boy is this a timely topic for me. I have been working for two years on a
massive manual for a southern state, and all along the way, the PMs stated
dogmatically that they wanted it to be a PDF. So I have created a type of
Web site from a PDF that is really cool.
Enter the new PMs . . . After about fifteen minutes of getting, maybe, 5
percent up to speed on the previous two years, they decide to scrap
everything, and save the PDF to a raggedy Word HTML file and put it on the
web. So there goes two years of exceptional work.
You know, what I have learned is that no matter how long you work for a
company and no matter how great it is, sooner or later you run into what I
call "The Department of Small Minds" Every company or corporation has one,
and it is only a matter of time before you find them or they find you.
This is how you can tell that you have entered the Department of Small
Minds:
1. A new PM enters the scene
2. The new PM has no eye for quality work, and really doesn't care. The PM
wants functionality, not style. The redwood picnic table in the kitchen will
do.
3. The new PM wants to control you completely, but they don't want that fact
to be obvious, so they proceed in what they believe is a slick manner. All
the while their intent is blindingly obvious.
4. The new PM says things such as "have you ever considered this," or "would
it better to do it this way?" These questions ALWAYS reference an idea that
has been disgarded long ago due to the idea's total weakness.
5. Any creative idea is immediately crushed. The Department of Small Minds
does not like creativity; it is tremendously threatening to them. They like
the familiar, the easy, the freakin usual.
Anyway, my project began with a steering committee and a project management
firm that knew how to build world-class hotels and casinos, but didn't know
JACK about creating a publication. I suggested a number of things that would
have helped, but they knew better.
After they were let go, my project management moved up a level to the
Governor's people. It was only through time and experience that I learned
who signed off on the project because a number of people had equal say in
theory, but practice proved the players.
I have to cut it loose there. I'm rambling. I have to turn this monster in
at 9am, and I have about four days work to do until then.
We have something in common--we have both run into the Department of Small
Minds.
Stay Strong
Kirk Turner
-----Original Message-----
From: techwr-l-bounces+royj=hughes -dot- net -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+royj=hughes -dot- net -at- lists -dot- techwr-l -dot- com] On Behalf Of
James Barrow
Sent: Saturday, July 21, 2007 9:58 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: PM Woe
Hello All,
My questions are these:
To whom do you report (what department)?
How much control does your project manager have over your daily activities?
The groups above were tasked with developing the following documents:
Document Creation
Document Change Request
I wrote the Document Creation doc and kept it fairly generic with our
organization's departments fitting nicely within a RACI matrix. The PMO
signed-off on this...then she went on vacation. This caused her PMs to
submit all sorts of changes to the document and the document creation
process. The most glaring of these were that the TWs had to ask permission
at every step of the process (permission to start a doc, permission to talk
to a SME, permission to submit a doc, etc.) It was absurd.
I pushed back and got a few of these steps deleted from the process.
Unfortunately, a few remain that make the process sound as if the TWs are
parolees. So, how do you handle your document creation process?
Do you inform your PM every time a document is started?
Do your PMs approve any templates that you create?
Who has the final sign-off on a document?
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as royj -at- hughes -dot- net -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
