Showing posts with label structure. Show all posts
Showing posts with label structure. Show all posts

Friday, February 04, 2011

A Wise King

‘A king with no advisors is king of ignorance.
A king with one advisor is king of bias.
A king who believes all-comers is king of confusion.


Years ago I worked for a very experienced Manager. He had a reputation for being strong willed and not suffering fools, and if you let him down or exposed him to trouble, you knew about it. He had many years of experience in the industry and you could pretty much say that he’d seen it all.

With all the experience and knowledge he still had an interesting habit. Every Wednesday, at the end of the day, he would sit down with the HR Manager and say ‘What do I need to know?’ and he would sit and listen. He listened to things that were not his favourite topic. He was not a fluffy kind of guy, he didn’t do the people stuff easily. But he listened and found out what was going on and sought the HR Manager’s counsel.

Over the many years since I have helped organisations re-structure and have seen many of the trends in that field. Outsourcing and insourcing come and go, the arrival of the COO and what that means for structure.
I’ve seen the trend to pull all your ‘service functions under one division with one manager looking after HR, Legal, Finance, Public Affairs etc to and its that one that I’ve been thinking about recently after a number of chats with CEO’s and MD’s. Many of these organisations are finding that the ‘Senior Team’ or ‘Executive’ is largely made up of the Business Unit or Operation Leaders, with the one head of ‘Shared Services’ and the CEO/MD themselves.
Any organisation is only going to be as good as the conversation that happens around that table. And whilst alignment is good, over-alignment caused by lack of balance is a risk for business.

I’ve always thought that one of the key roles of HR, Legal, Public affairs, Finance etc was to provide council and be the voice of conscience for their area of expertise. Not just a shared service function delivering functional transactional activity. So keeping these voices away from the executive table means the CEO might not be hearing everything that he or she needs to hear. Expecting the head of the shared function to do this is a risk too as there is no way that they can be an expert in all areas (and didn't you set up their role to create synergies and cost effectiveness, not to become an quasi expert in everything?)

I’m not suggesting that you restructure to create an executive of 12 so that you have all the subject matter experts at the table all the time. But a wise CEO finds ways of getting the guidance that is needed in balance and gives his/her councillors time to give counsel.

Just like my old boss, you might not like what you hear but what he knew was that not hearing it would mean that a problem would arise that you would like to hear even less.

Thursday, September 30, 2010

The Quake Test

In the last month New Zealand has seen some of its biggest earthquake damage in over 80 years. The impact in Christchurch has been significant and many buildings have come down, homes have been ruined, businesses destroyed and many lives changed forever.
Earthquakes are not unusual around the world so it was not a surprise that Murray McCulley, our minister for foreign affairs, spoke to the UN Assembly and mentioned the fact that, compared to many other countries, our structures and infrastructure did not fail as catastrophically as has been seen in other countries.

You might wonder why a change agent would write about earthquakes!

What occurred to me most, in watching the scenes from Christchurch, was how many of the tales told were about the response of the people and the way that they responded to the disaster, managed the disaster, and supported each other after the disaster.
What I saw was another reminder that when the structures fail, the ability to operate is down to the people. What I also saw was that the structures that did not fail had been designed for the conditions that they operated in. They weren’t designed for downtown London or the Chinese countryside. They were designed to work in New Zealand for the conditions that prevail here. They were designed to work for the people that needed to use them. The structure was for the people and not for itself.

It reminded me that in organisations we spend a lot of time on the way we are structured and we spend a lot of time restructuring, but that the structure itself delivers nothing. People do.

Now I am not saying that you shouldn’t care about the structure of the organisation. What I am saying is that your structure is there to pull people together in to groups or teams of common purpose to enable them to easily and effectively work together. It helps define boundaries where boundaries are needed. It should help define relationships so that people understand the connection between roles.
Organisational structure is not real. It is a self imposed concept and like all concepts it is designed to help give meaning and understanding to the people who need to use it.

Therefore the structure is not there for itself it is there for the people. The structure cannot be right or wrong or have a voice (as in the organisation says). It does not create or deliver. It cannot innovate or design or invent.

Structure shouldn’t be defined to ‘give a manager a job’ or to ‘create hierarchies of power’. It shouldn’t be redefined just to remove numbers from the business, nor should it be an alternative performance management tool. I have unfortunately seen it used for all of these and inevitably it doesn’t reap many benefits

Structure should be there to align, group, connect and make efficient work paths. And the unstated word there is people. Structure is there to support people.

The best test of a structure, and its suitability, is whether it supports the people within the conditions that the organisation finds itself.

Perhaps we can call this the ‘Earthquake test’.