<?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/cffbb68d35b14ecaac9c62b8c2269e91&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/cffbb68d35b14ecaac9c62b8c2269e91-b3ee5051cc9a88cd.gif</thumbnail_url><duration>2667.967</duration><title>How to Better Understand Feature Function for  User Testing </title><description>In this video, I discuss various design elements and decision-making processes related to our project. Key points include differences in ticket functionalities, the creation of AI action plans, and the challenge of combining design elements. I seek feedback on ticket versions and the execution plan, emphasizing the importance of clarity and user-centric design. Your input on feature-related information and usability testing tasks is crucial for our progress. Please review the video for detailed insights and action points.</description></oembed>