Product
Thinking
Product
Discovery
UX Design
UI & Design
Systems
Collab &
Delivery
Description
The problem comes first.
Before jumping into Figma, I want to understand what's actually worth solving. I look at user needs, business goals, and existing limitations to figure out where design can make a difference.
Sometimes that means building something new.
Other times, it's simplifying what's already there.
Before jumping into Figma, I want to understand what's actually worth solving. I look at user needs, business goals, and existing limitations to figure out where design can make a difference.
Sometimes that means building something new.
Other times, it's simplifying what's already there.
I'd rather question than assume.
I don't like designing based on assumptions alone. I explore existing products, look for friction points, compare different approaches, and use feedback to challenge my initial ideas.
I prefer spending time understanding a problem than polish a solution that doesn't solve it.
Complex doesn't have to mean complicated.
Working on information-heavy products has taught me that simplicity isn't about removing functionality.
I focus on clear navigation, logical flows, and interactions that help people get things done without having to think twice.
It's about making things easier to understand and use.
Working on information-heavy products has taught me that simplicity isn't about removing functionality.
I focus on clear navigation, logical flows, and interactions that help people get things done without having to think twice.
It's about making things easier to understand and use.
The details make the difference.
I'm particular about how interfaces come together.
I enjoy turning individual screens into a connected experience, whether I'm working within an existing design system or building reusable patterns from scratch.
Spacing, typography, components, states, and consistency all matter.
I'm particular about how interfaces come together.
I enjoy turning individual screens into a connected experience, whether I'm working within an existing design system or building reusable patterns from scratch.
Spacing, typography, components, states, and consistency all matter.
A Figma file isn't the final product.
I care about what happens after the design is approved.
Working with developers and stakeholders means understanding technical constraints, discussing trade-offs, and adjusting when needed.
For me, a good design isn't just something that looks great in a presentation. It needs to work when it's built.
Working with developers and stakeholders means understanding technical constraints, discussing trade-offs, and adjusting when needed.
For me, a good design isn't just something that looks great in a presentation. It needs to work when it's built.
(Scroll down)
0
/
05
1
2
3
4
5