Cox Automotive · Portfolio Visibility
Improved portfolio visibility by giving teams and leadership a shared lens for delivery health, blockers and support needs.
Context
Cox Automotive operated across multiple acquired products and teams, with different role models, delivery practices and reporting habits. Some teams had Scrum Masters, some had Technical Delivery Managers and some had Agile Delivery Managers, which made portfolio comparison difficult.
Challenge
Teams were often solving issues locally, but systemic delivery pain points were harder for leadership to see. The portfolio needed a consistent way to discuss throughput trends, release regularity, recurring blockers and where support was needed without forcing every team into the same process.
What I changed
- Introduced a lightweight portfolio view that made delivery signals easier to compare across teams with different histories and operating models.
- Used indicators such as throughput, release reliability, release regularity, recurring blockers and visible team pain points to support practical leadership conversations.
- Helped teams move from quietly “just fixing things” towards surfacing patterns that needed wider support or decision-making.
- Used historical Azure DevOps data in one example to support Monte Carlo probabilistic forecasting, shifting conversations from fixed-date certainty towards confidence-based planning.
Impact
Leadership had a clearer view of where delivery was healthy, where pressure was building and where teams needed support. The work improved the quality of portfolio conversations without pretending that every team could be measured identically.
Evidence / indicators
- Portfolio discussions could be framed around consistent delivery signals rather than disconnected status updates.
- Recurring blockers and team pain points became easier to describe and escalate.
- The Monte Carlo example used around 12 weeks of completed work data from a stable team period to support confidence-based forecasting.
Visual support
Demonstrative portfolio signal matrix
Portfolio examples are generalised for public use and avoid naming internal teams, individuals, programmes or sensitive commercial detail.