The Project Manager as an artist

The Project Manager as an artist

A dear colleague, Nick Heap, recently pointed out that as few as 16% of IT projects are successful; that is, delivered to time, budget and specification. And this is in an environment where project management is a core skill, well understood and with many qualified and experienced practitioners. It may be even lower elsewhere in business. So why is this?

Perhaps the problem is that we focus too much on the process of project management. Valuable though it is, introducing rigour, discipline and measurement, it will not deliver a project on it’s own. We may be seduced by the elegance of the project management software we use but the pretty timeline we produce is not reality. It is, at best, a guess at the future.

Nick’s research into the root causes of success found that they are all soft factors. This is hardly surprising. It’s not process that delivers a project, it’s people. Complicated, inconsistent, demanding, emotional people. The art of managing people is more important than technical project management skills.

Like any artist, project managers must develop the technical skills before their creativity can flourish. But it is their art that makes the difference.

 

You need rubbish plans

You need rubbish plans

People get very hung up about plans. They know they need them but they are freaked out by the idea of doing them. Why is this? It’s because they is an intellectual and emotional conflict within them. Plans are mostly rubbish, but they are essential for success. We need them but know they are pointless.

It’s the difference between the process of planning, and the output of planning, which is the actual plan.

Let’s face it, the only certain thing about a plan is that it is wrong. It’s a story we’ve made up about the future that won’t happen. It’s an illusion to make us feel that we are in control of our destiny, when we know we have very little influence on the future and can’t know what’s going to happen. It’s basically a big guess that we know we’re going to get wrong.

The process of creating the plan, however, is incredibly valuable and powerful. Thinking about the future, creating possible realities and testing them against each other and our experience, anticipating possible problems and creating solutions to them – all this makes us better prepared to actually respond to the unknown that is actually the future. Imagining ourselves in these future situations, testing out the options, exploring the possibilities; this is all incredibly motivating and energising and so puts us in a much better state to deal with whatever the future throws up.

So, you need plans. Even though you know they are rubbish.

No More Heroes

No More Heroes

Lots of companies have a hero culture. The people who are talked about are the ones who put in an all-nighter to get a customer’s system back so they can work the next day. They are brilliant, pulling off feats of endurance, persistence and skill that others only dream of.

If you run a break-fix IT service business, they are great. When it’s broken, they fix it. Things keep breaking, your heroes will keep rescuing you and your customers. Everyone’s happy.

Except when you are providing an always-on service. Things breaking is not so good then. In fact, the whole point about providing a service is to stop them breaking by anticipating what can go wrong and taking steps to prevent. You don’t need heroes. You need people who think ahead and put safety systems in place. You need ‘fire-watchers’ not ‘fire-fighters’. Different skills, different mind-set.

That’s why, to use the analogy of a previous blog, aircraft companies start by hiring designers, not crash investigators.

Computer says ‘No’

Computer says ‘No’

We’ve all experienced this. We have a problem, we are talking to a sentient being but apparently an inanimate piece of machinery is deciding we can’t have what we want. “Sorry, can’t help you” they say. “The computer says ‘no’”.

It’s rubbish, of course. They may well be able to help you. They probably would like to help you. it would give them job satisfaction, improve their self esteem and well-being and make them feel better. It would make you feel better too. But they’re not allowed to. They’ve been changed into an organic sound-card for a computer, their brains subservient to some thoughtless process and unbending programme.

Did someone really think it was a good idea to ‘design out’ the talent, skills, emotions and goodwill of that person? Someone really felt that would make a better service?

In case it’s escaped their attention, services are delivered to people. And they are much better delivered BY people. Make your people the centre of your service, not the computers. Your people have got much more to offer.

It’s funny on Little Britain. But that’s a comedy programme, not a instructional video.

Designed to Fail

Designed to Fail

I wish more services were designed to fail.

No, really. The problem is that they are designed to work. When they work, they’re great. We love them. It’s when they fail that we have problems. You don’t notice your broadband when it’s working. But when it fails, you feel like you’ve lost a limb. And then what happens?

Generally, your experience is terrible. No-one has thought very much about what to do when it goes wrong. Anyway, it only fails for 1% of the user base. Only when it’s you, you are 100% affected. No-one has thought about it from where you are.

Aeroplanes are a great product, aren’t they? That’s because they are designed to fail. That’s why Captain Chesley Sullenberger could land his Airbus 320 on the Hudson river and everyone could get out before it sank. (It helped that he was trained for failure, too)

We should be creating services that are designed to fail like that.