ITSM26 Recap: AIOps, Toblerones, and Moments Of Joy

ITSM26 conference venue shown as an aerial view of MK One Stadium at sunset, with event signage on the roof and bursts of painted color

Summary

ITSM26, the itSMF UK annual conference held at MK One Stadium, brought together over five hundred delegates across four presentation workstreams, and this recap by Vawns Murphy covers twelve of its sessions. The speakers argued that automation does not remove the need to look after people, and that organizations should adapt frameworks such as ITIL to their needs instead of adopting them whole. Their practical advice centers on small, visible steps, including improving one service at a time, making ownership explicit across handoffs, and putting AI governance in place first. Other sessions covered digital employee experience, coaching for new roles, building trust across teams through enterprise service management, and measuring culture with culture performance indicators.

It’s Milton Keynes, baby! itSMF UK held its annual conference at MK One Stadium this week (ITSM26). The conference drew over five hundred delegates and featured the usual four presentation workstreams, packed with exciting content. 

The itSMF UK conference

What I love about the itSMF UK conference is the sense of community, enthusiasm, and joy. Everyone gathers to learn new things, share ideas and see new ways of working.

In this article, I’ll take you through some of the highlights, including top tips, practical advice, and hard-won insights from the presenters.

ITSM26 #1 The ITSM landscape may be changing, but it’s the people that will make it work – Claire Drake, itSMF UK

The ITSM26 conference opened with the reigning queen of itSMF UK, Claire Drake. Claire started us off by asking the question, “The technology is changing, but are we changing along with it? If our services are self-managing, self-healing and self-delivering, what exactly are we managing? These are the conversations and questions that will shape the next 10 years of ITSM.”

She continued by saying that, no matter how automated the service, we still need to look after our people and deliver value, and she made the case for the next iteration of ITSM being less about managing processes and more about orchestrating outcomes.

No one has all the answers – that’s why communities like this are so important, so we can figure it out together. The future of our industry isn’t technology; it’s the people who deliver it, run it, and make sure it looks after the needs of the people we’re looking after.

ITSM26 #2 Reframing will help with resilience – Felicity Ashley

The Monday ITSM26 keynote focused on resilience. Felicity opened by talking about the importance of mindset, reminding us all that our mind can be a weapon or a weakness, so it’s important to make it work with us rather than against us.

One way we can do this is by using our superpowers. We all have them, and we’re all different. For Felicity, her superpower is being as hard as nails – she has survived a hip replacement, cancer, and has gone on to row across the Atlantic and run marathons at the Mount Everest base camp, raising thousands of pounds for charity.

The keynote explored how reframing can move us from reacting to responding, and from limiting beliefs to limitless opportunities. Felicity talked about the importance of believing in our people because if we believe in the people around us, they start to believe in themselves.

She continued by talking about the importance of finding your “why” so you can use it as an anchor when facing difficult situations. My favorite part about Felicity’s keynote was the resilience grab bag. Here’s what hers contains:

  • Know your superpower
  • Reframe not why me to why not me?
  • Know your why and expect it to change over time
  • Chocolate because small moments of joy matter.

ITSM26 #3 Change is changing, but we still need to enable and protect live services – Marida Lotz-Henning, Computacenter

Marida’s ITSM26 session explored how change enablement has evolved alongside increasing technology complexity, cloud adoption, microservices, automation, and artificial intelligence (AI).

The reality is, no matter what version of ITIL we’re on or how fancy the technology, change enablement is still about delivering change while protecting live services. Marida talked about the importance of proportionate governance, ensuring controls reflect each change’s risk rather than creating unnecessary administration. Key measures of change enablement include throughput, record quality, timings, results, and communication.

Her key messages were to:

  • Focus on collaboration rather than control
  • Reduce the noise by automating routine changes
  • Involve change teams earlier in project activity
  • Don’t panic about AI – start where you are, take an incremental approach to improvement and build your AI capabilities over time (this way you know they’re safe and work for your organization).

ITSM26 #4 We need to get things right at the design stage – Karen Brusch, Mastercard

Karen’s ITSM26 session explored how service design is essential to successful product management.

