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.
Subject:Don't Take Notes, Goats, or Bull! From:"Stephen C. Gillespie" <sgillespie -at- FEDEX -dot- COM> Date:Thu, 21 Jan 1999 08:40:37 -0600
Thanks for all of you -- male, female, or otherwise, who validated my
point...just one thing to clarify: I didn't mean that I "didn't take
notes" (at all)...of course, I do! I just don't take notes for the
project meeting (unless ORDERED to do so, of course).
Any project lead/manager worth his/her salt will realize the importance
of DOCUMENTING all relevant information pertaining to the progress made.
This is simply basic PROJECT MANAGEMENT. In my current org, I have not
been to a project meeting where this is not done: minutes, specs,
project objectives, business plans, work breakdown structures,"features
of service," "operating scenarios," schedules, and other pertinent
project records --all provided by the project lead/mgr or through
team/committee. Any of this sound familiar?
thanks, again,
Steve Gillespie
Project Lead/Editor
FedEx Ground Operations P&P Program (Policy Analysis)
Memphis, Tennessee
