Context
At DFINITY, I work on products where the interface has to explain how the underlying system behaves: accounts, identities, balances, transactions, governance actions, network data, permissions, and error states.
The Internet Computer ecosystem spans wallets, identities, governance, network data, tokens, subnets, developers, community products, and launch communication. The system is powerful, but people need to understand what is happening before they move funds, vote, delegate, interpret metrics, or act on irreversible states.
My role
My work connects product direction, technical constraints, interface patterns, prototypes, design systems, implementation support, launch assets, and QA across multiple product surfaces.
The shared challenge is not only making each screen understandable. It is helping product, engineering, marketing, leadership, and community communication stay coherent while the system underneath keeps expanding.
Product threads
OISY Wallet
I lead product design for OISY Wallet, shaping wallet flows where balances, recipients, fees, networks, confirmations, and transaction states need to be clear before users move funds.
ICP Dashboard
I contribute to the Internet Computer Dashboard, reframing network data, subnets, tokens, and ecosystem discovery from raw metrics into clearer product comprehension.
NNS Governance
I have also worked on Network Nervous System product design, where voting, delegation, proposals, rewards, permissions, and consequences need explicit product states.
Ecosystem touchpoints
Other contributions include InternetComputer.org, Internet Identity, design systems, launch assets, and special projects that help product, engineering, marketing, and community teams explain the ecosystem more clearly.
What had to stay visible
The design work often depends on mapping system behavior before interface polish: account states, identity states, permissions, balances, proposal consequences, network health, data relationships, loading states, failure modes, and support-facing explanations.
What this work is really about
The common thread is making technically complex product systems understandable enough to use safely and explain honestly.
For wallets, that means users should know what they are about to send, where it goes, what network or fee is involved, and what happened after confirmation. For governance, that means actions and consequences need to be explicit before people vote or delegate. For dashboard data, that means metrics need enough structure for people to build a mental model of the network, not just inspect numbers.
Artifacts and product decisions
The strongest artifacts in this work are not only final screens. The useful artifacts are the ones that reduce ambiguity before engineering commits:
- product frames and decision notes
- state maps for flows and edge cases
- before and after navigation structures
- prototypes for critical wallet and governance actions
- reusable interface patterns for repeated system states
- launch assets and product language that keep the product explainable
I joined DFINITY as a full-time employee in 2022, but I previously contributed as a contractor.