{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/f2136c07e3ab4ff6965d53031ddde753\" 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/f2136c07e3ab4ff6965d53031ddde753-e4dfccc741b51141.gif","duration":276.928,"title":"Conduit Walkthrough","description":"This Loom explains Conduit, a program built to unify a fragmented multifamily solar pipeline. The author describes how nine teams previously tracked projects in nine separate spreadsheets with no shared source of truth and lost handoffs via email, and shares an end to end rollout run in Jira across eight epics. In Salesforce, the system moves projects through a Kanban pipeline and automatically restamps stage entry dates and creates handoff tasks, while blocking invalid transitions (for example, pushing to design before the site survey is done). It also consolidates conflicting data sources into one deduplicated, reconciled dataset and provides leadership visibility through capacity by stage, average time in stage, at-risk project views, and a weighted forecast. The implementation was managed with full JIRA lifecycle, decision logs, a risk register, and user acceptance testing, including fixing and retesting a defect to closure."}