Error Tracking

Error tracking is a quantitative UX and product method used to capture, monitor, and analyse errors that occur during user interactionsglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→.

This includes technical errors such as failed API calls, form validation failures, broken links, crashes, and systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ exceptions.

It provides visibility into when something goes wrong, where it happens, and how often it occurs.

Unlike behavioural methods, error tracking focuses on failures in the experience rather than general usage.

The goal is to identify, prioritise, and fix issues that directly impact usabilityglossary×UsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term→, performanceglossary×PerformancePerformance refers to how quickly and efficiently a system responds to user actions and processes tasks.Open glossary term→, and conversionglossary×ConversionA conversion is any action a user takes that aligns with a defined goal, such as making a purchase, signing up, or completing a task.Open glossary term→.

Use this method when reliabilityglossary×ReliabilityReliability is the ability of a system to consistently perform as expected without failure.Open glossary term→ and performanceglossary×PerformancePerformance refers to how quickly and efficiently a system responds to user actions and processes tasks.Open glossary term→ matter.

It is most useful when:

Set up properly.

Before you start, be clear on what types of errors you want to track, how errors are captured and logged, and how errors are categorised and prioritised.

Ensure tracking covers both front-end and back-end issues.

Run the method.

Error tracking is continuous and dataglossary×DataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term→-driven.

Capture errors across the product in real time. Log details such as location, device, and user contextglossary×ContextThe surrounding conditions that shape behaviour and decisions.Open glossary term→. Group similar errors together. Measure frequency and impact. Prioritise based on severity and user impact.

Focus on patternsglossary×PatternA reusable solution to a common design problem.Open glossary term→ and high-impact issues.

Capture and make sense of it.

The value comes from understanding where failures affect users.

Look across dataglossary×DataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term→ to identify recurring errors, high-frequency issues, critical failures in key journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→, and differences across devices or environmentsglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→.

Use this to guide prioritisationglossary×PrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term→ and fixes.

Focus on:

Most issues come from:

Not all errors matter equally. Focus on impact.

Done properly, this method gives you:

If this sounds like something you need, we can help you identify what is breaking, prioritise fixes, and improve the overall experience.

No guesswork. No assumptions. Just clear insightglossary×InsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term→ you can act on.