In the familiar fairy tale of the three bears, we read about Goldilocks’ three options - one that is too much, one that is too little and one that is just right. In this parable, there’s a case for applying the Goldilocks principle in how we deliver change. For a long time, where waterfall-style projects were mainstream, change was often delivered in a linear approach with a list of artefacts to complete. Now, in a climate of complex and continuous change, there is an increasing expectation that change programs will be leaner and deliver outcomes in shorter cycles.
The pressure is on the change practitioner to be increasingly adaptive in their approach. What worked on Project THEN in the bank three years ago is unlikely to hit the mark as an approach on Project NOW in health care.
The Goldilocks approach to change management is about what is just right now.
The term Minimum Viable Product (MVP) is fast becoming a commonly used one in project and change parlance. But MVP doesn’t mean we discard our change management toolkit. Without a specific roadmap or prescription for how to plan and implement change, it means that the change practitioner needs to sharpen their capability of being adaptive and knowing when to scale up or down.
If there was a dictionary description for the Goldilocks Change Manager, it could look like this: ‘a change manager who is adaptive and can right-size their plan and approach so it’s fit for the change purpose at hand’
The nature of right-sizing in itself means there’s no prescription on how to be like Goldilocks. The scope and scale of the change initiative helps you size your work. The variables are countless, the possibilities are numerous. Experience and confidence helps of course, as does an adaptive, growth mindset. Here are some tips, all related to tweaking your mindset:
Let go of perfection
Are you attached to the need to develop a perfect document before you circulate it? I have a passion for infographics and material with high visual impact. It took me a (long) while to learn that I was spending a wee bit too much time perfecting my visuals. I learned that having a meeting with a stakeholder with an ‘imperfect’ artefact is okay. Manage expectations and explain that your document is in draft and you are covering points for discussion. I learned that drawing on a whiteboard or flipchart was a way of discussing that promoted a good deal more co-creation and engagement than rocking up to a meeting with big, colourful PowerPoint slide deck. The very fact that a document doesn’t have a high gloss finish is what invites collaboration. By way of example, this approach (and a big hop away from my comfort zone) helped me right-size output. This is also consistent with the agile manifesto principle of - individuals and interactions over processes and tools.
Draw a line, but only in pencil
I’m often asked - Where do I draw the line? How do I know when I’m not over-cooking it? There is no straight answer to this. We’ve all been in situations where the landscape changes and our well laid out plans are no longer relevant. You may have completed an impact assessment only to find out the project has been de-scoped. What started as a small project is now a program of work and you need to recast your change plan. More frequently now, the line changes. When you do draw that line, or make a plan, think about it as a pencil line. You may need to rub it out and redraw it. It’s okay to redefine it, to adapt to user needs and other shifting requirements. It’s not set in stone.
Put people at the centre of what you do
There’s that famous quote - people support what they help to create. Think about the last time you were involved in a decision or a change, even a small one. How did you feel? Sometimes, in all our busy-ness, we lose sight of this principle. The swing to Design Thinking and Human-Centred Design (HCD) is putting us back on the path to grass roots change practice. If we think about what we want our people to do and think, how do we want them to feel, we are on the right track to developing a change plan that is fit-for-purpose. Even better if you can involve your people in this conversation. This leads to the example in my next tip about experimenting…