change management

Everybody hates your project name

Posted on by Blog

One of the strange things about the corporate world is the love of a project name. We create these with the stated aim of confidentiality, rather than call something what it is – we give it a “project name” so that no-one will ever know what we’re working on. The corporate halls are filled with projects named after gem stones, countries, animals, plants and pretty much any other grouping that you get taught about in kindergarten.

Don’t get me wrong, there are clearly big commercial projects and programmes that require the sort of confidentiality that comes with a project name (and normally a Non Disclosure Agreement) too. But there are also a hell of lot where it simply isn’t necessary. I’m not naive, I recognise I’m not going to change that, too many people are circling back, to move the needle on project names and sometimes taking them offline to create a win win.

You get where I’m going…

But I do want to talk about those people related changes and why your project names are bad for you, bad for employees and bad for your business. HR loves a project name, because it makes us look special, important and allows us to hold power through secrecy. We create these because it makes US feel special, but ultimately disrupts the business more than necessary and makes us look like fools.

Fresh Start!

One Team!

Fit for the Future!

Reset!

Chrysalis!

Re-vision!

(The exclamation marks aren’t necessary but whilst I write this my inner voice is taking control)

The first reason not to do is this is the names are always divisive. The people coming up with them are seldom impacted by the change other than having to implement it. Whereas the people who have their lives turned upside down due to rubbish piece of branding have to go home and tell their families that they might not be able to pay the bills because of a project named after insects transforming.

The second reason is you create a “thing”. Organisation memory lasts longer than most leaders. It is much more likely that people will remember and talk about the impact of, “Fit For The Future” rather than the time they changed the management structure. The point of a brand is to make it memorable, but on people related change you want quite the opposite – you want people to move on as soon as possible.

And the final reason is it stops you thinking about the people. When you start to measure success in relation to a project, and stop measuring it in terms of the impact of people’s lives you fulfil all the stereotypes that people have of management and leadership. Imagine you were managing Project Cause No Distress. What decisions would you make then?

Sometimes changes need to take place in organisations, that goes without saying. Our job is to implement them with as little unintentional impact as possible and to help individuals, teams and the organisation to heal and move on as quickly as possible. There’s no project name ever created, that’s additive to that.

Why most management change fails

Posted on by Blog

Let’s face it, change doesn’t fail or succeed, it just is. When we try to do something and it doesn’t work, that doesn’t mean that change hasn’t happened, it just means the outcomes that we want haven’t been achieved. We need to understand the difference.

If I decide I want to get fit I might buy a pair of running shoes and commit to go jogging every morning before work.  After three weeks when I’m demotivated, tired and laying in bed longer than ever before, a change has occurred, just not the one that I intended. In my head I’d imagined this svelte, athletic new me who absolutely loved this new habit. In reality I developed a belief I couldn’t run, confirmed I didn’t like early mornings and chafed in places I didn’t know existed. If someone was in the future to suggest a run, I’d make my excuses and leave.

What does this mean in an organisational context?

Most of our employees and colleagues have experienced this sensation at work, however, the motivation for the original decision hasn’t been theirs. They’ve been subjected to multiple suggestions over the years that they need to go for the equivalent of a run.  And similar to the runner they start to form beliefs, “it won’t work”, “I don’t like it” or even “what’s the point?”.

Sometimes the most important “changes” that we make are choices to do nothing, rather than to do something. If we litter our organisations with initiatives, if we try to do too much that adds little value we start to create the sort of psychological fatigue that leads to beliefs that ultimately are counter productive to the changes that actually need to achieve. Through our actions we can cause the reaction that we then dub, “resistance to change”.

Nobody is resistant to change, we all make changes every single day. We shop with Amazon, send messages on our phones, we use satellite navigation systems and find love by swiping left or right. We are constantly changing and evolving. Organisations become resistant to change because of the experiences that have happened in the past, because of the belief systems that have developed and because of our inability to keep things simple and clear.

 

Gauging the speed of change

Posted on by Blog

