How I Approach Design

How I Approach Design

How I Approach Design

How I Frame UX

How I Frame UX

How I Frame UX

At its core, UX is about understanding people and their needs, including accessibility, while working with stakeholders to balance those needs against technical and business constraints. I use UX to reduce risk in product decisions and keep the team aligned on the intended player experience.


We design products to improve the lives of people, whether that’s making something easier to accomplish or creating games to allow people to escape to new realities and forget about the stresses of normal life, to socialise with friends, challenge themselves or express their creativity. Understanding users and their needs should remain central to decisions about the experiences we create.


In game development, UX has an important role in helping teams understand their intended audience, design intent and evaluate whether the experience they're creating aligns with their vision.

Understanding the problem

Understanding the problem

Understanding the problem

Before jumping into designs, I want to understand what we're trying to achieve, the intended experience, who we're designing for and what constraints we're working with. This means speaking with team members, reviewing any existing research and looking at how similar problems have been approached elsewhere.


Who are we making this for? What motivates those players or users? What do we want them to feel or experience? Having answers to those questions makes it easier to evaluate design decisions as development progresses.


I'm particularly interested in identifying what we know and what we're assuming. Throughout development, I can help identify and prioritise high-risk assumptions, determine which uncertainties present the greatest risk, help teams make more evidence-informed decisions and potentially avoid unnecessary rework or significant investment in features that may not deliver the intended experience.

Exploring and evaluating solutions

Exploring and evaluating solutions

Exploring and evaluating solutions

Once I have a reasonable understanding of the problem, I'll start exploring potential solutions through user flows, wireframes and prototypes.


I prefer to start at a lower fidelity, giving us room to explore different approaches without investing too much time in polishing something that might change. AI can make it much quicker to produce designs and prototypes, but I think there's a risk of jumping at the first solution that looks good without questioning whether it's actually solving the right problem.


I also like involving other disciplines early. Speaking with designers, artists and programmers helps identify potential problems, understand what's feasible and explore alternatives.


The level of detail depends on what we're trying to achieve. Sometimes a simple flow or sketch is enough to communicate an idea. Other times, an interactive prototype is needed to understand how something feels in practice.


Accessibility is also an important consideration throughout this process. I look to identify potential barriers early, consider how different players may interact with an experience and work with the team to address those barriers. Where possible, I also advocate for involving accessibility specialists and players with disabilities.

Testing and iteration

Testing and iteration

Testing and iteration

Where appropriate, I use heuristic evaluations ahead of wider playtests using Jakob Nielsen's usability heuristics and Celia Hodent's game UX principles. These can identify potential usability problems and unintended friction, giving us an opportunity to discuss as a team and address obvious issues before testing with players. This can help focus subsequent testing on questions that we can't answer through expert evaluation alone.


Testing is an important part of my process, but I think it's equally important to understand what we're trying to learn from it. Before running a test, I want to establish what questions we're trying to answer and how the findings will inform our decisions.


The research methods I use depend on what we're trying to learn. I've conducted internal moderated usability tests supported by surveys and interviews, comparing observed player behaviours with quantitative and qualitative feedback to better understand the problems identified and what might be causing them.


One consideration specific to games is distinguishing between intended and unintended friction. Games often deliberately challenge players, so difficulty isn't automatically a usability problem. The important question is whether that friction supports the intended experience.


Research and testing can also reveal things we hadn't considered. Those unexpected findings can be just as useful as answering our original questions. I try to use what we learn to inform the next iteration, while recognising that research is only one part of decision-making.

Supporting implementation

Supporting implementation

Supporting implementation

Throughout development, I work with the relevant disciplines to communicate design intent, understand technical limitations and review how an experience works once implemented. Things can change as a project progresses, whether that's due to previously unknown technical constraints, new requirements or findings from testing.


When research findings, creative goals or technical constraints pull in different directions, I try to communicate the trade-offs clearly and work with the team to find an appropriate solution.


This isn't a rigid process, and the order and methods I use will depend on the project, its stage of development, the time and resources available, and the problems we're trying to solve. I think it's important to be realistic and focus UX efforts where they can provide the most value.

UX isn’t just designing the experience.

It’s helping teams make better decisions about it.

UX isn’t just designing the experience.

It’s helping teams make better decisions about it.