Posts Tagged ‘leadership’

Are you getting the truth?

Sunday, September 20th, 2009

A project manager needs to hear the truth from the team and the sponsor. In a project that is making significant changes in an organization, the PM can only be successful if they get the truth. It’s not a case of “you can’t handle the truth” but more of a case of “you can handle anything as long as you get the truth.”

Let’s look at this from the team, then the stakeholders, and finally the sponsor.

The project manager is responsible to ensure the project team has the information they need to successfully deliver on the project objectives. The other side of that coin is that the project team needs to make sure the PM knows everything they need to know to successfully manage the budget, schedule and scope of the project.

What happens when the team starts cranking the sunshine pump? Let’s say there’s a deadline coming up and it’s a key decision point. The PM follows up on the progress half way through the work package. The team states everything is on track, they’ll make the deadline. Well, great news! Except, the team knows that they might be on time but the next task needs to be completed by a person who isn’t dedicated to the project and is known for being late with deliverables.

As the PM, you need to know what issues are coming up so you can handle them. As the team, they may not want to get the other person in trouble, or may have spoken up in the past and been ignored. Your job is to dig a bit deeper. You don’t ask how the team is doing and leave it at that; it’s too easy for them to dodge the hard message. What you do is ask the next question, too; do you see anything coming up that might change the status of the deliverable? Or, you can try to challenge them by asking what could we do to come in early?

The trick is to ask more questions until you are sure there’s nothing hidden, without interrogating your team.  Don’t worry; over time you can build a level of trust with your team that will reduce their need to protect you from the truth.

Moving on to stakeholders; you may not get the truth you need from the stakeholders if there is something happening in their functional area that is considered confidential. This can slow down your project, or even put it off track.  How does this look? Often stakeholders will lose interest, or suddenly become more interested in your project. Or, they will question the goals of your project all over again. These behaviours should make your spidey senses tingle. I’ve had mixed success in dealing with this type of ‘untruthiness’. The most effective approach I’ve found is to take the helpful route; ask what you can do to help them deal with their concerns.. Unfortunately, I have sometimes found myself plugging ahead with the project knowing something is about to go sideways but not having anything to hang a risk or issue on.

Finally, your sponsor may not give you the information you need. It seems counter intuitive that your sponsor, the person you are doing the project for, would not provide you with what you need to be successful. Believe me, it happens. In my experience, it is usually politics underlying this behaviour. The only effective way I’ve found to deal with this is to accept that the sponsor has information they can’t share, and keep the project as on track as you can. The politics maybe temporary, or it may be the first steps towards closing your project. The important thing to remember is that it is not within your control. Unless you are given other directions from your sponsor, you have to assume nothing has changed. You are still expected to deliver on your project.

One of the underlying causes of sunshine pumping is simply organizational behaviour. No one wants to seem negative, or finger pointing. No one wants to get someone in trouble. I’m sure you’ve all worked with the team member who consistently gets things wrong, or causes problems on the team. Did anyone try to get the problem resolved, or did they just work around it.

Another cause of, is lack of trust.  People may have been burned in the past when they raised an issue and don’t want to risk the fall out again.

The important tip this week, handle what you can. You are responsible for ensuring the project is successful. You are not responsible for changing the organizational culture of the company – except if that’s what your project is supposed to accomplish.

This site has some good tips on questioning

Here’s another site with tips on questioning

Good luck out in project management world this week.

What’s the buzz about certification?

Sunday, September 13th, 2009

I’ve seen lots of postings on LinkedIn, and heard lots of arguments around the question of certification. I have to admit, I’m confused by the whole controversy. Certification isn’t a magic bullet, nor is it the political nicety that people seem to think it is. Certification is a choice for the most part. It’s often a must have to get a job, and it’s a validation that you’ve completed a minimum knowledge and experience requirement. Just like an MBA doesn’t mean you’ll be a successful business leader, a PMP doesn’t mean you’ll be a successful PM but it does say something about what you should know.

The experience requirement is interesting; it states a minimum number of hours, but not a success rate. So, you can participate in projects for the required number of hours (3 or 5 years depending on whether or not you have a degree) but never participate in what PMI would suggest is a successful project. The educational requirement is not that onerous, and can be completed by studying for the PMP certification exam.

