Sprint 1 โ€” UX Narrative

A Day in the Life of Alex Rivera

How a 24-year-old college student uses BudgetPlanner across one ordinary Friday โ€” and why every screen in the prototype exists.
Document TypeUX Scenario Narrative
ProjectBudgetPlanner โ€” Class Project
Sprint1 of 4 โ€” Planning
DateMarch 2026
๐Ÿ‘ค
Alex Rivera
Primary User Persona
Alex is a 24-year-old junior studying Computer Information Systems at a state university. They work 20 hours a week at a campus IT help desk earning about $1,550/month, plus occasional freelance work. Alex graduated high school with no financial education, carries $18,500 in student loan debt, and has $2,840 on a Chase credit card from a rough semester. They want to save for a spring break trip and eventually move into their own apartment โ€” but always feel like the money just disappears before the month ends.
Young Professional Student Debt Credit Card Balance Irregular Income Savings Goal

The Five Screens

Each screen in the prototype maps to a real moment in Alex's day

๐Ÿ‘‹
Onboarding
Screen 1
๐Ÿ“Š
Dashboard
Screen 2
๐Ÿ’ณ
Transactions
Screen 3
๐Ÿ“‹
Budgets
Screen 4
๐ŸŽฏ
Goals & Debt
Screens 5โ€“6

Friday, March 6, 2026

From morning coffee to bedtime โ€” Alex's financial moments throughout the day

7:45 AM
1
โ˜•
๐Ÿ“ฑ Screen 1 โ€” Onboarding
Alex hears about BudgetPlanner from a friend
Alex's roommate mentions they've been using BudgetPlanner to finally stop overdrafting. Alex downloads it over morning coffee, skeptical but curious. They've tried Mint before โ€” it was confusing, full of ads, and eventually just stopped working. They don't want to link their bank account to yet another app they'll abandon in a week.
Why Onboarding Exists

The 4-step onboarding screen needs to answer Alex's three unspoken questions immediately: What does this do? Do I have to connect my bank? Is this going to be complicated? Each step addresses one of those fears, building trust before asking Alex to create an account. The progress dots show it's short. The copy emphasizes "no bank link required."

UX decision: Onboarding comes before signup. Forcing account creation first is the #1 reason users abandon apps. Show value first, ask for commitment second.
9:15 AM
2
๐Ÿ“Š
๐Ÿ“Š Screen 2 โ€” Dashboard
First paycheck of the month lands. Alex checks the dashboard.
Alex gets a direct deposit notification โ€” $1,200 from the IT help desk. They open BudgetPlanner and see the dashboard for the first time with real data in it. The net remaining number hits differently when you can actually see it: $813 left after known expenses. That's more than Alex expected. But the spending chart shows $163 already spent on shopping โ€” and it's only March 6th.
Why the Dashboard Exists

The dashboard is the "front door" โ€” it answers the one question every user has every time they open the app: Am I okay right now? The four stat cards (income, spent, remaining, savings rate) are ordered intentionally: good news first (income), then reality check (spent), then the number that matters most (remaining), then the habit goal (savings rate). The donut chart makes categories scannable in under 3 seconds.

UX decision: The dashboard shows a savings rate %, not just a dollar amount. Percentages are motivating and comparable across income levels โ€” they create a habit goal ("I want to hit 20%") instead of just a number.
12:30 PM
3
๐Ÿ•
๐Ÿ’ณ Screen 3 โ€” Transactions
Lunch at Chipotle. Alex logs it immediately.
Alex grabs a burrito bowl for $14.75. They open the app and tap "Add Transaction" before even finishing the meal. This is the habit they're trying to build: log it now, not at the end of the month when they can't remember where $400 went. They categorize it as "Dining Out," enter the amount, and see a green toast confirmation pop up.
Why Transactions Exist

This is the core input mechanism โ€” the app is only as useful as the data you put into it. The add-transaction flow is deliberately minimal: type, category, amount. Three fields, one tap. The category dropdown doubles as a budget tracker input โ€” every transaction logged here automatically feeds the budget bars on the next screen. The full transaction list gives Alex a searchable, scrollable record of every dollar.

