<?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/ef4d909f4d5f422ba6dc4360f4af3664&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/ef4d909f4d5f422ba6dc4360f4af3664-f236351f7dabe5d8.gif</thumbnail_url><duration>4736.21</duration><title>Designing an Effective Bug Reporting Workflow 🐞</title><description>In this video, I walk you through our bug reporting process, highlighting key decision points such as identifying the game, assessing bug severity, and determining if follow-up is needed. I emphasize the importance of allowing users to describe bugs in their own words rather than forcing structured responses, as this increases completion rates. I also outline the tools involved, primarily Google Sheets and Gmail, and explain how we can automate parts of this workflow using AI. Finally, I encourage you to think about how we can design a more efficient workflow together and ask you to take 15 minutes to brainstorm ideas.</description></oembed>