I have to be honest; I did learn a few things as I prepped for the exam. I learned why some of the processes were needed; I realized why some issues rose again and again – it was because we weren’t doing a great job earlier in the lifecycle.  I also had to memorize things I’ll never use (or have to do manually). I can’t manually estimate duration to save my life – that’s why we have PM software – but, I do understand what the software is supposed to do. I can see where it’s wrong even if I can’t calculate it myself. I have never had to use Earned Value; I memorized it for the exam but I assume I will get a spreadsheet or something to use if I ever need to report Earned Value.

Are people afraid to fail? I did pass the first time (yes, I’m bragging) but I passed mostly on my people management experience. I know 5 other people who sat the exam, only one failed the first time – over thinking the questions is a killer. It’s no harder than any other exam, if you know your stuff, you will pass.

I recommend certification for people who want to be project managers, not just within their current employer, but as a career. When you are looking for a job, or contract, you will meet the criteria to apply. Right now, it’s a buyers market in the job hunting field. That said it’s rarely a sellers market. Why would you want to exclude yourself from eligibility for a job just because you are missing those three letters? As someone who used to hire project managers, I can tell you that I wanted certified applicants because I knew they had the knowledge, and hoped they had the skills. I couldn’t spend my time interviewing people who may have the knowledge and hope they had the skills.

I doubt you’d go to a doctor or a dentist if they didn’t have their certification; or fly in a plane with an unlicensed pilot. But, you have probably experienced a doctor with no bedside manner, a dentist who doesn’t have a gentle touch, and had a bumpy landing in a plane.  Why do you think project managers should be different, it’s a profession and as such has certification.

Maslow’s Hierarchy of needs as a project tool

Sunday, August 9th, 2009

In the eighties, it was fashionable for management teams to go away for retreats to learn the latest managment theory and how to apply it in the workplace to better lead their teams. I’m sure you can guess that after the retreat managers made some efforts to apply the new skills, but life and work got in the way. The latest theory joined the rest of the management flavours of the day, ignored and put on the shelf.  I think that’s a big loss, these theories were valuable and, with a chance to become ingrained, could have helped more companies become more successful.

This blog posting will touch on the theory of hierarchical needs, from Abraham Maslow. There are links below to a few other theories for thought. In short Abraham Maslow theorized that people have certain basic needs that must be met before they can move on.  Here’s what it looks like.

A graphic representation of the priority of needs

A graphic representation of the priority of needs

Looking at this from the top down – just to be different. One day you are sitting there, enjoying the day, thinking big generous trusting thoughts. The world is everyone’s oyster, peace on earth, etc. Suddenly you need to pee; no problem, you go to the bathroom. Problem,  the door is jammed shut. Your priority drops to the next layer, what will people think if you have to go to a neighbor asking to use their bathroom? You shake the door handle again, no luck, drop another level as you start the pee dance. Where are your family, why is the door locked. Drop down again, what the heck are you going to do, why are you living in such a crappy house, isn’t there some kind of standard for bathroom doors? Drop down another level, to heck with the rules, you kick in the door and solve your basic problem.

So, think about how this relates to your project teams. Are you making sure their basic needs are met? Do they have to work overtime to meet deadlines? If so, where do you think their minds are as stomachs start to growl, and they enter work hour thirteen? Once the basic needs are taken care of, you need to ask about the work environment. Is it conducive to work; are your team members confined in stuffy rooms? Do they have a place where they can go to think? Is there enough trust to allow people to take a risk?

At belongingness and love – you don’t have to hug everyone – you need to make sure there’s social interaction; chatting around the coffee station, a football pool, these make for a feeling of camaraderie.  Satisfying the need for esteem comes from recognition activities, interesting assignments, and leadership opportunities.

Getting to the top is a bit different, I believe people take themselves to the top, that’s why it’s called self-actualization; you can’t take them. What you can do as the leader is help take care of the rest of the pyramid and create the possibility for people to get there.

So how does this impact your project? When people are in the lower levels of the pyramid, you tend to get crisis management. People are unsure of the safety and security of their basic needs to do the job – maybe it’s as simple as they don’t understand what the project is trying to accomplish – they take actions to create stability and security. In the belongingness and esteem areas, you have team members helping each other to succeed, and making sure there’s spotlight to share.

It’s well worth reviewing some of the fundamentals of people management theory – I think you’ll recognize so of the aspects of current people management trends there.

Tip, check some of these links out.

Maslow

Herzberg – an interesting idea that explains why money doesn’t always motivate people

McGregor – theory X and theory Y management, different styles work in different environments

Hawthorn – sometimes just paying attention helps