Last week, the project manager of one of our long-standing clients reached out with a set of very pointed questions. I thought it would be helpful to summarise our conversation here for any leaders steering technology transformation right now.
They’re in the middle of a major technology overhaul. New systems. Multiple AI pilots. Real investment with high expectations. And yet something was nagging at them…they realised that there was an expectation that the software would fix things that didn’t feel like software problems…
You know the saying, “I’ve bitten off more than I can chew”? I think a lot of transformation programs are quietly living a version of it. Not because the ambition is too big, but because we’ve handed the technology a mouthful it was never built to chew.
Software has brilliant teeth for some things: data, workflow, speed, and search. But put a disappointed client in front of it, or a handover that fell through the cracks, or a team member who didn’t think it was their job to call back, and there’s nothing for it to bite down on. That isn’t a system problem. It’s a human one. No amount of chewing will change that.
Technology can remove friction. But only aligned systems, standards and human behaviour can create trust.
Where technology stops and behaviour starts
Technology and behaviour meet at the moment of service. That’s where most transformations get tangled, because we ask one to do the other’s job.
Technology should solve the friction: repeated data entry, searching across five systems for one answer, routine drafting and summarising, workflow visibility, reminders, and access to accurate information.
Behaviour must solve the human moments: whether someone acknowledges the client, takes ownership, listens before responding, explains clearly, uses good judgement, escalates early and closes the loop. Whether the client feels seen and respected.
Leadership must solve what neither can: conflicting priorities, unclear accountabilities, tolerated inconsistency, workloads that make the standard unrealistic, and the gap between the values on the wall and the behaviour that actually gets rewarded.
Then ask yourself the hardest question in any transformation: If we gave people perfect software tomorrow, which client complaints would still remain?
Whatever’s on that list is not an IT problem. It’s a service problem wearing a technology costume.
The goal is consistency in the standard. Humanity in the delivery.
Consistency does not mean every conversation sounds the same.
Consistency means every client can reliably expect the same things, whoever they speak to and whatever channel they use. Ownership. Clarity. Timely acknowledgement. Accurate information. Respectful communication. Closure and follow-through.
Consistency in the standard. Humanity in the delivery.
So, here’s a question worth putting to your team this week: What are the five things you want every client to be able to rely on, regardless of the person, office, system or channel involved?
If the room can’t answer that quickly, your technology has nothing to aim at. Answer that question above, and then you can get to work on steering your technology transformation with confidence.
But wait … be mindful of the sequencing mistake almost everyone makes.
At ServiceQ we see many organisations begin building the tool before agreeing on the work, the service promise and the behavioural standard.
The result? You digitalise the existing workaround. You make the broken thing faster.
The better sequence starts with the client, not the platform.
- Define the critical client moments and what people should reliably experience in them.
- Diagnose the real friction, separating genuine system defects from broken workflows, unclear roles, capability gaps, capacity issues and behavioural inconsistency.
- Set a small number of observable service standards that apply across every role.
- Then redesign workflow and technology together, around the experience you want.
- When you pilot, don’t make it about “using AI”. Test whether one real client moment becomes clearer, faster and more reliable.
- Equip your leaders with routines to observe, coach and reinforce the new ways of working, because if leadership doesn’t hold the standard, people will quietly drift back to their local workarounds. Only then, scale.
We’ve seen this play out with many of our clients in the financial sector, energy sector and mining and resources. The desired Service Habits didn’t land as a standalone learning event. It was woven into operating routines, onboarding, development goals, coaching and internal influencers while technology was the enabler.
You’re not just modernising technology
If you’re leading a transformation right now, here’s the reframe I’d offer. You are not simply upgrading systems. You are designing how your organisation serves.
At the moment, you may have a technology stack. To create a service platform, you need a clear promise above it and leadership reinforcement around it.
That’s the work we love doing at ServiceQ, sitting alongside technology and project leaders to define the service promise, separate the technology problems from the human ones, and build the standards and leadership routines that make the investment pay off.
If this is the conversation happening inside your organisation, let’s have it together. Reply to this email or visit www.serviceq.co