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.
-> 11. Make sure you know who is supposed to be in charge of the document
-> and what your role is.
It's also useful to know who's in charge of the project <g>
On that note, I had an interesting discussion with the boss about how
project management fits into a "creative anarchy" style of development.
We want to be able to keep the free exchange of ideas paramount because
that's really at the heart of our corporate culture, but we don't want
to get snowed under with flowcharts, intermediaries, rigid
specifications, paperwork and bureaucracy that seem to evolve from most
models of project management I've seen.
We both left that meeting with more questions than answers, which is a
good thing.
-> my biggest nightmare has been either cases in which the
-> person who was supposed to be in charge would not or could not manage
-> the project, or those in which I was given responsibility over the
We want to avoid that scenario at all costs. A small company with a
handful of people can "share the vision" and work towards a common goal.
As companies and projects get bigger, as ours are sure to do, projects
get more and more fragmented, and the person with the vision is not
always in direct contact with the people expected to carry it out, and
is not necessarily the one directly managing the project.
So ... I don't wanna see no GANTTs, or PERTs or critical paths or any of
that stuff, I had enough of that in college and my boss breaks out in a
rash whenever I bring it up. What's a good model of project management
that lets us have our fun and still keeps everyone working together to
get the product out on time?
