{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/ef4d909f4d5f422ba6dc4360f4af3664\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/ef4d909f4d5f422ba6dc4360f4af3664-f236351f7dabe5d8.gif","duration":4736.21,"title":"Designing an Effective Bug Reporting Workflow 🐞","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."}