How a technology problem turned out to be a flow problem, and why fixing the operating system changed everything
When McMillan Shakespeare, the ASX-listed financial services organisation, engaged LeanCX for a large-scale operational diagnostic, the presenting problem looked familiar.
Rising operational pressure. Fragmented customer experiences. Teams overwhelmed by work that never seemed to reduce no matter how hard people pushed. And somewhere in the background, a sense that the technology was not delivering what had been expected of it.
It took about three weeks of observation to understand what was actually happening.
The organisation did not have a technology problem. It had a flow problem. And more specifically, it had a Strategic Operating Model problem that had been compounding for years.
We do not start engagements in boardrooms or with data packs. We start on the floor, with the people doing the work.
Across frontline teams, specialist support functions, digital channels, and operational processing areas, we conducted a deep diagnostic that included process observation, team interviews, workflow walkthroughs, customer pain-point analysis, demand and exception analysis, and a careful mapping of how customer journeys intersected with operational realities.
What emerged was not a list of isolated problems. It was a pattern.
Teams were working incredibly hard. Staff were capable and committed. But the operating model itself was generating unnecessary complexity faster than any individual or team could remove it.
Customers were not struggling because frontline staff lacked knowledge. Staff were not overwhelmed because they lacked effort. The system was creating friction. And the system had never been deliberately designed to stop doing so.
The most important insight from the diagnostic came from mapping the customer journey alongside operational workflows simultaneously rather than separately.
Customers were consistently struggling with the same things. Understanding the financial impact of their decisions. Knowing what would happen next and when. Navigating digital experiences that were fragmented rather than guided. Receiving different explanations from different people about the same products and processes.
At the same time, operational teams were drowning in repeat calls, manual validations, rework, exception handling, duplicate checking, and endless requests for clarification that ate capacity without adding value.
The critical insight was that these were not two separate problems. They were the same problem viewed from opposite sides of the service interaction.
Poor clarity created repeat demand. Repeat demand consumed capacity. Reduced capacity increased delays. Delays increased customer anxiety. Customer anxiety drove more contact. More contact created more operational pressure. Which produced more poor clarity.
The organisation had unintentionally designed a self-reinforcing demand loop. Nobody had set out to build it. But over time, it had become structural.
Breaking it required redesigning the operating model, not optimising the individual parts within it.
The work shifted from process review to operating model redesign. That is a meaningful distinction.
A process review asks: how do we make this step faster or more accurate? An operating model redesign asks: why does this step exist in the form it does, and what would need to change for the system to behave differently?
Some of what followed was structural. Clarifying operational ownership. Simplifying how teams explained products and processes to customers. Redesigning the sequencing of process flows to reduce handoffs and waiting. Identifying where digital and phone channels were creating confusion rather than resolving it and aligning them into a more guided experience.
Some of it was behavioural. Standardising the way teams communicated about timelines and next steps. Introducing lightweight feedback loops between customer insights and operational teams so problems surfaced quickly rather than accumulating. Building small but consistent operating rhythms that gave teams visibility into what was working and what was not.
And some of it was remarkably simple. Adding a clear next step to customer communications. Setting more specific expectations at the start of an interaction. Embedding proactive education into onboarding so customers arrived with better context.
These were not transformation programs. They were operating model corrections. Small, targeted, and collectively significant.
One of the most important conversations we had during this engagement was about what productivity improvement actually means.
The instinct in many organisations is that productivity means doing the same work with fewer people. That instinct is understandable but usually wrong, and it misses where the real opportunity sits.
Sustainable productivity comes from removing unnecessary effort. Not from asking people to work harder on work that should not exist.
The diagnostic identified significant capacity being consumed by rework loops, manual reconciliation activity, failure demand, operational duplication, poorly sequenced processes, and channel shifting caused by digital confusion. None of that work was adding value for customers. All of it was consuming time and resource that could be doing something better.
By redesigning flow, improving clarity at the customer interaction level, and reducing avoidable demand at its source, teams recovered capacity without anyone being pushed harder. The work simply became less chaotic and more purposeful.
That is the difference between cutting and redesigning. One removes people. The other removes the unnecessary effort that was making everyone's work harder than it needed to be.
The outcome of the engagement was not a single solution or a technology recommendation. It was a structured roadmap that balanced immediate operational improvements, behavioural changes teams could make without waiting for a project, digital experience enhancements, process redesign opportunities, and longer-term operating model shifts.
More importantly, the organisation had something it had lacked before: a shared understanding of how operational friction, customer experience, employee experience, and productivity were all connected to each other through the same underlying system.
That shared understanding matters more than most people realise. When a leadership team can see the system they are operating inside, rather than just the symptoms appearing in different parts of it, the quality of the decisions they make changes. Priorities become clearer. Resources get directed at causes rather than effects. And the conversations about what to do next become far more productive.
Sustainable transformation does not happen when organisations simply work harder. It happens when they evolve intelligently. That starts with understanding the operating model, not just the processes within it.
Sudharsan Raghunathan is the founder of LeanCX, a transformation consultancy helping enterprises evolve intelligently by aligning people, process, and technology.
leancx.com.au
