Role
Product Designer
Conn's was migrating to a new codebase to cut costs and adding a third financing offer the existing checkout couldn't hold. I redesigned how customers compare and choose a credit offer at checkout — and built the single source of truth that made the migration possible.
Conn's was switching to a new codebase to reduce costs — and at the same time, adding a third financing offer.
The prequalification page saw heavy traffic, and flexible payment options had a real impact on sales, so credit selection was a high-stakes surface. Two things stood in the way of getting it right.
I made the fragmented picture my first job. I created a dedicated Figma file that centralized and organized every credit possibility in one place — the resource development had been missing.
From there, I ran user testing across multiple design options to make sure the interface we chose actually resonated, and partnered with the product manager to reassess and redesign the credit offers and the checkout elements around them.
The business was moving from two financing options to three. The checkout design at the time simply wasn't user-friendly enough to fit a third offer cleanly.
An early attempt to rework the existing design just felt cluttered — and clearly wouldn't hold up on mobile. So the product manager and I rethought the flow from scratch around one question: how does someone compare three offers and confidently pick one, without the page collapsing into noise? That question pointed us toward a modal experience.
▸ Drop in your screen — the early rework that felt too cluttered
I led the testing phase. We introduced a modal built specifically for customers who had already prequalified at Conn's: as they moved from billing to payment, it surfaced the available credit offers to choose from. The open question was how to lay those offers out, so I tested two versions of that screen — offers side by side, and offers stacked — to see which made comparing easier.
▸ Drop in your two tested layouts
The side-by-side comparison became the direction we carried forward — letting customers weigh all three offers against each other at a glance before selecting one and continuing to payment.
▸ Drop in your final screen — "Select an offer to use at checkout"
Alongside the design work, I spent three weeks preparing a detailed document for the development team — the end-to-end map of every credit possibility the migration needed to account for. The testing moved the product team toward an improved experience, with ongoing initiatives like going deeper on the mobile flow.
The checkout enhancement is still in progress. Completing the code migration, though, was a clear milestone — and the results below come from that.
Eliminating duplicative coding efforts across multiple platforms streamlined operations and reduced the team's workload.
A unified codebase made updates, maintenance, and troubleshooting more efficient going forward.
Resources were optimized and development focused on a single, unified solution.
Mapping every credit possibility into one place did double duty.
It gave development the single source of truth the migration needed, and it gave the design a solid foundation to build the third offer on. Neither would have gone smoothly without it.
That's the part I keep coming back to across my work: the unglamorous structural artifact that makes everything after it easier. Next up is bringing the same clarity to the mobile checkout experience.