HAMM — Hybrid Assisted Media Module

A single workflow for a fragmented localisation pipeline.

Disney's media localisation involves multiple production partners, multi-track audio and subtitle assets, and tight quality requirements. Before HAMM, these workflows lived across different tools — file transfers, manual subtitle QA, and disconnected status updates between studios.

HAMM consolidates the pipeline: a producer uploads a video, the AI subtitle engine processes it, multiple roles (Super Admin, Disney Production, Production Company) review and approve at their respective stages, and final assets are downloaded — all within one workspace.

Where I owned design and quality.

As Product Intern, I worked between design, engineering, and the QA teams in Singapore and Japan. My responsibilities spanned the full feature lifecycle:

• UI design for new web product features — translating PM requirements into Figma flows and components.
• Coordinating Jira ticket development requirements with full-stack engineers.
• Functional testing, annotation, and data analysis for the AI Subtitle product.

Designing for clarity in a multi-role tool.

Mapping the user roles

HAMM serves three distinct user types: Super Admin (oversight), Disney Production (content owners), and Production Company (Pixelogic, Deluxe, etc.). Each role sees a different home page, navigation, and permission set. The first step was mapping these workflows onto a unified information architecture.

Dark mode, by design

Disney's media-review tools live in dark environments — colour grading, subtitle timing, and long viewing sessions are easier on the eyes against a dark background. We built the whole system on a #0A0A14 base with a single accent blue (#2C5DFF) for primary actions.

Testing

My responsibilities include manually annotating the letters translated by the platform's AI and the translation quality and error rate are calculated to comprehensively assess the feasibility of the product's functions.

What I learned working at Disney.

Six months at Disney's product team taught me that good design at the enterprise scale is as much about process as pixels. A clear Jira ticket, a well-structured MagicPod test, an SOP that reduces onboarding time — these are also design artefacts.

Working across Singapore, Japan, and Shanghai also rebuilt my expectations around asynchronous communication. Decisions had to be documented, options had to be visualised, and feedback loops had to run reliably across time zones.