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 conversation looks like problem-solving and ends somewhere else. Rejecting every suggestion leaves the room quiet, the original problem untouched, and the old conclusion newly proven: nothing can be done.

Eric Berne described the pattern in 1964 as Why Don't You - Yes But, and he treated it as the sequence that first showed him what a psychological game was. On the surface, one adult is asking another adult for a workable idea. Under that, the ideas are there to be faulted. A suggestion that dies leaves the old story standing: nothing can be done, and the people with advice have failed.

Hard problems produce real objections. A budget can be too small. A person can already have tried the obvious fix. The pattern is the sweep. Every option, including ones never tested and ones that would cost something payable, gets the same no. Berne noted that someone playing it fairly will take an idea they had not thought of. The habitual player objects even to moves they have already made, because the purpose of the exchange is the rejection.

The other chair matters. The people saying "why don't you" walked into a contest they were not going to win. Being the wise helper feels useful until the silence arrives, and then it feels like personal failure. That feeling is part of the scene. Drama Triangle is the larger map: helper, blamer, and the person with no moves, and the switch between them. Yes, But is the suggestion contest itself.

This is a sequence, not a personality. People run it without a plan to trap anyone. The useful question is which ending got collected: a next step, or fresh proof that the next step is impossible.

• "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."

The meeting that ends tired: a blocker has sat on the project for weeks. Five fixes get offered. Each one is reasonable and each one dies. The blocker leaves the room untouched. People stop bringing ideas to that person, which the next meeting then cites as proof that nobody has any ideas.

Dinner advice: a friend asks what to do about a parent, a boss, a lease. You offer one concrete move. It is almost right, except for a detail that was not mentioned until the move appeared. By dessert you are both talking about how impossible people are, which was available as a topic before the ask.

The couple's logistics: weekends, money, whose family called. Every plan has a fatal flaw discovered at the moment it becomes specific. The unmade plan is peaceful in a sour way. Nobody had to be the one who chose.

The helper's hangover: you leave a conversation full of suggestions and oddly ashamed. You were recruited as the person who should have had the answer. The shame means the contest worked. Their problem was never on offer as a problem.

The group chat: a paragraph of trouble, then a stack of practical replies, then a single "yeah but" that answers none of them and closes the thread. The poster gets the attention. The thread learns not to try.

Decisions stall in public and stay stalled in private. The hour felt like work. The situation is the same size it was at the start, with an extra layer of evidence that effort is naive.

Helpers burn out or get sharp. Friends start with advice, then switch to distance, then get accused of not caring. Teams route around the person who asks for input and vetoes the input. The route-around becomes the next grievance.

The story "help is useless" gets confirmed often enough to feel like experience. The next ask is even less likely to be a real ask. Closeness thins, because a talk that cannot land is a poor way to spend time with someone.

The ending is reassuring. If every suggestion fails, nobody is in a position to make you do the hard thing, and you still received the attention of being helped. Berne's clinical reading was a conflict about surrender: reject the plan so you never have to yield, while keeping the contact. That is his reading of people who favored the pattern. It is not a finding about everyone who says "yes, but" once.

A stuck conversation also structures the hour. Silence, for some people, is worse than a problem that cannot be solved. The exchange gives both sides a job until the job is exhausted.

The adviser side has its own payoff. Dispensing wisdom feels like competence. Berne treated that side as its own scene, the person who is only trying to help, and he thought the way out of Yes, But was to decline that job. The two chairs train each other.

In Games People Play (1964), Berne defined a game as an ongoing series of complementary moves with an ulterior quality and a predictable payoff. Straight requests, he said, stay straight. A request that was never after the stated goal, or that turns the reply to the helper's disadvantage, is the pattern he was naming. He was explicit that the games in front of him were sequences people were not fully aware of running. Game analysis, in his account, describes the sequence when it shows up. It is not a count of how common the sequence is.

Why Don't You - Yes But is the chapter he called the first game taken apart, and the one he saw most often in parties, committees, and therapy groups. The tacit test, in his summary, is whether anyone can offer a solution you cannot fault. The aim he named was reassurance. The roles are a helpless person and a set of advisers. The social talk can sound adult the whole time. He thought a bare transcript often looks reasonable, and that the living exchange gives the stuck person away by the steadiness of the no.

His practical counter was to stop playing the adviser. If the opening is "what do you do if," answer with the difficulty and hand the next move back. If the opening is "that didn't work," sympathy without a new plan leaves the contest with nothing to reject. Those are clinical suggestions from one tradition, not results from an experiment. Nobody has established a rate for how often the pattern occurs, and this page does not pretend otherwise.

• You asked for ideas and felt a small relief each time one failed.
• The silence at the end felt like winning, or like proof.
• You cannot name one suggestion you would test this week.
• You can play either chair: the stuck one, or the adviser who has to keep producing fixes.
• You get irritated when someone asks what you are going to do, instead of offering a plan.

Keep the real constraints. Retire the veto that covers the whole list. One untested move is enough to break the ending.

• 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." A contest with a single entry is hard to turn into a pile of failures.
• Hand the move back in a sentence Berne would have recognized: "That sounds stuck. What are you going to try?" Then wait. The wait is the point.
• Notice the quiet. Ask what it is for, out loud if you can: "We have retired every option. Do we want a next step, or were we done when the options died?"
• If you hear yourself say "I've tried everything," list three things you have not tried, including a smaller version of one you dislike. The list is private. It only has to contain one row you could do without anyone's permission.

What if the suggestions really are bad?

Then the no can be specific. Name the constraint, and name the move that is still standing. A room that cannot produce a usable idea is an ordinary event. Yes, But is a no that arrives already fitted to whatever was just said, including the version you have not tried.

Does this mean I am stringing people along?

Usually it means the ending is invisible while you are in it. Berne was describing exchanges that feel, from inside, like a sincere search. The check is practical. If you wanted a next step, one untested step would be acceptable. If every next step has to fail, the search was doing a different job, and you can see that without taking on a motive you did not plan.

Against Yes, But, keep the constraint that is real, and give one untested move a date before the conversation is allowed to close.

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.