Redesigning a Web3 ecosystem around trust

MINGO was expanding from a digital wallet into a wider Web3 ecosystem spanning assets, ticketing, collectibles and marketplace experiences. The wallet sat at the center, but the product felt assembled in separate eras rather than designed as one connected service.

The original request sounded visual: modernize the interface and make the experience consistent. The audit revealed a more important challenge. Users were being asked to perform unfamiliar, financially sensitive actions without always receiving enough guidance, confirmation or visible protection.

The project became a redesign of trust—not only a redesign of screens.

MINGO first hired me to redesign its landing page and marketing experience. That narrower project shipped and demonstrated how an audit-first approach could create a clearer public product story.

The engagement then expanded into the work carrying greater product risk: the wallet, onboarding, transactions, ticketing and collectibles. That sequence mattered. Responsibility for a financial product was earned through delivery rather than assumed at the start.

I resisted redesigning on instinct. Instead, I reviewed the live experience screen by screen and documented where users could lose clarity, confidence or control.

The audit evaluated four dimensions: clarity, consistency, feedback and risk. This separated cosmetic inconsistencies from problems that could affect a user’s money, account access or understanding of what had just happened.

The visible inconsistency was a symptom. The deeper issue was that trust-critical moments had not been designed as complete journeys.

There was no deliberate pause before some irreversible actions, transaction outcomes were not always explicit, and sensitive wallet information lacked a clearly bounded access pattern.

The short timeline meant that every stakeholder preference could not become a new design direction. I introduced four shared principles that the team could use to judge screens, flows and implementation tradeoffs.

The audit uncovered more issues than the four-week engagement could responsibly solve. I prioritized journeys by user-trust risk and product impact instead of treating every screen as equally important.

The wallet needed to support asset management while also connecting users to tickets, marketplace and collectibles. I treated it as the primary home base, with ecosystem products revealed as connected destinations rather than competing navigation structures.

The new hierarchy separated wallet actions, ecosystem destinations and account or security controls so users could understand both where they were and where they could go next.

Onboarding was redesigned as a guided sequence rather than a dense setup form. The experience explained value first, reduced unnecessary choices, introduced security in context and ended with a useful next action.

Sending digital assets was restructured into three distinct moments. Each stage answered a different user question and reduced uncertainty at the highest-risk point in the wallet.

Security was treated as a product behavior rather than a settings screen. The amount of friction matched the potential consequence of the action.

Once the critical journeys were structured, I standardized typography, spacing, action hierarchy, forms, feedback states, cards, navigation and responsive behavior.

Consistency was not cosmetic polish. Shared patterns reduced relearning for users and reduced the number of one-off solutions engineering needed to maintain.

The project delivered redesigned priority flows, visible security patterns and a reusable visual language across MINGO’s web and mobile experience.

The visible inconsistencies were real, but the more important gaps appeared where users had to understand risk, make a commitment and trust the result of an action.

The project reinforced three habits: audit before assuming, prioritize by consequence and make security understandable.

Given more time, I would conduct structured usability testing with both experienced Web3 users and people creating their first wallet, establish baseline metrics and compare error recovery across the redesigned flows.