How to End a Conversation That Is Going in Circles

A client comes to session and says they have just spent forty-five minutes on a call where the same sentence got rephrased three different ways. They offered two new processes, a revised timeline, a detailed breakdown of the last project phase. Each one was met with a sigh and some variation of “yes, but that’s not really the issue.” By minute thirty, the client had no new material to offer and could not figure out how to end the call without making it worse.

This pattern is a perfectly functioning system designed to go nowhere, and the client has been cast in a role inside it.

The roles inside the loop

In a circular conversation, two roles get assigned automatically. The client is the Solution Generator. The other party is the Problem Holder. As long as the client keeps producing solutions for a problem that stays vague, the system holds.

Both roles get something. The Problem Holder gets to feel heard without ever defining what would actually satisfy them. The client gets to feel like they are trying, even as they burn through energy and credibility. Neither party has to face the harder conversation that is sitting underneath: what is the actual demand, and is it something that can be met at all.

The engine of the loop is usually a demand that cannot be fulfilled because it has not been defined. “Be more of a leader.” “Show more ownership.” These feel like requests. They are containers for unspoken anxieties and mismatched expectations. The Problem Holder is often trying to solve an emotional problem through the client’s logistics, and the client is trying to solve a logistical problem the Problem Holder does not actually have.

This pattern is stable because it serves the wider system even when it frustrates the individuals inside it. Making a vague demand is easier than the hard work of defining what “stepping up” actually looks like in specific behaviors. It lets the Problem Holder maintain authority while placing the burden of translation on the client. The client, in turn, keeps guessing because guessing feels more professional than naming the structural problem with the demand.

The moves the client has been making

Re-explaining or adding data. “Maybe if I walk through the Q3 numbers one more time, it will click.” This treats the loop as a problem of understanding. The Problem Holder is not failing to understand. They are refusing to be satisfied by any answer that has been offered.

Offering yet another solution. “Okay, I hear you. What if we tried this instead?” This is the most common trap. The new option validates the premise that the undefined problem is solvable if the client just tries harder. The client is volunteering for another lap.

Validating language. “I completely understand your frustration, and I want you to know we are committed to getting this right.” This promises a future outcome without changing the present dynamic. The Problem Holder hears “I am going to keep saying nice things until you feel better,” which does nothing to stop the loop.

Delaying to a later date. “Let’s put a pin in it and circle back next week.” This guarantees the exact same conversation in seven days. The pattern is not resolved. A repeat performance has been scheduled.

The shift you are coaching them toward

The client’s job is to stop being the Solution Generator. The new job is to name the reality of the conversation itself.

This requires the client to let go of being seen as accommodating in the moment. The goal moves from solving the content of the complaint to addressing the structure of the conversation. The shift can feel abrupt or uncaring to the client. The reframe to offer: respecting the other party’s time and intelligence requires stopping the unproductive cycle, not extending it with more solutions.

The position moves from participant to facilitator. A participant gets caught in the weeds. A facilitator stays focused on whether the process is working, and when it is not, addresses the process directly without blaming the people inside it.

The moves that fit the new position

Name the loop. “I am noticing we have come back to this point about ‘getting ahead of things’ a few times, and my proposals do not seem to be landing. My sense is that we are stuck.” This shifts the focus from content to process. It is a neutral observation rather than an accusation.

State the limit. “I have offered the two solutions that are possible on my end.” Or: “I do not have a different answer for you on that today.” This is a calm factual statement of capacity. It stops the client from looking for a third or fourth solution that does not exist, and it signals that the current path has reached its end.

Define a concrete condition for re-engagement. “For me to act on this, I need you to send me an email with three specific examples of what ‘getting out ahead of this’ would look like. Without that, I am guessing.” This shifts the burden of clarity back to the Problem Holder. The conversation is paused with a clear, productive path back in.

Propose ending the conversation. “It seems like we have gone as far as we can with this today. I suggest we end here. I will take the action item to think about X, and I will follow up by email tomorrow.” Often the cleanest move. The client is deciding politely but unilaterally that the conversation in its current form is over.

What to listen for in the next session

Did the client try one of these? What did the other party do?

If the other party accepted the move, the loop is breaking and the alliance is intact. Reinforce the structure and watch for the second-order pattern: what does the working relationship look like once the looping is no longer the dominant variable?

If the other party escalated, the question is whether the escalation contained any new substantive information or simply pressed harder on the original undefined demand. Most escalations in this pattern are signals that the Problem Holder felt the structural challenge to their role and is defending it.

When the email with three concrete examples never arrives, that itself is a piece of formulation data. The Problem Holder either cannot specify what they want, in which case the demand was emotional rather than operational, or chose not to specify, in which case the demand was a way of keeping the client running rather than a real ask.

When the looping is not a vague-demand problem

Sometimes the other party knows exactly what they want and is using the loop to wait for the client to offer it. This shows up when the Problem Holder rejects everything until the client lands on a specific solution they had in mind from the start. Naming this dynamic is sometimes easier than waiting it out: “I sense you have something specific in mind. If you can tell me what it is, we can talk about whether it is something I can do.”

Sometimes the looping is a sign that the underlying issue is not what the conversation is ostensibly about. The Problem Holder is using a manageable surface complaint to express something they cannot name directly, like distrust of the client’s role, or a larger organizational anxiety that the client cannot solve. The conversation will not produce a different outcome until the real issue is on the table, and producing that surfacing is a different and longer piece of work.

Most of the time, the loop is the vague-demand version, and naming it ends it. The client comes back the following week and reports that the call lasted twenty minutes and produced a written follow-up. That is the win.