The Symptoms Are Not the Problem
Every transformation program has a list.Toxic culture. Messy systems. People who won’t change. Manual processes holding everything back. Departments that can’t talk to each other.The list gets long. It gets documented. It gets put into a slide deck and presented to the steering committee as the problem statement. And then — with genuine conviction — the organisation sets about fixing it.New systems. Change management plans. Culture programs. Roadmaps with milestones and owners and RAG statuses.Six months later, the same problems are back. Sometimes worse.
What’s Actually Happening
The list was real. The symptoms were genuine. But symptoms are not causes — and treating symptoms as causes is how organisations spend enormous energy on transformation and end up back where they started.Toxic culture doesn’t appear from nowhere. Messy systems don’t build themselves. Manual workarounds don’t survive for years against better alternatives unless something is sustaining them.These are the visible surface of something underneath: the decision-making patterns of the people in leadership.Not bad people. Not incompetent leaders. People operating inside systems — habits, incentives, relationship dynamics, risk tolerances — that consistently produce certain kinds of decisions. And those decisions, accumulated over time, produce the environment you’re now trying to transform.The culture is downstream of the decisions. The messy systems are downstream of the decisions. The dysfunction is downstream of the decisions.If the decisions don’t change, nothing changes.
The Trap That Catches Almost Everyone
It’s easy to see why organisations fix symptoms first. Symptoms are visible. They’re documentable. They can be assigned to workstreams with owners and timelines. A new system replaces a manual process. A new values framework gets rolled out. A consultant produces a roadmap.Progress looks real because motion is real. Reports turn green. Milestones get ticked.And then, somewhere in the months after go-live — or after the culture program wraps — the old patterns return. Because the underlying decision-making environment was never addressed. The new system gets worked around. The new values don’t survive the first difficult tradeoff. The roadmap was delivered but the transformation wasn’t.This is not a failure of planning. It’s a failure of diagnosis.
What Leaders Are Actually Being Asked to Do
Transformation leadership is not project management at scale. It’s something harder.It requires understanding what’s actually driving decisions in your organisation — the real patterns, not the stated ones. It requires sitting with uncomfortable questions: Why do we keep making this kind of decision? What does our system reward? What do people actually believe will happen if they raise a flag?And then it requires creating the conditions — at the executive and decision-maker level — where different decisions become possible. Where the people closest to the problems can surface them. Where the instinct to protect a decision gives way to the discipline of confronting it.That’s not a roadmap. It’s a leadership posture.
Why This Matters for Your Program
Most transformation programs are well-intentioned and well-resourced. They fail not because the plan was wrong but because the plan was aimed at the wrong thing.If your program is targeting symptoms — systems, processes, culture artefacts — without addressing the decision-making environment that produced them, you are building on unstable ground. You may deliver the program. You will not deliver the transformation.The question worth asking before the next steering committee meeting is not: Are we on track?It’s: Are we solving the right problem?
SP Singh is the founder of Bhani Consulting, providing independent ERP oversight and advisory services to executives sponsoring technology and transformation programs. He works with WA local government, Aboriginal corporations, and mid-sized organisations.
