Optimizing the Checkout Process

Date

2023

Role

UX Designer

Services

User Research

Rapid Prototyping

The Brief

Overview
Simplifying a complex purchase journey

As Samsung’s product ecosystem expanded, I helped rethink the checkout experience to make configuration choices clearer and help customers move toward purchase with greater confidence.

The Challenge
More choices made decisions harder

Device options, trade-ins, and pricing decisions accumulated throughout the journey, making it difficult for customers to understand their choices and anticipate the final price.

Fragmented knowledge

Component information lived across disconnected guides, trackers, and files.

Knowledge dependency

Usage guidance often depended on asking someone who already knew the answer.

Design Opportunity

What would make components easier
to find, understand, and apply across the team?

What would make components
easier to find, understand, and
apply across the team?

Design Principles

Three principles shaped the system

Three principles shaped the system

Work faster, together

Make components easier to find and apply, reducing time spent searching through scattered guides and trackers.

Branding example

One source of truth

Centralize components and documentation so teams can quickly access reliable, up-to-date guidance.


Product design example

Every teammate, aligned

Give designers, PMs, and partners a shared understanding of how components work and when to

use them.

Website design example
While applying the system..

Rather than simply recreating existing components, I focused on capturing the rules behind them—when they should be used, how they behave responsively, and what variations designers actually needed.

Scaling the system

Bringing the system into one shared library across 150+ components

Bringing the system into one shared library
across 150+ components

Bringing the system into one shared library across 150+ components

.Putting it into practice —from reusable components to launch-ready pages

Putting it into practice —from reusable
components to launch-ready pages

Looking ahead

Extending the system beyond the library

Bringing the system into one shared library
across 150+ components

What changed —
and what I learned

What changed —
and what I learned

Outcome
Designing for adoption, not just consistency
Designing for adoption,


not just consistency

Production time dropped noticeably — teammates no longer rebuilt the same patterns from scratch on every launch.

Consistency held up even as multiple designers worked independently across different launches.

Handoff friction eased, with fewer implementation discrepancies once components shipped with clear, documented specs.

Reflection
The Value of shared understanding

The harder part was getting a team of designers with different habits to actually adopt a shared system instead of quietly working around it. That meant treating documentation and rationale as seriously as the components themselves: a library nobody understands the "why" behind doesn't get used, no matter how well it's built.

This project also reframed how I think about working within someone else's brand system: the constraint wasn't the ceiling, it was the foundation I was responsible for building well on top of.

©2026 Nayeon Koong

Let's chat ☕️

©2026 Nayeon Koong

Let's chat ☕️

©2026 Nayeon Koong

Let's chat ☕️