UX decision: The "Add Transaction" button is always visible in the top-right of every screen โ€” not buried in a menu. Speed of logging is critical. If it takes more than 10 seconds, users stop doing it.
2:00 PM
4
๐Ÿ“‹
๐Ÿ“‹ Screen 4 โ€” Budgets
Alex checks budgets after lunch โ€” and gets a wake-up call.
After logging the Chipotle transaction, Alex taps over to the Budgets screen. The "Dining Out" card shows $121 spent of a $150 limit โ€” and it's still the first week of the month. The status badge reads "Near limit" in yellow. Alex stares at it for a moment. There are still three more Fridays this month. They set the limit down to $100 next month and make a mental note: cook more.
Why Budgets Exist

A transaction list tells you what happened. A budget tells you what's about to happen. The budget screen shifts Alex from reactive to proactive โ€” seeing "near limit" on March 6th changes behavior for the rest of the month. Color-coded status (green / yellow / red) makes the signal immediate without requiring any math. The progress bar is the most important element on this page: it externalizes a number that would otherwise live only in Alex's head.

UX decision: Warnings appear at 80% of the limit, not 100%. By the time you're at 100%, it's too late to change behavior. The goal is to interrupt the pattern before it becomes a problem.
6:30 PM
5
โœˆ๏ธ
๐ŸŽฏ Screen 5 โ€” Savings Goals
Payday treat: Alex moves $40 toward the spring break trip.
It's Friday night. Alex got paid, stuck to a budget today, and feels good about it. They open the Goals screen, find the "Spring Break Trip" card sitting at 77%, and tap "Add Contribution." They type $40 โ€” not a lot, but the progress bar nudges from 77% to 82%. Something about watching that bar move is deeply satisfying. Alex screenshots it and sends it to their travel group chat.
Why Goals Exist

Budgets prevent bad spending. Goals create a reason to save. Without a concrete target, "saving money" is abstract and easy to skip. The goals screen makes saving tangible: a named thing, an emoji that makes it feel real, a percentage that moves when you contribute. The visual progress bar is the most motivating element in the entire app โ€” it turns a financial behavior into something that feels like a game.

UX decision: Goals use emojis, not icons. This sounds trivial, but it's not. An emoji makes a goal feel personal and specific. "๐Ÿ–๏ธ Spring Break Trip" creates a stronger emotional anchor than a generic vacation icon.
10:15 PM
6
๐Ÿงพ
๐Ÿงพ Screen 6 โ€” Debt Planner
Late night, can't sleep. Alex opens the debt planner.
It's 10pm and Alex is doing what most 24-year-olds do late on a Friday โ€” lying in bed, anxious about money. The credit card balance has been sitting at $2,840 for six months. They open the Debt Planner, switch from Snowball to Avalanche method, and drag the extra payment slider from $0 to $100/month. The payoff estimate drops from 4 years to 2 years 1 month. Alex didn't know $100 extra could make that much difference. They set a reminder to add $100 to the Chase card next payday.
Why the Debt Planner Exists

Debt is the most emotionally charged part of personal finance. The debt planner doesn't just show the problem โ€” it shows the path out. The slider is the key UX element: it makes the relationship between extra payments and time visceral and immediate. Every $25 you drag on that slider shaves months off your payoff date. The avalanche vs. snowball choice respects that different users respond to different motivations (math vs. momentum).

UX decision: Show the interest paid, not just the payoff date. "$4,200 in interest saved" is more motivating than "2 years 1 month." Loss aversion is a stronger motivator than abstract timelines.

Screen-to-Scenario Summary

Every screen justified by a real user need

# Screen Alex's Need Key UX Element Time of Day
1 Onboarding "Is this worth my time? Do I have to connect my bank?" 4-step walkthrough, no login required 7:45 AM
2 Dashboard "Am I okay financially right now?" Net remaining stat, donut chart, quick summary 9:15 AM
3 Transactions "I just spent money โ€” let me log it before I forget." 3-field add form, instant toast confirmation 12:30 PM
4 Budgets "Am I on track this month, or about to blow my budget?" Color-coded progress bars, near-limit warnings 2:00 PM
5 Savings Goals "I want to save for something real โ€” let me see progress." Emoji goals, contribution modal, animated progress bar 6:30 PM
6 Debt Planner "When will I be out of debt if I pay a little extra?" Extra payment slider, avalanche/snowball toggle 10:15 PM
๐Ÿ’ธ
The Goal of BudgetPlanner
Alex doesn't need a financial advisor. They need a simple, honest tool that shows them where their money goes, warns them before they overspend, and gives them a clear path to their goals. BudgetPlanner is that tool โ€” designed around real moments in a real day, not around features on a product roadmap.