Operational logic for high-stakes systems.

My Role

I architect software where error tolerance is zero. In data-dense environments, causality matters more than trend. I work across both UX and UI — from analytical discovery and requirements mapping to high-fidelity interfaces and production-ready developer handoff.

I do not deliver screens; I deliver certainty. By defining rigid object models and state behaviors, I remove ambiguity for engineers and operational risk for users. I bridge the gap between product analysis, design decisions, and engineering implementation.

MENTAL MODELS

Design is the reduction of
operational risk.

The Object Model is the Design

A UI is only as competent as the data model it represents. I define objects and states before pixels. If the logic is flawed, the visual is a lie. I solve problems at the schema level.

Causality vs. Empathy

Empathy is an input, not a strategy. Users rely on deterministic outcomes. I design systems that enforce valid inputs and guarantee predictable states. Ambiguity is a system failure.

Constraint is Information

In high-stakes systems, unchecked optionality creates risk. I design constraints that prevent invalid states before they occur. In critical operations, protecting users from costly errors is itself the highest form of care.

INFLUENCES

• Edward Tufte — Visual Display of Quantitative Information
• Dieter Rams — Less but Better
• Don Norman — The Design of Everyday Things

Get in touch.