Currently browsingPlanning

How is work like a packet of muesli?

task order Have you ever noticed that the fruit and nuts in your breakfast muesli tend to stay at the top of the packet? So that when you are getting toward the end of the packet, you are usually left with mostly the boring bits? There is a simple explanation. When there are many large lumps (the fruit and nuts) together, they have large holes in between them, and smaller lumps (the oats) can fall through the holes. When many small lumps are together, they have small holes in between them, so large lumps can’t fall through. Consequently, with gentle shaking there is a tendency for the large and small lumps to separate, with the large lumps at the top. Interesting, but so what? Well, perhaps the same sort of thing happens with the order of work activities. The interesting, strategic lumps stay at the top and get done first. The boring – or difficult – bits may fall through the cracks, or at least get left to others or to later. The trouble is that to have a nutritionally balanced diet, we need the whole mixture, not just the exciting bits. Good delivery requires us to stick to doing things in the best order, even when that means tackling early some activities we would rather leave till later.  

Which matters most, the big picture or the detail?

strategy Is your high-level strategy adequately joined up with the realisation of the vision on the ground? The people who are interested in the strategy are often not very interested in managing the details, and perhaps are frustrated by the questions they are asked by implementers. The people who are delegated the task of dealing with the detail frequently do not have the strategic ability, or lack the information, to understand fully the context for what they have been asked to do. The consequence is a gap between intent and delivery which is often filled with misunderstandings, confusion, misalignment and ultimately frustration.

A joined-up strategy

Overcoming this requires a clear shared understanding of the big picture. It is not just about communications, although that is important. As they say, the devil is in the detail, so it requires working together to think through the implications of strategy – the roles cannot be separated. Both the big picture and the detail matter, but how you join them up is critical: the whole can be greater than the sum of the parts, but only if it really is a whole.

Are you Red or Blue?

Yesterday I spent the morning at WBMS, in a fascinating workshop run by Quirk Solutions exploring the value of ‘Wargaming’ as a way of testing the resilience of a strategy and related plans before putting them into effect.

Wargaming, as you might imagine, is based on the process developed by the military to evaluate their plans, but that is where any direct connection to anything military ends. If you called the process something else, nothing about it would tell you its origins. And in practice, it is really a somewhat more formalised and disciplined extension of testing approaches which you may well already use to some extent. Where Chis Paton and his team at Quirk really add value is in their in-depth experience of what works, and highly-polished skills for facilitating the process to make it maximally effective. I took away a number of key ideas for running a good process which I thought it would be worth sharing.

Wargaming

The process is based around two teams: the Blue (plan-owning) Team and the Red (plan-challenging) Team. Although that sounds similar to the common approach of ‘Red Team Review’ for proposal improvement, in this process it is made more effective by asking each Red Team player to represent the views of a major interested party or parties. This makes for a much more engaged and lively process, better bringing out emotive issues. It can also bring out the important potential conflicts between different interests which may otherwise be ‘averaged out’. At least some of the Red Team can be externals – where there are no commercial issues, they could even be the relevant interest groups themselves! – which is clearly likely to help avoid blind spots. Even in a brief exercise, it was clear that the role-playing approach could bring much greater richness to the output. The process is also iterative: the Blue Team present their outline plan (best not to develop too much detail early, as it is likely to change!); the Red Team make challenges back from their ‘interest’ perspectives; the Blue Team re-work the proposal to address as many of the issues as possible; further challenge, and so on. Clearly in a relatively brief review meeting, there will be very limited time for further analysis or data gathering between iterations, so the objective is not a finished plan, but the best possible framework to take away and work up, together with lists of actions and owners. That leads me to my final point: While a Red Team Review would normally be looking at a more-or-less finished proposal, the process we tested will add most value early in the process of development. No-one likes to make significant changes to a plan that they have put a lot of effort into, however important, and that may well lead to the smallest adaptation possible, rather than the best. Thanks WBMS and Quirk for organising a stimulating event!

Lovely day at The Shard!

best practiceI went to a fascinating talk by Adam Hoyle, Managing Director, Tradax Group Ltd, on Corporate Best Practice in Public Sector Bidding. I thought there were a number of lessons that apply more generally to running all kinds of projects that would be worth sharing.

Seven best practice tips

  • Don’t start projects unless they align with your overall strategy
Obvious, but I’ve often seen it ignored in the heat of the moment, too!
  • Make sure you have thought through exactly what decision-making authority each person involved should have, and that this has been clearly communicated and understood
