U-NEXT's product ecosystem spans Web, iOS, Android, and TV. Each platform had drifted into inconsistency: mismatched paddings, duplicate components, and color/typography divergences that were silently taxing every team and slowing delivery. I initiated and led the migration to Atomic 2.0 — establishing one shared source of truth across the entire product design organization.

With Web, iOS, Android, and TV each operating from separate, inconsistent component libraries, every new feature required redundant design work and endless back-and-forth with engineering. The lack of a unified system was creating design debt faster than teams could pay it down. I saw the opportunity to initiate a migration that could fix this at the root — even if it meant convincing skeptical colleagues that design systems enable creativity rather than stifle it. I was ready to make that case, and to do the work.

Applied a structured DesignOps framework with three layers: first, Audit & Inventory — cataloguing all components across Figma files for Web, iOS, Android, and TV, identifying duplicates and usage patterns. Then System Definition in Atomic 2.0 — migrating core style assets, building atoms, molecules, and organisms with full documentation. Finally, Ops & Governance — setting up Figma libraries, version control, branching workflows, and contribution guidelines. Delegated structured tasks to UXUI designers with templates, checklists, and review loops to scale the work efficiently.

Delivered a unified Atomic 2.0 system adopted across Web, iOS, and Android. Measurably reduced design-to-dev handoff friction. Established consistent UI patterns that scaled naturally with new feature work. Shifted team culture toward treating design systems as a shared investment rather than a constraint.

Not every designer embraces systems at first — resistance is real and it's personal. I learned that knowledge sharing and visible side-by-side comparisons build credibility faster than mandates ever could. Showing the chaos of duplicated components was what changed minds. Timing also matters deeply: I wish I had been braver about proposing this migration earlier in my tenure, when the impact could have compounded further.

I'd build on Atomic 2.0 by establishing a living component documentation site and a design tokens pipeline — so the system can evolve with the product without requiring manual synchronization across four platforms every time a brand decision changes. The dream is a system that updates everywhere at once.