<?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/d73ddfabb0554590ac44a2f6d7b58e4f&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d73ddfabb0554590ac44a2f6d7b58e4f-1716882013173.gif</thumbnail_url><duration>245.28</duration><title>Activity burden heatmap</title><description>In this Loom, I discuss the impacts of Project GoLives and the importance of considering all types of impacts. I explain how change management efforts occur before and after the go live, and how we can track these impacts using an activity burden report. I also demonstrate how to use a heat map to visualize the time away from regular work for each division. No action is requested from viewers, but this information is crucial for understanding the impact of projects on our organization.</description></oembed>