Yes, But

One objection is ordinary: "Tuesday will not work because I am on shift." Yes, But starts to show when Wednesday, a phone call, a smaller version, and asking for help all become impossible as soon as they are suggested. The person asks for advice, rejects each suggestion, and finishes with the same problem plus more confidence that nothing can be done.

Eric Berne described this pattern in 1964 as Why Don't You - Yes But. He treated it as the sequence that first showed him what a psychological game was. The request sounds straightforward: "What should I do?" But the repeated response is not to choose or test an idea. It is to explain why each idea cannot work. After enough rejections, the adviser has no suggestions left and the original belief remains: there is no solution.

Hard problems produce real objections. A budget can be too small. A person may already have tried the obvious fix. The important difference is whether the objection helps narrow the options or rules out every option. In this pattern, even untested ideas and affordable compromises receive an immediate no. Berne noted that a person who genuinely wants advice will consider an idea they had not thought of. In the pattern he described, finding a reason to reject the suggestion matters more than trying it.

The adviser is involved too. Offering ideas can feel useful, so the adviser keeps producing them. After every idea is rejected, the adviser may feel frustrated, inadequate, or responsible for finding a better answer. Drama Triangle describes a broader pattern in which people move among helpless, rescuing, and blaming positions. Yes, But is narrower: one person keeps asking for ideas while rejecting them, and another keeps trying to solve the problem.

This is a sequence, not a personality. People can repeat it without consciously trying to trap anyone. The practical question is simple: did the conversation produce a next step, or did it only produce more reasons that no next step will work?

• "Yes, but I don't have time."
• "Yes, but they would never go for that."
• "Yes, but I've already tried everything."
• "Yes, but that would cost too much."
• "Yes, but if I say it, they'll get upset."
• "Yes, but you don't understand my situation."
• "Yes, but what if it makes things worse?"
• "Yes, but that's easy for you to say."

A stalled meeting: a project has been blocked for weeks. The team offers five reasonable fixes. The person who raised the problem rejects each one, but does not suggest an alternative or agree to test anything. Eventually colleagues stop offering ideas. Their withdrawal can then be used as proof that nobody is willing to help.

Advice over dinner: a friend asks what to do about a parent, a boss, or a lease. You suggest one concrete action. A new detail appears that makes it impossible. You adjust the suggestion, and another objection appears. After several rounds, you are discussing how impossible the situation is instead of deciding what the friend will try.

A couple making plans: they need to decide how to spend a weekend, manage money, or respond to a relative. Every specific plan is rejected for a different reason. No decision means neither person has to risk choosing badly, but the practical problem remains.

An exhausted adviser: you leave a conversation after offering many suggestions and feel as if you failed. You assumed it was your job to find the right answer. The other person rejected every answer, and you kept accepting responsibility for producing another one.

A group chat: someone posts a detailed problem and receives several practical replies. They answer each reply with a reason it will not work, without saying what kind of help would be useful or what they are willing to try. People become less likely to respond the next time.

Decisions stall even though everyone has spent time discussing them. The problem remains unchanged, and the failed discussion makes further effort seem pointless.

Advisers burn out or become impatient. Friends may first offer advice, then pull back, and then be accused of not caring. Teams may stop asking the person for input or handle the issue without them because they expect every proposal to be rejected. That exclusion creates another real problem.

After enough repetitions, "help is useless" can feel like a conclusion based on experience. Future requests for advice become less likely to lead to action. Relationships also suffer because one person feels unheard while the other feels that nothing they say can help.

Rejecting every suggestion can reduce immediate pressure. If no idea is workable, the person does not have to risk trying one, making a difficult choice, or being held to a plan. They can also keep receiving attention and concern. Berne's clinical interpretation focused on a conflict about surrender: the person could reject the advice rather than yield to it while still maintaining contact. That was his interpretation of people who regularly used the pattern. It is not a finding about everyone who says "yes, but" once.

The conversation can also fill time and avoid a more direct request. A person may want sympathy, company, or permission to feel upset but ask for solutions instead. Because the stated request and the actual need differ, practical suggestions do not satisfy them.

The adviser has reasons to continue too. Giving advice can feel competent and caring. Berne also examined the role of the person who insists they are only trying to help. His practical response to Yes, But was to stop taking responsibility for generating more solutions. When one person stops offering idea after idea, the repeated rejection cannot continue in the same form.

In Games People Play (1964), Berne defined a game as an ongoing series of complementary interactions with an ulterior quality and a predictable payoff. A straightforward request, in his account, remains directed toward its stated purpose. In a game, the apparent request serves another purpose or leads to a disadvantage for the person who answers it. Berne said people were not fully aware of running these sequences. His analysis describes the pattern when it occurs. It does not establish how common it is.

Berne called Why Don't You - Yes But the first game he analyzed and said he often observed it at social gatherings, in committees, and in therapy groups. He summarized the implied challenge as seeing whether anyone could offer a solution that could not be faulted. He identified reassurance as its purpose and described the participants as a helpless person and several advisers. The words can sound like ordinary adult problem-solving. What distinguishes the pattern is that each suggestion receives another objection and no suggestion is accepted for a test.

Berne's practical response was to stop acting as the adviser. If someone asks, "What do you do if...?" the other person can acknowledge the difficulty and ask what they plan to do. If someone says a suggestion did not work, the listener can respond with sympathy without supplying another plan. These are clinical suggestions from one theoretical tradition, not results from an experiment. Research has not established how often this pattern occurs, and this article does not claim a prevalence rate.

• You asked for ideas and felt a small relief each time you found a reason not to try one.
• When the other person ran out of suggestions, you felt relieved or confirmed that nothing would work.
• You cannot name one suggestion you would test this week.
• You repeat either side of the sequence: rejecting every idea or feeling responsible for producing more ideas.
• You get irritated when someone asks what you are going to do, instead of offering a plan.

Keep the constraints that are real, but do not use one general objection to dismiss every option. Choosing one untested action is enough to change the sequence.

• Before you ask, write one move you are willing to test and one constraint that is actually real. When a suggestion arrives, sort it: already tried, real constraint, or untested. Untested gets a day.
• If you are the adviser, offer one idea, then stop. "I have one thought. If it does not fit, I will not keep generating more." This prevents you from taking full responsibility for solving someone else's problem.
• Return responsibility with a question Berne would have recognized: "That sounds difficult. What are you going to try?" Then give the person time to answer.
• If every option has been rejected, say what is happening: "We have ruled out every suggestion. Are you looking for a next step, or would listening be more useful right now?"
• If you hear yourself say "I've tried everything," list three things you have not tried, including a smaller version of one you dislike. You only need one action you can take without anyone else's permission.

What if the suggestions really are bad?

Then reject them for specific reasons. Name the constraint and say what kind of action could still fit it. Sometimes a discussion produces no useful ideas, and that alone is not Yes, But. The pattern appears when a new objection is available for every suggestion, including suggestions that have not been tried.

Does this mean I am stringing people along?

Not necessarily. Berne described exchanges that can feel like a sincere search for help while they are happening. Use a practical check instead of assuming a hidden motive. If you want a next step, you should be able to identify one untested action that you are willing to consider. If every action must be rejected, you may be asking for something other than advice, such as sympathy, attention, or confirmation that the problem is difficult.

Keep the constraint that is real, choose one untested action, and decide when you will try it before asking for more suggestions.

No time

Tried everything

They don't get it

Practice this pattern in the Reframing App - capture the trigger, label it (like Yes, But), check evidence, and write a more balanced thought.