The requirements for communicating project status to executives are often paradoxical: Be brief but thorough; don’t go into the weeds, but make sure I know all the important details. Responding to these constraints can be challenging, but you still need to clearly convey your work's significance and risks.
Payson Hall is a consulting project manager for Catalysis Group, Inc. in Sacramento, California. Payson consults on project management issues and teaches project management. Email Payson at [email protected]. Follow him on twitter at @paysonhall.
Connect with Me
All Stories by Payson Hall
Project managers often dread doing reviews, but they're necessary to make sure the project is on the right track. Progress can be affected by unclear definitions, risk, schedules, and cost, so it's important to evaluate whether the project manager, sponsors, and team members are all on the same page.
Programmers working with legacy systems often seek to understand how the program is designed, but that's not enough. When trying to understand legacy systems, special care must be taken to also explore, identify, and take inventory of interfaces, which can be integral to the entire system architecture.
People worry that asking for assistance will somehow undermine their standing in the eyes of peers or employers. But most successful people are quick to acknowledge what they don’t know and to ask for assistance. Honestly admitting to limitations in your knowledge is the sign of a true professional.
When life's little stresses start piling up, it's easy to become overextended before you're aware of it. Instead of ignoring the chaos that's slowly building, try to notice your personal warning signs that you're heading for a crash so you can correct your schedule and priorities before it's too late.
Of course meetings are often necessary, but sometimes they are just rituals without meaning. At your job, would anyone recognize if a meeting weren't efficient or essential? When was the last time a meeting you were scheduled to attend was canceled because it wasn’t a good use of anyone’s time?
We're all aware of the risks from projects that have overly aggressive schedules. But projects with leisurely schedules have risks, too. Extending a timeframe is supposed to give you more time to create quality products, but it can also lead to procrastination, changing teams and expectations, and more.