Current Issue

Chapter News
Features
Viewpoints
Student Views
From the Editor's Desk
Message from the President
Reviews
Society Notes & Community Announcements




 Article Archives 

Book Review
Career Development
Case Studies
Content Management
Contracting & Consulting
Core Competencies
Meeting Reviews
Usability
Networking
Online Help & Embedded Assistance
Technologies
Translation and Localization
Up and Coming Corner
Information Architecture


 Past Issues 

May, 2012
April, 2012
March, 2012
February, 2012
December, 2011
November, 2011
October, 2011
September, 2011
August, 2011
June, 2011
April, 2011
February, 2011
January, 2011
August, 2010
July, 2010
June, 2010
May, 2010
April, 2010
March, 2010
February, 2010
January, 2010
December, 2009
November, 2009
October, 2009
September, 2009
July, 2009
June, 2009
May, 2009
April, 2009
March, 2009
February, 2009
December, 2008
October, 2008
September, 2008
May, 2008
April, 2008
February, 2008
January, 2008
November, 2007
September, 2007
August, 2007
April, 2007
March, 2007
January, 2007
November, 2006
October, 2006
September, 2006
August, 2006
March, 2006
February, 2006

A little project management goes a long way

Share on Facebook :: Printer Friendly Version

—by Susan Patch

Published: February 2006 in Book Review, Viewpoints

We can lose sight of the fact that our work still needs to be managed, even if it is only us doing the managing.

Project management is not a core skill normally associated with technical writing, but it is one that technical communicators should have in their toolkits. I am not talking about heavy-duty project management exemplified by formal processes and important-sounding polysyllabic words, but about common sense — practical project management that is about getting the job done efficiently and effectively.

Technical communicators frequently do work that is or is perceived to be part of a larger project rather than a project unto itself. Unless we are involved in managing a department, we can lose sight of the fact that our work still needs to be managed, even if it is only us doing the managing. Anyone who has ever worked in the high-tech sector is familiar with our part of the project being allocated little more than a line or two at the end of the work plan.
One of the most practical and down-to-earth books on project management that I have read is The Art of Project Management by Scott Berkun (O’Reilly Media, 2005). Berkun’s writing style is lively — he makes the subject entertaining while providing a wealth of practical information. And he cuts through the jargon associated with the topic of project management.

In The Art of Project Management you will find useful tools and techniques immediately applicable in the workplace, described in a way that anyone can understand. Although the book is obviously rooted in the world of engineering and software development, Berkun manages to distill the information into a form that can be applied to other disciplines. Because of this, the book becomes a useful tool for any situation in which a technical communicator might find him- or herself working.

At the risk of stating the obvious, one way that not managing your work or project can cause you to suffer is by allowing other people to disrupt the flow of your work. This is particularly relevant if you need SMEs to provide the information that you need to do your job. If you have to wait for someone to complete his or her work before you can complete yours, you are at the mercy of your co-worker’s process and timing.

I have both observed and experienced how challenging the situation can become if the person you are depending on for your information is overworked or just chaotically disorganized. If you do not manage the situation, you can find yourself continually struggling to deliver your work at the last minute because you have not had sufficient time due to your co-worker’s lateness.

One of the hardest things to learn is to not take extraordinary measures to compensate when someone else’s timing has affected your delivery deadline. Project management includes communicating with the team when you see that deadlines will be affected.

I highly recommend reading The Art of Project Management for the real-life examples and hard-earned experience shared throughout the book. Find some tools that resonate with you and your particular situational challenges, use the checklists provided, and put your creative problem solving to work. After all, what can you lose except some of that stress!


Pull quote:

Susan Patch is the treasurer and past-president of the STC CWC Chapter.

Previous: How not to look for work

Next: Core competencies for a job I fell into?


 Subscribe via RSS

Visit the main STC website.

STC advances the theory and practice of technical communication across all user abilities and all media.


STC-related links

Note: You may need to be logged into these services to view the pages.

©2012 STC CWC | Home | .(JavaScript must be enabled to view this email address)