Helping customers understand
what Sezzle Up reports
Role
I owned enrollment and reporting design, from framing the customer understanding gap to defining the content hierarchy and interactions. My work combined AI-assisted investigation with product judgment to make credit reporting easier to understand and inspect.
Outcomes
+36.6%
Higher enrollment conversion in the first three full days after launch
Timeline
12 weeks
Team
Product, Product Marketing, Creative, and Engineering
Tools
Figma, UserTesting, Claude, Chatgpt, Rive
AI in my design workflow
01.
Understand reporting
AI support
My contribution
Set information priorities around monthly status and details on demand.
02.
Shape the experience
AI support
Sourced calendar and status references via Claude + Mobbin MCP; generated states from my designs and scenarios to identify gaps.
My contribution
Defined scenarios, hierarchy, and the month grid; checked state coverage, logic, and design-system fit.
03.
Test and refine
AI support
Organized testing transcripts into themes using my reusable AI analysis skill
My contribution
Checked themes against participant evidence, refined the AI analysis skill, and selected design changes.
Phase 1 · Enrollment
Remove requirements that kept customers from enrolling, and take customers straight into enrollment
We removed two enrollment requirements: completing and paying off an order, and connecting a checking account. Both were internal risk controls, not credit bureau requirements. I redesigned the entry flow to take customers directly from the landing page into enrollment, replacing a checklist.
Before · Choose a setup task
Customers selected individual requirements from a checklist to begin setup.
After · Start enrollment directly
“Join for free” takes customers into the enrollment steps, beginning with identity verification.
Phase 2 · Reporting
01 · Problem
Enrollment did not mean customers understood the service.
Product Marketing’s survey showed that many enrolled customers did not understand Sezzle Up’s credit-reporting role. The reporting redesign needed to address that gap: help customers understand what the service does after they join.
27%
Knew Sezzle Up reports payments to credit bureaus.
35.6%
Wanted to know which purchases count toward credit.
Enrolled respondents, n = 503 · June 2026. Figures reproduced in the supplied GTM survey summary; raw responses and exact question wording were unavailable.
The dashboard needed a purpose beyond displaying data.
I took the survey as a reason to make Sezzle Up’s activity understandable. It established the need for clarity; deciding what to explain required a closer look at the reporting mechanics.
The existing Sezzle Up reporting overview screen
03 · Defining content priorities
Ground the overview in what Sezzle actually reports.
The SVP’s Claude-generated concept provided a starting point for content. I used Claude to retrieve internal documentation and understand what Sezzle reports and how it relates to customers’ payment activity. This informed my decision to prioritize payment history and select key details for each monthly summary.
My direction: help customers understand what Sezzle reported, and when.
Content reference · SVP’s Claude-generated concept
04 · From content priorities to information hierarchy
Payment history first. Detail when customers need it.
I used the reporting mechanics to rank the proposed content by its relevance to customers. My sketch turned that judgment into three layers: payment history to scan, a monthly summary to understand, and the complete record to verify.
PRIMARY
Reporting history first
I prioritized credit reporting history because it matters most to customers.
ON SELECTION
Monthly detail on demand
Selecting a month reveals key reporting details, including balances, credit limit and account status.
OPTIONAL
Full record for verification
A secondary link lets customers compare the complete record with their credit report.
Early wireframe: Reporting history → monthly summary → full record.
05 · The reporting experience
Track progress. Inspect each month.
Check credit progress and select a month to review reporting status, credit usage, and payment details.
Overview and monthly reporting history.
Explore the details behind the overview.
Explore score changes, understand contributing factors, and inspect the complete reporting record.
Supporting views, available when customers want more detail.
Reflection & next steps
Making reporting visible is only the first step.
This project reinforced the need to distinguish payment activity from what was actually reported. With the reporting overview awaiting implementation, I would next test whether customers can explain each month’s status and understand which payments count.