UR

Shadowing

A practical in-context method for understanding how work unfolds across time, tasks, interruptions, and decisions.

How to use shadowing to see real workflows from start to finish and understand how people actually manage their day.

21 March 20255 min read

Quick take

If you want to see how work actually happens from start to finish, shadow users as they go about their day.

What it is

Shadowing is a qualitative UX method where you follow a user over a period of time to observe how they carry out real tasks in their natural .

It is a form of in- focused on continuity. Instead of observing a single task, you see how work unfolds across multiple activities, interruptions, and decisions.

Unlike interviews or short , shadowing captures the of over time, including how people switch between tasks and respond to real-world pressures.

The goal is to understand the full picture of how work happens, not just isolated moments.

Shadowing is most useful when the shape of the work matters just as much as the individual tasks within it.

When to use it

Use this method when you need to understand as they naturally unfold.

It is most useful when:

Tasks are spread across time, systems, or locations
Work involves interruptions, multitasking, or shifting priorities
You need to understand how different activities connect
Behaviour is difficult to capture in a single session
You want to see how people actually manage their day

It is less useful when:

The task is short and self-contained
You only need focused insight on a specific interaction
Access or time is limited
Shadowing is often used alongside contextual inquiry and field studies to deepen understanding.

Key takeaway

Use shadowing when continuity matters and you need to understand how work flows across a day, not just within a single task.

How to run it

Set up properly.

Before you start, be clear on what roles or users you need to observe, how long you will shadow them, and what activities or are relevant.

Make sure expectations are clear so users feel comfortable being observed over time.

Run the method.

Shadowing is primarily observational and continuous.

Follow the user through their normal activities. Observe how tasks start, evolve, and end. Pay attention to interruptions and switching. Take detailed notes on , , and interactions. Ask questions at appropriate moments without disrupting flow.

You are there to understand the day as it happens, not to control it.

Capture and make sense of it.

The value comes from seeing across time and activities.

Look across to identify how tasks connect and overlap, repeated and routines, interruptions and their impact, and workarounds and inefficiencies.

Map to show how actually function in practice.

What to look for

Focus on:

Flow of work
How tasks progress and link together
Interruptions
How users handle distractions or competing priorities
Context switching
Movement between systems, tools, or tasks
Workarounds
Adaptations that reveal gaps in processes or tools
Time and pressure
How constraints affect decisions and behaviour

Where it goes wrong

Most issues come from:

If you only capture snapshots, you lose the value of continuity.

interfering too much with the user’s day
focusing only on individual tasks instead of the bigger picture
failing to capture enough detail over time
observing without understanding context
making assumptions without validating them

What you get from it

Done properly, this method gives you:

a complete view of how work actually happens
understanding of workflows across time and tasks
visibility of interruptions and inefficiencies
insight into real-world pressures and constraints

Key takeaway

It helps you design for how people really work, not how you expect them to.

Get in touch

If this sounds like something you need, we can help you understand how work really happens across a full day or .

No guesswork. No assumptions. Just clear you can act on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is shadowing in UX research?

Shadowing is a method where a researcher follows a user over time to observe how they carry out real tasks in their natural .

When should you use shadowing?

Use it when you need to understand , interruptions, and how tasks connect across a day or .

How long should you shadow a user?

It can range from a few hours to a full day or longer, depending on the complexity of the work.

What is the difference between shadowing and contextual inquiry?

Shadowing focuses on continuous over time, while combines observation with more structured questioning during tasks.

Is shadowing intrusive?

It can be if not handled carefully. Setting expectations and minimising disruption is key.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20