Selected programme work
Decisions, dependencies and delivery evidence.
Six cases showing how I structured scope, clarified ownership and moved complex work through technical, organisational and regulatory constraints.
01Japan · Japan and Korea
Japan · Japan and Korea
Japan National Product Launch
Cross-market readiness on a newly migrated commerce stack.
RoleArea content-UAT co-lead
Evidence1M unique views in four days — programme-level outcome
AEMAdobe CommerceData layer+1
02Korea · South Korea
Korea · South Korea
Korea D2C Platform Requirements
Structuring commerce, CMS, CRM and integration scope into an auditable delivery record.
RoleRequirements and area-UAT lead
EvidenceRequirements, solution design and testing completed
Adobe CommerceAEMBFF+1
03Korea · South Korea
Korea · South Korea
Cross-System Account Creation RCA
Establishing root cause, corrective action and recurrence prevention across authentication and commerce.
RoleRCA lead
EvidenceRoot cause, fix and prevention action agreed
CommerceLocal authenticationAge verification
04Japan and Korea · Japan and Korea
Japan and Korea · Japan and Korea
Incident and Change Governance
Converting post-migration stabilisation into a repeatable operating cadence.
RoleMarket-side governance owner
EvidenceRepeatable governance across 26+ identified incidents
Adobe CommerceSalesforceLocal integrations
05Japan · Japan
Japan · Japan
Experience Analytics Security Review
Balancing cross-domain tracking coverage with privacy, trust and approval gates.
RoleLocal implementation lead
EvidenceArchitecture and security review completed; deployment not launched
Experience analyticsTag managementCross-domain tracking
06Public-sector EdTech · South Korea
Public-sector EdTech · South Korea
National AI Digital-Textbook Programme
Translating policy, pedagogy and AI requirements into a national platform proposition.
RoleK–12 Project Manager / Team Lead
EvidenceKRW 900 million contract; 50,000 monthly active users
AI-integrated LMSDigital textbooksPublisher ecosystem
These case studies have been sanitised for public use. Internal identifiers, confidential implementation details and private communications are excluded. Programme-level metrics are labelled separately from Andrew’s individual contribution.