https://esm-guide.com/en/tags/governance/Recent content in Governance on ESM GuideHugoen-USWed, 19 Aug 2026 00:00:00 +0000https://esm-guide.com/en/blog/itil-4-guiding-principles/Wed, 19 Aug 2026 00:00:00 +0000https://esm-guide.com/en/blog/itil-4-guiding-principles/<blockquote> <p><strong>In short:</strong></p> <ol> <li>ITIL 4, published in 2019, places seven guiding principles ahead of its 34 management practices.</li> <li>These principles are rules of conduct, not processes to execute: they exist to arbitrate, not to run.</li> <li>Three of them, start where you are, keep it simple and progress iteratively, are enough to frame most projects.</li> <li>The framework cannot certify an organisation: that certification falls under the ISO/IEC 20000 standard.</li> </ol> </blockquote> <h2 id="why-itil-4-starts-with-principles">Why ITIL 4 starts with principles</h2> <p>Earlier ITIL versions mostly described processes. ITIL 4 reverses the order and sets out seven <strong>guiding principles</strong>, 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.</p>https://esm-guide.com/en/blog/esm-vs-itsm-differences/Fri, 14 Aug 2026 00:00:00 +0000https://esm-guide.com/en/blog/esm-vs-itsm-differences/<blockquote> <p><strong>In short:</strong></p> <ol> <li>ITSM and ESM rest on the same objects: service catalogue, ticket, priority, turnaround commitment, knowledge base.</li> <li>The only structural difference is scope: IT for ITSM, every support function for ESM.</li> <li>Moving from one to the other is a governance project, not a technical one.</li> <li>Three technical capabilities gate the transition: multiple catalogues, multiple assignment queues, partitioned access rights.</li> </ol> </blockquote> <h2 id="two-acronyms-one-mechanism">Two acronyms, one mechanism</h2> <p><strong>ITSM</strong> organises the services delivered by the IT department. <strong>ESM</strong> 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.</p>