Technology is changing how organizations deliver IT services, but the people behind those services remain central to making them work. As organizations adopt AI and rethink their service management practices, the challenge is ensuring that technology supports people rather than defining how they work.
Humans of Support is our interview series featuring the people building, transforming, and shaping the world of IT support and service management.
In this episode, we speak to Simone Jo Moore, a digital business consultant and ITSM thought leader with over 20 years of experience in business transformation. Known for advocating a more human-centred approach to technology and service management, Simone brings together IT, organizational change, and AI governance in her work.
We discuss what humanizing IT means in practice, the importance of keeping people involved as AI becomes more embedded in service management, how support has evolved, and why organizations need to look beyond automation when planning their transformations.
Here’s the full interview with Simone.
You’ve spent much of your career advocating for more human-centered IT. What does “humanizing IT” actually look like in practice?
Humanizing IT means refusing to let technology define who we are. It should help people become who they want to be, rather than dictate how they work.
Simone Jo Moore, A digital business consultant and ITSM thought leader
Well, I would hope that we were all human at some point! It’ll be interesting to see what the future holds.
For me, humanizing IT isn’t just about adding a human touch to technology. It’s really refusing to let technology define who we are. Rather than technology creating what we want, we actually want to harness it so that we can become who we want to be.
Think about merging systems over a weekend, for example, particularly in mergers and acquisitions or restructures, which many organizations go through. You end up with two entities, two cultures, and two toolsets.
The technology integration might seem like the easy part. Bringing the cultures together is where the real work happens.
Whether you’re merging a website, bringing two service desks together, or thinking about what day one looks like for people who have been acquired and are being brought into a new culture, there’s a lot more to consider than the technology itself.
It’s really about finding a unique combination of sustainable change, blending business and technology approaches and frameworks to fit the people in front of you.
Bringing people together and building trust takes as long as it takes. That’s ultimately what determines whether the integration has worked.
As AI becomes more embedded in service management, how can organizations automate routine work without losing empathy, human judgment, and accountability?
AI can mimic emotions, but it cannot replicate human empathy, nuance, or judgment. Organizations must build empathy, risk awareness, and accountability into their processes before automating them.
It’s a really good question because a lot of people talk about emotional AI as if the AI itself has emotions, but it doesn’t really. It’s a mimic. You could ask the question: robots can cry, but should they? I think if robots could cry, they’d end up just rusting!
AI doesn’t have the ability we do to understand nuance and add meaning. That’s a very important part of our empathy and judgment. Our emotions are actually part of our dataset. That’s what helps us make decisions as well.
AI doesn’t correct poor governance. It actually accelerates the existing behaviours we have. So, when we think about empathy, the way we approach it really has to be designed upstream, not just supplied by support afterwards as an apology.
If we want good judgment and accountability, we need to make sure our people have the right understanding, along with risk management training and relationship management training. Empathy is innate to many people, but it’s also a competency. It’s something we can learn.
My mum once told me a story about when she was small. She had these little pockets in her dress and would put snails in them because she loved mooching around in the garden.
At that time, Nana had the old rollers to squeeze the water out of the washing, but she used to forget to check the pockets. So all you’d hear was this crunch, crunch, crunch!
In a way, that’s how I see automation. You can automate the ringer as much as you like, but you still have to make sure someone checks the pockets first.
That’s what I think we do in our human relationships. It’s about checking in with people and understanding the context we’re in. Otherwise, we’re just automating a broken process, and I guess that just commits a crime against humans faster.
You’ve worked across ITIL, organizational change, and AI governance. Can you share a client story that changed how you think about the relationship between people, processes, and technology?
Processes don't hold people and technology together; relationships do. Organizations need to look beyond documented workflows and understand the interactions between people, processes, and technology.
I think one of the key facets is organizational change. I started in organizational change a very long time ago, and we’, you’ll often hear people say, “We love innovative people, creative people.” The focus is supposedly all about the people, when really, the focus is actually on the process.
What I’ve observed is that most people think and hope that the process will hold the people and technology together. But the crux still comes back to relationships. Processes are simply how we write those relationships down. We can see the connectivity between relationships through the processes.
If people started looking at processes more as the conversations happening between people, I think we’d get a better outcome. It’s about those interaction points: how people work with processes, how they work with technology, and, importantly, how they interact with each other.
I also think there’s a fourth interaction. With the introduction of AI, a lot of people are looking at humanizing IT itself and humanizing AI. But that isn’t always going to be the best conversation. Again, it comes back to the context of the organization.
One of the greatest lessons I’ve learned is to keep adapting to that context and continually challenge the different lenses and perspectives people bring. We can’t simply accept things by saying, “That’s just the way it is.”
As a consultant, I’m sure you have many customers you work with as opposed to leading IT processes in one company. Do you have any stories on how you evaluate priorities of a company and suggest different frameworks?
Frameworks should be treated as ingredients, not fixed recipes. The key is to understand what an organization can adopt and blend different approaches to suit its needs.
I think the difference really comes down to helping organizations understand that they can actually create their own cocktail.
Many organizations have lots of different frameworks. They’ll have frameworks within HR, finance, technology, and other functions. I think it’s important to look at frameworks as ingredients rather than recipes.
The skill lies in knowing what an organization can actually take on board and how it can adopt those frameworks. Blending frameworks really beats following a single-framework approach all the time.
For example, we have frameworks for knowledge management, service management, integrating across different functions, and organizational change. All of these complement each other in so many ways.
Some organizations might say, “We’re a DevOps shop,” or “We’re focused only on project management.” But that’s not really how organizations work. Even as human beings, we don’t think in just one way. So why would we adopt an approach that only works one way? That doesn’t make sense to me.
When it comes to adopting frameworks, you also have to be mindful of working against the grain of what the organization already has. You can’t get a perfect implementation every time, but that’s part of understanding the organization and helping it learn how to adapt what it already has.
It’s not necessarily about going after the shiny new thing, as one of my other colleagues in the industry likes to call it.
Across 2006, 2016, and 2026, three decades, how has support changed at its core?
Support has evolved through changing tools, frameworks, and ways of working, but people's fundamental needs remain the same. They still need to be heard, understood, and helped.
If we go back 20 years and look at some of the milestones, we had phone and email desks, sort of the ITIL Version 2 era. Moving into 2007, things started evolving into another way of looking at support, but it was still mainly a fix-it function. There wasn’t a lot of forward thinking.
Then, if you think about 10 years ago, we had the original ideas around shift-left, moving knowledge closer to the customer base. We saw more Knowledge-Centred Service adoption and greater use of self-service portals. Other frameworks were still evolving and yet to come. Back then, in our pre-pandemic days, the world was still very much ordered in a traditional way, and that was reflected in how we worked.
Now, when we look at 2026, we’ve come through a pandemic that changed how people think about remote work. Earlier, many thought working remotely would never be a solution. But look at how many hybrid environments we have now and how easily people can work from different locations while still having really good team interactions.
In 2026, we have AI agents, another evolution of ITIL, and what I mentioned earlier as the fourth interaction. We’re now thinking about AI as a participant with its own agency in the work we do.
People haven’t fundamentally changed, but how we live has changed. People still need to be heard, understood, and helped.
I think we can look at it as an evolution in the tools, but not a revolution in the humans, so to speak.
What are the pros and cons of AI?
AI should enhance human creativity and empathy, not take away human responsibility. Without proper guidance and accountability, it risks weakening our ability to think independently
I would probably say that I hope AI won’t take away our responsibility. And that’s on us if that happens. Are we going to hand that over? Is it just another convenient shortcut to save time?
When you think about Frankenstein’s monster, it’s a really good analogy. The monster itself wasn’t the crime, if you like. It was because its creator walked away from it. Once the monster escaped, Frankenstein didn’t do anything about it. He didn’t nurture it or help it learn.
A common literary interpretation is that the doctor abandoned his responsibility. In doing so, he let the monster loose into the world. I don’t know if people would be very comfortable with that.
We know that with emotional AI, empathy is simulated. I would hope that it enhances our ability and understanding of how we use our own empathy.
But there’s a dark side to AI as well. It can become a cognitive parasite. Are we outsourcing our thinking until we lose our ability to think? Are we becoming more lazy? Are we handing over our ability to design, come up with ideas, and create new concepts?
I would prefer to work towards AI becoming more of a modern muse. It should amplify our creativity and capabilities. If we’re nurturing it, as we would do with any child, it needs data, and it needs good data to feed on.
We need to think about the cognitive nutrition side of it. Are we using AI intentionally? Or are we turning our data swamps into something more like an information grove, something we can go and learn from?
Of course, we also hope that it removes some of the drudgery so that we can enjoy doing the things we enjoy more.
When I think about machine humanity, I think the intelligence we’re creating is really the future we’re choosing.
What’s one ITSM trend today that’s genuinely underrated?
Automation and AI should bring knowledge closer to people, not push people out of the workplace. Organizations need to invest in reskilling, upskilling, and inclusive talent development.
I think that, with the natural focus on putting automation and AI at the front end and taking away some of the easier requests and incident issues, we’re missing something important.
The whole idea of shift-left was supposed to move knowledge closer to the people who needed it, whether that’s the client at the front end or the Level 1 person helping them. It was meant to do that, but it wasn’t meant to move the humans out of the building, so to speak.
One of the things that’s been happening is this idea that automation or AI can replace jobs. It does replace tasks. It does replace the way we do things, but it’s not there to replace people. If you cut the people, you cut off your nose to spite your face, and then you end up having to pay a recruiter to find someone new.
There have been a few cases where the people performing the tasks being replaced have been undervalued. We need to reskill and upskill in certain areas as well. There’s a lot that people haven’t looked at.
When we think about what a strong transformation looks like, a lot of that strength comes from good, inclusive talent stewardship. We should be able to spot where AI adoption is widening gaps in confidence and access, and act before we have uneven adoption in the pipeline.
There’s an awful lot we can do around these people-related issues. We still need people who can diagnose problems, redesign capabilities, build human-centred capabilities, and look at workforce dignity and resilience in leadership, particularly when dealing with uncertainty in complex environments.
Thinking that AI is simply going to replace people is very short-sighted.