Strategy
Goal Analysis
A practical UX and strategy method for defining user intent so teams can prioritise around outcomes rather than just features or processes.
How to use goal analysis to understand user intent, identify the outcomes that matter most, and make stronger design and product decisions.
Quick take
If you want to understand what users are actually trying to achieve, not just what they do, analyse their goals.
Related Services
What it is
Goal analysis is a UX method used to identify and define what users are trying to achieve when interacting with a product or glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term.
It focuses on outcomes rather than actions, helping you understand the intent behind glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term.
Goals can be functional, emotional, or social, and often exist at different levels, from high-level objectives to specific tasks.
Unlike guideTask AnalysisBreaking down a specific task into steps, decisions, and dependencies so complexity can be reduced and workflows improved.Open guide, which looks at how users complete something, goal analysis looks at why they are doing it in the first place.
The goal is to ensure products are designed around real user needs, not just glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term or glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term.
Goal analysis is most useful when the team risks optimising activity without being clear on the outcome users actually care about.
When to use it
Use this method when you need glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term on glossaryUser IntentUser intent is the underlying goal or reason behind a user’s action, search, or interaction.Open glossary term.
It is most useful when:
It is less useful when:
Goal analysis is often used alongside user research, personas, and journey mapping.
Key takeaway
Use goal analysis when better product decisions depend on understanding intent and priority, not just watching behaviour at the surface level.
How to run it
Set up properly.
Before you start, be clear on who the user is, the glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term in which they are acting, and what glossaryDataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term or serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service is available.
Use real glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term wherever possible.
Run the method.
Goal analysis is structured but flexible.
Identify high-level user goals. Break them down into sub-goals. Distinguish between functional, emotional, and social goals. Map how goals relate to tasks or glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term. Validate against real user glossaryDataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term.
Focus on intent, not just actions.
Capture and make sense of it.
The value comes from glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term and glossaryAlignmentAlignment is the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term.
Look across goals to identify common glossaryPatternA reusable solution to a common design problem.Open glossary term or priorities, gaps between user goals and current solutions, conflicting or competing goals, and opportunities to better meet user needs.
Use this to guide design and glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If you don’t understand the goal, you design the wrong thing.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps ensure you are solving the right problems.
Get in touch
If this sounds like something you need, we can help you define what your users are actually trying to achieve and design around it.
No guesswork. No assumptions. Just glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term that drives better decisions.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is goal analysis in UX?
It is a method used to understand what users are trying to achieve.
When should you use goal analysis?
Use it when defining or prioritising user needs.
How is it different from task analysis?
Goal analysis focuses on intent, while guideTask AnalysisBreaking down a specific task into steps, decisions, and dependencies so complexity can be reduced and workflows improved.Open guide focuses on actions.
What types of goals are there?
Functional, emotional, and social goals.
Does goal analysis improve UX?
Yes. It helps ensure products meet real user needs.