Lessons Learned for Project Managers - Part II

November 4, 2008 | Author: PM Hut | Filed under: Lessons Learned, Project Management Best Practices, Project Management Musings

Lessons Learned for Project Managers - Part II (#2 in the series 128 Lessons Learned for Project Managers)
By Jerry Madden

  1. Know who the decision makers on the program are. It may be someone on the outside who has the ear of Congress, or the Administrator, or the Associate Administrator, or one of the scientists — or someone in the chain of command — whoever they are, try to get a line of communication to them on a formal or informal basis.
  2. You and the program manager should work as a team. The program manager is your advocate at NASA HQ and must be tied in to the decision-making and should aid your efforts to be tied in too.
  3. A project manager should visit everyone who is building anything for his project at least once, should know all the managers on his project (both government and contractor), and know the integration team members. People like to know that the project manager is interested in their work, and the best proof is for the manager to visit them and see first hand what they are doing.
  4. Never ask management to make a decision that you can make. Assume you have the authority to make decisions unless you know there is a document that states unequivocally that you cannot.
  5. Wrong decisions made early can be salvaged, but “right” decisions made late cannot.
  6. Never make excuses; instead, present plans of actions to be taken.
  7. Never try to get even for some slight by another project. It is not good form — it puts you on the same level as the other person–and often ends up hindering the project getting done.
  8. If you cultivate too much egotism, you may find it difficult to change your position — especially if your personnel tell you that you are wrong. You should instill an attitude on the project whereby your personnel know they can tell you of wrong decisions.
  9. One of the advantages of NASA in the early days was the fact that everyone knew that the facts that we were absolutely sure of could be wrong.
  10. Managers who rely on the paperwork to do the reporting of activities are known failures.

Reprinted with permission from NASA. This article first appeared in NASA’s ASK Magazine, the NASA source for Project Management and Engineering Excellence.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

Related Articles

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories