Why Is It So Hard to Say No?
Saying no is hard because we badly misjudge how requests work — we overestimate the cost of refusing and underestimate how often people expect one.
Gizella Nagyne Palinkas
9/9/20266 min read
Saying no is hard because you are not really deciding about the task — you are predicting how the other person will react, and that prediction is systematically wrong. Research on how people misjudge requests shows a consistent gap between how the person asking sees a request and how the person being asked sees it, and the gap runs in a direction that makes every "no" feel more expensive than it is.
That is the pattern. It is not a character flaw, and it is not something you have. It is a prediction error, and prediction errors are correctable in a way that personality traits are not.
The question people are actually asking
This is a very live question. A keyword check run for this article on 9 September 2026 found the question "how to stop people pleasing" carrying an estimated 44,641 monthly searches, against a 30-day baseline of 72,070 — a fall of 38.06% — with a competition score of 46.0, measured as of 8 September 2026.
Two things are worth reading off that honestly. It is a large question by any measure. And the demand on that exact phrasing is falling sharply rather than rising, which is stated here rather than left out because it is the less flattering half of the number.
The prediction error, precisely
The most useful research here is a set of studies by Francis Flynn and Vanessa Bohns published in the Journal of Personality and Social Psychology in 2008, on what they called the underestimation of compliance.
Their core finding is that people asking for something badly underestimate how many others will say yes. In their first study, 42 students predicted how many strangers they would need to approach to get a set number of questionnaires completed. They predicted 20.5 people on average. The actual figure was 10.5. In a second study, participants predicted asking 10.1 people to borrow a phone and actually needed 6.2; 7.2 to escort them somewhere, and actually 2.3. Seventy-nine per cent underestimated compliance.
The most directly relevant piece is what happened when the researchers switched perspectives. In one study, people imagining themselves as the help-seeker estimated a compliance rate of 34.3%, while people imagining themselves as the potential helper estimated 49.6%. In another, the same split produced 50.8% from the seeker's chair and 63.8% from the helper's.
Read that gap carefully, because it is the whole article. The person asking you for something is standing in the chair where the estimate is lower. They expect refusal more than you assume they do. The awkwardness you are bracing for — the sense that a no will land like a betrayal — is calibrated against a version of them that does not exist.
One caveat stated plainly: this research measures how people judge requests for help, in mostly student samples in 2008. It does not measure how anyone feels after saying no, and this article does not have data on that. It is being used for what it does show — that both sides of a request systematically misjudge the other — and not stretched beyond it.
Why September concentrates it
The pattern is year-round and the pressure is not. In the second and third week of September, several request-generating systems switch on at once: the school year and everything attached to it, the new term of clubs and committees, and the Q4 stretch at work when people start pulling projects forward before Christmas.
None is unreasonable on its own. They arrive inside a three-week window and each is evaluated separately, so the total is never actually decided by anyone. What pushes people past capacity is rarely one large yes. It is eleven small ones nobody counted together.
What actually changes it
Insight alone does not move this much. What follows is behavioural, and it is deliberately short.
1. Separate the answer from the reaction. Before responding, write down the two things separately: do I want to do this? and what do I think will happen if I decline? Most of the pressure lives entirely in the second question, and it stops operating in the dark once it is written in words.
2. Buy time by default. "Let me check and come back to you tonight" is a complete sentence, and it is available for almost every request that is not an emergency. Immediate answers are where people-pleasing does most of its work, because there is no interval in which the prediction can be examined.
3. Say no once, without a case. A refusal with three reasons attached invites negotiation on all three. "I can't take that on this term" needs no supporting argument. Adding one converts a decision into a debate you did not want.
4. Do not offer a substitute unless you mean it. "I can't, but I could do X instead" is a genuine offer or it is a way of buying forgiveness with a smaller yes. It is usually the second. Notice which.
5. Count the whole term, not the request. Write down everything already committed for the next twelve weeks in one list. The individual request is nearly always reasonable; the list is what makes the answer obvious.
6. Test the prediction against what happens. After each no, write one line on how the person actually responded. This is the only step that changes the underlying error rather than working around it. If the prediction is systematically wrong, a handful of recorded outcomes will show it — and if it turns out to be right about a specific person, that is real information about that relationship, not about you.
What this article is not saying
Two limits are worth being clear about.
This describes a common pattern in how people evaluate requests. It is not a diagnosis, not a personality type, and nothing here identifies a condition. Difficulty saying no is an ordinary human tendency, not a symptom.
And "just say no more" is not the recommendation. Some yeses are the whole point of having people in your life. The argument is narrower: decide on the actual cost of the task and the actual value of the relationship, not on a forecast of someone's reaction that the evidence says both sides get wrong.
If difficulty setting limits is causing real distress — persistent anxiety, a relationship where refusing feels genuinely unsafe, or low mood that has settled in — that is worth raising with your GP or a qualified professional rather than solving with a framework from a blog.
Take the quiz
Six questions to find where your no gets lost — the moment of the ask, the reasons you attach, the substitute you offer, or the total you never count. Two minutes, no email, nothing stored.
Frequently Asked Questions
Q: Why do I feel guilty saying no even when I have a good reason? A: Because the guilt is not attached to the reason — it is attached to a prediction about the other person's reaction, which sits in a separate part of the decision entirely. That is why adding a better reason rarely reduces it. The research on requests suggests both sides misjudge each other: people asking for things expect refusal more than the person being asked assumes. The guilt is real; the forecast producing it is unreliable.
Q: Is people-pleasing a personality trait or a habit? A: Mind Decoded describes it as a pattern rather than a trait, and that distinction is practical rather than diplomatic. A trait implies something fixed about you; a pattern implies a repeated sequence — request, prediction, immediate answer — with identifiable points to intervene. Nothing in this article is a diagnosis or a personality classification, and the difficulty most people describe is an ordinary human tendency rather than a condition.
Q: What's the shortest way to say no without sounding rude? A: "I can't take that on this term." One sentence, no supporting case. The instinct is to soften a refusal with three reasons, but each reason gives the other person something to negotiate with, which turns a decision into a discussion. Warmth belongs in the tone and in what you say afterwards, not in a longer justification. If you need room to think, "let me check and come back to you tonight" is a complete answer on its own.
Q: Does saying no actually damage relationships? A: This article has no data on what happens after a refusal, and will not invent it. What the verified research shows is narrower and still useful: people consistently misjudge how requests land, and the person asking estimates a lower chance of agreement than the person being asked does. So the specific fear — that a no will be received as unthinkable — is calibrated against expectations the asker does not appear to hold.
Q: Why is it worse at some times of year than others? A: Because requests arrive in clusters rather than evenly. In mid-September the school year, the new term of clubs and the Q4 work push all begin issuing asks within about three weeks. Each is reasonable when evaluated alone, and they are always evaluated alone, so the total is never actually decided by anyone. The fix is structural rather than emotional: count the twelve weeks in one list before answering the next request.
Q: How do I know if I'm being a pushover or just a decent person? A: Check what the decision was made on. If you said yes because the task was worth doing or the person matters to you, that is a choice. If you said yes primarily to avoid an imagined reaction, that is a forecast making the decision. The same yes can be either. Keeping one line of notes on how people actually respond when you decline is the quickest way to find out which one is running your week.
Connect
Questions or thoughts? Reach out anytime.
subscribe to our newsletter
hello@minddecoded.com
© 2026. All rights reserved.
