Director Solutions Platform, UK

About WPP Media
WPP is the trusted growth partner for the world’s leading brands. With exceptional talent, trusted data and intelligence, and world-class partnerships – all united by our pioneering agentic marketing platform, WPP Open – we help clients navigate change, capture opportunity, and deliver transformational growth.
WPP Media is WPP's AI-driven media operating unit, bringing together media, data, and partnerships to deliver creative personalisation at scale. Connected through WPP Open and powered by Open Intelligence, clients see exactly where, how, and why their media investment is working.
For more information, visit wppmedia.com.
Role Purpose
The Platform Operations Director is responsible for ensuring that solutions developed and released for the Solutions team are operationally ready, properly tested, clearly documented, effectively released, and provide support once live.
The role acts as the bridge between delivery, business readiness and BAU operations. It supports the transition of work from project delivery into stable operational use, ensuring that users, stakeholders and support teams understand what has changed, how to use it, how to raise issues, and how ongoing support will be managed with appropriate priority, impact and SLAs
This role is particularly important as Solutions Integration moves from a more reactive service model into a structured product and agile delivery function. The Platform Operations Director owns QA, release management, documentation, stakeholder communication, support processes, training, adoption and post-release improvement including BAU bugs and triage.
The role works closely with Product Owners, Scrum Master, Engineering, Data, Reporting, QA, Platform Operations, and business stakeholders to make sure delivery does not stop at “built”, but continues through testing, launch, adoption, support and measurable operational value.
Senior / Specialist-Level Expectations
As a Director within the team, this role is expected to help define and improve the operating standards around BAU management, QA coordination, release readiness, business readiness and service transition. Manage and proactively manage risk, resolution SLAs and ensure we are adhering to platform operational best practices.
The Platform Operations Director should be able to identify operational risks early, challenge whether a solution is genuinely ready for release, and recommend practical improvements to processes, documentation, testing, support models and stakeholder communications.
For smaller initiatives, the role should be able to advise Product Owners and delivery teams on the appropriate level of QA, training, release planning, handover and BAU support required. For larger or more complex initiatives, the role should escalate risks, dependencies or readiness gaps to the Product Manager Lead, Scrum Master, Lead Engineer / Solutions Architect or relevant leadership stakeholders.
Key Responsibilities
1. BAU Operations Management
Own and coordinate BAU operational processes for assigned platforms, tools, reports, workflows and solutions across all Media solutions.
Monitor recurring issues, support trends, operational risks and user pain points.
Triage and prioritise BAU requests, incidents, defects and enhancement requests.
Ensure BAU work is captured through the agreed intake and backlog process rather than unmanaged emails, verbal requests or fragmented ticket routes.
Work with Product Owners and the Scrum Master to distinguish between BAU support, defects, enhancements and new product requirements.
Maintain visibility of BAU demand and help identify where recurring issues should become product improvements or engineering fixes.
Support continuous improvement of support processes, documentation and operational workflows.
This links directly to the team’s wider shift away from fragmented request routes and towards clearer delivery rhythms, structured backlogs and improved operational process discipline. The existing documentation notes the need for clearer team rhythms, sprint cadences, retrospectives and mentoring as part of the transition plan .
2. QA Coordination and Testing Readiness
Coordinate QA activity across delivery workstreams, ensuring testing requirements are understood before development begins.
Work with Product Owners to ensure acceptance criteria, test scenarios and success measures are clearly defined.
Support test planning across functional testing, regression testing, data validation, reporting checks and user acceptance testing.
Ensure defects are logged, prioritised, tracked and resolved through the agreed delivery process.
Work with engineers, analysts and business users to validate that solutions meet functional, operational and reporting requirements.
Support the creation of reusable QA checklists, test scripts and validation templates.
Ensure solutions are not released without appropriate testing evidence and business sign-off.
This is consistent with the Product Owner responsibilities already defined around testing requirements, success criteria, UAT coordination, business validation, release readiness and operational handover . The Platform Operations Specialist would support and operationalise those activities.
3. Business Readiness and Adoption
Ensure business users and operational teams are ready to adopt new or changed solutions.
Coordinate training, guidance, demos, FAQs, release notes and user communications.
Work with Product Owners to identify impacted teams, users, processes and workflows.
Confirm that business teams understand what is changing, why it is changing, when it is happening and what action is required.
Support stakeholder communications before, during and after release.
Gather early feedback from users and ensure issues are captured and prioritised appropriately.
Help ensure delivered solutions are embedded into day-to-day operations, rather than remaining underused or misunderstood.
The handover documentation highlights the importance of clear communication with users, proper release notes, demonstrations and adoption support for new features and solutions . This role should own the operational discipline around making that happen consistently.
4. Release Readiness and Service Transition
Own or coordinate release readiness checklists for assigned solutions.
Ensure each release has appropriate testing evidence, documentation, support ownership, training material and stakeholder communication.
Coordinate operational handover from delivery teams into BAU support.
Confirm that runbooks, troubleshooting guides, known issues and escalation routes are in place.
Work with engineering and data teams to ensure monitoring, alerting or manual checks are defined where required.
Support go-live planning, release scheduling and post-release hypercare.
Track post-release issues and ensure learnings are fed back into future delivery cycles.
This role should become the person asking:
“Are we actually ready to put this live, support it, explain it, and measure whether it worked?”
5. Documentation and Knowledge Management
Maintain clear operational documentation for platforms, reports, tools, processes and workflows.
Support the creation of user guides, SOPs, runbooks, release notes, FAQs and support documentation.
Ensure documentation is stored in the agreed location and kept up to date.
Work with Product Owners, engineers and analysts to document key dependencies, business rules, known limitations and support processes.
Help reduce reliance on individual knowledge by making processes and system behaviour transparent.
Support onboarding of new team members by maintaining accessible knowledge resources.
This is important because the team is moving away from legacy ways of working and informal knowledge transfer into a more structured operating model.
6. Platform and Process Governance
Support the consistent use of agreed tools, workflows, ticketing processes and delivery governance.
Help ensure work is captured, categorised and progressed through the correct routes.
Maintain standards for BAU tickets, defects, release requests, support issues and operational change.
Identify process gaps, duplicated effort or inconsistent ways of working.
Recommend improvements to BAU processes, support models, QA standards and release governance.
Support reporting on operational performance, support demand, defect trends and release readiness.
Help ensure changes are controlled, documented and aligned to agreed team practices.
This aligns with the documented need to improve proactive behaviour, structured product management, backlog grooming, stand-ups and retrospectives across the team .
7. Stakeholder and Cross-Team Coordination
Work closely with Product Owners, Engineering, Data, Reporting, QA, Scrum Master and business users.
Coordinate with Activation, Operations, Channel Development, Commercial and other impacted teams where relevant.
Ensure operational dependencies are understood and managed before release.
Help stakeholders understand support routes, known