Some Things Just Take Time.....

There is always the great debate about throwing resources at a project to try to pull off the impossible timeframe.  However, some things just take time.  When I train project managers, I use an analogy of what effort driven in Microsoft Project means.  I ask them, “Are you painting a fence or driving to Nashville?”  If you are painting a fence and it takes 8 hours to paint the fence, then it will also take the full 8 hours of time.  If you add a resource, it will still take 8 hours of effort, but will only take 4 hours of elapsed time since two people are splitting the work.  If it takes you 4 hours to drive to Nashville and you add a second person, it doesn’t mean you cut the time in half.  Now two people are spending 4 hours in the car so it doubles the amount of effort.  This is a cleaner version of the way that I used to explain this.  I used to say that you can’t always throw resources at a problem.  The example I would state is that you can’t put 9 women into a room and produce a baby in a month, some things just take time.  I used that for a couple of years and every once and a while, someone would be offended.  So I changed it to a cleaner version for most of my trainings.  However, a good friend John Ragsdale sent me this and it made me laugh.  I don’t know where this originated to give it proper credit, but to whoever pulled this together….it reminded me of when I got started.  Enjoy!

Definitions of Designations:

Project Manager is a person who thinks nine women can deliver a baby in one month.

Developer is a person who thinks it will take 18 months to deliver a baby.

Onsite Coordinator is one who thinks a single woman can deliver nine babies in one month.

Client is the one who doesn’t know why he wants a baby.

Marketing Manager is a person who thinks he can deliver a baby even if no woman or man is available.

Resource Optimization Team thinks they don’t need a man or woman; they’ll produce a child with zero resources.

Documentation Team thinks they don’t care whether the child is delivered; they’ll just document it in 9 months.

Quality Auditor is the person who is never happy with the PROCESS to produce a baby.

Tester is a person who always tells his wife that this is not the right baby.

HR Manager is a person who thinks that a donkey can deliver a human baby in 9 months.

I don't acknowledge it....therefore it doesn't exist!

Is this a reality?  I overheard a conversation last night at dinner where a guy was explaining to his friends that he has not gotten a cold in the last 15 years.  He stated that his grandmother told him that there is no such thing as a common cold.  He believed her and ever since he has never gotten a cold.  One of his friends asked, “Do you ever not feel good?”  He said, “Sometimes my nose will be stuffy or I get a sore throat or cough.  I will feel run down and will stay in bed a couple of days……but it’s not a cold!  They don’t exist!”  Call me old fashioned, but that sounds like a cold to me.
It reminded me of my top 5 favorite quotes from a sponsor.  We were running a project and the sponsor had announced to the entire customer base the completion date of the project before the project was even opened in the organization.  Her statement committed us to a 10 month project to be delivered in 4 months.  I approached the sponsor and told her that we would have to do some serious risk management on the project.  Her response is still a classic: “Rick, this project has no risk because it must be done on time!”  If we don’t acknowledge it, it must not exist.
This same denial seems to be true for sponsors when they set a project date or budget.  They often will tell a project manager, “just figure it out,” or, “just make it happen.”  As if the project manager can just wave their magic wand and a new month will be created or a bag of cash will appear.  Projects have been run this way since the beginning of time.  Why is it so misunderstood?  I like to compare projects to weight loss.  Look, I would love to take a pill at night, never have to work out, eat whatever I want, and lose weight.  The reality is that eating right and exercise is what it takes.  The sales numbers for weight loss fads, products, pills, exercise machines, etc. is staggering!  Every day I hear an ad for a new product that promised dramatic weight loss without changing and of the bad habits that lead to the weight gain in the first place.  It is this same mentality that continues to plague projects.  This mentality that if we put it out there it will happen and if we don’t acknowledge the bad stuff, it doesn’t exist is the basis of many of the organizations in business today.  Then everybody is surprised when something doesn’t go as planned.  This goes all the way back to the way the project was selected and how most likely the budget was trimmed via a spreadsheet to get it to meet an arbitrary number that feels right to the executives.  Sure we can cut 20% of this project, there was probably padding in it anyway!
Risk does exist.  Project failure is a very real and repeatable process.  Yet we continue to not acknowledge it.  For example, a project manager will be told that they do not have time to plan, the project must start now.  The project fails.  The project team does a lessons learned session and blames the lack of planning as the reason why.  Then the team will agree that more planning will be necessary.  Then the next project comes along and the same project manager is told that there is no time to plan, it must start right away!  One of the greatest things we can do as project managers is simply acknowledging that these things do exist.  Documentation and metrics capture that show these patterns is paramount.  We must acknowledge these failures.  It is the first step in resolution.
Go forth and document!
Rick

