I started with visual craft
Before product design, I learned through visual work. Composition, typography, hierarchy, rhythm, and detail taught me that clarity is something people often feel before they can explain it.
I learned design by making things, noticing what felt unclear, and slowly understanding that good design is not only about how something looks. It is about how people make sense of what is in front of them.
The thread through my work is not a tool category. It is the habit of turning what felt unclear into something visible enough to discuss, test, and improve: a map, a prototype, a language system, or a working model.
Before product design, I learned through visual work. Composition, typography, hierarchy, rhythm, and detail taught me that clarity is something people often feel before they can explain it.
I am self-taught, which means my path into design was built through repetition, curiosity, mistakes, and practical work. Making became my way of understanding.
At Deloitte Digital, I learned how design works inside complex organisations. The problem is rarely just the screen. It is the stakeholders, rules, legacy systems, business pressure, and people trying to make good decisions with imperfect information.
Over time, I stopped looking only at interfaces and started looking at workflows, handoffs, roles, decisions, incentives, and the hidden operating model behind the product.
I use prototypes to make ideas tangible. A prototype gives teams something to react to, question, improve, and align around. It turns abstract discussion into visible progress.
AI has changed parts of my work, but it has not changed the core responsibility of design. People still need to understand what is happening, why something is being suggested, when to trust it, and when to challenge it.
I am interested in teams building thoughtful products for complex domains, products where design helps people understand, decide, create, collaborate, or work in better ways.