The key message was that service design needs to take a holistic approach, bringing together product strategy, development, and ongoing service management, with a clear understanding of how customers actually use products and services.

Karen suggested that rather than following frameworks such as ITIL or COBIT blindly, organizations should adapt them to their needs and engage service design teams early, from the initial idea stage.

The session also highlighted how an agile, iterative approach can make service design more effective at scale, building service requirements and design packages incrementally through sprints rather than trying to complete everything upfront.

One of my favorite parts of Karen’s session was this:

“At the end of each sprint there’s something. It might only be a small release, but you will still have made progress – we need to work in a more piecemeal way to enable rapid progress.”

Ultimately, service design is about engaging with people. If we do that, we can build stronger relationships with product teams and support faster, more collaborative delivery leading to better products and customer experience.

ITSM26 #5 We need to stop dropping the baton (and blaming our supplier doesn’t work) – Claire Agutter, Scopism

Claire opened by talking about the need to fix incident ping-pong. We’ve all seen it, but let’s be real – the end customer doesn’t care whose fault it is or which supplier is affected; they just want their issue fixed.

Claire talked about how service integration and management (SIAM) can help tackle the complexity of multi-supplier environments, and how getting involved and asking the right questions early can save a lot of heartache down the line.

Claire used the Toblerone model to show how SIAM can clarify ownership, simplify handoffs and reduce incident ping-pong, while working with our teams to understand how our complexity and interfaces work together, reducing future risk and interface debt.

Some of the practical advice included:

  • We need to look at our interfaces and figure out  how they collaborate and work together
  • SIAM can help us identify those interfaces with support gaps (and we all have them) and put the right shared measures in place to look after them. These include end-to-end AI governance and continual improvement
  • Look for scope for errors, such as swivel-chair processes and double keying; talk to people; and do some process mining. If you start with something that hurts, the results you get will give you buy in for next steps
  • Make ownership explicit – think about the accountability and if it needs to move, and don’t confuse assigning a ticket with transferring responsibility
  • Agree the rules of exchange – we’ve identified these high-friction scenarios; let’s look at the contract to see how we can collaborate so we can make everyone’s life easier
  • Manage the gaps as well as the athletes – stop managing the silos; focus on the end-to-end service
  • Practice your handovers – this isn’t a paper exercise; it needs to become muscle memory and will pick up anything you’ve missed
  • Win your race – SIAM doesn’t have to be a huge project, doing small simple steps can make a real difference.

The key message was to focus on the end-to-end service rather than individual silos, talking to people and making incremental improvements that reduce toil, rework and stress.

ITSM26 #6 Good experiences are being able to work freely without interruption – Barclay Rae and Ian Aitchison, BRC Associates

Barclay opened this ITSM26 session by explaining that digital employee experience (DEX) is understanding and improving the effectiveness of technology that enables people to be successful in their work. It’s not about sending satisfaction surveys, turning SLA satisfaction metrics into XLAs, or fast outage communications.

The reality is that a good digital experience isn’t complicated. It’s about being able to work freely without interruption, and DEX is an experience that is helpful, supportive

 and uncluttered.

DEX principles:

  1. People shouldn’t be sensors.
  2. People don’t want to contact IT (hard relate Ian)
  3. We don’t need another hero
  4. We don’t exist to make our users happy.
  5. Time is the currency of DEX.

Ian continued by explaining DEX activities, which include:

  • Collecting data so you can show improvement over time
  • Avoiding things that can cause issues, e.g. rebooting your laptop once a week
  • Detecting and monitoring performance so we can understand issues earlier
  • Remediating – taking the appropriate action to fix things at the source
  • Communicating – letting the colleague know what’s broken and automatically fixing it
  • Integrating – and knowing our edge points
  • Automating – the glue that ties these stories together
  • Informing – we need to communicate in a helpful way
  • Improving – can be used to leverage the relationship.

DEX enables IT to move from a reactive to proactive support model as creating DEX teams means moving your people into more productive roles. The DEX roadmap helps you sort out what you do in the future, and time helps you get there.

ITSM26 #7 GenAI plus Observability = proactive incident management – Anushka Odedra and Lavender Bansal, Barclays 

