Type your search and hit enter
​How to suck at project management

​How to suck at project management

Here's a few pointers if you are still unsure as to where to go wrong

If you want to prove to other organisations that you really suck at project management, there are so many ways to do it.

The Standish Group’s annual Chaos Report outlines the factors that make projects successful. You should ignore this, particularly the bit around the importance of having emotionally mature people.

Similarly, the Project Management Institute’s “Pulse of the Profession” report’s blueprint for success, or ‘champions’ as the institute calls them, would just be a distraction.

There are many other surveys that produce statistics which contain lists of the mistakes that are made over again when it comes to any kind of project delivery. Check which ones are relevant to you right now and ensure that you change nothing.

Here’s a few more pointers if you’re still unsure as to where to go wrong.

Set unrealistic targets

One way to demotivate everyone involved in a project, and this is an important failure mechanism, is to pad the business case with grand statements about cost and time savings. That is, of course, if you had a business case in the first place.

Think you’ll save $50,000? Let’s make it a round $1 million! Think a new IT system will save five minutes per day of someone’s time?

Let’s plan to make 10 people redundant. Whatever the target, make sure it’s one that stretches the bounds of believability and doesn’t line up with any kind of strategy you may have.

Ensure senior managers don’t have time for governance

It’s well documented that sponsoring a project is hard work, has different responsibilities to business as usual tasks and takes up time. Therefore, as well as ensuring that precious time isn’t wasted on them attending unnecessary planning sessions (see below), you also want to ADD more projects to your senior manager’s plate.

You should constantly look for opportunities to do this to create a level of disinterest necessary for project failure. Take care not to upskill them or cancel any other projects, as prioritisation is overrated. Make everything top priority and watch in awe as decisions aren’t made and projects fail. It’ll be poetic.

Skip planning

The best projects bring people together. These people spend time learning to be a team, before working together over a period of weeks and months to build a plan that confirms whether the targets you’ve set in the business case (or email, that’s a better way to do it) are realistic or not.

So you definitely want to skip this entire phase. Don’t go near it or do anything at all to encourage it. Remember, getting things right and doing things in the right way isn’t the goal here. Just take what you thought was possible – based on the consultants that you employed to tell you what you wanted to hear – and press play. Job done.

Invest in processes but not leadership

If you want consistency, repeatability, role modelling and cultural evolution in the way you fail at your projects, then you’ll definitely want to spend all of your development money on implementing a complex method. Preferably by someone who’s never managed a project.

This method should have at least 10 mandatory templates that need to be filled in, a dashboard with lots of traffic lights and an unreadable process diagram to pin up on the wall. If that starts to work, say you’re going ‘agile’ instead.

You’ll have to buy a table tennis table and make the office open plan, but it’ll be worth it to maintain the failure rate. Don’t fall into the trap of training people or asking them to change their mindset. That might improve things as well and you don’t want that!

Make everyone a project manager

Project management is a skill that everyone has. From birth. So regardless of whether you’re fitting out a store, changing a process, writing a new policy (usually on the whim of a government official), implementing an IT system or running an event, make the nearest person to you a project manager.

The only criteria they have to meet is a willingness to accept everything the disinterested sponsor says, to question nothing and to rigorously avoid common sense. Oh and if you have a poorly performing individual that you don’t know what to do with simply make them ‘head of special projects.’ That will help keep the capability where it needs to be.

Being bad at projects is something that any average organisation can achieve and will also ensure that the culture will remain exactly as it is, for eternity.

There are some organisations out there investing in things proven to work and seeing positive results in many areas of their business, but you don’t want to be like that, do you?

Colin Ellis is the author of the upcoming book The Project Rots From The Head and is an award-winning international speaker and trainer. He works with organisations around the world to transform the way they deliver projects. You can find out more about him at www.colindellis.com or catch him at the CIO Summit in Perth and Sydney.

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags Project Management InstituteupskillChaos ReportPulse of the Profession

More about LeaderProject Management InstituteStandish GroupTribe

Show Comments