Situation
Multiple partners needed a buildable cross-system specification from fragmented market requirements.
Aligned various stakeholders to produce structured scope and sequence integration dependencies.
System flow
Traceability of ownership and gate dependencies across systems.
Korea D2C Platform Requirements sequential logic
- Business requirements (External approval gate)
- BRD / FRD and feature mapping — Andrew-led analysis (Andrew led)
- Architecture and event-flow alignment — Shared reviews (Shared ownership)
- Engineering backlog — Vendor-owned (Partner-owned delivery)
- Area UAT — Andrew-led checks (Andrew led)
- Completed design and test record — Parity complete (Partner-owned delivery)
- Business-level cancellation — Market decision (External approval gate)
My scope
Andrew owned or led
- •Requirements mapping and business scope translation
- •UAT scenario planning and area testing readiness
Partner or external ownership
- •Engineering implementation and solution architecture
- •Vendor test-plan authorship
Decisions & execution
Decision 01
Structured fragmented commerce, CMS, CRM and middleware requirements into an auditable delivery record
Why it mattered
Aligned multiple vendors around a buildable cross-system specification.
Key Execution Actions
- Mapped business rules to commerce features.
- Sequenced integration dependencies for commerce, CMS and CRM.
Outcome & attribution
Outcome & System Change
Requirements, solution design and testing were completed before the programme was cancelled for a separate business reason.
Individual Contribution & Boundary
Structured commerce, CMS, CRM, BFF and Salesforce integration requirements and owned testing readiness.