I learned customer experience before I learned to call it customer experience.
My path into product design came through real businesses, real clients, real operations and the friction that appears when systems meet human behaviour.
My background crosses hands-on service businesses, customer experience, business operations, branding, market strategy, digital products and technology.
Working with more than 100 clients in a month as a PT shaped my view of customer experience in a way that a screen never could. In a treatment room, the product is not only the treatment. It is the booking, the arrival, the environment, the conversation, the trust, the boundaries, the handoffs, the follow-up and the memory the client leaves with.
At that volume, patterns stop being abstract. You see where expectations break, where language creates friction, where operational decisions become customer experiences, and how small details can either increase trust or quietly erode it.
That is why I tend to look for the operational, behavioural or commercial problem before I look for the interface. I do not believe every problem needs custom software, and I do not measure good product work by how much code it produces. The objective is a product or system that works better after it exists.
“The customer does not experience your departments. They experience one continuous relationship with the business.”
What should exist, who is it for, what behaviour should it enable and what problem is worth solving?
How does it earn attention, trust, adoption and commercial value in the world around it?
What does the customer actually move through before, during and after the core interaction?
How should the moving parts work together without creating unnecessary complexity?
Say hello.
For thoughtful product, market or systems work, or anything connected to the notes and books published here.