Where Has Customer Service Gone?

As many of you know, I travel quite a bit.  I am extremely loyal to my brands often going out of my way or not taking the convenient path to maintain that loyalty.  For example, I drove 55 miles each way for a speaking engagement to stay in the nearest Marriott.  However, more and more, I am seeing customer service get worse and worse.  In this economy, it is even more important to retain your customer base than ever.  I try not to complain, but two situations that just occurred have led me to this post.  Unfortunately, I will not change the names to protect any innocents.

The first experience was with the Vanderbilt Marriott in Nashville, TN.  They have one of the most amazing and wonderful staffs ever.  From the valet to the desk manager to the Concierge team, they are a class act.  I have had several customers in Nashville and have stayed over 100 nights in that hotel.  At one point, I didn't have to stay in Nashville for 6 months, yet everyone still knew me by name when I came in.  Most hotels have corporate rates and when I travel, I use the client's rates to lower expenses.  In every hotel I have ever stayed, if the corporate code is unavailable, I have been told to book a room anyway and get the code changed at the front desk.  This was the case for this particular reservation.  I booked the room and headed to Nashville.  When I arrived, I was greeted by the familiar valet guy by name.  The front desk manager welcomed me as she has for years.  We asked about each other's families and made the usual small talk.  I told her the rate situation.  She told me she can no longer change it and I can see she was upset at the inability to do so.  I asked her why.  She said that a new owner had taken over and that policy is not in effect anymore.  She stated that the owner representative was there and I could discuss it with him.  When I talked to him, I was appalled at the answer.  He said that the reason is due to a revenue model to ensure they stayed as viable as possible.  I explained to him that I had earned my platinum status at that hotel.  Not just that I am platinum, I earned enough nights at his hotel to become platinum.  The rate difference was $80.  I asked if an extra $80 was worth losing a customer that had spent easily $20,000 at that hotel.  He said that it was policy and his hands were tied.  So I cancelled my reservation and found another Marriott in Nashville.

The second item happened on my latest trip.  I rent with National Rent-A-Car and have been an Executive member for several years.  I realized when I arrived in Houston at IAH that I had left my driver's license at home.  It is Sunday night late and I am stuck at the airport.  I go to the rental counter and talk to the manager.  I explain what I had done, but that I rent a car from her counter every other week for quite some time.  I could have my wife fax her a copy of my driver's license to prove that she was in possession of it and that it was valid.  She was going to overnight the license to where I was staying.  I had my passport with me to prove my identity.  I had just rented a car there the prior week so it wasn't as if I was an unknown entity.  I can appreciate the policy and I can appreciate the adherence to it as well.  The attitude that I received from the manager was flippant and she just said, "I can't do anything," and walked away.  As she walked away I asked was there anything that could be done, any options, or anyway to get a cab from the location.  She continued to walk away mumbling and let the office door close behind her.  Fantastic customer service, I must say!  Again, I understand my mistake.  I can understand the policy.  The attitude was what was so infuriating.  She didn't even look up my name or what type of customer I was.  She didn't even try to assist when I was in need.

What happened to customer service?  There used to be trust in the consumer.  If I had never rented a car at that location or stayed at that particular hotel before, I can understand.  Even if I had only done so once or twice, I could understand.  To attain the highest level statuses of their loyalty programs and have their locations be where I attained those statuses, unforgivable.  Sometimes you have to look at the money lost or loyalty lost versus the immediate gain.  Policies are there to protect and serve, but not to the detriment of customer service.  Everything these days is recorded, outsourced, and has a total lack of empathy.  Bring back the human.  Bring back the humanity.  Please, loyalty should be more than a free gift.  Loyalty should mean the company should strive just as hard as the consumer.  It is just as easy for me to book somewhere else.

Stay loyal!

