Addition Wealth • 2022–2025

Addition Wealth • 2022–2025

Designing a new approach to financial wellness for employees

Designing a new approach to financial wellness for employees

Designing a new approach to financial wellness for employees

Problem

Problem

Millions of employees face challenges with financial literacy and decision-making, often resulting in poor financial outcomes. According to the PwC Employee Financial Wellness Survey, over 72% of employees reported feeling stressed about money, yet most companies fall short in providing the support they need. This financial stress directly impacts workplace productivity, leading to preventable losses for employers.

Role

Role

As the Founding Product Designer, I was responsible for helping Addition financial wellness platform build from zero to one, supporting design through Seed to Series B ARR ($5M+).

Wearing many hats, I drove UX/UI, customer research, product strategy, branding, and front-end development. During my time here, I worked directly with leadership, engineering, product, and GTM to build our product used by thousands of employees nationwide.

Outcomes

Outcomes

12+

12+

major feature launches

2M+

2M+

unique users onboarded

90%

90%

average monthly CSAT score

$5M+

$5M+

annual recurring revenue

Establishing Addition's first design system

Establishing Addition's first design system

When I joined Addition Wealth, the product lacked a cohesive visual language and user experience, which made it feel forgettable and untrustworthy to users. In the context of a financial product, establishing trust is critical.

I designed and build our design system (Compound) in Figma; defining front-end component guidelines, maintenance processes and core design patterns.

I also led the enterprise-scaling of Compound, scaling it to support multiple product ecosystems across our client portfolio.

When I first joined Addition, the product was in a rough spot. The result was inconsistent components, hardcoded values, no tokens, and a visual language that felt low-quality for a product asking users to trust it with their finances. It was clear why they'd brought a full-time designer in.

I built our design system (Compound) from scratch over four weeks. Engineering adopted it immediately, not because I sold them on it, but because the downstream impact was obvious – cleaner handoffs, faster builds, fewer one-off decisions.

Balancing craft with data to build end-to-end products

Balancing craft with data to build end-to-end products

My design process follows the Double Diamond – discover, define, ideate, deliver. In practice it's rarely that clean. The clearest example was diagnosing low engagement in our resource library. My hypothesis going in that the content wasn't good enough. Articles were too long, too technical, too generic. If we fix the content, we fix the engagement. I was already sketching solutions before I'd talked to a single user.

Customer interviews killed that hypothesis fast. Users weren't bouncing because the content was bad, they were bouncing because they didn't know where to start. The entry point was broken. Someone overwhelmed by debt, a lack of savings, and no retirement plan doesn't browse a content library – they freeze. We weren't dealing with a content quality problem, it was a motivation and framing problem. Instead of improving what we had, we built a guided entry point that met users where they actually were. Financially anxious, time-poor, and needing someone to tell them what to do first. Once we implemented this new strategy, engagement naturally followed.

The point I'm trying to make is there was a lesson I carried through every project after that: the hypothesis you walk in with is just a starting point.

My design process involves adapting the Double Diamond framework, moving from discovery to definition, then into ideation and delivery. However in practice, this process is far from linear and required constant adaptation.

As a solo designer, I scoped and led projects end-to-end, often going beyond my role responsibilities, drafting PRDs and conducting QA testing to ensure that we shipped features on time. Not only did we exceed client expectations, we constantly raised the bar for our industry's design.

What were our user pain points?

1.

1.

1.

Users want to understand their individual, unique financial situation.

2.

2.

2.

Users want to receive clear, personalized guidance.

3.

3.

3.

Users want to measure their progress over time.

What were our business challenges?

1.

1.

1.

Low engagement limits user adoption.

2.

2.

2.

Lack of personalization reduces relevance and trust in the product.

3.

3.

3.

Inconsistent user experience weakens product cohesion and user confidence.

Building tools to support employees through their financial journey

Building tools to support employees through their financial journey

Equity calculators

Equity calculators

Equity is one of the most valuable (and most misunderstood) parts of a compensation package. Most employees either ignore it or accept it without understanding what they're actually agreeing to. This included me when I started this project.

I had no domain knowledge on equity going in. So I treated that as an advantage. I researched until I had a working knowledge base, then went directly to Addition's financial advisors and users to test what I'd learned. The gap between what I assumed and what users actually needed became the design brief.

