Why Do PMO’s Fail?

PMO Failure.

We hear about PMO’s failing all the time. Some fail to deliver expected results but somehow tend to linger on in a semi-effective state. Others suck so bad they just get shut down and disbanded. Stats on PMO failure rates are all over the map based on your definition of “failure.” But one thing is for sure, it happens enough where people in the project management profession talk quite a bit about it.

What follows is a list of reasons PMO’s fail from my experience and what I’ve gathered from others. This is not a comprehensive list as I’m sure PMO’s have failed for reasons many of us can’t fathom. If you have one of those stories, please let me know!

Lack of Strategic Alignment. I have a book idea. It’s written by an executive and it’s called “My Company Has A Strategy But No One Knows What It Is And We Don’t Deliver On It.” Catchy! According to PMI, about 41% of organizations with an enterprise-wide project management office (EPMO) report that it is highly aligned to the organization’s strategy. That also means 59% are NOT. Sure, PMO leaders can blame sr. management and say strategy can’t be realized if execs don’t share what it is. Let me tell you; it’s your job to ask, and re-ask, and ask again! Projects need to align with strategy, and PMO’s need to ensure that happens. Not doing so can lead to failure. Someone will be happy to share strategy with you (probably because their bonus depends on it), so keep asking!

Too Much Focus on the Tactical & Not Enough on Strategic. And since we’re talking strategy, if you’re not focusing on it because you’re spending too much time on tactics, you’ll do the wrong thing really well! That’s still a failure. I have seen PMO’s spend the majority of time perfecting processes and artifacts while executing “pet projects” that don’t add value. PMO leaders must focus on business outcomes. Processes are important, but should not require 100% focus. Again, know the strategy!

Lack of Senior Executive Commitment to the PMO. One of my favorites! The “I think a PMO is a good idea but I’ll just let everyone else take care of it” executive. Sure, they’ve probably heard of this PMO thing and wanted to keep up with the Jones’. But, they’re not fully committed to its lasting success or there to help promote change to the greater organization. They also don’t influence other execs to work with the PMO leader on building its capabilities. Strong exec sponsorship is a must!

PMO Metrics Don’t Show Visible Value. Per the recent PMO Squad report from ’22, 78% of PMO’s don’t have a formal process in place to measure PMO value. So if a company is going to invest a lot of dollars and time into a PMO, shouldn’t it show some kind of ROI? Understand what metrics are important to the company and report on those. Have your own, too. PMO’s that don’t show value eventually won’t be around.

PMO Reporting Level is Too Low. Expanding on the reporting of value, there is another reporting issue I’ve seen; too low level in the organization. Even if this is a rockstar PMO getting projects done, if you’re reporting too low in the organization, those with influence won’t see the value you’re creating. Report high enough up the chain so leaders see the value you’re bringing.

PMO and PMO Leader Unable to Pivot. There are two things here:

  • What worked at one company should work at the next, so follow the playbook. That answer is False! Every company, culture, team, structure, and more is different, so be ready to adjust the PMO approach to the company, not the company to your playbook. Stay nimble.
  • The needs of the business and the market can quickly change. PMO’s that can be at the frontlines of change will be a value-add department. Those that hear of change and say no thanks can be replaced. Don’t stay stuck in current state…it may disappear.

Heavy on Following the Rules Precisely Philosophy & Bureaucracy. If the PMO creates processes and then says “follow them or else!”, you’ll have a problem. PMO’s that are heavy on governance and managing to strict practices make for grumpy project managers, who then turn stakeholders grumpy. If a PMO is also too bureaucratic, it can lead to non-value add overhead, delays, and frustration. I like to think in terms of rules and guidelines. For example, the rule is to have a project schedule. The guideline is make it as simple or complex as the team feels necessary. Not every project needs a 100 line schedule. Also, go easy on the documentation. Some industries require it, some don’t. Find the right level without being burdensome.

Lack of Impact on Project Success. This should be a no-brainer, but a PMO was created to positively impact project success. If that quantifiably doesn’t happen, it’s on the wrong track. Figure out what the issue is and fix it! It’s quite possible the PMO is doing good, but lack of perception the PMO is having visible impact on projects can also lead it down the wrong path.