Rick

"I want a PMO!" - Validate What They Mean

Clients will often state that they want me to come in and help them create a PMO. Unfortunately, that is all that they say. It is like me saying, “I want to be a better project manager.” It is a pretty vague statement. When the decision is made to create a PMO, there is some general reason why that is happening. It is important that you uncover those meanings.

 

For instance, a client had recently stated that a PMO was being created in a division and that all of the certain projects of a certain type would be brought into the PMO. At the time, there were 150 of these projects identified in the group. The group also had 6 project managers who already had a portfolio of 30 projects. There were several questions that this posed:

• What do we mean by “brought into”? Does that mean we own the projects completely or we own the status reporting?
• Will we get more staff to run these projects?
• Why do we feel the need to create the PMO?
• What is the end result of creating the PMO that you envision?
• Will the PMO be part of the strategic planning of the division or just told to execute the projects?

Unfortunately, not many answers were provided. I compare the explosion of PMO’s to the Six Sigma craze. There was a popular article that stated a Six Sigma Master Black Belt could bring a company an average savings of $2M. Based on the article, many companies went on the hunt to find their Master Black Belt. They approached it as if the person would show up with a $2M check!

 

I fear that the explosion of PMO’s is due to the same reason. An executive will read an article or see a result published from a company that shows that a PMO increased revenues, decreased cost, and improved efficiencies. Therefore, they conclude that they must have one. In my experience, few executives are willing to make the changes that achieve the results in the article. Change must occur in order for results to be realized.

 

Faced with the situation above, my suggested course of action follows what is taught in my seminars and books. The path was:

• Identify what it takes to manage a project in the environment and come up with a percentage of time on average it consumes of a project manager.
• Apply the percentages to the projects to determine the number of project managers needed.
• Identify alternate actions should head count not be increased (including not accepting the 150 additional projects)
• Ensure that the data you are presenting is accurate.

Once all the steps have been completed, meet with the sponsor. Ask for the 30 additional project managers that would be necessary to accept the additional project load. If the answer is no, show the alternatives of what is possible with the current staff (including some of the ideas that I have blogged earlier titled “Do We Have to Own Projects Start to Finish” in May of 2011.) From there, this will take a life of its own. The important part is to ensure that you have validated what they mean when an executive states, “I want a PMO!”

 

Until next time,

 

Rick

 

The Plague of Ulterior Motives

I continue to be amazed at how much time, effort, and money is wasted internally by companies.  One of the number one causes of this waste is ulterior motives.  These are people who will deliberately say and do things in public, but in private have another motive to their actions.  This is a rampant disease that can cost organizations millions of dollars.  Instead of having uncomfortable conversations or debating issues, the person or group would rather act is if they are playing along and hope that the initiative fails.  There are several of these types to watch for:

The Two Faced Approach.  This approach is been around for a long time.  As soon as any social structure is developed, this approach is evident.  My kids experience this in school and unfortunately, some never seem to grow out of the behavior.  The approach is to act one way in front of one group and then act a completely different way in front of the sponsors and executives.  For example, an individual can be openly combative and antagonistic towards you in a closed meeting.  Then in the team meeting, be open and friendly and act as if they have been working with you all along.  One of the greatest examples of this behavior is Eddie Haskell from Leave it to Beaver.  Eddie was conniving, manipulative, and mean to everyone.  However, when the parents were around, he had his best manners on display and gave the illusion to the parents that he was perfectly behaved. 

Transference of the Issue.  This approach will make sure to not answer a direct question or issue.  If you ask a direct question, they will talk around the subject without answering directly, transfer the answer back to you, or deflect the answer to a person or group that is not available at the time.  They make an art of not answering the question.  They will respond to questions with, "It will take whatever you think," or "What do you want it to do?"  These are purposefully vague answers to questions that can allow them to say they are being responsive without actually answering the question.

Secret Saboteur.  This group will secretly try to make the initiative fail.  Either they disagree with the initiative or they are scared of the change that it might bring.  Instead of working with the initiative, they purposefully delay, don't deliver, cause rework, or otherwise sabotage the work.  This is a particularly dangerous group. 

