American Century Investments project hero
American Century Investments
CMS Migration · Features · Dashboard · Design System
Fintech Wealth Management Design System CMS Migration Dashboard Cross-Platform Enterprise

Overview

My Role

I worked across five surfaces of American Century Investments\' digital experience: Contentful migration, landing pages, design systems, client portal, and the internal ESG dashboard. Each one had its own constraints, but they all rolled up to the same goal: bring a fragmented set of investor-facing tools onto a shared foundation that the rest of the business could build on.

My Role and Experience: five workstreams across Contentful Migration, Landing Pages, Design Systems, Client Portal, and Internal ESG Dashboard

Process

Same shape across every workstream: understand the problem, the user, and the business context, then identify the highest-leverage opportunities, then execute with the team that owns the surface.

Process: Understand, Identify, Execute

Typical Work Flow

Inside each project, the work moved through requirements, research, user flows, wireframes, UI, prototypes, usability testing, deliverable handoff, QA, launch, and measurement. Some steps got compressed under tight timelines, but the structure stayed the same.

Typical work flow from Requirements through Launch and Measure

Contentful Migration

Why Contentful

Marketing and product needed to ship pages without filing engineering tickets. The legacy stack made every change a release. Contentful gave us a headless backbone that the team could compose from, but only if the design system and the content model were designed together.

Approach

I leveraged the existing design system style to build and migrate components into Contentful, mapping each marketing surface to a small set of reusable blocks. Editors could re-arrange sections and variants without breaking the brand or the layout.

Contentful migration: live page examples
Documentation: page templates, grid system, and 2/3/4-card component layouts

Documentation includes annotations for limitations, functionality, and structures.

Design Systems

Foundations

I inherited a maturing design system and elevated it: aligning typographic scale, form components, alerts, color tokens, and buttons across the ecosystem so that every team pulled from the same source of truth.

Design system: type scale, components, form fields, alerts, and color tokens

Inherit and elevate current design system components. Manage and align components across ecosystem.

Components as Building Blocks

The same components powered the marketing site and the client portal. Landing pages were composed from system blocks rather than designed page-by-page, so brand and behavior stayed consistent at scale.

Landing pages built from system components

Client Portal

Features

Building new features into an already mature dashboard: Move Money, Assets Allocations, Balance History Charts, Required Minimum Distribution (RMD), ESG Dashboards, Documents Management, and more.

Client Portal feature inventory and dashboard mocks

Move Money: Legacy vs. Update

The legacy Buy Request flow buried critical inputs and gave users no sense of where they were in the process. The update reframes the same task around a clear single-page form, plain-language fields, and a confirmation pattern that doubles as a record.

Move Money: legacy three-step modal vs. updated single-page Buy Request

Mobile

The same flows had to feel native on phone. Bottom sheets for account selection, single-action transaction tiles, and a persistent tab bar that kept Total Assets, Transact, Feedback, and Contact one tap away.

Mobile transaction flow: Buy, Sell, Exchange, Auto Invest tiles plus account and fund selection sheets

Let's Work Together

Good Design Starts with a Good Intention.