Thursday, 16 September 2010

A leader's dilemma: Get a grip? Or let go?

This week I’ve had some great conversations with former civil service colleagues about how to do change. I also attended the launch of a report on a vision for public services in 2020, and a seminar by Brian Dive, author of ‘The Healthy Organisation’.


I’ve found myself chewing on the leadership dilemma of ‘controlling’ or letting go. This isn’t a new dilemma for me. It haunted me for most of my time as the director of a caseworking operation.


My default preference is towards letting go. The more I look at things systemically, the more attracted I am to devolving authority and power, to trust the frontline.


The theory goes like this. From the centre you get the birds’ eye view, from the balcony, and you’re able to make strategic decisions, for example changing organisational priorities, or responding to external changes in context. But you don’t get the detail and local variation, and in not getting the detail, you inevitably mess up implementation. So it’s best to let the detail be handled closer to the frontline and allow sufficient flexibility for first line managers to do that.


That’s for performing the job you know about and are trying to manage well. Throw in a dose of chaos theory, and add to your organisation’s context the idea that you can’t predict everything that’s going to happen to your clients and your staff. Then you need even more local adaptability and autonomy to deal with sudden shocks. (This is the Ralph Stacey way. I haven’t read Managing the Unknowable, but have had it recommended)


There are lots of examples where ‘the centre’ failed to do this well and local implementation hasn’t been sufficiently nuanced for local circumstances. The target setting that happened under the Prime Minister’s Delivery Unit in the early 2000’s had some beneficial effects but some detrimental ones, particularly around dealing with variation. (Review of ‘deliverology’. I also like this article from the Systems Thinking Review about benchmarking, showing how that doesn’t deal with variation either.)


In addition, there’s good psychological research that upholds the idea that the more autonomy you have in your job the happier you are in it - and therefore the more ‘discretionary effort’ you put in to the job.


Certainly this approach should be more beneficial for partnership working and collaboration. When I allocated cases to casework team leaders on a locality basis, and then gave the autonomy to team leaders to contact the relevant local authority directly, rather than trying to manage relationships with about 20 key local authorities myself, suddenly our stakeholder management improved vastly. We were able to plan our caseworking more effectively to deal with local authorities’ anxieties in a more bespoke way that we could never have managed if we were planning centrally.


So my prejudice towards letting go was comfortably confirmed by the 2020 Public Services Trust at the Royal Society of Arts. I went to the launch of their new report on Tuesday. In particular they argued for a shift in culture towards coproduction, and a shift in power towards devolution.


The shift in culture they asked for was for public servants to value themselves only to the extent to which they engage and enrol citizens, families, communities and enterprises in creating better outcomes. That all sounds a bit jargony. But I understood it to mean, blurring the line between the ‘state’ and the ‘community’ so that, (to quote a song with an entirely different intention!) ‘sisters are doing it for themselves’. If you think about it, a child isn’t just taught by a teacher. A child has to be up for learning for that to work. And it really helps if the parents are involved too. This is co-production. But, as Stephen Dorrell MP said at the launch, none of this can be delivered unless there’s a change in culture, public servants need to see their role differently. And this is the hardest and most important thing.


The shift in power was basically anti Whitehall.

Our Whitehall model cannot deliver the integrated and personalised public services that citizens need. We need to invert the power structure, so that services start with citizens.”


Departmental silos should be replaced with citizen-centric and place-centric organisation structures, and with much more autonomy for local authorities and other local bodies.


Hooray, then, for ‘letting go’, trust, complexity and localism.


But, but, but. One of the members of the audience (who were in general very select and impressive - there were more than a couple of Chief Executives and key British opinion shapers in the room) at the RSA on Tuesday night asked, ‘Is localism more expensive because you can’t get economies of scale?’ Systems thinkers often snort at the idea of economies of scale and say this is a myth, given the waste that gets created by dealing ineffectively with variation and detail. (A long piece on it by systems thinker John Seddon is well argued.) However, my experience of running a caseworking directorate did throw up this shadow side of devolving power. I gave more autonomy to team leaders. This vastly improved relationships with stakeholders and our client group. But after a couple of years, I also found a lot of double working and inefficiency had perpetuated within teams. Best practice from one team wasn’t being picked up and implemented by another team. In fact, in the worst cases, the autonomy had allowed bad practice to flourish.


There are plenty of people who work in the centre of Government who have this experience over and over again. They feel like they’ve set the direction, they’ve made the mission clear. But what they have designed isn’t implemented in the way they had envisaged.