No Marketing Plan. I learned from one of my earliest mentors to have a PMO Marketing Plan. To keep the PMO relevant, it needs to highlight the wins to a broad audience. If you’re not the type of person who can promote the PMO in the organization, get help! Ask someone in marketing or communications to lend a hand. If the PMO is doing great work, have a marketing strategy to communicate that.

PMO Leaders Over Their Heads. Want to make an exec mad? When they ask “How are you going to do ______?” and you just answer with um’s and ah’s. If you’re new to the PMO game, it’s OK (and encouraged) to get help. You’re going to need support when starting this journey. There’s a healthy mix of tactical, strategic, political, psychologist, fire fighter, and negotiation skills needed in this role. If you take the approach of figuring it out as you go along and hope for the best, good luck. Leadership is critical, so make it a priority.

Underperforming Staff. So you have some project managers working for you. Great! But they’re struggling with their projects and pissing stakeholders off. Not great! The PMO has to train the project managers and provide coaching. Hire experienced PM’s. Fight for a training budget. Making stakeholders mad and underperforming projects don’t make for a lasting impact.

No Concept of Capacity/Resource Management. When a leader asks “What are your people/those people working on? Why can’t we do this [what THIS is] too?”, you need to be ready to answer. Understanding capacity and your finger on resource management helps with those more strategic priority discussions.

No “Customer Service” Mindset. Who are your “customers?” Understand your customer’s (internal and external) expectations and then meeting or exceeding those expectations. Actively listen to your customer’s problems or opportunities. If you don’t have a customer service mindset, your customers will get upset with you!

PMO’s fail for a number of reasons. Again, the list I’ve created isn’t comprehensive but I hope I’ve covered the big ones. If you have a story, please share it!

Success! You're on the list.

What’s Your Risk Tolerance?

I grew up in a bit of a risk-adverse home. One parent was an engineer who had been with the same company since graduating school.  The other was an administrative assistant who worked for the same school for many years.  Both believed you find a job, stay with that job, try not to rock the boat, and retire. I thought this was the way it was done. That is, until I graduated college and started out on my own.

When I graduated from college, my intention was to go into HR. I interned and then went to work for a staffing agency. After six months, I knew the staffing agency life wasn’t for me. So, I took a contract job at a tech company we staffed for. Four months later, that contracted ended and went to another company. My dad pulled me aside one day and said after three jobs, I had to stay put. No one would ever want me if taking more than that. Don’t take the risk!

Then, I wanted to bike in a race with a friend. We signed up. I pulled my old Cannondale out of storage, dusted it off and hit the road. A family member caught wind of my race and said don’t do it! I could crash or even get hit by a car. Play it safe! Don’t take the risk.

Since those conversations, I’ve taken several risks in my career and in my personal life. My resume has a wealth of experiences from consulting across a variety of industries. My personal resume has a number of ultra-endurance races. I’ve written articles that were broadly published and scrutinized. I’ve given presentations to different groups, and admittedly bombed a couple. Each one of these required me taking a risk. Whether putting my livelihood, physical well-being, or reputation at risk, each was calculated and never done on a whim.

Everyone has a different tolerance for risk, and I’m not here to change that. As with everything, personal risk tolerances can change with experience. What I hope is my approach will get you to see risk a little different.

There are four criteria I have when it comes to taking risks in my life. These criteria are for those “bigger” pursuits (i.e. new job, asking for a promotion, publishing a book, big race, etc). Everyone’s definition of risk can be different, so you’ll need to understand what a “bigger” risk is for you.

Throttling up to V1 – Taking Small Steps to Taking Off for Big Things. Ever watch a YouTube video of airline pilots taking off? Or, have you been behind the flight controls yourself? There is a critical point during the take off process called V1. V1 is the max speed you can safely reject the takeoff. It is also the minimum speed you can take off following an engine failure. But once you go past V1, the only option you have is to “rotate”, and take off.