Anushka and Lavender explored how organizations move to a more proactive incident response model by combining AI with observability.

They opened the session by talking about the fact that we’re surrounded by information, but that doesn’t give us insights – and that’s the thing. We can have all the data points in the world, but without context, it’s just noise that doesn’t help anyone.

One reason AI can be a gamechanger is that it can collect this information more efficiently and reduce risk. But here’s the thing: even with greater accuracy, that’s not the whole story. Enter observability.

Observability can enhance monitoring by providing more context at the service layer. It can improve incident and problem management by enabling us to ask more proactive questions.

Observability platforms can provide real-time insights into technology services, enabling AI to detect, respond to, understand, improve and prevent incidents. We all know that quality data = quality AI output, and observability platforms can help with that.

Some examples include:

  • Automated log analysis
  • Identifying recurring patterns
  • Predictive trend identification
  • Root cause analysis.

Controls of AI and observability include:

When getting started, Anushka and Lavender advised:

  • Governance first
  • Standardize for consistency
  • Validate and trust
  • Collaborate and scale.

ITSM26 #8 Coaching is the best thing you can do for people starting a new role – Akshay Anand, Mars

Akshay’s ITSM26 session investigated the challenges of transitioning into new roles and highlighted how important the people aspect is.

He started by saying past performance isn’t an indicator of future success. Instead, the question is – what are you prepared to start and stop doing in order to level up?

Akshay continued by saying coaching is the best thing we can do for people starting in a new role. Explaining that we need to have a dedicated coaching program rather than relying on social dynamics to guide someone through the workplace. When changing roles, there is often a “transition tax,” and it looks like this:

  • Who do I have to become to succeed in this role?
  • Is my expertise portable? What skills are transferable, translated, or trivialized?
  • How do I recalibrate my network? Networks change, and you will speak to different people over time.
  • How and where can I exert influence?
  • What new skills will I need?

Key takeaways:

  • Understand what you need to start / stop doing. Ask leaders about their role transitions and ask for their advice.
  • Take on a safe to fail project to build confidence and skills.
  • Start journaling to develop your ambitions
  • Only you are accountable for your success

#9 Trust is everything – Alex Cosma , Square Enix

Alex started her ITSM26 session by asking the question, why does Enterprise Service Management matter now? It’s an opportunity to grow our service ecosystem and have more conversations. ESM is one service supporting multiple teams, and given that AI is only as good as the information it is fed, ESM can ensure that it is a single, trusted source of the truth. The conversation should be noticing the gaps in experience so we can fix the end to end service. Why is this important? We can be guilty of working in silos – where each team sees their individual part of the system, the end users sees the end to end service.

Some practical tips include:

  • Leading is not the same as deciding. You can lead the conversation without owning the problem.
  • Stop defending solutions. Start testing needs. What must work? What can change? Who decides? What evidence can help?
  • Notice, challenge, and enable. See the whole service, the end-to-end journey. Test your assumptions and discuss solutions. Enable your people to agree on what happens next.
  • See the whole service, not just your team’s part. The earlier you see the dependency, the cheaper the conversation.
  • Build trust before you need a favor. Listen first, be useful, do what you say, and share credit. The worst time to build a relationship is the moment you desperately need something.
  • Challenge and use critical thinking. Do we agree on the problem? Challenge your team, challenge the assumption. What do we know, and what are we still assuming? Let’s have a conversation.
  • When someone says no, it’s data, and we can find out the reason behind it. It could be differing views, priorities, risk appetite, or authority. Understand the reason, adjust the proposal, involve others, or accept the decision.
  • Help the right people agree on what happens next. Agree on actions, ownership, timings, and follow-ups. Relationships create willingness; structure turns willingness into delivery.
  • Imperfect still works. Imperfection is not the opposite of success. Launch is the foundation, not the finish line.
  •  An imperfect launch can be a good foundation if: the risk is visible, decisions are clear, people can act together, and what is deferred is agreed then improved after launch.
  • When does helping become owning? Help within boundaries (what am I helping with, who owns it afterward, when do I step back?), convene, and integrate. Leave each decision with its delegated owner.

