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.
>There have been two basic problems in the production schedule:
>first, I was given roughly one tenth of the time the project actually would
>require (given its scope), and secondly, my project leader keeps changing my
>priorities (one week it is to get a small section of it stable so it can be
>passed over to another team member for translation into French, the next
>week it is have an interim version we can release to the user population by
>the end of the week, and so on)....
Been there, done that. :-) or :-(
Three words -- document, document, document.
I found that it helped me to create a flow chart that included the various
pieces of the system, so that I could make notes about my progress on each
piece. This made it easy to see how each piece related to the others, and if
I had to make changes to one piece, I could easily see where I needed to
change the related pieces.
You may also want to keep a log of your daily progress including every task
you are asked to do and every change you are asked to make. Don't just
record the negative aspects of the project. Try to find some positive
aspects -- things that worked well -- input that helped you. This can serve
two purposes:
1) It will help you organize your progress in your mind and will force
you to see that you are, in fact, making some.
2) In the end, when this mis-managed project is evaluated (assuming that
it will be), you and your help system shouldn't have to take the fall. Your
records may protect you, and they might help the "team" to work together more
efficiently next time.
I was fortunate. My job was a contract. I could fire the client.
Good luck.
Gayle Stroup
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html