About

Who I am

I'm a senior UX designer in Dublin. I design interfaces and I design conversations. I studied psychology before I studied UX, and I still start there: what do people understand, what do they expect, what do they actually do? Then I build around the answers. I do my best work on complex products, where the job is to take a tangle of systems and make it easy to use.

What I do

I'm a Senior UX Designer at Genesys, and the senior conversation designer on Genesys Cloud Copilot. Copilot helps people while they work, so how it behaves matters as much as how it looks. When should it speak up? How should it sound? What does it do when it's wrong, or when a person needs to take over? I work through those questions with product and engineering.

Background

Before Genesys I spent four years at Brown Thomas Arnotts, where I was promoted through three roles to Product Lead across two retail brands. I led in-house design on the new apps, which grew their share of demand by over 10 percentage points and won Best App at the Spider Awards. I directed design and delivery on a two-year rebuild of both websites, and I built and maintained the design systems for all four products. I also sat on the panel that set the company's policy on AI in design and engineering.

Before that I spent five years at Human, working up from intern to lead designer. Most of it was with Chupi, where I led UX and UI while the team grew from 15 to 60 people. I set product OKRs with the C-suite, managed a small cross-functional team, and launched tools like the Engagement Ring Finder.

I have an MSc in User Experience Design and a BSc in Applied Psychology, both from IADT, where I now teach Psychology of UX. I mentor early-career designers at UX Tree, and twice they and the other mentors voted me best mentor. I've published academic research too, presented at the Future Technologies Conference in London in 2024 and at Irish HCI in Dublin in 2025.

Approach

• Start from how people think. Psychology lets me explain why a design works, not just whether it does. That makes decisions easier to defend and easier to test.
• Build systems. Design systems helped BTA ship faster and get tickets right first time. A conversation needs the same things: a consistent voice, clear patterns, behaviour people can predict.
• Translate. I'm often the one who explains a technical or ambiguous problem to executives, engineers and customers, each in terms they can act on.
• Design for when it goes wrong. In a conversation that means repair, fallback and handoff. I design them first, not last.

Contact

The best way to reach me is on LinkedIn.