Fieldwork worldwide · Offices in the USA, India and Singaporecontact@researchandmetric.com+1 240-980-1551
  1. Home
  2. Case studies
  3. In-home use test of a household cleaning product

Fieldwork case study

In-home use test of a household cleaning product

A two-week in-home use test with regular buyers of surface cleaners, with diary feedback coded into themes.

Research and Metric3 min read

The challenge

A household products manufacturer wanted a household cleaner home use test to show how a new surface cleaner performed in real homes. The comparison was against shoppers' usual brand. Diaries produced hundreds of open comments about scent, streaks and ease of use. The team needed to compare those comments fairly.

A shelf test or a hall test cannot show how a cleaner behaves on a real worktop, hob or bathroom tile. Homes differ in surfaces, water and cleaning habits. For that reason, the manufacturer chose an in-home use test, which lets people use the product as they normally would.

Our approach

We placed blind-coded product with regular category buyers and coded their diary feedback into consistent themes.

Why blind product testing matters

Brand names shape opinions before anyone opens the bottle. Blind product testing removes that influence. Each participant receives a coded pack, so their comments reflect the product itself and not the label.

This matters most when you compare a new product with a familiar favourite. Without blind coding, loyalty to the usual brand can hide real strengths in the new formula.

How the household cleaner home use test worked

  • Recruited regular surface-cleaner buyers and recorded their usual brand
  • Delivered blind-coded product with simple usage instructions
  • Collected short online diaries during use and a recall survey at the end
  • Coded every diary comment into themes such as scent, streaking and effort

As a result, every comment in the test sat in the same theme framework, similar to the approach in our open-end coding case study. Diary studies like this also raise consent and privacy questions covered in the ESOMAR international codes.

How the product diary study captured real use

A product diary study records opinions while the experience is fresh. Participants note what they notice soon after cleaning, so they do not have to rely on memory weeks later. Short entries also keep the effort low, which helps people keep going across a two-week test.

The end-of-test recall survey added a second view. It asked every participant the same questions, so the team could rate the product on common measures. In this way, the diaries explained the detail and the survey gave the overall picture.

Turning open-end coding of diary feedback into themes

Open comments are rich, but they are hard to compare in raw form. Open-end coding of diary feedback solves this by sorting each comment into a defined theme. Scent, streaking and effort are typical examples for a surface cleaner.

Good coding follows a few simple rules:

  • Build a clear code frame, with each theme described in plain words
  • Apply the same frame to every participant and every diary entry
  • Check a sample of coded comments to keep coders consistent
  • Count how often each theme appears, then compare it with the survey ratings

Once comments become themes, the team can see which topics come up most often. They can also see whether people mention them positively or negatively. This turns loose opinions into evidence that a product team can act on.

What to consider when planning a home use test

Home use test market research works best when the design stays simple for participants. Several points are worth settling before fieldwork starts:

  • Recruit genuine category buyers, because their habits match your real market
  • Record each person's usual brand so you can make fair comparisons later
  • Give short, clear instructions so everyone uses the product in the same way
  • Keep diary questions brief, since long forms reduce completion
  • Explain consent and data use clearly before participants begin

Planning these points early also protects data quality. Consistent instructions and a stable code frame make the final comparison easier to trust.

The results

  • A real-home read on performance against usual brands
  • Diary themes quantified alongside the survey ratings
  • High retention across the two-week test

This consumer product testing case study shows how diary themes and survey ratings can sit side by side. Together, they tell the product team what people felt and how often they said it. As a result, decisions about the new surface cleaner rest on real-home evidence and not on guesswork.

Illustrative scenario based on typical engagements. Client details are anonymised.

Next step

Planning your next study?

Send us your brief and get feasibility, timelines and costs within 24 hours.