One moment that changed everything: learning how vesting cliffs work. I'd always assumed equity was like a salary – you earn it continuously. The reality is more nuanced, and users were making decisions without understanding the timing implications. I added contextual elements to surface that information at the exact moment users needed it, without overwhelming people who just wanted a simple number.

It felt like being a tutor who'd just learned the subject themselves. That proximity to the user's confusion made the tool better.

Financial accounts

Financial accounts

The insight that drove this feature came from a customer interview that stuck with me: a user didn't know how much money was in their checking account. They weren't irresponsible, they were just caught up by real life. Multiple accounts across multiple institutions, no single place to see the full picture. That was the real problem – not that people lacked financial knowledge, but that they lacked financial visibility.

The technical reality was also difficult. Banking, investment, and retirement data all come from different providers with stubborn, inconsistent APIs. There was no out-of-the-box solution. We stitched it together, and my job was to make that complexity invisible to the user and presenting a comprehensive view that felt simple even though the infrastructure underneath was anything but.

Once accounts were connected, the design priority shifted to scannability. Users didn't need to analyze their finances – they needed to feel oriented. Net worth at a glance, cash flow patterns visible without digging. The goal was to answer the question users didn't know how to ask: where am I, right now?

Life events

Life events

One pattern kept surfacing in user interviews: when people started talking about their finances, they'd spiral. No retirement savings would lead to crippling debt would lead to no emergency fund – one anxiety cascading into the next. Sessions with financial advisors suffered for the same reason. The problem was too unspecific to solve and you can't help someone who's overwhelmed by everything at once.

The insight was simple but counterintuitive: users who were guided to focus on one problem, specifically the most time-sensitive one, made more progress and reported better financial outlooks. Focus wasn't a limitation. It was the unlock.

It became our highest-traffic feature for a practical reason: it was the easiest entry point into a complex product suite. New users didn't have to figure out where to start– the life event did that for them. Lowering that barrier turned what could have been an overwhelming platform into something that felt immediately useful on day one.

Learning courses

Learning courses

The brief was almost impossible on paper: teach people concepts they'd spent their whole lives avoiding, in a format they'd always found boring, in a product they opened twice a month.

The existing resource library wasn't working. Articles full of jargon, webinars that felt like homework. User research confirmed what we already suspected – people don't learn finance by reading about it. They learn by seeing it and connecting it to their own numbers.

So I designed an interactive course format across 15+ financial topics. The personalization was the differentiator – once a user linked their accounts, courses stopped using hypothetical examples and started using their actual numbers. In the equity 101 course, the 'how to calculate your equity value' equation pulled your real strike price and share count. Abstract concept became personal reality.

That became the template for the whole course system: let the financial experts define what's accurate, then fight for what's actually learnable.

Aligning enterprise clients with our product vision

Aligning enterprise clients with our product vision

As Addition expanded into the enterprise market, I led design for three major partnerships – Balance Wellbeing, Edward Jones at Work, and AARP – extending our platform's reach to millions of users outside our original audience. Each partnership came with its own legal, brand, and compliance requirements. What made it tractable was the design system I'd built for the core product – modular enough to refit for entirely different brands and user groups without starting from scratch. What made it hard was everything else.

Addressing the challenge

The decision to go enterprise wasn't in the design roadmap – it landed at an all-hands when leadership announced we'd be building Balance Wellbeing for New York Life. There was internal debate about whether to white-label our technology at all; nobody wanted Addition to become a dev sweatshop. But our CEO saw it as the unlock for enterprise revenue, and she was right.

For me, the immediate implication was clear: the design system I'd built for a single product now needed to support multiple branded platforms simultaneously. I had days, not months, to make it happen. The saving grace was that I'd been designing modularly from the start – not because I anticipated this pivot, but because clean systems are just how I work. That instinct ended up being the thing that made the enterprise expansion possible.

Conflicting interests

Not every enterprise decision was the right one. When scoping Balance Wellbeing, leadership wanted to ship a basic resource library and recycled online calculators – a significant step down from the personalized, advisor-backed experience we'd built at Addition Wealth. I pushed back. Users weren't getting access to financial advisors, the content wasn't personalized, and we were essentially shipping a worse product under a premium brand. But the pressure to close the sale won out.

