Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Fri, Nov 20, 2009 15:04 EST
|
Posted by: Josh Nankivel in Questions Topic: IT Organization Management
Current Rating: |
What I wish I had known when I moved from a technical role into project management!
Don't act like you know it all 
When you're new to a role, it's natural to cover up your own ignorance. You want to earn respect, and everyone is looking at you. So you may not speak up when a topic is discussed that you don't understand...you nod your head instead of asking a "stupid" question.
Here's the thing: you will only learn by asking questions. Why not do it while you're still the "new PM" on the block? Your teams and collegues will cut you some slack for awhile, but not for long. You need to learn quickly, and the best way to do that is by asking "stupid" questions.
Be results-oriented
Start asking yourself the following question constantly. "What is the goal?" Apply that to every part of your day. In a meeting? What's the goal? You assigned a task? What's the goal? For your project as a whole or pieces of it....what's the goal? What does "done" look like and how will you know you've acheived it?
Hone your people management skills
Managing people is what project management is about. If you can't manage people well, get better at it or go back to being an individual contributor. Luckily, management skills can be taught, and you can become a great manager (even if you stink at it now!)
Hone your project management fundamentals
So many project managers, new and experienced ones, fail to grasp some of the most fundamental concepts specific to project management. For instance, if you think a WBS is a task list and not a primary, central artifact to manage your project, please go get some good training on it.
Hone your political skills
The great thing about managing projects is that you get to interact with everyone! You need to speak the language of your team, sponsor, and key stakeholders. Understanding the incentives and needs of each individual and group goes with the territory.
You also need to be able to negotiate compromises between these individuals and groups. This takes finesse and you'll probably screw up at least a few times. Just realize what this is and get better at it. Use tools like a stakeholder analysis to formalize and articulate the process.
Learn how to run meetings well 
This goes along with general management skills and being results-oriented, but I can't stress it enough. Running great meetings is a science that can be learned, and you need to protect your team from being involved with poorly-run meetings as much as possible. Meetings should have an explicitly stated goal, clear time-based agenda, be facilitated well, and followed up on with minutes and accountability assignments.
Trust your teams
Too many new project managers come into a team with a good intention, but it comes across like this. "I'm the new project manager. You've all been doing things wrong, and I'm here to fix your problems."
That doesn't go over well. I have a 60-90 day change policy. Unless it's going to make the project fail, I don't change anything except for a few general management basics for 60-90 days. I tell the team this is my policy. I give them the
I like the advices you give. I'm quite new with the whole project management area and it's nice to read articles for a "beginner". I liked lots of "Don't act like you know it all" because I really don't much, at least not yet. I'm all the time asking whats this and this or using Google to find explanations for new words etc. It's good to bring up involving your team and how to treat them. Sometimes we just forget the basic things and assume that everything is done ok. But sometimes there can be some deficiency...
I agree, that's why I started my blog at pmStudent.com, to address the questions that new and aspiring project managers have. A lot of PM articles look like gobledy-gook to people who are new to the discipline.
Josh Nankivel
WBS Training
Hi Josh,
Here's a couple more:
- Don't micromanage (which may be included in the "Trust Your Team" point)'.
- Know who your real stakeholders are. Stakeholder identification is extremely critical to have the full picture of the real requirements.