In my experience the latter are frequently neglected, even if the former is not. Too many people think governance is boring, so don’t bother. It should provide the rock that success is built on
  • Give everyone involved a clear written briefing pack at the start, providing them with all the basic information about the project that they will require
Saves a lot of repetition, and makes sure everyone has a single reference point they can go back to, so things are more likely to join up later. It saves you time in the long run
  • Standardise what you can – but everything that is standardised needs an owner who takes their ownership seriously
We all know how fast most of the stuff on our intranets goes out of date, but still sits there. The corollary may also be true: what you can’t find an owner for, you probably won’t be able to standardise effectively
  • Think hard about what information would really make a difference to your performance if you had it, and work creatively (legally of course) to get it – for example using FoI requests
I think the key is identifying what information would lead to specific and worthwhile improvement actions if you had it. Too often, people ask for information without having thought about what they would do with it. When they get the answer, they realise it is interesting, but not actionable
  • Use the information you have intelligently – there is probably much more that you can learn than is immediately obvious, if you put it all together
E.g. draw graphs of trends across projects, and work out what they are telling you. And don’t ignore what you see because you don’t like the message, as people often do!
  • Transitions between teams – for example on winning a bid, or starting to operate an asset – are high-risk boundaries, which need careful planning to make sure they go smoothly
I recommend running readiness reviews for these. It is not the review that counts – by then it may be too late – but the knowledge that that discipline will happen Do go and listen to Adam talk and hear his views on best practice first-hand, if you get the chance! He’s an inspiring speaker.

What a scorcher

joining things up There is a rather impressive new office building going up in the City of London at the moment. Colloquially referred to as the Walkie Talkie building (London likes its building nicknames), instead of the usual flat walls, its walls are gently curved, giving it a very sculptural quality. And like many modern office blocks, it is covered with floor to ceiling glass. It will look amazing when it is completed. However, people living, working, or even just passing nearby are feeling amazed for all the wrong reasons. It seems that the architects didn't join things up - they forgot to take account of – or underestimated – the effects of the laws of optics. Think of a reflecting telescope. It works because the concave mirror in the telescope focuses the light from the stars that falls on it. What have the architects put on the front of the Walkie Talkie building? In effect, a gigantic concave mirror. And like all such mirrors it focuses the light – in this case particularly the sunlight - falling on it. On a hot summers’ day, the temperature in a nearby street has risen enough to blister paint and melt plastic. Now it’s called the Walkie Scorchie.

Joining things up

It’s a great idea to reflect sunlight so that your offices don’t overheat, but it is not OK to give someone else your sunlight problem instead. Frequently an internal focus on solving our own problems can blind us to the difficulty that our solution may export to someone else. However expert each of us is in the areas we know about, we may blunder into basic problems outside those areas. In this interconnected world, it is wise to think carefully about any possible external effects; otherwise an embarrassing oversight can quickly become a PR disaster. Joining things up so that such things do not happen is far from easy, and needs a commitment to cross-silo working that few organisations seem to recognise. Busy managers may not have time – and frequently have no incentive – to consider wider impacts. Making it happen requires explicitly recognising the need and creating processes in response.  

Which end of natural selection are you on? Evolution and strategic change

[caption id="" align="alignright" width="300"]evolution Tyrannosaurus rex, Palais de la Découverte, Paris (Photo credit: Wikipedia)[/caption] Evolution is the natural process by which all forms of life adapt to changes in their environment. It is a very slow process, in which many small changes gradually accumulate. It is unplanned and undirected: who knows how the environment may change in the future, and so what adaptations would put us ahead of the game? Successful changes are not necessarily the best possible choices, merely the best of those that were tested. Different individuals start from different places, and so the adaptations which seem to work will vary.  Consequently, over time, divergence will occur until different species result, even though each species can be traced back to a common ancestor. But evolution is brutal too: not all species will make it. Some find they have gone down an evolutionary dead end, and some that change is simply too fast for them to adapt to. Sometimes organisational change can be like this. I once worked for a public-sector organisation which was privatised, so that it had to change from being ‘mission-led’ to being profit-led. Management set out a vision for what it wanted the organisation to become – essentially a similar, unitary, organisation but in the private sector – but was unable to make the radical changes necessary to deliver it fast enough. Evolution carried on regardless as the primary need to survive forced short-term decisions which deviated from the vision. Without a unifying mission as a common guide, different parts of the organisation evolved in different ways to adapt to their own local environments. Fragmentation followed, with a variety of different destinies for the parts, and a few divisions falling by the wayside. Despite starting down their preferred route of unitary privatisation, the eventual destination was exactly what the original managers had been determined to avoid. What is the lesson? Ideally of course it should be possible to set out a strategic objective, and then to deliver the changes needed to get there. But if the change required is too great, or the barriers mean change is brought about too slowly, the short-term decisions of evolution may shape the future without regard to management intentions. That does not necessarily make the outcome worse in the greater scheme of things: after all, evolution is about survival of the fittest. But natural selection is an overwhelming force, and if short-term decisions are threatening to de-rail management’s strategic plan, it may be wise to take another look at the plan, and to try to work with evolution rather than against it.

