<?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/668e70bb4c4e49d5aa197930c1971cf9&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/668e70bb4c4e49d5aa197930c1971cf9-14003f0796348592.gif</thumbnail_url><duration>50.75</duration><title>The 150 Model: A Strategy for Effective Product Testing 🚀</title><description>In this video, I introduce the 150 model for transitioning from beta to GA, emphasizing the importance of shipping working code internally first. The &apos;1&apos; represents our internal organization where we can quickly test prototypes, the &apos;5&apos; stands for a select group of friendly customers who help us identify usability issues and adoption blockers, and the &apos;50&apos; signifies scaling our testing efforts. This approach allows us to gather real data and discover potential blockers early, ultimately saving us time and resources. I encourage you all to consider implementing this model in our upcoming projects to enhance our product development process.</description></oembed>