Project Context
Lead the redesign of the pre-moderation process of Traveloka's content management system (CMS). I worked with another designer and product manager to deliver the redesign of flow and UI mockups.

• Role: UX & UI Designer
• Scope: Research planning & execution, user flow and interaction design
• Timeline: 3 weeks

Background Context
Traveloka’s marketplace relies on accurate hotel inventory data to ensure users can book accommodations seamlessly.

Behind the scenes, a dedicated Content Operations team (Curators) manages the mapping and verification of hotel data provided by partner hotels. Their work is later audited by a separate Audit team to maintain data quality and consistency.
To manage this large-scale data flow, Traveloka developed an internal Content Management System (CMS) supported by limited Machine Learning (ML) capabilities.

The ML model assists curators by recommending potential duplicate or similar room entries that may be merged, reducing redundancy and improving data structure.
Over time, incremental system updates have addressed bottlenecks in the process. However, these improvements were local fixes rather than systemic redesigns, leading to fragmented workflows and inefficiencies.
With the curation team set to scale rapidly (from 9 to 30 members) while the auditor team remains limited, there was a growing need for a holistic solution that improves throughput, accuracy, and feedback visibility.
Problems
Design Goal
• Integrate curation and auditing into a single cohesive workflow with shared visibility.
• Enable performance monitoring and feedback mechanisms to close the learning loop.
• Reduce manual dependencies and fragmented communication channels

How might we design a unified operational tool that streamlines the curation and audit process, enhancing efficiency, accuracy, and collaboration — while also embedding a feedback loop?
Approach – Journey Mapping
In the beginning of the project, we interviewed all stakeholders involved (Auditor, Content Ops and Product) to understand the current flow, their pain points, and identify areas for improvement.
The pain points and needs are then consolidated into ideas for features. This forms the basis of the requirements, where we listed out:
● What abilities and information needed to perform user task
● And who needs them (user roles)

You may also like

Back to Top