Spheron Network hero

Lead Product Designer

/

2024 — PRESENT

Spheron Network

Designing the interface layer for the world’s largest decentralized compute network.

Web3 · AI Infra · Product

SNAPSHOT

[ ROLE ]

Lead Product Designer

[ TIMELINE ]

2024 — PRESENT

[ FOCUS ]

Web3 · AI Infra · Product

44,000+

Wallets onboarded

6

Core flows shipped

3.2×

Activation lift

// CONTEXT & PROBLEM

The business and user problem

Spheron Network arrived with a powerful engine but an interface that only insiders could navigate. Growth was capped not by demand, but by how much the product asked people to understand before they could act.

The constraint was trust under complexity: every decision had real financial or infrastructure weight, so the design had to make consequences legible without dumbing the system down.

// ROLE & PROCESS

Role, team & process

I led product design end to end, partnering with two engineers, a PM, and the founder. We mapped the real jobs behind the dashboard, then pressure-tested flows against live user sessions.

Discovery moved fast and messy — whiteboards, clickable stubs, and throwaway prototypes — before we committed to a system that could scale across every surface.

Process shot

Early exploration — mapping the core job.

Process shot

Iteration on the primary flow.

Process shot

Testing hierarchy and states.

// SOLUTION

Solution walkthrough

The final direction reframed the product around a few confident moments: a clear entry point, a single primary action per screen, and status that always answered “what happens if I do this?”

Solution screen

Final home surface with a single clear action.

Solution screen

Detail view with legible status and consequences.

// OUTCOMES & IMPACT

Outcomes & impact

The redesign shipped in stages and held up under real usage — activation climbed, support load dropped, and the team gained a shared visual language to build on.

// REFLECTION

Reflection

The lesson that stuck: clarity is a feature you have to defend every sprint. The hardest work was removing things, not adding them.

// NEXT CASE STUDY

Let’s design something people trust.

START A PROJECT