<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ITSM and ITIL on ESM Guide</title><link>https://esm-guide.com/en/categories/itsm-and-itil/</link><description>Recent content in ITSM and ITIL on ESM Guide</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 21 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://esm-guide.com/en/categories/itsm-and-itil/index.xml" rel="self" type="application/rss+xml"/><item><title>Incident and problem management: stop confusing them</title><link>https://esm-guide.com/en/blog/incident-management-vs-problem-management/</link><pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/incident-management-vs-problem-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;An incident is measured in time to restore, a problem in incidents avoided.&lt;/li&gt;&#10;&lt;li&gt;A workaround closes an incident but never closes a problem.&lt;/li&gt;&#10;&lt;li&gt;Grouping recurring incidents is the main entry signal for problem management.&lt;/li&gt;&#10;&lt;li&gt;A known error is a problem with an identified cause and a documented workaround, ahead of the permanent fix.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="two-practices-two-clocks"&gt;Two practices, two clocks&lt;/h2&gt;&#10;&lt;p&gt;An &lt;strong&gt;incident&lt;/strong&gt; is an unplanned interruption to a service or a reduction in its quality. The associated practice pursues one objective: restore service as quickly as possible. Restart, fail over, reassign a licence, the means hardly matter, including when they fix nothing fundamental.&lt;/p&gt;</description></item><item><title>ITIL 4: the 7 guiding principles explained</title><link>https://esm-guide.com/en/blog/itil-4-guiding-principles/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/itil-4-guiding-principles/</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;ITIL 4, published in 2019, places seven guiding principles ahead of its 34 management practices.&lt;/li&gt;&#10;&lt;li&gt;These principles are rules of conduct, not processes to execute: they exist to arbitrate, not to run.&lt;/li&gt;&#10;&lt;li&gt;Three of them, start where you are, keep it simple and progress iteratively, are enough to frame most projects.&lt;/li&gt;&#10;&lt;li&gt;The framework cannot certify an organisation: that certification falls under the ISO/IEC 20000 standard.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="why-itil-4-starts-with-principles"&gt;Why ITIL 4 starts with principles&lt;/h2&gt;&#10;&lt;p&gt;Earlier ITIL versions mostly described processes. ITIL 4 reverses the order and sets out seven &lt;strong&gt;guiding principles&lt;/strong&gt;, valid in any context, before going into practice detail. The intent is explicit: avoid the mechanical application of a procedure catalogue to an organisation whose actual maturity nobody has examined.&lt;/p&gt;</description></item></channel></rss>