(01)
About me
I am a product designer that believes in looking at the full picture, aligning user needs, business goals, and technical constraints into cohesive, scalable solutions. I believe strong product design comes from understanding the entire product ecosystem and shaping thoughtful design processes that support long-term growth.
Driven by curiosity and continuous learning, I enjoy exploring ideas across disciplines and translating them into clearer product thinking. I thrive in collaborative environments, value teamwork as a catalyst for growth, and am seeking a long-term role where I can contribute meaningfully, grow alongside the product, and help shape impactful user experiences.
(01)
About me
I am a product designer that believes in looking at the full picture, aligning user needs, business goals, and technical constraints into cohesive, scalable solutions. I believe strong product design comes from understanding the entire product ecosystem and shaping thoughtful design processes that support long-term growth.
Driven by curiosity and continuous learning, I enjoy exploring ideas across disciplines and translating them into clearer product thinking. I thrive in collaborative environments, value teamwork as a catalyst for growth, and am seeking a long-term role where I can contribute meaningfully, grow alongside the product, and help shape impactful user experiences.



(02)
My work process
1. Knowledge
I start every project by building a deep understanding of its ecosystem, the client, product, market, and end users. I focus on real user behaviors, business goals, and existing solutions to identify meaningful, day to day pain points. This foundation allows me to accurately frame the problem, ask better questions, and base design decisions on insight rather than assumptions.
1. Knowledge
I start every project by building a deep understanding of its ecosystem, the client, product, market, and end users. I focus on real user behaviors, business goals, and existing solutions to identify meaningful, day to day pain points. This foundation allows me to accurately frame the problem, ask better questions, and base design decisions on insight rather than assumptions.
1. Knowledge
I start every project by building a deep understanding of its ecosystem, the client, product, market, and end users. I focus on real user behaviors, business goals, and existing solutions to identify meaningful, day to day pain points. This foundation allows me to accurately frame the problem, ask better questions, and base design decisions on insight rather than assumptions.
2. Design
My design process is intentionally non-linear. It’s driven by continuous learning, iteration, and validation, with a constant focus on solving the right problem, not just producing a solution. As insights evolve, so does the design, allowing ideas to be tested, refined, and challenged until they meaningfully address the core need we defined.
2. Design
My design process is intentionally non-linear. It’s driven by continuous learning, iteration, and validation, with a constant focus on solving the right problem, not just producing a solution. As insights evolve, so does the design, allowing ideas to be tested, refined, and challenged until they meaningfully address the core need we defined.
2. Design
My design process is intentionally non-linear. It’s driven by continuous learning, iteration, and validation, with a constant focus on solving the right problem, not just producing a solution. As insights evolve, so does the design, allowing ideas to be tested, refined, and challenged until they meaningfully address the core need we defined.
3. Implementation
Once the direction is clear, I focus on tightening the details. I refine user flows, interactions, and edge cases to ensure the design is clear, consistent, and ready for development. The goal at this stage is to create a seamless handoff that enables engineering teams to build with confidence and minimal friction.
3. Implementation
Once the direction is clear, I focus on tightening the details. I refine user flows, interactions, and edge cases to ensure the design is clear, consistent, and ready for development. The goal at this stage is to create a seamless handoff that enables engineering teams to build with confidence and minimal friction.
3. Implementation
Once the direction is clear, I focus on tightening the details. I refine user flows, interactions, and edge cases to ensure the design is clear, consistent, and ready for development. The goal at this stage is to create a seamless handoff that enables engineering teams to build with confidence and minimal friction.
4. Design In Practice
Design doesn’t end at launch. Every solution remains open to evaluation once it’s live in the product. I revisit assumptions, observe real usage, and assess whether the design truly delivers the intended value. This ongoing feedback loop often leads to further refinement, or even better solutions, ensuring the product continues to evolve alongside its users.
4. Design In Practice
Design doesn’t end at launch. Every solution remains open to evaluation once it’s live in the product. I revisit assumptions, observe real usage, and assess whether the design truly delivers the intended value. This ongoing feedback loop often leads to further refinement, or even better solutions, ensuring the product continues to evolve alongside its users.
4. Design In Practice
Design doesn’t end at launch. Every solution remains open to evaluation once it’s live in the product. I revisit assumptions, observe real usage, and assess whether the design truly delivers the intended value. This ongoing feedback loop often leads to further refinement, or even better solutions, ensuring the product continues to evolve alongside its users.



