About
About
About
Service Design is the title I use now, but for most of my twenty-year career it went by other names — Web Designer early on, Information Architect, later Senior and Lead UX Designer. The label doesn't matter much; the work did, and looking back, most of it was service design in practice long before the industry had a word for it.
Service Design is the title I use now, but for most of my twenty-year career it went by other names — Web Designer early on, Information Architect, later Senior and Lead UX Designer. The label doesn't matter much; the work did, and looking back, most of it was service design in practice long before the industry had a word for it.
Service Design is the title I use now, but for most of my twenty-year career it went by other names — Web Designer early on, Information Architect, later Senior and Lead UX Designer. The label doesn't matter much; the work did, and looking back, most of it was service design in practice long before the industry had a word for it.
I've mostly worked within fintech, where processes tend to grow complicated for good historical reasons nobody quite remembers anymore. What I enjoy most is the detective work: sitting with a customer's confusion or a colleague's workaround until the real problem surfaces, which is almost never where anyone expects it to be.
I've mostly worked within fintech, where processes tend to grow complicated for good historical reasons nobody quite remembers anymore. What I enjoy most is the detective work: sitting with a customer's confusion or a colleague's workaround until the real problem surfaces, which is almost never where anyone expects it to be.
I've mostly worked within fintech, where processes tend to grow complicated for good historical reasons nobody quite remembers anymore. What I enjoy most is the detective work: sitting with a customer's confusion or a colleague's workaround until the real problem surfaces, which is almost never where anyone expects it to be.
That pattern repeats throughout my career. A knowledge base wasn't underperforming because of bad content, but because editors and customers spoke two different languages. A payment platform wasn't losing merchant trust because of a clunky dashboard, but because merchants had no visibility into what was happening to their money. Finding that root cause, then redesigning the content, workflow, and interface together, is where I do my best work.
That pattern repeats throughout my career. A knowledge base wasn't underperforming because of bad content, but because editors and customers spoke two different languages. A payment platform wasn't losing merchant trust because of a clunky dashboard, but because merchants had no visibility into what was happening to their money. Finding that root cause, then redesigning the content, workflow, and interface together, is where I do my best work.
That pattern repeats throughout my career. A knowledge base wasn't underperforming because of bad content, but because editors and customers spoke two different languages. A payment platform wasn't losing merchant trust because of a clunky dashboard, but because merchants had no visibility into what was happening to their money. Finding that root cause, then redesigning the content, workflow, and interface together, is where I do my best work.
Twenty years in, I still like this work as much as I did when I started as an Information Architect. Every organisation I've worked with has had complexity someone assumed was permanent, and untangling it never gets old. I'm currently looking for the next place to do that, somewhere the stakes are real and the problems are worth the effort.
Twenty years in, I still like this work as much as I did when I started as an Information Architect. Every organisation I've worked with has had complexity someone assumed was permanent, and untangling it never gets old. I'm currently looking for the next place to do that, somewhere the stakes are real and the problems are worth the effort.
Twenty years in, I still like this work as much as I did when I started as an Information Architect. Every organisation I've worked with has had complexity someone assumed was permanent, and untangling it never gets old. I'm currently looking for the next place to do that, somewhere the stakes are real and the problems are worth the effort.
Every organisation has its own version of complexity. Let's solve yours.
Every organisation has its own version of complexity.
Let's solve yours.
Every organisation has its own version of this complexity.
Let's solve yours.