Disasters and how you can (try to) avoid them

[caption id="" align="alignright" width="300"]disasters View of Chernobyl taken from roof of building in Pripyat Ukraine. Photo Taken by Jason Minshull, then digitally zoomed. (Photo credit: Wikipedia)[/caption] Have you noticed how often it happens that when things go wrong, they don’t just go wrong, they go horribly wrong? From the truly horrendous disasters like Chernobyl and Fukushima to the merely painful like a company going bust, once things have started to go bad, the interventions people make often exacerbate the situation. Why is that? When things start to go wrong, there can be a number of immediate reactions, depending on the circumstances. One is to hide your head in the sands, and pretend that there is nothing wrong. That is almost guaranteed to make things worse! More common is the fire hose approach:  do something drastic with the intention of stopping the immediate threat, which may deal with the underlying causes (although it may also exacerbate them), but certainly soaks everything, whatever the consequences. Following the analogy, the fire hose is good at putting out some sorts of fires, but inadvisable on oil or electrical fires! In between is the timid approach – not wanting to do any more damage than can be avoided, the attempted cure finishes up being too little and too late. How difficult it is to get the balance right!

Fast disasters …

It is understandable that in a crisis people react by tackling the obvious problems. If your house is on fire, stopping the flames obviously seems more important than avoiding ruining the furniture.  When the situation is relatively simple, that approach works. The problem comes when the situation is more complex. In a crisis, you act instinctively, and you do not usually have time to think through the consequences of your actions. Almost by definition, complexity will bring unforeseen consequences. How many organisations have no more complexity than they need? What to do about this? There are two possible approaches. You can minimise the risk of unforeseen consequences in a crisis by keeping the organisation as simple as possible. Or you can practice crisis management through exercises and so attempt to learn what adverse consequences might occur and how to avoid them. Or you can do both, of course. Clearly though, both of these have a cost which needs to be incurred when there is no crisis in sight.

… and slow disasters

Slow disasters pose different and much more difficult problems. The fire-hose approach is much less likely; head-in-the-sands and timidity more so. It all starts with ability to acknowledge the problem in the first place. The organisation’s leaders may not believe that what they are seeing are signs of a problem. Even if they do think there is a problem, they may not want to admit this. They or people they are connected to may have vested interests; they may be unwilling to admit failure, or believe that admitting problems will damage confidence and make them worse; they may believe that other issues are more urgent. Perhaps the most common situation is that leaders recognise the problem, but simply underestimate what is needed to fix it. Most managers are optimists at heart, and in deciding what – often painful - actions are required, optimism bias will tend to creep in to minimise the pain. These can be very difficult decisions:  for example, no manager wants to make any more staff redundant than they absolutely have to. However, if the ‘cure’ is insufficient, the problem remains, and will have to be treated again – with the ‘patient’ now in a weaker condition than previously. Underestimating can be fatal: death by a thousand cuts is a phrase I have heard repeated too often, and the consequences for staff can be worse than being bold at the outset. In summary then, perhaps the message in both cases is the same: optimism rarely provides salvation; taking what feels like unnecessary pain early may do.

Be prepared!

interview A few years ago I needed to hire an assistant. I’d fixed an interview, and everything was organised. It was five minutes before the time the candidate was due, and I was just collecting my papers and my thoughts. At that moment, the din of the fire alarm started up. There is – of course – nothing that you can do. Down the concrete back stairs, and out round the back of the building to the assembly point, into the London drizzle without a coat, while I imagined my interviewee arriving at the front. I had left all my papers on my desk in the dry, and had no other record of his contact details, so I had no way to suggest an alternative plan. A little while later, my mobile rang. Having arrived and been barred from entry, he had managed to track down my mobile number himself, and we were able to arrange to carry on with the interview while we dried out in a local coffee shop. Needless to say, his resourcefulness impressed me and he got the job. Despite the unhelpful circumstances of the interview, he was one of my best hires ever. Life has a habit of not going the way we plan it. Unexpected circumstances can often be turned to our advantage though, if we grasp them rather than trying to stick to the plan, and often the results are better than you could possibly have expected.