The work is for someone else.

Why This Work

I'm in UX because I want to make people's lives better. That sounds simple. It gets complicated quickly.

The complication is that "better" isn't obvious, and the people who would benefit most often can't tell you directly what they need. They describe symptoms, workarounds, the frustration with the thing that exists. Listening past that — to what's actually underneath — requires slowing down when speed is the pressure, staying curious when you're supposed to have answers, and giving the work enough room to miss.

Missing the mark is part of it. Not as failure to be avoided — as instruction. Each iteration gets you closer to something genuinely useful, often in ways the people benefiting will never consciously notice. That's not a failure of visibility. That's the whole point.

I've spent a lot of time thinking about how we actually come to know things — and how looking at the same problem through different lenses changes what you see. My faith, rooted in Jesus Christ and read through both Eastern Orthodox and Western theological traditions, shaped that instinct early. Not because I'm undecided between them, but because holding those perspectives in tension showed me that truth doesn't flatten when you examine it closely. It opens up. That's the same thing that happens when you bring research, systems thinking, and direct observation to a problem at the same time. The answer almost never lives inside a single frame.

The Work

I've spent 20+ years doing this across healthcare, SaaS, higher education, and critical infrastructure — leading teams across India, Poland, Belgium, and the US, in organizations where UX had to earn its place by demonstrating actual value, not by claiming it. I've built teams, designed systems, run research programs, and influenced product direction. The common thread in all of it is the same question: what does this person actually need, and are we building toward that?

At Arcos, I built a UX practice from the ground up — growing from one designer and two consultants to a senior team with its own ways of working, its own design system, and a delivery model that takes work from discovery through to draft front-end code without leaving the design function. I built that not because it was technically clever, but because the people we were designing for couldn't wait two weeks for a decision. Speed in service of people is worth finding. Speed as a substitute for understanding isn't.

The same conviction shapes how I think about AI in design. It should extend thinking, not replace judgment. It should free up the time and attention that belongs on the actual question.

Beyond the Work

Outside the office, I'm usually doing something that requires patience, systems thinking, or a willingness to be wrong.

I design and play board games — and game design has taught me more about user experience than most UX books I've read. Mechanics have to be learnable, fair, and satisfying. Feedback loops have to be calibrated. Players have to feel agency even when they're constrained. Sound familiar?

I cook my way through cuisines I don't know yet. It's the same practice as research: approach something unfamiliar with genuine curiosity, learn its logic from the inside, and then make something with it.

I take coffee and bourbon seriously — not as lifestyle accessories, but as exercises in sensory discernment. Training your palate to identify what's actually there, rather than what you expect to be there, is a discipline. One that transfers.