We’ve all been there, the conversation where the speed of change is, “just not quick enough”. I’ve probably uttered the words myself. One of the biggest tricks for any leader in this circumstance is being able to differentiate between the input activity and the desired output. Or, the things we need to do in order to get the results we want to see.

It’s a wonderfully alluring concept to equate the speed of delivering the first with the achievement of the second, but sadly there is no direct line between the two. Regardless of their experience, leaders will be told to reduce the time to implement, to condense the programme of activities to realise results much more quickly.  And many will happily comply to demonstrate the activities have been done, ahead of schedule. Which is good, right?

Except the desired change doesn’t happen as we wanted.

But that’s ok, because it must be the fault of someone else, somewhere else. We absolutely nailed our contribution – they just didn’t do what we needed.

The inescapable issue is that there is an optimum rate of change in any organisation and in any situation and it won’t always be the same, dependent on context. The key to successful change is twofold –

  • Understanding the contextual climate for change
  • Measuring success on outputs and inputs

To give a simple example, let’s imagine a bottle of organisational goodness (aka water) which we trying to unlock and set free into a new organisational design (aka a bowl). On one end of the spectrum, we could hold the bottle upside down and shake it frantically, the water will probably come out pretty quickly, the chance of splashing, missing the bowl and causing a mess though are high. At the other end the spectrum, we could tip it slightly below horizontal, place the neck against the lip of the bowl and transfer all the water. It will be super slow, but highly effective.

The reality is that somewhere between the two is the most effective spot, based on the deign of the bottle and the bowl.

Ultimately, the answer to success lies in the name itself – “change”. If all we were interested in was the activity, we’d probably call it “stuff”. One of the key skills of any leader is to be able to articulate the importance of the embedding and sustaining of change and not get caught into the organisational pressure to do some stuff quickly. It won’t always be the answer people want to hear, it won’t always make you the most popular, but if you’re genuinely keen on delivering success, you need to be sure everyone knows and agree what it actually looks like.

Note: Having researched the optimum way to extract water from a bottle at speed, I’m led to believe that in principle it is to swirl the bottle in a circular motion, creating a vortex through the centre that allows water to extract via the sides whilst air rises through the vortex. Sounds complicated.

Are you running a marathon, or becoming a marathon runner?

Posted on by Blog

 

One of the fundamental reasons organisations struggle with change is that they frame it in the wrong way. I’m not a huge fan of sporting analogies, but forgive me this once.

One day I wake up and say that I want to run the London marathon. There are clear success criteria, clear steps to take and a very clear deadline. I can get my friends and family energised, maybe get them to sponsor me or come and cheer me through to the finish line. Of course, there are things that might get in the way – I might not get a place, I might pull a muscle, but other than that it’s a pretty straightforward (if daunting) task.

This is the “change” that most organisations like to face and are well equipped to achieve.

Now what if I was to wake up that day and say that I wanted to be a marathon runner? How would that change the approach and the context? When would it be achieved, when I’ve done one, two, ten? When I can run a marathon at will? My friends will probably not be too interested, they might even find me a bore and wonder why I’m slogging my guts out after work rather than going for a pint.

This is the change that most organisations are trying to achieve and are struggling with.

The joy of the first scenario is that once it’s done we can forget about it. Go to the pub and have a pie and a pint and spend every weekend on the sofa watching other people run around. We can revert back to our previous behaviours, with the task complete.

The issue with the second scenario is that we are talking about sustainability underpinned by behavioural change. We are transitioning into a new form of being, with no real sense of measurement, but a pretty clear sense of whether it has been achieved or not.

The difference between acting with agility and being an agile organisation.

The problem comes when organisations approach sustainable change with the mindset of task completion. We want to know when it will be done, why it hasn’t happened yet and why no one is coming along on the journey with us. We want the razamataz of the finish line and the medal and all we get is a pile of sweaty training clothes.

Creating meaningful, sustainable change is hard. It takes time, practice and repetition, it takes failure and despair. Worst of all, you’re never really sure if you’ve achieved it, or when or if you’ll arrive. Despite all the sweat, blood and tears, despite all the hard yards, you will only see how far you’ve gone, not how far you need to go.