Cross-functional delivery
Creating launch clarity across a complex multi-brand rollout
Two brands were approaching launch. Hundreds of UAT findings were moving between Engineering, Design, QA, and Product. The constraint was no longer only fixing issues—it was getting the right answer to the right person quickly enough.
- Cross-functional delivery
- Decision systems
- Launch leadership
Answers had become a delivery dependency.
During a broader GM brand-platform initiative, Buick and GMC were being built in parallel while more than 700 UAT findings across the programme needed resolution, validation, or clarification. Many findings depended on newly introduced brand requirements. Engineers were trying to fix issues while repeatedly seeking answers from Design, Product, and QA, making communication itself a delivery constraint.
Make the route to clarity visible.
Gaurav introduced an asynchronous clarification queue, shared dashboards, explicit ownership, and response SLAs. Live triage remained available for true blockers instead of becoming the default path for every question.
Keep progress moving without losing context.
Engineering could park items that needed more understanding and continue with actionable work. Design, Product, and QA could answer the questions routed to them from one shared view.
- 01Reported
- 02Needs clarification
- 03Ready
- 04Fixed
- 05Verified
Leadership principleCoordination is part of the delivery system. When the route to a decision is visible, specialists can contribute without every dependency becoming a meeting.










