01
About me
I design things that work and look clean
Education
03
Things I believe
Simplicity comes from knowing what to keep, remove, and structure
Great design doesn’t remove complexity for the sake of it. It organizes the right details, reduces unnecessary effort, and makes the next step feel clear.
T.01
Trust is built into the flow, not added at the end
People trust a product when the path feels clear, the information arrives at the right moment, and every step reduces doubt instead of creating more of it.
T.02
Complexity works better when clarity builds over time
Not every detail needs to appear at once. Good design reveals the right information at the right moment, helping people move from understanding to action without feeling overwhelmed.
t.03
Products scale better when the system is designed first
A strong system creates consistency without slowing the product down. It helps teams move faster, reuse patterns, and extend the experience without redesigning from scratch every time.
04
How I work?
What working together actually looks like.
I work closely with PMs and engineers when there’s a team, and own the process end-to-end when working independently, staying close to the product, constraints, and decisions.
H. 01
Discovery in the open
I keep discovery visible and collaborative, sharing early thoughts, questions, references, and tradeoffs so the direction gets sharper before the design gets polished.
H. 02
Decisions documented, not just designed
I don’t just design the final state. I make the reasoning visible, so decisions feel clear, intentional, and easier to build on.
H. 03
Clear specs, fewer gaps
I design with implementation in mind, defining states, specs, components, and context so the work moves smoothly from Figma to build.
H. 04
Support where it matters
I stay close to implementation where the project allows, helping clarify edge cases, states, and interaction details so the final build holds up beyond the handoff.