Enterprise · HR Tech · Fintech

Amazon

Investigating and improving financial well-being for Amazon employees.

Amazon employees report lower financial health than peers at Google, Meta, or Apple. The HR & Benefits organization wanted to give employees consolidated tools for planning their financial futures — instead of scattered wikis, peer docs, and benefits portals.

I led research and shaped the product roadmap — a 5,000-employee survey, 30 in-depth interviews, and prototype calculators that translated the findings into a working planning surface.

5,000

Employees surveyed

across the organization

30

In-depth interviews

5 internal departments

5

Life-event journeys mapped

retirement to vacation

Project at a glance

Company

Amazon

Industry

Enterprise · HR Tech

Product

Internal Financial Well-being tools

Phase

Discovery → Prototype → Roadmap

My role

UX Research & Product Design

Methods

Surveys, stakeholder interviews, qualitative & quantitative analysis

Sample

n = 5,000 survey · 30 interviews

Output

Press release of findings, UX plan, prototype

The Context

Why this mattered.

Amazon employees were navigating major financial decisions — retirement, parental leave, home ownership — by digging through fragmented internal wikis, peer-written documents, and benefits platforms that didn't talk to each other.

HR & Benefits leadership wanted a single, opinionated experience that connected compensation, benefits, and life events into one planning surface — without forcing employees to become spreadsheet experts overnight.

The problem

Research question.

What financial life events most affect Amazon employees, and where do the current internal tools fail them at the moment of decision?

That question framed the entire study — every interview, survey cut, and journey map had to either answer it or sharpen it.

Methodology

Mixed methods, real evidence.

  1. 01

    QuantitativeAttitudinal

    Survey of 5,000 employees

    Identified the top financial goals across roles, geographies, and income bands — and pressure-tested assumptions from HR leadership.

  2. 02

    QualitativeGenerative

    30 in-depth interviews

    Sessions with employees across operations, corporate, and tech roles in the US and UK — pickers, drivers, SSAs, and managers.

  3. 03

    QualitativeJourney mapping

    Five life-event journey maps

    Retirement, starting a family, home ownership, life insurance, and vacation planning — mapped end-to-end with internal touchpoints.

  4. 04

    EvaluativePrototyping

    Calculator prototypes

    Two tools: a retirement contribution calculator and a per-paycheck spending allocator based on the 50/30/20 rule.

Voices

What employees told us.

"I had to dig through benefits platforms, reference peer-written documents, and Amazon wikis related to paternity leave just to understand the coverage and financial implications."

Amazon employee, US

"I want to save up for a trip to Spain for my honeymoon, but I'm not sure how much to set aside per month. I'd love to plan a realistic timeline alongside my PTO."

Amazon employee, UK

Key Findings

What the data surfaced.

  1. 01

    Information is everywhere — and nowhere

    Employees described a scavenger hunt across 4–7 internal sources just to make one decision. The blocker wasn't access; it was synthesis.

  2. 02

    Life events are the right unit, not products

    Employees don't think 'I need a 401(k) page' — they think 'I'm having a baby.' Organizing tools around life events outperformed product-led IA in every test.

  3. 03

    Best-practice defaults reduce paralysis

    The 50/30/20 starting point unlocked engagement. Employees adjusted from a sensible default rather than designing from scratch.

  4. 04

    Trust requires transparency

    Monte Carlo style 'strong vs. weak market' visualizations were the single most requested feature once employees saw a static projection.

What I designed

The prototype surfaces.

Two connected calculators powered the prototype: a retirement planner that consumed an employee's total compensation, 401(k), HSA, and vested RSU balances; and a per-paycheck spending allocator with recommended categories based on financial best practices.

One-click changes routed back to Amazon-sponsored benefit elections, including stepped contribution increases that ramped over a self-selected timeline — minimizing the shock of a lower net paycheck.

Success Metrics

How we'd know it worked.

  1. 01

    Feature adoption

    Percent of employees accessing the Financial Well-being tool from the A to Z portal.

  2. 02

    Behavior change

    Equifax score delta, new savings accounts opened, retirement contribution changes, life-insurance enrollment.

  3. 03

    Journey completion

    Per-calculator session journeys and ClickStream completion rates per life-event flow.

  4. 04

    Qualitative resonance

    Recurring quarterly interviews to ensure the tool kept pace with how employees' financial lives actually changed.

Reflections

What I'd carry forward.

  • Financial well-being products fail when they mirror the company's internal org chart instead of the employee's life
  • Reorganizing the IA around life events — not benefit products — was the change that made everything else click
  • Front-load a tighter quantitative read on adoption willingness by tenure and role
  • Arm Product with sharper prioritization weights from day one, not just qualitative signal