View Case Study

Pier Two

I challenged the core logic of a staking platform and reshaped its architecture to support 15+ networks

Pier Two is a blockchain infrastructure provider offering non-custodial staking for institutional clients. At the center of the product is the Control Centre — the primary tool where users manage digital assets, staking, unstaking, and monitoring positions in real time across protocols and accounts.

I led the redesign of Pier Two’s Control Centre, initially focused on improving the UX of complex staking workflows. But the experience kept breaking as new networks were added. So I restructured the product to support multi-network staking at scale.

Scope
  • Design audit
  • UX/UI design
  • Prototyping
  • Design System
Role
  • Product Designer
Problem
The more networks the platform supported, the less reliable the experience became. The problem wasn’t that staking was inherently complex. It was that the product was structured in a way that made complexity harder to handle:
  • No shared mental model across networks
  • Account-first structure fragmenting the system view
  • Limited portfolio visibility across accounts and networks
Ultimately, the Control Centre wasn’t built to support multi-network staking at scale. That meant every new network added more friction, more adaptation, and less clarity for the user.
Solution
Instead of improving individual screens, I restructured the product — shifting from an account-first model to a network-centered architecture. This created a shared mental model across protocols, reduced relearning, and made staking operations consistent as new networks were added. I replaced fragmented, modal-heavy flows with a step-by-step experience in a single view, making system states and actions easier to understand. The result is a product that scales without increasing complexity.
Product breakdown
Research and internal flows are under NDA — what follows focuses on the final product decisions and their impact on the experience
This shift reshaped three core areas of the product:
  • How users orient across networks
  • how staking actions are executed
  • how positions are monitored over time
Log In screen
Choosing account type
01. Dashboard
The dashboard shifts the product from fragmented account-by-account monitoring to a clearer cross-network view. It gives users a consolidated picture of stake metrics, recent actions, and positions in progress — reducing the visibility gaps that made the system harder to operate at scale.
Earnings view Dashboard (Portfolio) screen
Dashboard stakes manager
Dashboard staking in progress
02. Stake
The staking flow replaces cluttered, modal-heavy interactions with a step-by-step experience in a single view. Protocol information, required inputs, and system states are revealed in sequence, creating a more consistent model for execution across networks.
Stake screen including all available protocols
Staking flow
Deposit confirmation in progress
Completed transaction
03. Account
The account section turns scattered staking positions into a structured operational view across networks. By combining portfolio-level insights with detailed tables, it supports monitoring, analysis, and unstaking decisions without forcing users to reconstruct the system from disconnected screens.
Account Overview empty state
Account selected
Account selector default state
Switching between accounts
Account Reporting empty state
New report created
Unstaking wallet connection
Unstaking flow
The system
To support the new architecture, I built a modular design system that could scale as new networks were added while keeping interactions and data patterns consistent across the product.
Within Figma, this translated into a flexible component system of over 100 components, making complex product states easier to assemble, maintain, and extend across flows.
result
My work enabled Pier Two to scale across 15+ networks without adding complexity to the experience. What started as a structural fix became the foundation the product needed to grow — giving both users and the team a consistent model to operate, extend, and build on.
Next Case