Culture eats strategy for breakfast. – Peter Drucker
If this is the case, why is Change Management, an effort to address the Cultural underpinnings of Change Initiatives, often seen as wasteful?
We think about the technology, battle over price and then completely ignore that the technology being introduced is the “strategy” part of Drucker’s statement. What about the culture?
Perhaps one of the reasons we have to re-learn this lesson is because we constantly forget. Remembering the last implementation that lost out to Culture is like remembering the first two years of your child’s life.
Everyone generally remembers that it sucked, but no one can point to the details. They have somehow vanished.
As for why implementations often fail, it is certainly possible that the solution may not have met the success criteria. It’s possible. But a more plausible explanation requires us to dig a bit deeper — the success criteria was a mask for a foundational blocker preventing new technologies from being introduced. In all likelihood, the implementation probably challenged some cultural norms. What often happens is that Culture refused to take on something new, and instead of blaming itself, it blamed technology.
So knowing this, it’s time to look at the cultural norms. How often are new technologies or innovations embraced in your organization? When was the last time a new technology challenged the norms – the way things were or are in your Company – and won?
To do a deep dive into Cultural norms, I would suggest the following steps before taking on a Culture-challenging change initiative.
Step 1 – What is your Hostile Architecture?
Hostile Architecture (or Anti-homeless architecture) is designed to deter the homeless population from lingering.
I haven’t met an organization that doesn’t have some hostile architecture – things that are intended to inconvenience Change in an organization. What is the Hostile Architecture in your organization?
Do structures in your Culture keep innovation out? What foundational pillars or organizational structures are in place to keep new technologies and new ideas from lingering?
Step 2 – What are the ghosts in the machine?
Since the dawn of computers, there have been random strings of code. Occasionally, these random strings cause errant issues; no matter how hard people try to remove them, they remain. These random strings are referred to as ‘Ghosts in the machine.’
Simplify it when looking at your company culture and trying to assess what ‘Ghosts in the machine’ might have to do with cultural norms. There are undoubtedly lingering ideas and beliefs that are slowing you down — baggage from the beginning of your Company’s creation.
What is the thinking in your Culture built to keep innovation out? Are new employees shown the ‘right’ way? What systems or beliefs have you held onto that block new technologies from pushing the Culture forward?
References and Resources
Reboot by Jerry Colonna