<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service Management on That Bearded IT Guy</title><link>https://thatbeardeditguy.co.uk/tags/service-management/</link><description>Recent content in Service Management on That Bearded IT Guy</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© 2026 That Bearded IT Guy</copyright><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thatbeardeditguy.co.uk/tags/service-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Sometimes Improving a Process Means Removing Things</title><link>https://thatbeardeditguy.co.uk/blog/sometimesimprovingaprocessmeansremovingthings/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/sometimesimprovingaprocessmeansremovingthings/</guid><description>Why sometimes the best way to improve an IT process is to remove the things that only add unnecessary complexity.</description></item><item><title>From Fixing Problems to Asking Why They Keep Happening</title><link>https://thatbeardeditguy.co.uk/blog/fromfixingproblemstoaskingwhytheykeephappening/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/fromfixingproblemstoaskingwhytheykeephappening/</guid><description>How my thinking has developed from fixing individual issues to looking at the service around them.</description></item><item><title>What I Actually Took Away From ITIL v5</title><link>https://thatbeardeditguy.co.uk/blog/whatiactuallytookawayfromitilv5/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/whatiactuallytookawayfromitilv5/</guid><description>The parts of ITIL v5 that have actually changed how I think about my day-to-day work.</description></item><item><title>Documentation Isn't Just Something You Write After the Work's Complete</title><link>https://thatbeardeditguy.co.uk/blog/documentationisntjustsomethingyouwriteaftertheworkscomplete/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/documentationisntjustsomethingyouwriteaftertheworkscomplete/</guid><description>Why useful, current documentation is part of delivering a good service.</description></item><item><title>What Working in an MSP Has Taught Me About IT</title><link>https://thatbeardeditguy.co.uk/blog/whatworkinginanmsphastaughtmeaboutit/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/whatworkinginanmsphastaughtmeaboutit/</guid><description>What working across multiple customer environments has taught me about support, communication and service.</description></item><item><title>What a Good Escalation Actually Looks Like</title><link>https://thatbeardeditguy.co.uk/blog/whatagoodescalationactuallylookslike/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/whatagoodescalationactuallylookslike/</guid><description>What I try to include when handing a technical issue to another team.</description></item><item><title>The Problem With Just Closing the Ticket</title><link>https://thatbeardeditguy.co.uk/blog/theproblemwithjustclosingtheticket/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/theproblemwithjustclosingtheticket/</guid><description>Why resolving an incident can be useful while still leaving a wider problem worth looking at.</description></item></channel></rss>