7 Habits of Highly Ineffective Project Managers


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • This is kind of like having one of those relationships with someone where all you do is talk about the relationship. You know the ones, right? You don't actually get a chance to have a relationship and instead all you do is spend your time talking about the kind of person you want to be and the kind of person he/she should be.
  • Really, this is sort of self-explanatory, but the more time you spend
  • 7 Habits of Highly Ineffective Project Managers

    1. 1. <ul>The 7 Habits of Highly Ineffective Project Managers </ul><ul>Carol Smith Google, Inc. </ul>
    2. 2. <ul>Who am I? </ul><ul>-Googler -Project manager in network operations, enterprise software, and now open source software -Administering the Google Summer of Code program for the Google Open Source Programs office </ul>
    3. 3. <ul>Habit 1 </ul><ul>Spend more than 2 hours per week in meetings with the engineers going over the project. </ul>
    4. 4. Habit 1 <ul><li>Maker's Schedule, Manager's Schedule – Paul Graham
    5. 5. If you're spending more than 2 hours per week in meetings about the project, how much time have you got to actually work on it?
    6. 6. Ask yourself if you're empowered to do your job. </li></ul>
    7. 7. <ul>Habit 2 </ul><ul>Assume all the engineers you work with are purposefully trying to do a bad job and sabotage the project. </ul>
    8. 8. Habit 2 <ul><li>Assume competence.
    9. 9. People want to take pride in their work and do a good job. </li></ul>
    10. 10. <ul>Habit 3 </ul><ul>Keep a checklist. </ul>
    11. 11. Habit 3 <ul><li>Constant pings to an engineer about when a task will be done does not project management make.
    12. 12. Be familiar enough with the project and technical details to understand when an engineer tells you why a task has been delayed. </li></ul>
    13. 13. <ul>Habit 4 </ul><ul>Let your middle-level and senior-level managers meddle with the timeline and the goals of the project whenever they see fit. Extra credit: Let managers talk to the engineers and confuse them about your own purpose on the project </ul>
    14. 14. Habit 4 <ul><li>It's human nature to want to meddle in something for which you are ultimately responsible.
    15. 15. Maintain your credibility and authority and managers will feel less inclined to meddle. </li></ul>
    16. 16. <ul>Habit 5 </ul><ul>Make everything an emergency.  </ul>
    17. 17. Habit 5 <ul><li>Don't cry wolf.
    18. 18. Get people to understand that when you do say something has to be done today it really does. </li></ul>
    19. 19. <ul>Habit 6 </ul><ul>Break down your rapport with the engineers whenever possible. </ul>
    20. 20. Habit 6 <ul><li>Be personable, be approachable, be sensible.
    21. 21. Cookies
    22. 22. It takes some people time to feel comfortable with their coworkers; this is even more true for engineers. </li></ul>
    23. 23. <ul>Habit 7 </ul><ul>Assume the dates that the engineers give you are spot-on and make promises to customers and coworkers based on these dates. </ul>
    24. 24. Habit 7 <ul><li>Everyone wants the reaction of, “Wow, I didn't know you could do it so quickly!” Not, “Wow, it's going to take you that long?”
    25. 25. Know the engineers you work with well enough to not have to ask them how much they are(or aren't) padding their estimates.
    26. 26. Underpromise and overdeliver. </li></ul>
    27. 27. <ul>Special Thanks to: </ul><ul>Stephen Covey, author of The 7 Habits of Highly Effective People </ul>Josh Berkus, for the idea of the &quot;7 Habits of Highly Ineffective...&quot; Paul Graham, for the “Maker's Schedule, Manager's Schedule” article - http://www.paulgraham.com/makersschedule.html