There are few things more frustrating for a product designer than watching preventable problems ship.
Every experienced designer has been there. You identify usability issues early, back them with research, present alternatives, and explain the long-term impact on the product. Sometimes those conversations lead to better outcomes. Other times, the business chooses a different direction.
This dashboard is one of those stories.
The screen you’re looking at comes from Spring Financial, where I worked as a UX Manager. During my time there, I advocated for a different philosophy around the product – one that prioritized clarity over marketing, transparency over urgency, and user confidence over visual excitement. Many of those recommendations never made it into production.
I no longer work there, but the product continues to evolve, and looking at this screen today, I still see many of the same design decisions I pushed back against.
This isn’t about claiming I had all the answers. Product development is messy. Every feature is a compromise between engineering, marketing, compliance, executive priorities, and timelines. I’ve worked in enough organizations to know that no single designer gets everything they want.
What interests me is what happens when those compromises begin to outweigh the user experience.
Financial products live or die on trust. Every interaction should make users feel informed, confident, and in control of their money. Instead, this interface illustrates something I see far too often in fintech: marketing objectives competing with usability.
Let’s break down why.
The Dashboard Doesn’t Know What’s Important
Within the first few seconds of opening the screen, I’m pulled in half a dozen different directions. The “NEW!” badge demands attention. A large “$1000” sticker competes with the headline. A flame icon suggests some kind of reward or achievement. A progress bar stretches across the card, while the “Accept Loan” button tries to anchor the entire experience.
Every one of these elements has been designed to stand out, but collectively they compete with each other instead of working together. The result is visual noise rather than hierarchy.
One of the fundamental principles of interface design is that users should instinctively know where to look first. This screen asks them to make that decision themselves, and that’s unnecessary cognitive work.
The Product Loses Trust in Seconds
The most serious issue isn’t visual design – it’s communication.
At the top of the card, I’m told I have a $1,000 loan offer. A few lines later, the interface tells me that I already qualify for a $100 loan.
Those are two completely different messages.
Is the offer worth $1,000? Is my current approval $100? Is the $1,000 a future limit? Is this a promotional badge? Am I supposed to infer the relationship between the two?
Financial interfaces should never force users to interpret critical information. The moment someone has to stop and wonder what they’re actually being offered, trust begins to erode.
This was one of the conversations I repeatedly had while working on the product. Clarity isn’t a nice-to-have in fintech. It’s the product.
Decorative UI Is Not Good UX
One of the more interesting decisions is the progress bar running across the promotional card.
At first glance, it looks functional. Naturally, users assume it represents progress toward something meaningful. But what exactly?
Is it showing approval progress? Eligibility? A loyalty program? Loan utilization? Credit building?
Nothing on the screen explains it.
This is a common design trap. We borrow familiar interface patterns because they look engaging, but we forget that users assign meaning to those patterns. If a progress bar exists, people expect it to communicate progress. When it doesn’t, it becomes decoration masquerading as functionality.
The flame icon suffers from the same problem. It attracts attention, but it doesn’t answer a question or help someone accomplish a task.
Marketing Has Taken Over the Dashboard
A dashboard should answer one question before anything else:
“What do I need to know today?”
For someone with an active loan, the priorities are fairly obvious. When is my next payment? How much do I still owe? What’s my remaining balance? Have I missed anything important?
Instead, the first thing users see is another loan offer.
That tells me the interface has been optimized around acquisition rather than customer management.
There’s nothing inherently wrong with cross-selling financial products. Every lender does it. The problem is when promotional content becomes more prominent than the information users actually came to see.
Helping someone manage existing debt should always take priority over encouraging them to take on more.
Good Design Doesn’t Need to Shout
As I continued reviewing the screen, another pattern became obvious. Almost every element is trying to create urgency.
There are multiple font weights competing within the same paragraph. Bright promotional badges overlap content. The oversized “$1,000” sticker demands attention. Purple dominates almost every major component. Even the decorative graphics compete for visual priority.
None of these choices are objectively wrong in isolation. Together, however, they create an interface that constantly asks for attention instead of guiding it naturally.
Good interfaces don’t shout.
They lead.
Trust Should Come Before Conversion
Perhaps the biggest missed opportunity is the call to action itself.
The interface asks users to “Accept Loan” before providing any meaningful context about the product they’re accepting. Important information like repayment terms, interest rates, fees, or total borrowing costs is nowhere to be found on this screen.
Whether those details exist later in the flow isn’t really the point.
The first impression establishes trust, and trust is built through transparency – not urgency.
Users shouldn’t feel like they’re clicking a marketing campaign. They should feel like they’re making an informed financial decision.
The Bigger Lesson
One of the hardest realities of working in product is accepting that not every recommendation gets implemented.
I’ve worked with brilliant engineers, marketers, and executives throughout my career. I’ve also sat in countless meetings where user research lost to quarterly goals, accessibility lost to deadlines, and usability lost to conversion metrics.
That’s not unique to Spring Financial. It happens across the industry.
The reason I’m writing this series isn’t to settle old scores. It’s because these conversations rarely happen publicly. We celebrate polished case studies after products succeed, but we rarely examine the everyday decisions that slowly introduce friction into an experience.
Those are the moments designers learn the most from.
This dashboard is one of those moments for me.
Not because I think I would have designed the perfect solution, but because I remember sitting in those discussions, raising many of these exact concerns, and understanding what the product could have been if user experience had carried a little more weight.
