Menu

UR

Co-discovery Sessions

A practical research method for understanding collaboration, shared reasoning, and how people make sense of things together.

How to use co-discovery sessions to observe collaborative behaviour, richer verbalisation, and how shared understanding develops in real time.

4 min read

What it is

Co- are a qualitative UX method where two participants work through tasks together while thinking aloud and discussing what they are doing.

They are often used in and exploratory to observe how people collaborate, explain decisions, and react in real time.

Unlike individual , co- introduces social . Participants naturally question, challenge, and explain things to each other.

The goal is to uncover , reasoning, and shared understanding through conversation and collaboration.

Co-discovery sessions are useful when the interaction between people tells you as much as the task itself.

When to use it

Use this method when collaboration or shared understanding is part of the experience.

It is most useful when:

Users naturally work in pairs or groups
You want to understand how people explain and justify decisions
You need more natural verbalisation than traditional think-aloud
Tasks benefit from discussion and shared problem-solving
You want to observe how understanding develops in real time

It is less useful when:

Tasks are highly individual or sensitive
You need independent, unbiased responses
One participant may dominate or influence the other too strongly
You require precise measurement of individual performance
Co-discovery sessions are often used alongside usability testing and interviews to provide both behaviour and reasoning.

Key takeaway

Use co-discovery when collaboration itself is part of the behaviour you want to understand.

How to run it

Set up properly

Be clear on the tasks, whether participants should already know each other, and how collaboration fits the real . Pairing people who would never work together produces an artificial dynamic.

Choose tasks with enough substance to discuss. Trivial tasks produce narration rather than reasoning.

Run the method

Co- puts two people through a task together. Because they explain themselves to each other rather than to you, you hear reasoning that a think-aloud protocol never surfaces.

  1. Introduce the task and make clear they should talk to each other, not to you.
  2. Encourage genuine conversation, including disagreement about what to do next.
  3. Let them work through the task together, and tolerate longer silences than feels comfortable.
  4. Observe how they explain, question and decide. The explanations one gives the other are the , stated aloud without prompting.
  5. Intervene only to keep things moving. Every intervention converts the into a moderated test.

Let the pair . The method works precisely because you are not the audience they are performing for.

Capture and make sense of it

The value comes from naturally verbalised reasoning. After the , document:

  • Explanations participants gave each other, which reveal
  • Points of disagreement about how something works
  • Questions they asked each other, which are the gaps in your
  • Where they collectively got stuck

Use this where reasoning matters more than . It suits complex or unfamiliar products better than routine ones.

What to look for

Focus on:

Collaboration: how participants work together to complete tasks
Verbalisation: how they explain actions and decisions
Misunderstandings: where participants disagree or correct each other
Decision-making: how choices are made and justified
Language: how users describe the product or experience

Where it goes wrong

Most issues come from:

If the feels controlled, you lose the natural dynamic.

Pairing people who would never work together, which produces performance
Letting one participant drive while the other watches
Intervening, which converts it into a moderated test
Choosing a task too simple to require discussion
Listening only to the words and missing how they negotiate

What you get from it

Done properly, this method gives you:

Reasoning verbalised naturally, because they explain to each other
Disagreement about how something works, which reveals the model
The questions they ask each other, which are your interface gaps
Richer verbal material than a think-aloud produces

Key takeaway

It helps you see how understanding is formed, not just what people do.

Get in touch

If this sounds like something you need, we can help you understand how people think, decide, and work together.

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

FAQ

Common questions

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

What are co-discovery sessions in UX?

Co-discovery sessions are a research method where two participants complete tasks together while discussing their actions and decisions.

When should you use co-discovery sessions?

Use them when collaboration is natural or when you want more verbal insight than individual sessions provide.

What is the difference between co-discovery and usability testing?

Co-discovery involves two participants working together, while usability testing typically involves one participant working alone.

Should participants know each other?

It depends. Familiar participants may collaborate more naturally, but unfamiliar pairs can reveal different behaviours.

Are co-discovery sessions better than individual sessions?

They provide different insights. Co-discovery reveals interaction and discussion, while individual sessions show independent behaviour.

Quick take

If you want to see how people figure things out together, not alone, run co-discovery sessions.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer