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’s your lowest price?

[caption id="" align="alignright" width="300"]negotiation English: Terraced house façades, Montague Street See also 1608624 (Photo credit: Wikipedia)[/caption] I’ll never forget my first serious experience of negotiation. I was selling my first house, a small, terraced house in a cheap part of the city. I loved it, because it was the first house I had owned, and because I had put a lot of work – and a lot of myself – into it. I had decorated every room; I had refitted the kitchen; I had installed central heating to replace electric storage heaters. I was moving to a new area, where I knew housing was going to be a lot more expensive. I had received an offer to buy my house from a junior colleague at work. Obviously that made things slightly awkward to start with. But I was unprepared for what happened when he asked if he could visit again, with a family friend. They duly arrived, and I showed them around. The family friend, an older gentleman, was very appreciative, admiring everything I had done, complimenting me on my workmanship, and so on. And then, at the end of the visit, he pitched me a new price, substantially lower than the offer my colleague had previously made. I was caught off guard. Having refused the new price, I felt I had to respond to his questions, starting with what was the lowest price I would accept? He came back with requests to throw in this and that if they agreed to a higher price, and so on. We eventually agreed a deal – which actually was not such a bad deal from my point of view – but I was left feeling bruised. Looking back, I have to admire the technique. All the praise, all the efforts to make me feel good first, worked a treat, and there was nothing in the negotiation itself that I could criticise. He did a good job for my colleague. So why did I feel bruised? The one thing that was missing in the exchange was creating an honest expectation. I had been led to believe that the friend was there to give a second opinion. It was my colleague’s first house purchase, just as it had been mine, so understandably he wanted someone else to endorse his judgement. I had not expected that the friend was there to negotiate on his behalf – after all, an offer had already been made. Perhaps I was a bit naïve, but I was caught unprepared; the negotiation had high financial and emotional value for me, and I had no experience of handling something like that. I felt that I was backed into a corner, and that personal trust had been breached. So what is the lesson? Don’t just play fair – make sure everyone knows what game you are going to be playing beforehand, especially if personal relationships are involved. Trust is too important, and too hard to rebuild, to risk losing.

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.

If it isn’t broken, why fix it?

innovation Let's face it, if innovation isn’t change, what is? So in thinking about why change is difficult, and how to overcome the challenges, thinking about how to make innovation successful may help. A frequent characteristic of innovations is that the needs they address, or could address, are not recognised. History is littered with examples, from Marshal Foch’s view that aeroplanes were of no military value to Thomas Watson’s famous assessment that there might be a global market for at most 5 computers. Most people have heard the saying “build a better mousetrap, and the world will beat a path to your door”. Innovations still fail, though, because the world didn’t know it needed a better mousetrap, and so it wasn’t listening. Before you can even start to persuade people to adopt your innovation, you may have to help them to recognise that they have a problem it can address. Change initiatives are no different. I was recently helping an organisation plan a major change. I believed that the change would have consequences for other aspects of the operations, and that these consequences needed to be planned for too. Although I made several attempts to explain this to the CEO, I failed to convince her. Needless to say no such planning was done, and so I shall not be surprised if there are later problems requiring emergency solutions. A pity, but you can’t win ‘em all! How do change initiatives start? One or a few people have an idea about how to do things differently. Sometimes there may be a widely-recognised problem, but even then it may be a big step to create the link to the proposed solution. Often most people – even management – have not yet recognised that there is a problem, and before they will consider any change, they need to be persuaded that the need is real. Change initiators are often the people who are able to see what will trip up the organisation before others can, but that means that they also have the challenge of helping others to see what they see. Think of the lookout on a boat – their vantage point means they can see rocks ahead before anyone else, but before they can get the boat to change course they have to be believed. The power of the human mind to cling on to existing beliefs, for example that the rocks are miles away, is very strong. So change management starts with taking the time to educate people about the problem that needs to be addressed. Until they believe that there is a problem – that there are rocks ahead – trying to persuade them to accept the change required to address it is likely to be wasted breath. If you need help seeing the rocks, or persuading people they are real, do get in touch.