<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/47acdfeabb0e4fc381115f68c2f37ede&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/47acdfeabb0e4fc381115f68c2f37ede-2771a5397a0075dc.gif</thumbnail_url><duration>416.92</duration><title>Start Where You Are: The Second ITIL 4 Guiding Principle, in Practice</title><description>This Loom explains how to apply ITIL 4 Guiding Principle 2, Start Where You Are, to avoid failed, radical ITIL implementations. The author criticizes organizations that begin with consulting-led pilots and then face live implementation fiascos, and instead recommends taking a measured approach by assessing tools and current conditions. They demonstrate an open-source, deterministic Python app that ingests a CSV of ticket data, generates an executive summary and 30-, 60-, 90-day roadmap, and purges data after 30 minutes. Example outputs include analysis of 360 service requests over 90 days, deflection and MTTR trends, and findings like median approvals and workflow at 92 hours.</description></oembed>