2015 — 2026 · Ho Chi Minh City
No case studies. No gallery. Just the trade-offs I faced and the calls I made — from a legal-tech startup to a game millions of people played.
About
How I think about product
Product is the job of seeing the trade-off clearly, making the call, learning from what the data says — and doing it again.
Make the call with what you know. Own it out loud.
Every good option costs something. Name what you're giving up.
Let the data and the users tell you if you were right.
Take what you learned into the next decision.
Ten times over ten years. Here's each one.
Part one · 2015 — 2019
A legal-tech startup building software for private capital transactions. Engineers everywhere, design still finding its place.
Define what design means here — not just what to design.
Ship more screensvs.define what "good" looks like
To make sure what shipped actually matched the design standard we had set, I stopped handing off designs and built most of the product's front-end myself.
Own the outcome, not the artifact.
Time spent designingvs.a product that matched the design
Part two · 2019 — 2025
Its first product designer — three months before Axie Classic, the company's first game, went live. A tiny team building a game where players owned their creatures. No playbook existed yet.
Bet on something nobody had a name for yet.
A stable path in legal-techvs.an unproven team, pre-launch
A small team that really cares is the fastest team there is.
I designed version one. It was rough — but the layout made buying and selling NFTs obvious, and that's the part other NFT sites cloned.
Clarity before polish. Polish can wait. Trust can't.
Visual polishvs.a clear market, live sooner
There will always be something to fix. Don't wait for perfect — ship, and let real use test the direction.
I built the Product Design team — and still shipped key Web3 products myself: the Ronin explorer, the bridge, the Axie Marketplace and staking.
Scale judgement, not just headcount.
Doing the work myselfvs.building people who could do it without me
Letting go of my own design work was hard. It gave back far more than I expected.
06 · 2021
The company grew faster than any org chart could hold. Ronin and Axie split into separate squads.
Own Axie Web3 end to end. Advise Ronin until it had a product leader of its own.
Breadth across every productvs.depth where it mattered most
Head of Product, Axie Web3 — app.axieinfinity.com, staking, and the economy around every Axie. And from 2021, I managed Axie's product and graphic design team — 3 graphic and 3–5 product designers.
Move from design into product — and own the outcome, not the pixels.
The craft I was known forvs.the problems that mattered more
A clear direction beats a pile of nice features. Connect the dots across the system first.
08 · 2022 — 2024
The market turned and trading dried up. Plenty of people still played Axie Origins — they just never touched the chain. I worked with the game team on retention, and built Bounties: on-chain quests made for people who only played the game.
Stop waiting for traders. Bring Web3 to where the players already were — inside the game.
Wait for the market to come backvs.give the players we still had a reason to go on-chain
You can't predict the market. You can adapt to it — there's always another way in.
A new MMO for the Axie world. I managed 2 PMs across the web app and the game. When the demo deadline slipped, I stepped in as PM, cut a new NFT character and player-owned land, moved the date publicly with the community — and shipped the first playtest. I also planned the pre-registration page and ran the campaign with Growth.
Cut scope, not trust.
The full visionvs.a date the community could trust
Set KPIs and deadlines carefully. And only promote someone to lead after they've shown they can.
10 · 2025 — 2026
Years of leading teams had moved me away from what got me into product: turning an idea into something people can use. AI changed the cost of doing that. One person can now research, design, code, test and ship at a speed that used to take a team.
Get dangerous with the tools again. Not to become an AI expert — to close the distance between an idea and a shipped product.
Stay the leader who directs buildersvs.become a builder again
My sense of “that'll take a sprint” has changed for good. I'll bring that to the next team.
So I started building
Problem → Product → Design → Code → Deployment
No designer to brief.
No engineer to hand off to.
No org chart to hide behind.
Just an idea and the responsibility to make it real.
Fast, text-first nutrition tracking in Vietnamese and English.
Open · sign-in ↗ 02My son's first year as a 3D universe — every photo a star, every month a world you can fly into.
Open ↗ 03A job-fit quiz that shows which roles fit how you actually work.
Open ↗ 04A baby meal planner: porridge and baby-led weaning, balanced and age-safe.
Open ↗11 · Now
I'm looking for a product worth spending the next few years building.
Talk to Leoh →
