Atomic research

Q: How do you set up an atomic research approach?

Setting up an atomic research practice in-house happens through successive steps. As with atomic design, it means thinking about governance, forums, procedures, and so on. We recommend starting small with a limited group. Once the foundations are in place, you present the directions to the future users. The goal is to make sure you're heading in the right direction. And you build up incrementally.

Q: What's the difference between atomic research and a research repository?

Atomic research describes an approach to analysis for generating user knowledge. Where there's knowledge management, there's a knowledge base. The research repository is the knowledge base that is fed by an atomic research practice.

Q: What tool should you use to practise atomic research?

To get started without a dedicated tool, a table in a tool like Notion or Airtable is enough. It's methodological rigour that will make the difference, not the tool. Atomic research serves as a guide for that.

Q: What type of project is atomic research for?

Atomic research is particularly useful for product teams doing continuous research on their solutions. In that case, applying the principles of atomic research changes the status of user research and its results. It's no longer a one-off activity that produces static material. It's an infrastructure for accumulating knowledge and making use of it dynamically.

Concept

Structuring the user knowledge generated by your UX research studies

User research aims to create new knowledge about the uses and behaviours of the users of your services. To help translate field observations into shareable findings, several authors have proposed interesting conceptual frameworks. Among these approaches to processing the results of user studies, the atomic approach that exists in design also appears in user research.

Atomic research is a framework that breaks each user study down into independent facts, insights and recommendations. Proposed in 2017 by two professionals (Tomer Sharon and Daniel Pidcock), the idea is to treat the knowledge generated by a UX study as independent units, reusable from one project to the next. The goal is therefore to build capital in order to make better use of the results of user studies.

For each fact put forward, atomic research maintains the link with a piece of evidence (a quote, a screenshot, a video clip). These units can be cross-referenced between projects, retrieved by keyword, and remain consultable years after the session that produced them.

What is atomic research for?

structuring how you make use of the data from user studies
connecting research insights with concrete applications for the product or service
bringing the different disciplines together around a clear, shared logic for user studies

Why adopt atomic research?

defining a uniform approach to analysis and use within an organisation, across different teams
increasing other teams' buy-in to UX research results
documenting the studies carried out rigorously (topic, context, panel)
nurturing a shared UX research culture within the organisation

Experiments

these are your data sources, the field sessions carried out, of every kind (user tests, interviews, observations).

Facts

what was genuinely observed, without interpretation. To each fact, an attached piece of evidence: a quote, a screenshot, a video clip.

Insights

what several converging facts allow you to formulate. It's the key step, the one that separates observation from recommendation. Contradictory facts can also produce an insight, a more nuanced one.

Recommendations

they follow from the insights, and from them alone. Without an insight to support it, a recommendation is only an opinion.

The atomic research approach offers a working framework, not a magic recipe. The principles it describes are meant to support a change of posture towards user research. It is common for analysis reports from a study to be only partially used. By breaking down the elements of each study and indexing them, atomic research makes it easier to search through the knowledge already produced. If it is easy to share, and can be browsed according to one’s own needs (e.g. by journey stage or type of difficulty), then teams will take an interest in user knowledge.

How do you set up an atomic research approach?

What's the difference between atomic research and a research repository?

What tool should you use to practise atomic research?

What type of project is atomic research for?

When life turns upside down for a MAIF policyholder, what role should the insurer play?

View the case study

Alma behind the counter: from checkout flow to cash drawer

View the case study

For the Cultura Foundation, how do you give young people a taste for reading?

View the case study

Related methods

Research protocol

The research protocol describes the conditions, the resources and how an experiment or test runs, along with the questions it sets out to answer.

UX benchmark

A benchmark explores current trends in usage, features and design: the good ideas, and the ones to avoid.

Research Repository

The research repository centralises the findings from UX studies. Its value lies in retrieval, not in storage: an unused repository is nothing but an archive.

Research Ops

Research Ops organises the practice of UX research within an organisation: methods, tools, recruitment, sharing user knowledge.

Design Ops

Design Ops optimises the practice of design: tools, processes, handoff, documentation. It lets designers focus on designing rather than on managing.

Qualitative research

Qualitative research explores users' motivations and barriers. It answers the why where quantitative metrics stop at the what.

Curious to learn more about us?

Everyone talks about user experience, service design, ergonomics...
It's not always clear, and you'd like to find out, or sharpen what you already know.

Let's talk