The result was predictable: engagement tanked. Users weren't returning because there wasn't enough value to come back to. It validated the design POV I'd raised early, but being right wasn't the point – we now had an enterprise client with a struggling product and a redesign ahead of us.

Designing for a new user group

Designing for New York Life's user base required unlearning almost everything that worked at Addition Wealth. Our original users were tech workers who wanted depth – they'd read the long explainer, play around with the calculator, come back for more. Balance Wellbeing's users were different. Elderly and hourly workers accessing a financial wellness benefit they didn't ask for, on devices they weren't fully comfortable with.

The shift was from education to accessibility. Less information per screen, simpler language, clearer next steps. Addition Wealth rewarded curiosity. Balance Wellbeing had to work for someone who wasn't curious – just confused, and maybe skeptical. That constraint made me a better designer, it forced precision over comprehensiveness.

Challenge

Challenge

The decision to go enterprise wasn't in the design roadmap – it landed at an all-hands when leadership announced we'd be building Balance Wellbeing for New York Life. There was internal debate about whether to white-label our technology at all; nobody wanted Addition to become a dev sweatshop. But our CEO saw it as the unlock for enterprise revenue, and he was right.

For me, the immediate implication was clear: the design system I'd built for a single product now needed to support multiple branded platforms simultaneously. I had days, not months, to make it happen. The saving grace was that I'd been designing modularly from the start – not because I anticipated this pivot, but because clean systems are just how I work. That instinct ended up being the thing that made the enterprise expansion possible.

Conflict

Conflict

Not every enterprise decision was the right one. When scoping Balance Wellbeing, leadership wanted to ship a basic resource library and recycled online calculators – a significant step down from the personalized, advisor-backed experience we'd built at Addition Wealth. I pushed back. Users weren't getting access to financial advisors, the content wasn't personalized, and we were essentially shipping a worse product under a premium brand. But the pressure to close the sale won out.

The result was predictable: engagement tanked. Users weren't returning because there wasn't enough value to come back to. It validated the design POV I'd raised early, but being right wasn't the point – we now had an enterprise client with a struggling product and a redesign ahead of us.

New user group

New user group

Designing for New York Life's user base required unlearning almost everything that worked at Addition Wealth. Our original users were tech workers who wanted depth – they'd read the long explainer, play around with the calculator, come back for more. Balance Wellbeing's users were different. Elderly and hourly workers accessing a financial wellness benefit they didn't ask for, on devices they weren't fully comfortable with.

The shift was from education to accessibility. Less information per screen, simpler language, clearer next steps. Addition Wealth rewarded curiosity. Balance Wellbeing had to work for someone who wasn't curious – just confused, and maybe skeptical. That constraint made me a better designer. It forced precision over comprehensiveness.

Met a lot of awesome people along the way. Here are some shoutouts from my team .ᐟ.ᐟ.ᐟ.ᐟ

Met a lot of awesome people along the way. Here are some shoutouts from my team .ᐟ.ᐟ.ᐟ.ᐟ

“Tim has a great eye for design, and all his work leads to a product that is pleasant to use. He also understands the tradeoff between usability and aesthetics, so when engineers push back on certain design choices because it could cause inadvertent issues, he will go for whatever is best for the user.”

“Tim has a great eye for design, and all his work leads to a product that is pleasant to use. He also understands the tradeoff between usability and aesthetics, so when engineers push back on certain design choices because it could cause inadvertent issues, he will go for whatever is best for the user.”

Robert Ferguson
Staff Software Engineer

“Tim is a talented designer and is very responsive. Whenever I have a question or am looking for a resource he is always helpful. He has helped transform the app and it looks beautiful! It’s a great interface and our clients and anyone who sees the platform can appreciate all of the work he has done!”

“Tim is a talented designer and is very responsive. Whenever I have a question or am looking for a resource he is always helpful. He has helped transform the app and it looks beautiful! It’s a great interface and our clients and anyone who sees the platform can appreciate all of the work he has done!”

Hally Peck
VP of Marketing & Communications
© 2026 Tim Pham · All rights reserved.
© 2026 Tim Pham · All rights reserved.
© 2026 Tim Pham · All rights reserved.