ITSM26 #10 We need to get better at making things simple – Neil Burrell and Gary Mulqueen, MOD

Gary and Neil’s ITSM26 session began by reminding us that complexity can be overwhelming and there absolutely has to be a better way of doing this.

We can all agree that ITIL, has stayed relevant, but we don’t have to do it all. It’s a toolbox, and we can pick and chose what parts can help our organization rather than trying to do the whole thing and, in Gary’s words, “over egg every available pudding. Instead, it’s much more sensible to add proven ITSM practices that will be helpful than to create the entire book verbatim, because our service ecosystems need to grow, generate and flux with the flow around them. It’s also important to be careful with templates because they can force the wrong priorities, if all people can see is the process rather than the output.”

Neil continued by talking about how service ecosystems work in a defense environment, explaining, “We don’t stop using ITSM just because we’re being shot at; it’s just incident management is a radio message from the edge of a battleground to the next level rather than processes and portals.”

What can work well with operational ITSM ecosystems:

  • Adapt proven ITSM practices to fit your organization
  • What you already do is key
  • Flexibility and adaptability are key
  • Required vs. developed, don’t do things for the sake of them. Ask the question, does that demand help you deliver the required value?

In summary:

  • Flexibility and adaptability are critical
  • Different isn’t wrong
  • Operational ecosystems evolve on need, not templates
  • Organizations work together to deliver ITSM
  • ITSM should deliver complexity via simplicity.

ITSM26 #11 Iterative change can help you win service delivery – Karl Lucas, Department for Transport

Karl opened his ITSM26 session by reminding us that we need to keep pace with rising demand; otherwise, we’re just standing still, and we can do this by making our change practices iterative.

Why iterative change wins:

  • Small blast radius
  • Fast feedback
  • Gains compound
  • The team owns it
  • No cutover to fear
  • Self-reinforcing.

The three foundations for iterative change are culture, time, and data. By allowing people to try new things, we move forward.

The start-on-Monday list:

  • Pick one service
  • Agree on the baseline
  • Create the time
  • Set the guardrails
  • Ship one change
  • Make the win visible
  • Do one thing, get it done. Be proud of it, announce it, and make it visible.

In summary:

  • Iterative change is a team game
  • Give people time to invest in learning and improvements
  • The team is the engine; listen and support their ideas
  • Same people, more output, reinvesting time
  • Small wins reinforce themselves.

ITSM26 #12 CPIs can up your game – Nigel Murphy, Fujitsu

The final ITSM26 session I attended was on Culture Performance Indicators or CPIs.

And why is culture so important? In Nigel’s words, “it eats strategy for breakfast.”

ITIL, COBIT, and VeriSM all have slightly different definitions of culture, but they all reference getting work done. Culture is so important.

One of Nigel’s favorite explanations of how culture can impact service delivery is that some languages don’t have a word for “no.” The Irish language doesn’t have a direct word for no – what we do instead is repeat back the negative form of the word used in the question.

I get that not many people will experience IT troubleshooting in Irish, but it spills over into English, too. Possibly one of my favorite moments of the afternoon is Nigel explaining what “I will, yeah” means as an Irish person. Spoiler alert to every other nationality – it means no! But unless you’re Irish (or have lots of Irish friends), you’re not going to know this, and suddenly major incident management can get a lot more complicated.

Some practical examples of CPIs:

  • Velocity CPIs: Average response time to emails and chat messages. Lead time to approve/reject a business case or initiative. Average response time to customer queries, complaints or RFPs.
  • Collaboration CPIs: Percentage of employees assigned a mentor. Presence of diverse, equitable representation in cross-functional teams and projects. Response rate to requests for assistance from colleagues and customer stakeholders (collaboration requests).
  • Engagement CPIs: HR analytics on training participation and the percentage of employees undertaking professional development (PD) activities. Number of active members in Teams channels or equivalent forums. Innovation and idea contribution (aligned to strategic priorities) and percentage of ideas implemented. Percentage of time employees spend on independent side projects and improvements.
  • Experience CPIs: eNPS – derived from Pulse surveys, including DEX and Employee and Customer Effort Scores (CES). Retention, turnover rates, internal mobility, and percentage of positions filled by internal candidates. CSAT and NPS, with a focus on People, Technology, and Process elements.

