About the role
Role summary
Techno-functional Product Owner to own end-to-end delivery of a Google Analytics to Adobe Customer Journey Analytics (CJA) migration. Acts as the single point of accountability across business and technology — translating measurement and reporting needs into a well-governed backlog, and safeguarding data parity and reporting quality across migrated experiences. Success requires strong PO discipline paired with medium-to-strong understanding of digital analytics and the GA→CJA migration path.
Product Ownership & Backlog
• Own end-to-end delivery of the GA→CJA migration as single point of accountability across business and technology.
• Own and prioritise the product backlog; author well-defined user stories with clear, testable acceptance criteria for tracking, data mapping, and reporting workstreams.
• Drive epics prioritisation, scope clarity, and timely decision-making throughout the lifecycle, including phased migration across sites/microsites.
• Partner closely with engineering and analytics teams to translate measurement needs into actionable, appropriately-scoped backlog items.
Delivery Governance & Process
• Lead quarterly planning; align backlog and epics to business and reporting objectives across the roadmap.
• Proactively manage dependencies, risks, and assumptions impacting delivery — including parallel-run and cutover sequencing.
• Lead UAT coordination, data-parity validation, feedback triage, and approval gates.
• Enforce change control; protect agreed scope and timelines.
• Run structured planning and maintain continuous stakeholder alignment across agile ceremonies (planning, refinement, reviews).
Stakeholder Management
• Act as the primary bridge across business and technology stakeholders, driving alignment and decision-making.
• Manage expectations, communicate progress and trade-offs, and present plans and outcomes to senior stakeholders.
• Align decentralised site/microsite owners on migration approach, standards, and reporting expectations.
Analytics Techno-Functional Ownership
• Bring medium-to-strong understanding of digital analytics and the GA→CJA migration: event-based data models, data layer, tag management, and the GA-to-CJA data flow.
• Own definition of tracking and reporting requirements; map GA metrics/dimensions to CJA equivalents and govern metric/dimension parity across platforms.
• Govern the correctness and consistency of migrated dashboards, data views, segments, and reporting.
• Coordinate parallel runs and validate explainable variance between GA and CJA before sunsetting the legacy platform.
Hold credible techno-functional discussions with engineering and analytics specialists (without acting as the technical architect) — enough depth to challenge decisions, unblock the team, and safeguard measurement integrity.