Delivery Lead

Hartford, Connecticut

The Delivery Lead is accountable for the end‑to‑end delivery of business solutions and understands the strategy, needs, and challenges of the business s/he supports, as well as the associated end‑to‑end processes. Oversees all products supporting that customer group to make sure service levels are received and system changes are delivered to expectations. Accountable for the design, delivery, and support of solutions.

In a Platform Enablement context, the Delivery Lead is accountable not only for direct delivery, but for enabling predictable, high‑quality execution across multiple platform teams. This includes providing dedicated execution capacity, delivery coaching, acceleration support, and structured demand absorption to reduce dependency on ad‑hoc or volunteer‑based contributions.

This role does not own engineering standards, tooling definitions, or competency frameworks, which remain under the accountability of the Engineering Chapter. The Delivery Lead partners closely with Chapter Leads to make sure pragmatic adoption of standards through execution, without redefining or governing those standards.

• Establish, develop and maintain close collaboration and partnership with Business stakeholders, Technology Transformation Functions and key strategic partners/vendors
• Facilitate coordination among various teams within the delivery process, ensuring that work items are prioritized and completed in alignment with the delivery timeline. Holds team and partners/vendors accountable for delivering the appropriate business outcomes as per the business transformation roadmap
• Holds end‑to‑end accountability for technical delivery, including coordination of vendors, SI partners, and integration teams
• Produce and maintain the technical delivery roadmap for the assigned portfolio/domain/segment
• Hands‑on role in managing operational aspects of delivery, such as resource allocation, workload balancing, and addressing immediate roadblocks. Assess team performance and productivity, identifying areas for improvement and implementing changes to optimize delivery processes
• Develop change management strategies and approaches and assist business partners with readiness and change implementation
• Facilitate cross‑domain ceremonies and synchronisation events across Teams of Teams
• Establish and communicate the Agile cadence/calendar of events and ensure reporting of Key Performance Indicators (KPI) on the delivery/products
• Drive improvements of ways of working via periodic synchronization events (e.g. PO Sync, Scrum of Scrums, Retrospectives to ensure cross stream alignment, progress / improvement on agile ways of working as a community of practice)
• Owns the Platform Enablement execution model, ensuring reliable delivery support to platform teams without centralizing product ownership
• Distinguishes clearly between BAU, transformation initiatives, and enablement‑driven execution to ensure focus and cost transparency
• Acts as an execution partner to Platform Foundations (architecture, standards, engineering practices), ensuring pragmatic adoption through delivery
• Works in close partnership with Engineering Chapter Leads to operationalize standards and practices through delivery
• Does not define or govern engineering standards, coding practices, or career frameworks

• Establish the scope of services, service levels, and key processes required to deliver application services within the application portfolio/domain/segment
• Accountable for managing the stability and performance of the products responsible for
• Holds accountability for resolution of user incidents/issues within the agreed response and resolution SLA’s
• Manages the BAU/Breakfix team that will help resolution of any critical problems, bugs/defects that are raised through user backlog
• May take part as a member of a Major Incident Team
• Support resolution of escalated risks and issues within assigned portfolio/domain/segment
• Ensures platform stability while enabling platform teams to progressively adopt standardized frameworks, automation, and shared practices
• Treats incidents, defects, and SLA breaches as…