Case Study
Product Finder: Helping new users take their first step with confidence
A scenario-driven redesign that made an intimidating start accessible to new users and got copied by competitors.
The Problem
Summer.fi's Product Finder is where new users decide whether to stay or walk away — and most chose to walk away. I worked with the Design Lead and a researcher to redesign the entry point from the ground up: replacing a filter-heavy table with a scenario-driven interface so users could find the right position without needing to understand the underlying protocols.
Pain Point: Don't know where to start from and which position fits my needs
Old design: Promotion cards showed options without explaining trade-offs. Filters required protocol knowledge most new users didn't have, so instead of narrowing the choice, the page created more confusion.
User feedback revealed a consistent pattern:
New users didn't know which position matched their goal, and the interface gave them no way to figure it out.
The promotion cards at the top surfaced arbitrary options with no context, and the filters (assets, networks, protocols) weren't helpful unless you already knew what you were looking for.
What we learned
We didn't run formal research, but feedback was consistent: users found it hard to choose a position that fit their needs. They knew they wanted to Borrow or Multiply, but they couldn't tell the difference between strategies or what the trade-offs meant for them. The problem wasn't the filters. It was that the interface assumed knowledge users didn't have yet.
Design Solutions
Scenario tabs (Token Farming, Staking Rewards, Restaking, Yield Loops)
We introduced five common user goals as groups to help users take the first step. A user who wants to Yield Loops doesn't need to blindly find positions. They just need to recognize their intent and let the interface do the filtering for them.
Expanded filter row (Collateral, Debt, Protocols, Networks + Strategy chips)
For users who wanted more control, we kept advanced filters. But we moved them below the scenario layer. Power users could still filter by collateral, protocol, or network, even TVL. But that complexity was now opt-in, not the default entry point.
Automation column in the table
One of the most common questions in user feedback was whether automation was supported. We added an explicit Automation column to the table so users could see at a glance which positions supported it. It removed one of the key blockers to opening a position.