How about this for an example. Different Whitehall departments have in the past had very different approaches and some autonomy in setting pay for a new recruit into the Senior Civil Service (SCS), or indeed in offering a package on voluntary redundancy. In so doing, we’ve probably seen a lot of inflation in average SCS pay. Mostly to attract ‘experts‘ from the private sector, particularly in IT and change management. (Who wouldn’t want an aboslute expert in charge of all the benefits and pensions data of the whole nation, at the Department for Work and Pensions (DWP)? But even with that thought, it’s hard to swallow that the Chief Information Officer at DWP is paid around £250,000, which is about £50,000 more than his boss, the Permanent Secretary at DWP. Full high earners list. Perhaps we needed some tighter central control, or even accountability to parliament, for these kind of appointments?


That’s a ‘spending public money’ example. There are examples all over the place of how it looks like too much freedom have resulted in things have going horribly wrong. The case of Baby P is extreme and it feels almost inappropriate to invoke it, but it shows the worst kind of consequences. And there are standard policy solutions to this kind of situation. Minimum standards. Inspections. Guidance. Regulations. Audit. Tight performance management. Central databases to get organisations who deal with the same client to share data.


The question is, how much, when you devolve autonomy, can you trust those you devolve it to, to do the right thing? What is the ‘both/and’ answer here? Clearly it’s good to devolve. But you can’t let go so much that things go wrong.


I’m reminded of something the good people at Harthill consultancy said on the training I attended last year. You can’t ask an organisation to behave from a strategist action logic (i.e. looking at connections, at the big picture, integrating lots of different ways of seeing the world, multi-perspectives) if it hasn’t got it’s ‘bottom floor’ of basic systems and processes right first. A fellow pupil on that course described it as choosing to behave ‘like a War God’ when you’re dealing with people who need direction and clarity. The ultimate in situational leadership, maybe? The bottom line is that maybe there’s a very important place for the rules, the standards, the frameworks, the audits and inspections and standard operating procedures.


That’s the both/and. “It depends on the context”. My question is, when do you know you’re overdoing the ‘getting a grip’ and you should choose to let go?

5 comments:

Paul@BASIC said...

I think you were getting at something near the end when you were talking about the centre setting the framework - the boundary, the vision and objectives... the standards, audits and inspections. The key of course is the approach taken in these activities, and the encouragement to innvoate within what is acceptable, and the encouragement given to experiment. My Dad used to say 'rules are there to be broken'... a good leader will be clear about the rules, and then encourage their people to break them IN COOPERATION with her.

In my tiny world of tiny NGO, my job as the Director, in working with the Board, is to set the objectives of the organisation, but I encourage staff to think creatively on the methods of delivery, and to approach me with their ideas on how to achieve the work. Of course I consult them on the strategy, but in the end that's up to the governing body, the Board, and myself. But the quid pro quo is that the Board do not interfer with the day-to-day... though they are welcomed in where they can assist.

Paul@BASIC said...

FROM JOHN MILES:

I think there has to be a constant learning dynamic and building of trustful working between the nominated leader (the boss) and the people who are notionally working for him/her.

"Letting go" is fine if those who are let go of are "on mission", have the skills and capability to deliver that mission and are reliable. (Sorry if this sounds a bit New Labour-ish)

If people are not on mission or are only partly on mission, if they are incompetent or just plain unreliable that can be a real headache. So you have to have some appreciation of their capabilities, their degree of loyalty and motivation, and be prepared to cut the cloth accordingly.

For delegation not to end in tears there also needs to be a high degree of mutual accountability. There has to be care on the part of the leader in setting the mission goals and associated requirements, boundary conditions etc, to keep things realistic and attainable; also in accepting feed-back; and in being prepared to respond and adapt the mission if things start to go
wrong. This implies a good measure of trust and confidence-building
between the leader and those he/she leads. The leader has to convince everyone that he/she has a good grasp of the overall plot - the view from the balcony - so that when he/she asks for things to be done in a certain way it is understood that what is being asked for is reasonable. Secondly the leader has to be confident that reporting back will be responsible and trustworthy, and proportionate - particularly for any exception reporting if there are important new developments or plans which don't work out.

There's lots of scope for power games and treachery in this kind of dynamic, and personalities come into it too. (I speak from experience.)

Emily Miles said...

From JAKE CHAPMAN:

The issue that you have raised has been seriously studied by systems thinkers and organisational theorists - probably by other disciplines and groups as well. I am not up with all the literature but will summarise my current understanding of some of the issues.

For the system theorists the most important context issue is the degree of variation (called /variety/ in the systems literature) involved in the *demands* on the organisation/system. The greater the variation the more essential it is to devolve power out from the centre; the greater the uniformity of demand the more effective central direction and control will be. Note that a lot of political systems either presume, or aim to impose, a level of uniformity that would be consistent with centralised control. But if the system is exposed to demand that has a large degree of variation then there will be front-line innovations to try to make the system more responsive.

For the organisational theorists a very important context issue is scale. Once an organisation exceeds a certain size (and I forget the details but I think it is around 1000 people) the only structure that will work is a hierarchy, and within such a framework both devolution *and* central control are fraught with problems due to the adequacy of information flows up and down the hierarchy. Basically if the downward flows are distorted then devolution will result in chaos; if the upward flows are distorted then central command will be leading the armies into minefields unnecessarily. And a key factor in determining the authenticity of information flows is the issue of trust. If people trust those above and below them then they will give honest reports. If there is a lack of trust or a blame culture then the information will be distorted and the system crippled.

In his books on organisational theory Stafford Beer was at pains to document the *necessary* conditions for devolving power to work. These included a very clear statement of the boundaries of responsibility and innovation, agreed methods of evaluation negotiated between centre and periphery and a clear understanding of resources and timescales. For a readable summary of his work have a look at "Ten Pints of Beer" at http://www.kybernetik.ch/dwn/Ten_Pints_of_Beer.pdf .

So rather than advocate one approach or the other it might be better to explore the conditions under which different leaders are operating and the degree to which these conditions constrain their choices. And if a leader wishes to change in either direction (i.e. letting go more or controlling more) then there will be a number of things that will have to be managed - particularly information flows and negotiations between centre and front-line.

Good luck with the research!

Jake

barry/emma said...

Hi Emily et al

Not sure if this is of any value to the discussion, but here goes ...

I have just been doing a report on Cisco, a big techno firm (70,000 employees), which has been undergoing some interesting changes. They call it a radical transformation in its business structure - which was, up to 2005, a traditional command-and-control structure dominated by competing departments. They went to a cross-functional structure based on councils, boards and working groups, c. 2006-7; and then to an enterprise-wide collaborative structure (at least at the executive level) from 2008.

Cisco describes itself as moving from an organization “where all decisions came from 10 people at the top,” to one with its leadership and decision-making devolved right across the organization (Sankar & Bouchard, 2009).

This appears to have greatly speeded up the company’s priority decision-making processes (Duperrin, 2009), improved productivity 5% and saved millions of $.

And the key enabling factor? Providing all employees constant access to a variety of social networking technologies within the company (i.e., on its intranet). These include:

• a Facebook-style employee directory and "follow" network;
• a Wikipedia-style corporate wiki which all employees can edit;
• another wiki for proposing new ideas, again open to all;
• a YouTube-like network for internal video sharing;
• an assortment of discussion forums, blogs, RSS feeds, social bookmarking, etc.

Between 2011 and 2012, Cisco will focus on a concept called “New Work”. In this phase, all new projects and initiatives will be advertised on the intranet so that employees will be able to find and bid for the things they would like to work on, and “swarm” to participate in activities with other members of the community (Sankar & Bouchard, 2009).

Cisco is looking very pleased with itself for making this move and seeing a substantial ROI.

Cisco believes its framework for collaboration serves as a model for other companies. Essentially, it recommends organizations must "carefully cultivate the three components of collaboration: people, processes and technology." (Marks, 2009)

So, perhaps new technology goes some way to resolving the information flow issues of the past.

A number of other major organizations have also pioneered the idea of using social networking technologies to create/foster mass collaboration within the enterprise, notably IBM, BT, NASA and Booz Allen. I have more info if anybody is interested.


cheers

Barry

Emily Miles said...

From DAVID ROOKE, HARTHILL:

I think the question of letting go or getting a grip lies at the heart of the human condition. It runs through bringing up children, being in a relationship over time, how we use our agency in life and of course how we lead. So I think you are tapping into a fundamental human dilemma. I have, of late been reading Eckhart Tolle's fascinating (to me) book 'A new Earth' and in many ways he is exploring this question - from an entirely spiritual dimension.

He wonders if we can let go of our ambitions, hopes and constructions enough to enter fully the present moment - which is our connection to the infinite or ground of all being or God or whatever words you want to use. He is, of course, asking a different question to you, but under the layer of managerial efficiency is a spiritual question about what we free in people as we let go.

Ultimately at the practical leadership level I think what is required is a judicious mix of the two - but under that I believe passionately that the leader has to have explored his or her ego. In other words what are they attached to - so much leadership control is an expression of the ego at play, "look at me" and I think this can be confusing in deciding what to let go and what to control.

I recommend Tolle's book strongly - but if the questions he answers are not the ones you have it will all seem a bit irrelevant or indulgent.

With warmth

David