top of page

Design Strategy and Delivery

Role

Lead UX Designer and Design Strategist

Platform

Amazon Tablet OS

Team

Tablets Design, Product, Engineering, Legal, 1P/3P Capabilities, Domains, Alexa Core, Kids+ Tablets

oobe.png

Setting up a new device is a customer's first real interaction with a product. For Amazon Fire Tablets, that moment was broken and fixing it was more complex than we had originally scoped.


What started as a visual refresh became a full strategic overhaul unifying two separate backend systems into one seamless onboarding flow. Even as the sole UX designer under an extremely fast deadline, the biggest constraint wasn't time or creativity, but technical complexity. Two platforms, each with non-negotiable system and visual design requirements, had to merge into one experience and feel effortless to the customer holding the device.

Problem

50+ screens. Two backend systems. One flow.


The existing OOBE had grown around system logic, which included steps for data that the backend needed to collect, not for what makes sense to a first-time user. Customers were signing in twice without understanding why. They had to read walls of text and tap through without absorbing any of it. And with a new OS launch adding data transfer, multi-account sign-in, and AI features to the flow, setup time had ballooned from 6–7 minutes to over 15.

Solution

The question wasn't how to make it look better. It was how to make 50+ screens into something a customer could move through without noticing how much was happening underneath.

About
THE APPROACH

Audit first, Redesign second

Self UX Audit

Before touching any screen, I mapped every technical dependency across the full flow, understanding what each system required, what legal protected, and what could actually be moved.

Users were spending too much time on redundant steps like signing in twice or going through unnecessary permissions. The current design lacked visual clarity. Each page was text-heavy, cluttered, and didn’t convey information effectively.

Competitor Audit

I audited competitor onboarding flows from Apple, Samsung, Google, and Lenovo. The pattern across all of them was:

  • one message per screen

  • progressive disclosure

  • visuals doing the work that text was doing for us

oobe1.png
Screen Shot 2026-01-24 at 7.00.24 PM.png

That audit produced three structural principles I applied to every decision that followed:

  1. Consolidate steps that share a logical relationship

  2. Order processes by the customer's mental model not the system's

  3. Earn attention with visuals before asking for anything

KEY DECISIONS

The work behind the work

This project involved five specific design problems within the larger onboarding flow, each requiring its own research, stakeholder navigation, and trade-off analysis. Some of the most significant outcomes came from decisions that weren't in the original brief.

 

For example, customers were signing into whichever account appeared first and skipping the second. That wasn't a UX problem, but a system sequencing issue with a direct impact on Amazon account linking rates. Resolving it required making a case to the engineering team for an infrastructure change, not just a screen reorder.

​

In another example, leadership had a strong preference for a backup and restore approach that preserved legacy branding but increased completion time and buried new platform features. I built a full trade-off analysis across 4 architectural options and presented it directly to L10 leadership: information density, technical feasibility, flow complexity, cross-platform consistency for each. The outcome was a hybrid solution that didn't exist before that presentation.

oobe2.png
RESULT

A new standard, not just a new flow

The redesigned OOBE reduced screen count by up to 65%, from 50+ screens to 15–20, and introduced more capability than the previous version. OOBE completion rates improved, subscription conversion increased, and two processes I created during this project, a trade-off analysis framework and a new design-to-development handoff format, were adopted as standards across other Tablets work streams.

Frame 1664679924.png
Welcome
Wi-Fi
Quick Start
(loading screen)
Amazon Sign-in with value props
Back up
and Restore
Device Protection
Key Screens (without branding)

Impact

1

2

3

4

Up to 65% reduction in screen count

250K+ annual subscription signups driven

more upsell offer signups

Delivered in 3 months as sole UX designer

This project is under NDA.

Reach out for more!

bottom of page