When you make a survey question required and look at the results, you’ll notice that some people answer it thoughtfully. Others type “N/A,” mash their keyboards, or enter false information just to get past the question and out of the survey. They were told the information was required, and some part of them pushed back against being told what to do.

That pushback has a name in psychology, and it accounts for a large share of the unusable data hiding inside otherwise well-designed surveys. Required fields don’t only filter out incomplete responses. They can also actively provoke bad ones.

What Psychological Reactance Actually Is

Psychological reactance is a motivated response that occurs when people feel their freedom of choice is being threatened. It prompts them to restore that freedom, either by doing the opposite of what is required of them or by avoiding the requirement, even when complying would cost them nothing.

The concept was introduced by psychologist Jack Brehm in the 1960s, based on the observation that people have a basic need to feel in control of their own decisions. When that sense of control is threatened, even by something as small as a mandatory form field, it creates an uncomfortable internal state that people are motivated to resolve. One of the most common ways to resolve it is by resisting the restriction itself, whether or not resisting makes practical sense.

This is different from simple laziness or disengagement. A reactant response often takes effort. Typing a fake answer, writing something sarcastic in a required open-text box, or picking a random option just to move forward takes more active pushback than skipping the field would, if skipping were allowed. The behavior is driven by a need to reassert the sense of choice the form removed, not by a wish to avoid effort.

Why Required Fields Specifically Trigger This Response

Not every instruction provokes reactance. Understanding what makes a required field different from a normal request helps explain why surveys are especially exposed to this effect.

A required field removes the option to decline, which is the kind of restriction that most reliably triggers reactance. Research on the topic consistently finds that the strength of the reactant response increases with how strongly a choice is being restricted, and “you cannot proceed without answering this” is about as direct a restriction as a form can present. A polite request leaves room for respondents to feel the choice is still theirs. A hard requirement makes the loss of control explicit and unavoidable.

Framing matters a great deal here. A field marked “required” delivers the restriction as a flat command. The same question framed as “This helps us tailor your experience. Feel free to skip it if you’d rather not” delivers a request instead of a demand. Research on compliance shows that requests which preserve a visible sense of choice provoke far less resistance than demands, even when the practical outcome, answering the question, is the same.

Sensitive or personal questions make the effect stronger. Being required to disclose income, health information, or personal opinions feels like a bigger intrusion on autonomy than being required to give a shipping address. As a result, reactance tends to be stronger and more likely to produce dishonest or low-effort answers on the questions where accurate data matters most.

How Reactance Shows Up in Survey Data

The damage from reactance is rarely obvious. It shows up as data quality issues that look like ordinary noise.

• Nonsense answers in required open-text fields: A required “Why did you cancel your subscription?” box that can’t be skipped will collect answers like “because,” “N/A,” or strings of random characters from respondents who had nothing to say but weren’t allowed to leave it blank.
• Deliberately extreme or contrarian ratings: Some respondents forced to answer a satisfaction question they’d rather skip will select the most negative option available. This doesn’t reflect their actual opinion. It is a way of registering irritation at being made to answer at all.
• Survey abandonment: A respondent who reaches a required field they don’t want to answer often won’t fight it. They close the tab. This shows up as a completion rate problem rather than a data quality problem, but it comes from the same cause.
• Fabricated demographic information: Required demographic fields, especially ones that feel invasive, such as exact income or age, are a common source of low-effort or clearly false entries. The respondent has decided to comply technically without complying honestly.
• Speeding through later questions: Reactance triggered by one required field can carry over into the rest of the survey, with respondents rushing through the remaining questions with little attention. This pattern is documented in research on survey fatigue and resistance.

None of these problems look like reactance on a dashboard. They look like bad data, and without knowing what to look for, it’s easy to blame the respondent rather than the form design that provoked the response.

The Research Behind Choice, Autonomy, and Compliance

Reactance is part of a larger body of psychological research on autonomy and motivation, and that context helps explain why the effect is so persistent.

Self-determination theory, developed by psychologists Edward Deci and Richard Ryan, identifies autonomy as one of the core psychological needs that drive human motivation. Autonomy here means the sense of acting by one’s own choice rather than under outside pressure. When autonomy is undermined, whether by a manager micromanaging a task or a form demanding an answer, motivation and engagement tend to drop, and resistance becomes more likely.

Studies on compliance and persuasion have repeatedly found that people are more likely to agree to a request, and to follow through on it honestly, when the request explicitly preserves their sense of choice. Research on the “but you are free” technique found that adding a phrase reminding people they are free to refuse a request, without changing anything else about it, increases genuine compliance. Acknowledging the person’s choice appears to prevent the reactant response before it starts.

This research helps explain why heavy-handed mandatory fields tend to backfire in ways a completion rate metric won’t show. A required field might raise the percentage of surveys with every question answered, while lowering the percentage of those answers that are honest or useful.

Balancing Data Completeness With Respondent Autonomy

The instinct to mark every field as required is understandable. Missing data is frustrating, and a complete response feels more usable than a partial one. But forcing an answer on every question applies that instinct too broadly, and the cost shows up as quality problems that are harder to detect than missing values.

A more effective approach is to reserve “required” for fields where an answer is essential to the survey’s core purpose, rather than applying it by default. Requiring “Which product did you purchase?” on a product feedback form is reasonable, since the rest of the survey depends on that answer. Requiring an open-ended “Any other comments?” box is much harder to justify. The purpose of an optional comment field is to capture voluntary input, and forcing it defeats that purpose and invites the low-effort answers described above.

Framing required fields in a way that preserves a sense of choice also helps, even when the field can’t be skipped. A brief explanation of why the information is needed, such as “We ask this so we can route your request to the right team,” gives the respondent a reason rather than just a rule. Research on compliance suggests this noticeably reduces resistance compared with an unexplained requirement.

For sensitive questions, offering an easy opt-out, such as a “Prefer not to say” option, captures far more honest data than forcing respondents to choose between disclosing and abandoning the survey. Surveys that let respondents decline sensitive questions tend to see less fabrication in the answers people do give, because those who answer are doing so voluntarily.

What This Means for Survey and Form Design

The purpose of a required field is to collect accurate, usable data. Psychological reactance is how that purpose fails, because required fields can produce answers that satisfy the requirement without serving the reason the question was asked. A completed survey full of resentful, rushed, or fabricated answers is a worse result than a survey with a few fields left blank, even though only the second one looks like a problem in a completion rate report.

Designing around reactance doesn’t mean removing required fields altogether. It means using them selectively, explaining them where possible, and giving respondents a way out on questions where forcing an answer is more likely to produce a made-up response than a true one.

Conclusion

Required fields are meant to protect data completeness, but they can also undermine data quality by triggering people’s need to push back against restricted choice. The solution is to use required fields more deliberately: reserve them for essential questions, explain why the information is needed, and offer real opt-outs for sensitive questions. Surveys that respect respondents’ autonomy where possible tend to get more honest answers overall, which is what required fields were meant to achieve in the first place.