Showing posts with label consulting. Show all posts
Showing posts with label consulting. Show all posts

Friday, 11 January 2008

Reaching for the revolver

The business of change is about the practicalities, so don't try to fix the culture.

Apologies for the delay in getting this one out, but I've been offsite with some nice people who've been letting me practice on them. It went pretty well, although there are a few things that we need to tweak, which is great - I would worry if it had all gone perfectly.

I spent two days with this team - a set of people I trust, who do a tough job very well indeed. They have a transformational role in an international technology firm that is helping to lead a revolution for customers.

I was helping them to scope their quarterly objectives and work out the specific issues and jobs that needed to be done to meet them. This work was counter-cultural - their organisation is very action-oriented, so that people are expected to take objectives and run with them delivering as they go, and not take time to think about them properly.

And this, of course, was the problem. The business is now awash with people running round trying to do things that they only partially understand, have only partly under their control and which have a practical planning horizon of only days or weeks. The outcome is that everyone spends more and more time trying to establish control of vague clouds of action, having endless meetings to establish boundaries and accountabilities for things that are unclear, generating huge amounts of office politics and resulting in...not very much, really.

All I did was enable this team to understand the specifics of what they needed to do. Now they are in a position to take control of their remit, and be very clear about they need from others. In practice, what the rest of the business will see is that this team will question others in more rigorous ways, and set a higher standard for the information that they need to get and use. I expect, however, because they now know how to use such higher quality information, there will be a step change in their performance.

Which is what we wanted to do. It was a good chance for me to prove the Bloomstorm model of using new skills to solve real issues, and a fair return, I think, for two days of their time.

There is, however, a wider point. It is easy to think that the solution to such problems is to understand the culture that leads to the behaviour we were trying to change. This is lazy thinking. You change culture by changing the way the business works - not the other way round. Viewed in this light, efforts to change culture are usually a complete waste of money with little or no return.

If, however, you set out to change specific behaviour for practical purposes, then you get the results you want - and as a side-effect, the culture has to change. But that's not why you make the change. You make the change to make the business better - the culture just follows along.

- Mike

Thursday, 6 December 2007

Out Of The Soup

If you concentrate on changing the culture rather than the business, you'll end up in the soup.

A long time ago I was doing a Master's degree and my thesis concerned the implementation of a manufacturing planning and scheduling system in a food factory. The system took customer orders and worked out which machines did what and when and with which ingredients to make for the order. In theory, the order came in to the factory and at the alloted time, the right materials in the right amounts arrived at the right machines and were turned into baked beans.

In theory.

In practice, the stuff was late or the materials were wrong or the machine was busy or the order couldn't be traced and everyone knew that the cardinal sin was to leave a machine sitting idle - so they kept some stock back so that if the worst came to the worst, they could make the standby product: tomato soup.

So their warehouses ended up stocked with (I kid you not) three years' worth of tomato soup.

This was not a viable way to proceed.

The company had spent millions on the system and had millions tied up in unsold tomato soup (you could just imagine the eBay auction now, can't you: 'For sale: 100 million cans tomato soup, no reserve'). Part of my project was to design and deliver the training necessary to equip the business to work in the new ways - without treading on the toes of the folk doing the technical and systems training.

Anyway, I was delivering a workshop on the importance of managing inventory correctly at 4am in the morning (permanent night shifts are a very strange world) when it struck me that many of the problems we faced were because we were confusing two kinds of change. What I christened 'first order change' were things like the installation of the physical system; 'second order change' was the change needed in the organisation and the individuals who had to work with it. Addressiing one without equal emphasis on the other was a recipe for disaster.

This was the heart of the company's problem. It needed the system to do what it was supposed to do: what they were learning (at great expense) was that getting the system right is much easier - and is much less important - than having people to do the right thing. What we ended up doing was using the system as a vehicle for changing behaviour - and changing the system as a result.

This distinction has stood me in good stead ever since. Now, whenever I have to oversee implementation of a system or a physical change in an enbvironment, I immediately seek to understand how people need to work differently as a result - and strive to make the work we put in on the people side is a real and as specific as that on the systems side. At the same time, I am with Herman Goering who made famous the quote from Hanns Johst, "Whenever I hear the word 'culture', I reach for my revolver." In other words, change does not happen simply because we seek to 'change the culture' - the only sustainable way to change the culture of an organisation is through delivery of real things that require people to work differently: workshops don't do it.

In short, don't spend money on systems without spending equivalent time working with your people on helping them to work differently - and don't waste money on training to improve culture unless you are implementing real, physical change in the work environment.

For example, currently I'm working with a team developing a two-day workshop to change attitudes - so we are making it a 90-day programme to deliver real change, with two days' of training at the start.

Simple, really.

- Mike