Back to all articles
Product Research4 min read

How cognitive bias shapes product research

When research validates the wrong product decisions, the cost is real. Here's how bias affects your bottom line.

CB

CogBias Product Team

Published August 9, 2026

How cognitive bias shapes product research

When good research measures the wrong thing

Coca-Cola ran nearly 200,000 taste tests before launching New Coke in 1985, at a research cost of about $4 million. The sip tests were well executed and the finding was real: in blind tastings, people preferred the sweeter formula. The launch still became one of the most expensive reversals in marketing history, because the research measured taste preference while purchasing behavior was driven by brand attachment and loss aversion; forces a sip test cannot see. Executives compounded the instrument problem with a judgment problem, discounting the 10 to 12 percent of tasters who reacted with open hostility to the idea of replacing the original. The signal was in the data. Confirmation bias filtered it out.

The pattern is not rare. McDonald's spent $300 million developing and marketing the Arch Deluxe on research that said customers wanted a premium burger; its core audience did not. Amazon took a $170 million write-down on the Fire Phone. Estimates in the insights industry hold that up to 95 percent of new products miss their revenue or market-share targets, and flawed research is a recurring cause. The uncomfortable explanation is that product research is a psychological transaction between two humans, and cognitive bias operates on both sides of it.

Bias on both sides of the research process

On the respondent's side, the distortions are well documented. Social desirability pushes people toward answers that make them look sensible and virtuous, which is why surveys reliably understate gambling, drinking, and impulse purchases. In our work with FanDuel, we found market research surveys running at 40 to 60 percent reliability, with actual behaviors underestimated by as much as 50 percent, largely because respondents were reporting the self they wanted to present rather than the self that places bets. Acquiescence pushes people toward agreement with whatever is asserted. Framing determines whether the same trade-off reads as a gain or a loss. Hypothetical questions invite answers about an imagined future self who is more patient, healthier, and more willing to pay than the real one. Researchers call the resulting gulf the say-do gap, and it is wide enough that stated purchase intent alone is a poor basis for a launch decision.

On the researcher's side, the biases are quieter and arguably more damaging, because the researcher writes the instrument. Confirmation bias shapes which questions get asked at all: a team that believes in its roadmap drafts questions that invite validation. A leading question does the persuading before the respondent speaks. The availability heuristic lets one vivid interview quote outweigh thirty contradicting data points, and anchoring lets the first user quoted in the readout set the frame for everyone who reads it. The Nielsen Norman Group's work on why user interviews fail lands on the same underlying problem: people cannot accurately report the causes of their own behavior or predict their future actions, and interviewers who take such reports at face value are collecting fiction with good production values.

The compounding effect is what makes this dangerous. A biased question produces a distorted answer; a motivated analyst interprets the distortion favorably; a leadership team anchored on the original strategy hears the interpretation as validation. By the time the product ships, the error has passed through three or four hands, each adding confidence and none adding accuracy. The data told them what they wanted to hear. New Coke, the Arch Deluxe, and the Fire Phone all followed this path.

Building more reliable product research

The defenses are practical. Ask about past behavior rather than intentions: what someone did last month predicts what they will do next month far better than what they say they will do. Separate discovery research from validation research, and be honest about which one you are running, because a validation study designed by the roadmap's owner will validate. Field instruments only after auditing them for embedded cues, from anchoring numerals to authority claims to response scales with no way to disagree. Where the stakes justify it, run split tests on wording itself and observe behavior directly, through prototypes, pre-orders, and pilots, rather than through attitudes alone.

Bias auditing also cuts in a direction that surprises most teams: some biases help. When we analyzed 36 post-flight survey questions for Delta Airlines, we identified 85 bias instances across 12 bias types, then recommended eliminating the 17 high-severity instances that corrupted the data while deliberately preserving 23 helpful ones, psychological cues that reduce survey fatigue and keep completion rates up without distorting answers. A blanket purge of everything that touches psychology would have produced a purer instrument that fewer people finish. The judgment call, harmful versus helpful, is exactly the kind generic tooling gets wrong.

There is also a mindset correction worth making. When we remove biases from research questions, respondents become measurably more likely to say they are undecided. Teams sometimes read this as weaker data. It is better data. A market that is genuinely undecided about your product concept is a fact worth knowing before the capital is committed, and a research process that converts that ambivalence into polite agreement hides the risk until launch day, when it is most expensive to discover. Coca-Cola's tasters could have told the company what would happen. Some of them did. The research just was not built to hear it.

Better questions start here

Make bias work for you.

CogBias helps teams identify and improve biased survey questions before they affect the results.

Request a Demo!