Here’s the thing about V1; there are a lot of small steps that must be taken before you hit that speed. Plane prepped. Checklists followed. Run-ups on the engines done. Lots of throttle to get you moving down the runway before V1 speed is achieved. You don’t just get in and go. There are opportunities to abort early on. If you’re going to ask if I’m a pilot, the answer is no. I have flown in a few single-engine aircraft and helped with the checklists and have taken off a few times.

When taking a risk in your career or personal life, think of it like taking off in a plane. Start by doing little things. Want a new job? Update your resume. Share it with a friend. Talk to the friend. Talk to the friend’s boss. Interview. Get an offer. Accept. Quit old; start new. Even early on during those initial, smaller steps, you could abort. But as things continue, momentum builds until you hit V1. Evaluate your risks by starting small and throttling up as success is seen.

If I Need a Plan B, My Plan A Probably Sucked. In 2009, I signed an employment agreement with a consulting company. I had never officially consulted before (I was brought in to help other depts. from time to time). After giving my two week notice, a co-worker heard I was leaving. We talked and he told me I probably wouldn’t make it in the consulting world and wanted to know what my Plan B was.

At first, I thought the guy was an asshole. I may have even called him that. But in hindsight years later (yeah, it’s stuck with me), his comment made sense. When you’re looking at a risk and making a plan, is that plan thorough enough given the information you have, and can you pivot when the inevitable punch in the face happens? If I need to make a Plan B before I even start Plan A, Plan A wasn’t solid enough. Take the time to understand the risk, make a plan to conquer understanding you don’t have all the information now, and get ready to pivot when necessary.

Is This a TED Talk-Worthy Story, Even if the Outcome Isn’t What I Want? I like TED Talks. They’re short, informative, and concrete. They can be inspirational, emotional, and thought provoking. I listen to TED podcasts and watch them frequently.

If I’m taking a risk, I ask myself; could I give a TED Talk on this? Is this story worth standing in front of others and telling it, even if it doesn’t go the way I imagined? If yes, it’s probably worth pursuing. If no, is it really important to me?

Every risk we take has a story and a purpose behind it. Ask yourself; is this risk worth explaining why I took it in the first place? If it’s worthy of presenting it in a TED Talk format, you can also talk about it with family, friends, and peers. Chances are you won’t give a TED Talk about the risk you undertook, but starting there makes the conversation with a smaller group easier.

Could I Die Despite All My Preparation? This is a legit question I ask myself! Could I die doing this? Or, could I have lasting, life-altering injuries?

Let me explain. I love ultra running and ultra cycling. These events span multiple hours, even up to a full day (I haven’t done a 24+ hour event…yet). But during these events, there are risks involved ranging from cliffs to cars, wildlife to weather, and lots of risks in between. Yes, I’ve nearly mountain biked off a cliff at dusk and have run in the open during a lightning storm. Your day can end badly!

Try as hard as we do to train and prepare for events such as these, you can’t mitigate all risks. Is the risk worth the reward? Do I want to risk a rattlesnake bite in the Badlands of South Dakota or come across a bear on the north shore of Lake Superior? So far, yes I have. Before I hit the “Submit Payment” button to commit, though, I do ask myself if I could die.

Everyone’s risk tolerance will be different. It may start low and go higher over time. Others start high and stay high, or start low and stay low. It’s up to you to define what level of risk you’re comfortable with. I suggest having criteria to help. If you don’t have any, take mine! Or, create your own. But in the end, good luck with all risks you take on.

Success! You're on the list.

Don’t Punish Your Teammates for Being Honest

“Please tell me what you’re thinking. I promise I won’t be upset!”

She looked nervous. She was smart, forward thinking, and I could tell from her body language she didn’t agree with me. But, given the last project manager wasn’t open to feedback and often got upset when he received it, she didn’t want to repeat scoldings that were given in the past.

I have this baseball analogy I frequently tell people. A baseball player hitting .300 could make the hall of fame. That means for every 10 at bats, they get a hit 3 of them. Thinking in those terms, a professional baseball player getting it right 30% is awesome. Therefore, if I’m right 50% of the time, I’m having a really good day!!

