<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Processes on ESM Guide</title><link>https://esm-guide.com/en/tags/processes/</link><description>Recent content in Processes on ESM Guide</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 14 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://esm-guide.com/en/tags/processes/index.xml" rel="self" type="application/rss+xml"/><item><title>ESM vs ITSM: what actually changes</title><link>https://esm-guide.com/en/blog/esm-vs-itsm-differences/</link><pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/esm-vs-itsm-differences/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;ITSM and ESM rest on the same objects: service catalogue, ticket, priority, turnaround commitment, knowledge base.&lt;/li&gt;&#10;&lt;li&gt;The only structural difference is scope: IT for ITSM, every support function for ESM.&lt;/li&gt;&#10;&lt;li&gt;Moving from one to the other is a governance project, not a technical one.&lt;/li&gt;&#10;&lt;li&gt;Three technical capabilities gate the transition: multiple catalogues, multiple assignment queues, partitioned access rights.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="two-acronyms-one-mechanism"&gt;Two acronyms, one mechanism&lt;/h2&gt;&#10;&lt;p&gt;&lt;strong&gt;ITSM&lt;/strong&gt; organises the services delivered by the IT department. &lt;strong&gt;ESM&lt;/strong&gt; applies the same reasoning to every function delivering an internal service. The building blocks are identical: describe a service, open a channel to request it, assign the request to someone, commit to a deadline, measure.&lt;/p&gt;</description></item><item><title>Enterprise Service Management: definition and scope</title><link>https://esm-guide.com/en/blog/what-is-enterprise-service-management/</link><pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/what-is-enterprise-service-management/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;ESM applies to non-IT departments the service management practices born in IT: catalogue, request portal, workflows and measured turnaround times.&lt;/li&gt;&#10;&lt;li&gt;The four functions most often involved are human resources, facilities, finance and legal.&lt;/li&gt;&#10;&lt;li&gt;An ESM initiative is not a tool purchase: it starts with a written service catalogue and its committed turnaround times.&lt;/li&gt;&#10;&lt;li&gt;The ITIL 4 framework describes 34 management practices, a large majority of which apply as-is outside the IT perimeter.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="what-enterprise-service-management-covers"&gt;What Enterprise Service Management covers&lt;/h2&gt;&#10;&lt;p&gt;&lt;strong&gt;Enterprise Service Management&lt;/strong&gt; means applying, across the whole organisation, the service management principles formalised in IT since the 1990s. The reasoning is straightforward: a badge request sent to facilities and a password reset sent to IT raise exactly the same organisational problem. Who receives it, within what deadline, following which procedure, and how does the requester track progress.&lt;/p&gt;</description></item></channel></rss>