The Other Option.  I have seen this option several times.  This is where the group or individual wants the theme of the solution to be successful, but not necessarily the current selected solution to work.  For instance, a company wanted to do workforce management.   They looked at a portfolio and project management system and an enterprise resource platform.  The business and users wanted the project management system.  A key executive had former ties to the enterprise system and wanted that one.  Instead of debating the decision, the executive allowed the project management system to be purchased.  During the implementation, the executive put unrealistic demands on the team, changed the scope, and changed success criteria.  The first implementation group did not succeed.  A decision was necessary to continue with the current tool or get the one that the executive wanted.  Surprisingly, the business wanted to continue with the current system.  The executive again sabotaged the implementation to the point that the second implementation team failed.  Finally, the executive got the system that she had wanted.  However, it ended up costing the organization millions of dollars.

This can also manifest itself by stating that a group wants something when it isn't the true thing that they want.  For example, an organization that fights for a change of a tool.  The existing tool does what they want, but they convince the organization to change.  The reality is that they want control of the tool.  It isn't that one tool is better than the other.  It is that they can control the tool better if they own it.  I see this quite often with centralized IT departments.  You will get a department that wants to go rogue and get another tool.  In the end, what they wanted was to not have to utilize the centralized IT group.

We will explore how to deal with these types in later blog postings.  The first step in dealing with ulterior motives is to try to understand which one of these categories the group or individual belongs to.  From there, we can start to create a game plan on how to deal with them.

Am I missing any?  Would love to hear from you on this topic!

Rick

More Metrics!

Building on my last post, we are continuing to build some new metrics.  The last post talked about resource management metrics.  Here are some other ones that we are tracking now.

Execution Metrics
# of tasks
# of tasks on time
# of tasks past due
# of tasks severely overdue
# of team members
# of opportunities to turn in status report
# of status reports turned in

Planning Metrics

Date Project Assigned
Requested Project End Date
Project End Date Original Planned
Mandated?
Date Agreed upon with Sponsor
Date Project Actually Completed

There will be much more to come as we are developing a new concept that we are titling now as "Metrics 2.0:  New Metrics for a New Project Management Era"

Do you have some unique metrics that you track?  Please share!




SRH25JZFSYVH

New Metrics: Resource Management

I have several requests from people asking about some of the metrics that I track on my projects. I am working on a new book of metrics and new ways of thinking about metrics. Here is a sneak peek of some of the types of metrics that I track:

Resource Management Metrics
# of times invited to a meeting
# of times showed up to the meeting
Participation type (called in, showed up in person, etc.)
# of issues assigned
# of risks assigned
# of issues resolved
# of risks resolved
# of issues introduced
# of risks introduced
# of tasks assigned
# of tasks completed on time
# of tasks completed past due
# of e-mails sent (by pm)
# of e-mails responded to

This takes the metrics just a bit beyond what we normally track. It is not all % complete or estimates. It is also about quality. For example, I had a very large project that had impact on multiple departments. One of the departments was finance. Right at go live, the finance department went to the project sponsor and said that the project should be stopped. The project manager (which was me) did not consult them or did not get their input on the project. Therefore, since finance was not consulted, the project should be stopped.

When I was called in to the Sponsor’s office, I stated that I had not gotten their input. What finance had stated was completely correct. However, they were not an identified stakeholder on the project and based on their project focus rating, they did not appear to want to be involved. Finance asked, “What do you mean by a project focus rating?” I explained that I track how many times I had invited them to meetings, asked for input, number of issues assigned, number of e-mails that were sent and went unresolved, and overall participation on the project. Based on the information that I had, they were invited to 47 meetings and never showed, 31 e-mails went unanswered, 3 issues were assigned that never were completed, and 2 direct requests for assistance were not answered. Since all I can do is facilitate, I took the 83 separate times to have them provide input as a sign that they did not want to participate. In the end, finance didn’t have a leg to stand on. If they wanted to have direct input, they could have. What happened is that they felt the project would not impact them and they blew off the project. When they finally saw that there was impact, the project was too far down the road.

This is a common occurrence in projects. This is why we have to look at metrics that go beyond. The point is that we have to manage more of the quality or focus of individuals on a project. In environments when there are tons of competing projects and priorities, it is a necessity to measure the amount of focus a resource gives to the project.

Hope this helps!

Rick