[
MY PHILOSOPHY
]
Not the patch,
the blueprint.
[
01 / WHERE I WORK
]
Broad enough to connect. Deep enough to solve.
I have worked across B2B, B2C, and B2B2C products, but a recurring pattern is that the products involve many interconnected rules, roles, workflows, and technical dependencies.
I am good at these environments because I naturally try to understand how the pieces affect one another rather than treating a screen or feature in isolation.
I enjoy problems that initially feel messy. Turning fragmented information into a coherent system is energizing to me, and I would like to continue working on complex, high-trust, or platform products.
[
01 / WHERE I WORK
]
Broad enough to connect. Deep enough to solve.
I have worked across B2B, B2C, and B2B2C products, but a recurring pattern is that the products involve many interconnected rules, roles, workflows, and technical dependencies.
I am good at these environments because I naturally try to understand how the pieces affect one another rather than treating a screen or feature in isolation.
I enjoy problems that initially feel messy. Turning fragmented information into a coherent system is energizing to me, and I would like to continue working on complex, high-trust, or platform products.
[
02 / HOW I THINK
]
Patient enough to question. Fast enough to decide.
When a problem is ambiguous, I usually do not start designing immediately. I first collect information and map the relationships between people, workflows, rules, and technical dependencies so I can understand how the system actually works before deciding where to intervene.
I pay particular attention to constraints, but I do not automatically treat every constraint as fixed. I tend to trace a constraint back to why it exists, what problem it was originally meant to solve, and whether that reason still holds. I naturally distinguish between hard constraints that need to be respected and soft constraints that may simply come from inherited decisions, existing processes, or assumptions.
I enjoy balancing competing constraints, but I also enjoy questioning the constraint itself. My goal is to understand what truly has to stay, what may be changed, and then find the clearest path through the system.
[
02 / HOW I THINK
]
Patient enough to question. Fast enough to decide.
[
03 / A RARE SKILL
]
Early enough to shape. Present enough to protect.
I see accessibility as part of product quality rather than a compliance task added at the end.
I enjoy understanding interaction patterns and edge cases that are easy to miss, especially how different people may need to use the same product in different ways.
I have deliberately developed knowledge of accessibility standards, assistive technologies, and implementation, so it has become part of how I design rather than just an area of interest.
[
03 / A RARE SKILL
]
Early enough to shape. Present enough to protect.
[
2019-2026
]
Seven years of transforming lives through designing meaningful experience.
Projects completed with meticulous attention to detail
Client satisfaction through personalized design solutions
Client satisfaction through personalized design solutions
Diverse experience in regulated industries
Delivering transformative experience design
Delivering transformative experience design
[
HOBBIES
]
Hiking
Hiked up a snowy peak of 979m elevation in 4h40min (and much more)
Golfing
Golfed by the gorgeous ocean of Cuba (as a newbie)
Language nerd
Speaks Cantonese, Mandarin, English and Korean (for now)
[
MY TOP TRAITS
]
Absorber. Mapper. Investigator.
Three ways I get to the real problem before I design a solution.
Absorb quickly. Contribute quicker.
Learner
I learn a new system before I'm asked to, apply it before I'm comfortable with it, and share it once I've mastered it. That's how I moved across five domains and stayed useful in every one.
Absorber
Embedder
Grounder
Bridger
Untangle the logic. Align the room.
Discipline
I map the dependencies nobody asked me to map, name the assumptions nobody questioned, and build the template that outlives the project.
Mapper
Framer
Anchor
Codifier
Question the brief. Reframe the work.
Intellection
I question the brief before I accept it, test the assumption before I trust it, and reframe the problem before I solve it. That's how a request for engagement became a fix for compliance anxiety.
Investigator
Reframer
Auditor
Unraveler
Absorb quickly. Contribute quicker.
Learner
I learn a new system before I'm asked to, apply it before I'm comfortable with it, and share it once I've mastered it. That's how I moved across five domains and stayed useful in every one.
Absorber
Embedder
Grounder
Bridger
Untangle the logic. Align the room.
Discipline
I map the dependencies nobody asked me to map, name the assumptions nobody questioned, and build the template that outlives the project.
Mapper
Framer
Anchor
Codifier
Question the brief. Reframe the work.
Intellection
I question the brief before I accept it, test the assumption before I trust it, and reframe the problem before I solve it. That's how a request for engagement became a fix for compliance anxiety.
Investigator
Reframer
Auditor
Unraveler