Monday, 16 April 2007

The Cult Of Execution

Over the last two years, for the first time, I've been trying out managing teams of varying sizes. Previously I've been a technical specialist, and while there's plenty of room for me to progress there, I'd got to the point where I figured some experience in coordinating the execution of work would be useful in terms of amplifying my effectiveness (in the sense of this bunch here: http://www.ayeconference.com/).

One of the interesting aspects of the managerial world (as someone coming relatively late to the manager party) is what I've started to call the "Cult Of Execution". To see what I mean, start reading periodicals such as the Harvard Business Review (http://www.hbsp.harvard.edu), and see how many times execution is mentioned as an end in itself.

Now, this is hardly surprising in one way. Executives are responsible for execution. That's their job! But as someone who views line management as another useful skill to do my best to acquire, rather than my main thing, I've started getting a bit of a sceptical air about this one.

No question that a manager needs to successfully execute projects if he or she is to get ahead. But what if, when you look a bit closer, you realise that either that the project has been executed in a manner which will lead to a lot of very expensive trouble later on, or that the project as delivered actually has no business value at all?

What is execution actually worth?

Execution in itself is not actually worth anything. Execution must create value or you're actually costing the organization money by taking resource away from other, potentially more useful activities.

So please don't tell me someone's a good manager because he's been successful at execution. Show me what he's executed, and how it's doing a year down the line.