For the other 50%, I need help. Therefore, I need those smarter people to essentially take me by the shoulders, point me in the right direction, and say “Go that way.”

In this scenario, we were looking at an overall delivery process. I thought it was pretty solid and told the team that. However, this project manager found an inefficiency with the deployment method. She knew there would be issues and wanted to mitigate them before projects got to that point. I didn’t see it, but as she dove deeper, the issue started coming to light. Yep, this was a problem I didn’t see. I was happy for the feedback.

If you’re in a leadership position, you will likely be giving your team members feedback. But what about feedback to you? Your best employees tell you what you need to hear, not necessarily what you want to hear. Honest feedback can be a gift, so when you get it, don’t get upset with the messenger. Here are some tips for accepting feedback from others.

Put your ego aside and actually listen. This one’s not easy and a lesson I was fortunate enough to learn early. Our self-esteem and self-importance is tied to ego, and to have it threatened with feedback is tough. When you do receive feedback, try to put your ego aside and listen intently. Ask for clarification and thank the person giving you feedback. They showed courage bringing it up.

Loyal criticism is a blessing. Your best team members, those who want to see you succeed, will point out blind spots. Chances are, you didn’t even know these existed, but were there. Take this feedback as a blessing! You wouldn’t have seen them otherwise.

The best teams are built on honesty and trust. Honesty and trust are two words not used enough in business. Teams who practice psychological safety where they are honest with each other and value feedback, develop trust that delivers results for the organization. As a leader, it’s your responsibility to create an environment where feedback is encouraged.

Feedback are gems, not stepping stones. We all want to advance our careers. We go along thinking we’re doing a great job and then BAM!, passed over for a promotion. When we ask, blind spots are identified that we didn’t even know existed. However, if we were open to feedback, they may be identified. These little gems of information could help us move up in the organization.

If you’re not ready to take feedback from employees, you’re not ready to lead them. If you’re a supposed leader, then you give feedback to employees frequently. Why shouldn’t it be a two-way street? You should get feedback from more than just your boss. If you’re ready to lead people, you need to be ready to receive feedback from them, also.

Feedback is critical to our growth. As leaders, we provide feedback to those who report to us. But as leaders, we must also accept feedback from those we lead. It helps us identify what we may not see and grow. Remember, when receiving feedback, consider it a gift, and don’t punish your team for being honest.

Success! You're on the list.

The Importance of Having a Project Manger, per ChatGPT

I finally gave ChatGPT a try. My kids and I have been messing around, having it write songs, create jokes, and rewrite a paper my one kiddo already did. It’s been interesting and funny. I wondered what else it could write.

I recently read about a company having financial issues because one of their key projects was behind schedule and over budget. Reading on, one of the steps they’re taking to get it back on track is to hire a project manager. No, they didn’t have one until this point! Interesting.

That got me thinking; what would ChatGPT say about this. So I asked, “What’s the importance of having a project manager lead your organization’s project?” Below is its response.

Having a project manager lead an organization’s project is important for several reasons:

  1. Project planning and organization: A project manager is responsible for creating a project plan that outlines the tasks, resources, and timeline for the project. They ensure that the project stays on track and is completed within the specified time and budget.
  2. Communication and collaboration: Project managers are responsible for communicating project status and ensuring that team members are working together effectively. They help resolve conflicts and facilitate communication between team members, stakeholders, and other departments.
  3. Risk management: Project managers are trained to identify potential risks and develop strategies to mitigate them. They ensure that the project is completed on time, within budget, and with the desired level of quality.
  4. Resource allocation: Project managers are responsible for allocating resources such as time, money, and personnel to the project. They ensure that the right people and resources are available when needed, and that the project is completed efficiently.
  5. Project tracking and reporting: Project managers use various tools and techniques to track project progress, including schedules, budgets, and performance metrics. They report on project status to stakeholders and make recommendations for course correction when necessary.

In conclusion, having a project manager lead an organization’s project is essential for ensuring its success. They bring a wealth of experience, knowledge, and skills to the table that are essential for delivering projects on time, within budget, and with the desired level of quality.

Thank you, ChatGPT! Anything else you’d add?

Success! You're on the list.