Important decisions about how a product works are often still open when its screens look finished. What happens after an action, when a process fails, or when data changes? As a product designer specialising in UX architecture, I work through these questions before implementation, bringing together user needs, business rules and technical constraints to define how the experience should work.
The foundation of my approach is understanding both the user and the business. I began my career in advertising for hair salons, where I combined conversations with owners and staff, observations of the local area, trends and performance data to make decisions about customer acquisition and branding. I carried that approach into more than 20 website projects. For a beauty appliance manufacturer, I worked with the CEO to clarify the brand’s direction, then reshaped the website and product pages around the questions people had before buying. I also created FAQs based on questions the support team regularly received.
Working in software development brought another set of challenges into focus. Even in a financial SaaS team with detailed designs and thorough reviews, decisions about how features should behave did not always have a clear owner. On a startup MVP, I worked through behaviours that the designs had not covered, including failed processes and returning to an interrupted process, and implemented them myself. At a game company, I also helped resolve unclear responsibilities between development and QA by bringing the team together to agree on what needed to be checked before handover.
These experiences showed me that important decisions about product behaviour often emerge between design and implementation, even in well-organised teams. Engineers can make those decisions during development, but defining the intended behaviour earlier helps maintain a consistent user experience and reduces misunderstandings and rework.
More recently, I worked as a UX Architect on an energy operations dashboard, designing interactions, data handling and error behaviour based on the needs of the people using it. For example, I specified checks to prevent CSV data from being uploaded against the wrong date, and error messages that help users identify and correct problems themselves. I used Figma and working prototypes to develop requirements with stakeholders, documented the decisions in implementation specifications, and stayed involved through code reviews, implementation changes and the start of live operations.
My software engineering experience is also hands-on: I build and improve applications with TypeScript, React and Next.js, and can contribute to prototyping or implementation when a project needs it. My approach combines an understanding of how people think and act with practical knowledge of how software works. I care about the decisions beyond the screen design, and about making sure they work in the finished product.
I also have a background in accessibility. When relevant, I consider what screen readers announce when content changes and whether errors can be understood without relying on colour alone. I hold the IAAP CPACC certification, have written about accessible interfaces, and have built Contrastly, a tool for checking colour contrast.