Culture roadmaps matter because they help with course corrections. Sometimes the smallest changes can avert disaster, and the earlier the better.

Final thoughts:

  • AI is upending how employees and customers experience culture
  • Culture can be course-corrected
  • Culture should be linked to strategy
  • Culture is a value stream
  • Prioritize Cultural Intelligence (CQ) to improve Cultural Experience
  • Target Velocity as a leading indicator
  • Balance CPIs – don’t just measure experience.

If people feel supported and encouraged to use AI, they will feel more comfortable using it, more benefits will be realized, and the culture will improve.

Feel free to add to this

That’s my take on ITSM26. What did you think? Please let me know in the comments.

FAQs

What was ITSM26?

It was itSMF UK’s annual conference, held at MK One Stadium in Milton Keynes. It drew over five hundred delegates and ran the usual four presentation workstreams, with the opening keynote from itSMF UK’s Claire Drake on why the people running ITSM matter more as services become automated.

What is the Toblerone model, and how does it reduce incident ping-pong?

Claire Agutter of Scopism used it to show how service integration and management (SIAM) clarifies ownership, simplifies handoffs, and reduces ping-pong across multi-supplier environments, while exposing complexity and interface debt. Her practical advice included making ownership explicit, because assigning a ticket isn’t the same as transferring responsibility, agreeing rules of exchange with suppliers, managing the gaps between teams rather than the silos, and practicing handovers until they become muscle memory.

What is digital employee experience (DEX)?

Barclay Rae of BRC Associates defined it as understanding and improving the effectiveness of technology that enables people to succeed at work. It isn’t about satisfaction surveys, turning SLA metrics into XLAs, or fast outage communications. Ian Aitchison’s five principles are that people shouldn’t be sensors, people don’t want to contact IT, we don’t need another hero, we don’t exist to make users happy, and time is the currency of DEX. He added that DEX moves IT from reactive to proactive support.

How can generative AI and observability work together on incidents?

Anushka Odedra and Lavender Bansal of Barclays argued that data without context is just noise, and observability supplies the context at the service layer that AI needs to detect, respond to, understand, and prevent incidents. Examples include automated log analysis, recurring pattern identification, predictive trends, and root cause analysis. Their advice for getting started was governance first, standardize for consistency, validate and trust, then collaborate and scale.

What are culture performance indicators (CPIs)?

Nigel Murphy of Fujitsu described CPIs as measures of culture grouped into four types: velocity (such as response times and approval lead times), collaboration (such as the percentage of employees with a mentor), engagement (such as training participation and ideas implemented), and experience (such as eNPS, retention, and effort scores). He urged balancing them rather than measuring experience alone, and linking culture to strategy.

How can a team start making change iterative?

Karl Lucas of the Department for Transport built the case on small blast radius, fast feedback, and compounding gains, resting on three foundations: culture, time, and data. His start-on-Monday list is to pick one service, agree the baseline, create the time, set the guardrails, ship one change, and make the win visible.

Vawns Murphy Photo
Vawns Murphy
Senior ITSM Consultant at Logiq

Vawns Murphy holds qualifications in ITIL V2 Manager (red badge) and ITIL V3 Expert (purple badge), and also has an SDI Managers certificate. Plus she holds further qualifications in COBIT, ISO 20000, SAM, PRINCE2, and Microsoft. In addition, she is an author of itSMF UK collateral on Service Transition, Software Asset Management, Problem Management and the "How to do CCRM" book. She was also a reviewer for the Service Transition ITIL 3 2011 publication.

In addition to her day job as a Senior ITSM Consultant at Logiq, she is also an Associate Analyst at ITSM.tools.

Want ITSM best practice and advice delivered directly to your inbox? Why not sign up for our newsletter? This way you won't miss any of the latest ITSM tips and tricks.

nl subscribe strip imgage

More Topics to Explore

Leave a Reply

Your email address will not be published. Required fields are marked *