All projects

Home Equity & Home Refinance

Math that usually takes a spreadsheet or a broker, answered in seconds inside the NerdWallet app.

Role
Senior Product Designer
Timeline
2026
Platform
Mobile (iOS + Android)
Team
Product Designer, Product Manager, Engineering, Content

Overview

Two complicated financial features with the same job: help people understand a home equity or refinance decision at a glance. I designed both end to end, from lo-fi to handoff. They shared one product pattern, so I solved it once and applied it twice, giving each its own identity.

Product DesignMobileFintechHome EquityRefinance

Context

Two financial features, one underlying problem. A calculation that normally takes a spreadsheet, a broker or a call to the bank had to become something anyone gets in seconds, inside the app.

Home Equity shows how much of their home's value people have already "unlocked" and what they can do with it: a loan, a line of credit or a cash-out refinance. Home Refinance asks the opposite: "is today's rate better than mine, and is it worth switching?" Both came from the same kind of brief and follow the same product flow. I treated that as an advantage and solved the pattern once.

Process

There was no brainstorming phase. We went from the brief (business and requirements docs) straight to lo-fi, then hi-fi, with two sprints per stage. That changed how I worked. Instead of exploring widely and then converging, the job was constant translation and refinement, with frequent check-ins with PM, engineering and content to validate state logic, copy and feasibility before each phase. The final handoff covered every screen state, data variation and edge case, not only the happy path.

With no room for big explorations, each screen came down to one question: what does this person need to understand first, and what can wait?

The shared flow

Both products enter the app the same way:

Home (or the relevant tab) → contextual entry card → dedicated L2 product page

The entry card is never generic. In Home Refinance it sits inside the loans dashboard and leads with the conclusion ("today's rates are lower than yours, here's what that means"), with the estimated new rate and monthly savings up front. People can tell whether it's worth a look without tapping anything. In Home Equity the card only appears when it has something to say: it's hidden if no property is linked, changes state while equity is being calculated, and shows the full version only once there's enough data. The screen never promises what it can't deliver yet.

The L2 is where the complexity gets organized. Result first, front and center. Then the explanation, then the action.

Home Equity: UI decisions

The L2 opens with a dark green header and a gauge showing how home value, loan balance and available equity relate. In text that ratio would take a full sentence; as a shape it reads in under a second. The supporting numbers (equity, balance, home value) sit right below in a secondary level. Nobody needs them to get the message, only to double-check it.

Next comes a "borrowing power" card that turns the abstract number into something usable: how much the person could borrow. Below it are the product options (home equity loan, HELOC, cash-out refinance), each with one short, jargon-free line on when it makes sense. Educational cards close the screen for anyone who wants to learn more before acting, and stay out of the way for people who already know what they want.

Home Refinance: UI decisions

Here the hard part was trust, not visuals. To calculate a new rate the product needs credit data, and that's usually when people get nervous. Instead of a cold form, I designed an activation bottom sheet that frames the ask around the benefit ("let's grab your mortgage details via credit tracking"). People who want details get an inline "why do we need this?" link. People who just want to know it's safe get a reassurance line right under the main button ("your information is always protected").

After activation, the rate comparison follows the Home Equity logic: result first (current rate, new rate, estimated monthly savings), details after (lender, term, balance). Less common cases, like several linked mortgages, a very long lender name or a new rate that's higher than the current one, were designed as variants from the start instead of patched in later.

Simplifying the complex

One principle ran through both projects: never make people do the math. Whenever I could show a raw number or a ready conclusion, I picked the conclusion. "Your rate could drop to 6.2%, about $148/month in savings" says more, and faster, than an amortization table. The visualizations (the equity gauge and the loan trend chart) carry weight that text usually has to, and the interface only goes one level deeper when someone asks for it.

States and handoff detail

I documented every state for each product: default page, next-step tip, loan paid off, low equity (under 15%), calculation error and legal disclaimers. Refinance added pending credit activation, activation with no open mortgage, and a new rate higher than the current one. Mapping all of this in lo-fi saved rework in hi-fi, and engineering had a complete spec before the first build sprint.

Next project

Charts: data visualization component library