TT Wallet · Referral · 2022
When growth goals meet new-user trust
Our referral feature brought users in fast and lost them just as fast. It was pulled after two weeks.
Role
Product Designer: research, strategy, UI/UX
Team
Product, Engineering, Marketing
Duration
2 months
2 months
From kickoff to launch
2 weeks
Live before it was pulled
+20%
Monthly actives, first two weeks after launch (token price +16%)
The wrong moment
The team wanted a referral program to bring new users into TT Wallet and drive deposits into TT Mining. The PM owned the business case and the timeline; I owned design research.
I saw a loop with a missing piece
Our loop was missing a key step: onboarding that builds trust. New users were asked to make money decisions right after downloading, with no context.
People signed up quickly, but they didn't understand the product or feel safe yet.
The loop we shipped. Red marks what was missing.
dApp partners
A reason to download TT Wallet
Sign-up that builds trust
Onboarding that explains the product
ThunderCore Ecosystem
Referral
Users share
Show value
Users share returns from TT Wallet
What I did: I mapped the user journey and the growth loop, wrote up the research, and argued that onboarding fixes should ship with the referral feature.
Why the scope didn't change: I tried to get it into scope, but it was too late. The PM had already locked the timeline. I framed my findings in design terms instead of business terms, and I didn't offer a small option that fit the constraints.
My call when the loop was broken
I couldn't change the scope, so I focused on what design could still protect. I had three ways to design the entry point.

Option C · Value-first
Pulled after two weeks
Referral brought a short spike in active users, but they didn't stay. Some left as soon as they got their reward, so the loop never closed. Spend was high and results were low, so the team pulled it after two weeks.
What I do differently now
Timing matters as much as the insight
Research only matters if it lands while the scope can still change. A complete report that arrives late changes nothing.
Translate design language into business language
I talked about a trust gap and cognitive load. The team decided on retention, risk and ROI. Now I bring my findings in their terms.
A year earlier, on Bridge, I got the team to look at risk before scope was set. Here I raised it after scope was locked. That is the lesson: bring risk up early, in the team's language. See the Bridge workshop