Andrew Do

I turn ambiguous platform requirements into delivery plans teams can execute.

I define scope, sequence system dependencies and close release decisions across business teams, engineers and delivery partners.

Complex systems, made executable.

Three programmes showing how requirements, system boundaries and release gates were turned into decisions teams could act on.

Japan National Product Launch

Launch-scale content and product pages had to be signed off against a fixed date while readiness was slipping.

Outcome
The launch completed and successfully exited hypercare.
My role
Area content-UAT co-lead
Read case study
Public Japanese myglo application landing page shown after launchPublic Japanese commerce product listing showing the launched catalogue

Korea D2C Platform Requirements

Multiple partners needed a buildable cross-system specification from fragmented market requirements.

Outcome
Requirements, solution design and testing were completed before the programme was cancelled for a separate business reason.
My role
Requirements and area-UAT lead
Read case study
Public Korean glo desktop product page used as market platform contextPublic Korean glo mobile storefront shown within a phone frame

National AI Digital-Textbook Programme

A national programme needed one credible proposition across policy, pedagogy, student safety and publisher participation.

Outcome
Secured the KRW 900 million research contract.
My role
K–12 Project Manager / Team Lead
Read case study
Elice public announcement confirming approval of its elementary and middle-school AI digital textbooks

Across commerce, EdTech and enterprise IT.

View full experience

42dot

Technical Programme Manager

July 2026Present

British American Tobacco

Digital Solutions Analyst

March 2024July 2026

Elice

K–12 Project Manager / Team Lead

December 2021February 2024

TikTok Korea

QA Analyst

November 2020December 2021

Reduce uncertainty before it becomes rework.

  1. Clarify ownership

    Define who recommends, decides and executes.

  2. Surface dependencies

    Expose system and delivery constraints before commitment.

  3. Close with evidence

    Make claims, gates and closure conditions traceable.

  4. Retire the process

    Keep only the governance needed to reduce uncertainty.

His rare combination of technical and business acumen … made him the connective tissue across teams and systems.
Ananya SinghProduct and e-commerce collaborator
He’s one of those Product Managers who understands both the business and technical side equally well, which makes collaboration with him very smooth.
Sadullah JavedFormer colleague at BAT

Need clarity across teams and systems?