Derek Rose is to many Chicagoans as the star team member is to an IT project. He's who you count on to drive the team even if you don't ask him to. He's the one who has the most skills and knowledge because he has passion for what he does. He's someone who listens to the Coach and offers advice at the right time that is deemed necessary and valuable to everyone involved. He isn't afraid to ask questions or be a team player because he knows exactly how useful he is to the team.
Derek Rose is this year's NBA's MVP (Most Valuable Player) because of all of the above attributes he brings to the team (and I also like to think no one wanted to give the MVP to his annoying pompous nemesis, Lebron).
Similar to the NBA, the organization relies on the Project Managers (Coaches) and their teams to bring success to the organization through their various projects. Throughout these teams, there's usually that one MVP team member who you use for their knowledge, teamwork, and experience.
The problem, which Derek Rose had, is that our MVPs are overworked (playing all 4 quarters in every game), or carrying a heavy load of responsibility, or letting others down if they do not perform at their highest standards at all times. After watching Derek Rose last night, I decided that the MVP may not be the best thing to have on your project. Wouldn't it be ideal to have everyone equal (especially if they're all extremely great at what they do). However, MVPs are a reality. If you do have an MVP, here's how to make sure there's no let down at the end of the project.
Encourage Creative Shots in the Beginning
Derek Rose (and his other teammates) flawed throughout games 3 and 4 of the playoffs by taking these creative (and in the end, worthless) shots in the last minutes of the game. New ideas, creative moves, and risky shots should be what happens in the beginning, not when we can't correct our mistakes. By the end, the pressure to be successful and finish is way too strong, putting even more demands on the team members, much less your MVP. It is much harder to fix something with only a week to go on a project than it is when it is the first week of the project. Take advantage of the time you have, build in 'playing around' in your timeline, and take those crazy shots in the beginning.
Allow All Team Members to be MVP
The only MVP award I was presented with was in 5th grade for the Most Vicious Pinky. Yes, we used to play thumb wars with our pinkies (enough on that topic though). Although my MVP honor didn't put much pressure on me (okay, maybe on my pinky), it did allow me to feel honored, just like any award does to someone. No matter what, an honor is an honor and everyone wants to be the MVP at some point.
My suggestion; allow all of your team members to be the MVP. For instance, allow other team members to:
- Hold a meeting or two in your place
- Attend a meeting with you (as the SME) that's with upper management
- Be the first point of contact for questions you have that normally would go to your MVP
- Decide what (s)he feels is best to do on a piece of functionality
I'll use the example of Kurt Thomas, who usually sits on the bench. Last night, for one night, he came on the court and played like he was an MVP, making shots that helped Bulls fans feel better about the game. I credit their coach for keeping him active in trainings and allowing him to step up. Final words on the topic: We all want to feel special (feel free to insert an adorable "aww" here).
Recognize Reality
This one's a quick point: Recognize that your MVP is a person. What does that mean? It means we make mistakes. It means we try and we fail. It means we get nervous. It means we need help every once in awhile. It means we could let you down because your expectations are way too high and unrealistic. Just recognize and accept these facts and there will be no need for let down.
Don't Stop Coaching Ever
Don't give up! Don't stop coaching! Unfortunately, in Game 4 last night, the Bulls and our MVP, Derek Rose seemed to give up. Game 3 was different, we tried to the very last second to win and it showed. This team mentality has to come from the coach. Always be there for your team. Coach them through questions, impediments, training they need, etc.
Being a Project Manager isn't about directing or simply implementing projects. It's about coaching your team to be successful.
Think about it. Like Derek Rose was, the best high school athletes are aggressively recruited by colleges, promised the best in life, and given a multitude of colleges to choose from. Yes, they may choose to play for different teams based on many reasons. However, I'm guessing a major decision maker is the coach.
Don't be a good Project Manager; be a great one and include coaching in your skillset. If you're not familiar with how to successfully coach, read books, view webinars, do something. And, once you start coaching, don't stop ever!
