My way of thinking began long before I entered UX. I studied architecture in a program that was unusually hands-on for its time — one that taught me to design within constraints, understand clients deeply, and create solutions that were both functional and human.
Architecture gave me my first exposure to design theory, but more importantly it gave me psychology — perception, cognitive mapping, biases, semiotics. It taught me that design is not decoration; it is cognition, behaviour, and meaning.
After six years I moved into web design, retrained, and rebuilt my career. The architectural foundation never left — it became the quiet structure beneath my work: systems thinking, pattern recognition, the way I see relationships between parts and wholes.
I've always been drawn to the parallel between scientific method and design method: hypothesis, test, iterate, validate, conclude. Over time, that parallel became a core part of my worldview.
Design, at its best, is not art. It is structured problem solving — evidence-based, methodical, rigorous, repeatable, testable.
The scientific mindset gives design its integrity: solutions that are not just beautiful but accurate, not just intuitive but validated. This layer is subtle in my work — never loud, never academic — but always present.
Frameworks are not boxes to follow — they are lenses to reveal the next best step. The craft is in the selection.
{{ ddDesc }}
The industry standard — because it works. It reflects the twofold nature of design, and of BINAL itself.
Slide any row or column — like solving a cube — to bring a different set of frameworks into view.
Every framework resolves into something real. These are the artefacts I produce at each phase — hover any one to see what it involves.
No single framework or artefact carries a project — the skill is choosing the right lens for the problem in front of you, and knowing when to set it down. See how they play out in the work →
My thinking has been shaped by breadth — industries, organisations, problem types, team structures, constraints. Over time I've developed a way of seeing patterns quickly, synthesising complexity rapidly, and moving teams toward clarity with confidence. These strengths are not loud; they are quiet, calm, and consistent.
AI is not replacing designers — it is augmenting them. I've used AI extensively in enterprise environments: transforming transcripts into insights, synthesising workshop data, conducting deep research, generating visual concepts, accelerating documentation, and supporting design systems.
AI expands what is possible — but the thinking remains human. It is a modern extension of my clarity-driven practice.