DOMAIN EXPERIENCE
Where travel flows met real service.
Publicly shareable experience spans European rail, London theatre booking and travel-service operations. Each represents a different kind of travel complexity: overseas supply, customer decision-making and continuity after release.
EXPERIENCE, NOT CLAIMS
We describe the work at the level that can be shared publicly.
These examples reflect development and operations experience. They do not imply current contracts, official partnerships, undisclosed customers or unverified outcomes.
CAPABILITY MATRIX
Domains that required connected thinking.
EUROPEAN RAIL
Italo & Deutsche Bahn
Development and operations experience connecting European rail products and reservation flows to Korean travel-service experiences.
LONDON THEATRE
Performance booking
Operations experience structuring overseas performance information and booking choices before purchase.
GLOBAL API
Overseas travel capability
API-connected service experience considers the gap between supplier data behavior and local expectations.
TRAVEL OPERATIONS
Systems behind the journey
Work includes product information, multilingual content, reservation data and operational screens.
API → 데이터 → 예약 → 현지화 → 운영
What each domain made visible
Supply
Global supplier capability enters the service.
Structure
Rules and content become product-ready information.
Decision
Customers search, compare and commit with confidence.
Meaning
Overseas complexity is expressed for Korean users.
Continuity
Teams can manage change after the launch moment.
OPERATING PRINCIPLES
The common pattern across the work.
OVERSEAS TO LOCAL
Complex products need a local interface
International travel products have their own terminology and conditions; a service must give them useful local form.
INFORMATION TO DECISION
Booking UX is decision support
The task is not simply to display availability but to explain what matters before commitment.
RELEASE TO OPERATIONS
A product stays alive after launch
Reservation data, product updates and working screens determine whether service remains manageable.
DOMAIN EXPERIENCE
Scope of publicly shareable work.
PRODUCT
Travel information and booking flows
Product information and reservation paths were considered as one customer-facing experience.
LOCALIZATION
Korean-language service context
Overseas options were approached through what Korean users need to understand and decide.
OPERATIONS
Operational structures
Admin and operations remained part of the system design after the front-end journey was defined.
