Insights Curry
All case studies
InsignAICase study

The recommendation that used to take three weeks took three days

The recommendation that used to take three weeks took three days
Category
Consumer packaged goods, product development
Team
Insights, Product
Question
Does the new product proposition have enough market appeal to justify moving into development?
Time in InsignAI
End to end, brief to recommendation, in days rather than weeks
What changed
Questionnaire design, fieldwork, quality checks, analysis and reporting moved from five separate stages to one workflow. Research turnaround dropped from two to three weeks down to two to three days.

The situation

A consumer brand needed to know whether a new product idea was worth the development budget behind it, before committing further resources. That meant more than collecting opinions. It meant a questionnaire built to catch the right signals, fieldwork clean enough to trust, an understanding of why consumers reacted the way they did, and a recommendation the business could actually act on.

Under the team's usual process, each of those stages sat with a different person or a different tool. Questionnaire design happened in one place. Fieldwork ran through another. Analysis waited for a separate analyst to pick it up. Every handoff between them added time, and the full cycle typically ran two to three weeks, often longer than the decision itself could wait for.

What they put in

The team started with the business objective itself: whether this proposition had enough appeal to move forward. They ran the study inside InsignAI from that starting point, rather than treating it as a project split across a questionnaire tool, a fieldwork vendor and an analyst's spreadsheet.

What InsignAI did

InsignAI took the business objective and helped translate it into a structured questionnaire, suggesting relevant questions and a survey flow the team could still review and adjust before fieldwork began.

Once the study launched, the team watched response quality as data came in, rather than finding problems after the fact. When fieldwork closed, analysis ran in the same environment the data had been collected in. Quantitative results sat next to open-ended responses, so the team could see the direction of consumer sentiment and the reasoning behind it at the same time, instead of running two separate analyses and reconciling them afterward. Cross-tabs and visualizations let the team check results across the segments that mattered, and automated summaries carried the analysis toward a narrative the business could use.

What they asked

The questions were the ones any product decision needs answered. Did the proposition land. Who it landed with. What was driving the reaction, not just the direction of it. And what the business should do next, given what the data showed.

What changed

Analysis that used to take three to four days came down to two to three hours. The first useful signals, which the team used to wait four to five days for, showed up almost as soon as responses started coming in. Total turnaround for the study fell from two to three weeks to two to three days.

  • Research turnaround: 2 to 3 weeks → 2 to 3 days
  • Analysis effort: 3 to 4 days → 2 to 3 hours
  • Time to first insight: 4 to 5 days → Near instant

The time back did not disappear. It moved. Instead of managing handoffs between teams and tools, the researchers spent their time on the part of the job that actually needed them: interpreting what the data meant for the business.

Let's Talk AboutYour Next Insight.

Tell us what you are trying to decide and our team will show you how Insights Curry can help.

Talk to an Expert