<?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/586a601436c645fb89251084213fd569&quot; frameborder=&quot;0&quot; width=&quot;1742&quot; height=&quot;1306&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1306</height><width>1742</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1306</thumbnail_height><thumbnail_width>1742</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/586a601436c645fb89251084213fd569-ff39b8e3ebca1a75.gif</thumbnail_url><duration>219.5302</duration><title>Project Configuration and Connections Overview 🔗</title><description>In this video, I walk you through a sample configuration involving three projects: the Dealership Project, which hosts Opportunities and Risks, and two team projects focused on solutions and experiments. I explain how to connect solutions to opportunities and opportunities to risks, emphasizing the importance of defining opportunities once and linking them through a global connection field. I also discuss the option of creating a fourth project for company-level OKRs or integrating them into existing team projects. Please consider how you might implement this structure in your own work.</description></oembed>