ThunderCore · Bridge · 2021

A workshop that put risk disclosure before a UI refresh

Bridge was treated as a product to keep running, not one to invest in. I designed and ran a company-wide workshop that changed what the team fixed first.

Role

Product Designer: workshop design and facilitation

Team

PM, Engineering, BD, Marketing, Operations, Leadership

Duration

2021

UX StrategyCross-functional alignment

$10M+

Cross-chain assets migrated (platform scale; $10M+ of a $40M goal)

The workshop

Everyone wanted to spend on new things

Bridge mattered, but the team was focused on new growth and saw only an outdated UI. To me, its real job was holding users' trust as they entered the ecosystem.

Main competitor

BNB Chain Bridge

BNB Chain Bridge

Modern interface, familiar to most users.

Our product

ThunderCore Bridge (Old UI)

ThunderCore Bridge (Old UI)

Outdated interface, but familiar to long-time users.

Users had to make risky calls on their own

A wrong chain, asset, or address often means the money is gone, and users couldn't easily confirm they had it right.

The points in the flow where users make a judgment

I marked each point where users have to make a judgment, then decided what to show earlier and what to block until it was clear.

Before talking about speed, I showed the team the risks

If we talked about the UI first, the team would drift back to "faster and newer." So I used a metaphor: we kept fixing the boat, but the risk was in the sea.

$40M goalUSD to migrate
Thrust
⚠️ Resistance

I redesigned the conversation first

I ran a company-wide workshop around one question: is Bridge a legacy tool to maintain, or infrastructure that holds user trust?

  1. Diverge

    Everyone wrote Bridge a break-up letter

  2. Synthesize

    How might we, tested on one hard case

  3. Decide

    A fake $100 each to fund one fix

March 2021, about two and a half hours, around 15 people: the company's first product workshop open to everyone. It ended with needs, pain points and solutions on one board.

The workshop in progress

The team changed its priorities

After the workshop, the team saw Bridge as infrastructure that shapes user trust. The question moved from "Should we fix Bridge?" to "What do we fix first?"

Key insight

“Some problems have to be fixed first, or new growth won't hold.”

Then I fixed the points where users decide

I didn't redesign everything. I changed only the steps where users make judgments, and those fixes went into a sprint and shipped.

·

Clearer balance display

·

Min and max limits shown up front

·

Clearer address hints

·

No action until conditions are met

The four fixes shipped in the next sprint. The question the team asked had changed, and that was the outcome I was after.

Reflections

Two things I learned on a product kept in maintenance mode

  • When a team won't fix something, change the question first

    The team saw Bridge as an outdated UI, so no one thought it was worth the effort. I asked whether it was a legacy tool to maintain or infrastructure that holds user trust, and the talk moved from "should we fix it" to "what do we fix first".

  • Letting people see it works better than persuading them

    The break-up letters had everyone name Bridge's problems in their own words, and the fake $100 had each person pick one fix to fund. Four fixes shipped in the next sprint.