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.
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 glossarySearch IntentSearch intent is the underlying goal or purpose behind a user’s query, such as finding information, making a purchase, or navigating to a specific site.Open glossary term 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
Be clear on who the user is, the glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term they are acting in, and what serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service you have. Goals inferred from a 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 list will reproduce the feature list.
Distinguish goals from tasks before you start. A goal survives a redesign; a task usually does not.
Run the method
Goal analysis identifies what people are actually trying to achieve, above the level of any particular glossaryInterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term. It is the layer that stays stable while everything else changes.
- Identify high-level goals in the user's terms, not the glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term's.
- Break each into sub-goals, stopping before you reach glossaryInterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term steps.
- Distinguish functional, emotional and social goals. Most products serve the first and lose to competitors who noticed the other two.
- Map how goals relate to observed tasks and glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, and note where a task serves no goal you can name.
- Validate against real glossaryDataData is raw, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term. A goal nobody's glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term supports is a glossaryHypothesisA hypothesis is a testable assumption about how a change will impact an outcome.Open glossary term about users, which is fine as long as it is labelled.
Separate the goal from the current means of achieving it. Designing around the means locks you into whatever the last implementation happened to do.
Capture and make sense of it
The value comes from designing for outcomes. After the analysis, document:
- Goals stated in user language, at a level above the glossaryInterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term
- Functional, emotional and social dimensions of each
- How current tasks map to goals, and where they do not
- Goals currently unserved by anything you offer
Use this to guide glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term and structure. Goals are the most durable input a glossaryRoadmapA roadmap is a strategic plan that outlines the direction, priorities, and timeline for a product or initiative. It communicates what will be delivered and why, rather than just listing features.Open glossary term can have.
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 clarity 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 task analysis 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.
Quick take
If you want to understand what users are actually trying to achieve, not just what they do, analyse their goals.
Related Services
