We were launching a new health feature and I needed alignment from design, engineering, and legal. I set up a weekly sync, created a shared tracker, and made sure everyone had visibility into dependencies. Legal had some concerns about data language in the UI, so I connected them with the design team directly and they worked it out. Engineering had timeline pressure so I helped reprioritize the sprint. We launched on schedule and the feature shipped without any compliance issues. It was really about keeping everyone informed and making sure communication channels were open.
We were six weeks from a Health feature cutoff when design and legal reached a hard impasse. Design wanted persistent on-screen health context; legal said that language created a regulated medical-device risk. Neither team would move and engineering had already frozen the scope. I mapped exactly what each function needed to protect — design needed continuity of experience, legal needed a clean regulatory boundary. I proposed a single architecture change: surface the data in a passive ambient display that explicitly disclaimed diagnostic intent. I wrote the framing document, ran it past legal counsel directly, got design sign-off on the interaction model, and brought engineering a revised spec with a two-day delta on the schedule. We shipped on time. Zero compliance flags post-launch.