Paul James

I started my career in graphic design, studying at the University of Hull and graduating with a BA (Hons). That background still plays a big part in how I design today, especially when it comes to hierarchy, layout, visual clarity, and how information is presented on screen.

Over time, my work moved more into digital product design. I became less interested in just how something looked and more interested in why people struggled with it, how a workflow could be improved, and how design could make complicated products feel easier to use. That naturally led me into UX and UI.

Most of my work has been across SaaS products, often in areas where the details really matter, including fintech, healthcare, sustainability, logistics, and compliance-led platforms. These are the kinds of products where users are dealing with important tasks, sensitive information, dense data, or business-critical decisions, so clarity and structure are just as important as the visual design.

A lot of my experience has been shaped by complex product challenges, whether that meant defining something from the ground up, improving an existing flow, or helping a team bring more structure to an evolving product. The work is rarely just about a single screen. It is about understanding how the product fits together and making the experience clearer, more consistent, and easier to use.

One of the projects that shaped how I think about product design was the LCA Calculator at Anthesis Digital. It became the second most-used product in the Anthesis Hub within its first year, and it showed me how much good UX can influence adoption. It was not just about designing screens. It was about helping shape a product that people could understand, trust, and keep using.

Working across different industries has taught me how to adapt, ask better questions, understand different users, and balance business goals with real user needs. Each project has added something to the way I think, whether that is handling complex data, simplifying regulated journeys, or helping teams bring structure to a product as it grows.

Today, my work is focused on designing SaaS products that are clearer, more accessible, and easier to build on. Whether I am working on a fintech platform, a healthcare product, or a complex internal tool, the aim is always the same: to make the product easier to understand, easier to use, and easier for teams to grow over time.

For me, design is about clarity, alignment, and practical impact. A good interface should not just look polished. It should help people understand what they need to do, reduce friction, and make the product feel more confident and usable.

I believe the best design work starts with listening, but not just taking everything at face value. What users say and what users actually do can be two different things. That is why research, workshops, testing, and observation are so important. They help uncover the real problems behind the feedback.

Workshops have become a big part of how I work. Bringing developers, stakeholders, product teams, and people close to the users into the same conversation usually leads to better decisions. It creates alignment early and helps avoid designing around assumptions.

A lot of the products I work on are complex by nature. There may be regulations, permissions, data, approvals, financial rules, clinical journeys, or operational processes behind the screen. I do not think complexity is always the problem. The problem is when that complexity is passed directly onto the user.

My role is to make that complexity easier to navigate. That means simplifying workflows, improving structure, making information easier to scan, and thinking through edge cases before they become problems later.

At the centre of it all, I want my work to make complicated products feel simpler. If users can understand what to do, complete tasks with less friction, and trust the product while using it, then the design is doing its job.