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.
>With this last project, I wrote up a project plan..... It included
>responsibilities, dependencies, and deadlines. I forgot that most
>people don't read this sort of thing, so next time I'm going to go over
>it verbally as well.
Verbally won't help; they'll miss your meeting or forget they agreed.
The trick here is to put a cover memo on the project plan asking (very
non-defensively, very non-threateningly) for it to be initialed and
returned by a certain date with one of the appropriate boxes checked:
either "approved", "approved with comments", or "see me".
By the day after that date, you can start bugging them for their
comments/approval, and if they continue to stall, you can procede to
whatever next steps you want to take whenever it seems most efficacious
to do them.
Technical Writer, Editor, Page Designer
Producing clear, concise, accurate documentation for technical
wmblank -at- ix -dot- netcom -dot- com