FMCGCase study

Global Website Programme (45 markets): How I ran it

Led the redesign and rollout of a corporate website platform across 45 markets, coordinating the client, local markets and external translation, content and technology partners around a single roadmap.

2022 – present · 45 markets · Europe, LATAM, APAC, MEA

How I ran it

Cadence, roles, risks and the decisions behind the delivery.

Governance

  • Two weekly meetings, each with different market representatives and other stakeholders involved
  • Jira as the single source of work (3,000+ tickets)
  • The same six gates for every market, from discovery to hypercare

Who did what (RACI)

RACI matrix: for each activity, who does the work (R), approves (A), is consulted (C) or informed (I)
ActivityClientUX/UIDevQAMarketsContentSEOLegal
Master site design and approvalClient: AUX/UI: RDev: CQA: IMarkets: CContent: not involvedSEO: CLegal: not involved
Wave plan and go-live calendarClient: A/RUX/UI: not involvedDev: CQA: not involvedMarkets: CContent: not involvedSEO: not involvedLegal: not involved
Content upload and translation per marketClient: IUX/UI: not involvedDev: not involvedQA: not involvedMarkets: A/RContent: RSEO: CLegal: not involved
Development sprints and integrationsClient: IUX/UI: CDev: A/RQA: CMarkets: not involvedContent: not involvedSEO: not involvedLegal: not involved
QA and UATClient: AUX/UI: not involvedDev: CQA: RMarkets: RContent: not involvedSEO: not involvedLegal: not involved
Accessibility compliance (80% target)Client: AUX/UI: RDev: RQA: CMarkets: not involvedContent: not involvedSEO: not involvedLegal: C
AI-search (GEO) implementationClient: AUX/UI: not involvedDev: RQA: not involvedMarkets: not involvedContent: not involvedSEO: RLegal: not involved
Consent and data protectionClient: AUX/UI: not involvedDev: RQA: not involvedMarkets: not involvedContent: not involvedSEO: not involvedLegal: R
Go-live and hypercareClient: AUX/UI: not involvedDev: RQA: RMarkets: IContent: not involvedSEO: not involvedLegal: not involved
Local market sign-off before go-liveClient: AUX/UI: not involvedDev: not involvedQA: CMarkets: RContent: not involvedSEO: not involvedLegal: not involved

R does the workA approvesA/R approves and doesC consultedI informed

Main risks and how I handled them

Local markets slip on content and translation deadlines

Content

Content readiness reviewed with each market ahead of its wave; slippage raised in the weekly meeting.

Different legal and consent requirements per market

Legal

Legal and data-protection checks planned into each wave before go-live.

Scope creep from 45 local stakeholders

Scope

One roadmap, Jira as the single source of work, changes agreed in the weekly meeting.

Late fixes on one wave affect the next

Technical

Structured QA and UAT gate before each launch; hypercare period after go-live.

Decisions

Master site + eight waves

Context
A 45-market launch concentrates risk if everything goes live at once.
Decision
Ship one Master site, then group markets into eight waves.
Outcome
Every wave went through the same gated process, from design to hypercare.

Two weekly meetings, different market representatives

Context
Dozens of local teams, 45+ nationalities and several external partners.
Decision
Two weekly meetings, each with different market representatives and other stakeholders involved.
Outcome
Stakeholders from every market stayed aligned on one roadmap.

Accessibility as its own project

Context
European accessibility regulations set a compliance requirement that can’t slip.
Decision
Run a dedicated project with an 80% compliance target instead of folding it into the backlog.
Outcome
Compliance work was planned, owned and reported on its own.

Invest in AI-search (GEO) readiness

Context
Generative search engines are becoming a discovery channel.
Decision
Add schema markup, landmarks, breadcrumb schema and an llms.txt file at platform level.
Outcome
Implemented at platform level; measurement in progress.

Jira as the single source of work

Context
Work from many teams and markets needs one shared view.
Decision
Track all work in Jira.
Outcome
3,000+ tickets opened and closed.

What I learned

  • Managing many stakeholders at once only works if everyone sees the same picture: one roadmap, one source of work and visibility of progress for all of them.
  • Risks are cheaper to handle when they are anticipated. The wave plan and the weekly meetings were where I surfaced them before they reached a go-live.
  • A fixed set of touchpoints gave 45 markets the same rhythm, so each wave started from a known playbook instead of renegotiating how we worked.
  • Content and translation readiness was the first thing to slip in every wave, so I asked each market for it earlier.

Working on something like this?

Download my CV or message me on LinkedIn.