The Exhaustion of Conversations Where Nothing Gets Resolved

The glare from the conference room screen reflects in your colleague’s glasses. You’ve been in here for forty-seven minutes. The spreadsheet on the screen shows the project is on track, the numbers are clear, and the next steps are listed in column G. But you’re not talking about column G. You’re talking, again, about ‘alignment’. For the third time, he says, “I just don’t feel we’re all on the same page.” You resist the urge to point out that you are all literally looking at the same page. You want to ask, “what page do you want to be on?” but you know it won’t help. You’re stuck, and you can feel the energy draining from your body as you prepare to circle the same point again, wondering in the back of your mind, “how to deal with a colleague who derails every meeting.”

This is more tiring than a shouting match. A direct, angry conflict is a fire, hot and dangerous, but it burns fuel and eventually goes out. This is a swamp. Every move to get out just sucks you in deeper. The reason it’s so uniquely draining is that you’re being asked to solve an unsolvable problem. The conversation isn’t actually about the project plan, the budget, or the timeline. It’s about managing the other person’s feelings, and they’ve made you responsible for it. You’re not in a negotiation; you’re in a feedback loop where the only goal is to achieve a state of feeling that the other person can’t define and you can’t deliver.

What’s Actually Going On Here

The core of a circular, irresolvable conversation is the difference between a concrete request and an abstract demand. A concrete request is something you can do. “Move that deadline to Friday.” “Give me access to the shared drive.” “Tell me you disagree with my conclusion.” You can do it, not do it, or negotiate it. Either way, there is movement.

An abstract demand is a request for an internal state. “I need you to be more supportive.” “You need to show more respect.” “We need to have more alignment.” These demands feel significant, but they are functionally empty. There is no action you can take to guarantee the other person feels supported, respected, or aligned. When you try, you end up guessing. You offer more data, you rephrase your commitment, you schedule another meeting. In response, they don’t say, “Great, that action made me feel respected.” They simply restate the original demand: “I still feel like you’re not really hearing me.” This is a communication trap known as a paradoxical injunction: you are being ordered to do something that, by its nature, cannot be done on command. You cannot make someone feel a certain way.

This pattern doesn’t happen in a vacuum. It thrives in systems, teams, families, organisations, that are allergic to clear decisions and direct conflict. If the culture rewards those who express concern over those who take action, there is an incentive to keep conversations in the abstract realm of feelings. As long as someone “feels unheard,” the decision can be postponed. The person blocking progress gets to look thoughtful and responsible, while the person trying to move forward looks impatient or insensitive. The system protects the stalemate because a clear decision might create open disagreement, which the system can’t tolerate.

What People Usually Try (and Why It Backfires)

Faced with an abstract demand, competent people try to be helpful. They treat the unsolvable problem as a real one and apply logical solutions. Each one makes perfect sense, and each one fails.

• You offer more evidence.

  “Here are the engagement numbers from last quarter. As you can see, the strategy is working.” This backfires because the conversation was never about the evidence. The other person isn’t disagreeing with your data; they are telling you the data doesn’t make them feel secure. Presenting more of it just makes them feel like you aren’t listening to their actual (unspoken) concern.

• You try to provide reassurance.

  “I want to assure you that I’m fully committed to this project and I value your input immensely.” This is an attempt to directly give them the feeling they’re asking for. But words are cheap. Because there is no concrete action tied to the reassurance, it can be dismissed as insincere. The loop continues, now with an added layer of questioning your motives.

• You ask for a specific, actionable solution.

  “I understand you feel we’re not aligned. What is one specific thing I could do in the next hour that would represent better alignment for you?” This is the most logical move, and it’s also the one that exposes the trap. Because the person isn’t seeking a specific action, they will almost always deflect with another abstraction. “It’s not one thing, it’s the whole approach.” They bat away your request for clarity and put the burden of solving their feeling right back on you.

What Shifts When You See It Clearly

The moment you correctly identify the pattern, the demand for a feeling, you stop trying to solve it. This is not about giving up. It is a fundamental shift in your objective. Your goal is no longer to make the other person feel aligned, supported, or respected. Your goal is to identify the next required action and make a clear decision.

This shift feels like putting down a heavy, invisible weight. The weight of being responsible for another person’s emotional state. You stop diagnosing their psychology and start managing the situation. You realise their feelings are their own to manage; your responsibility is to the project, the team, or the shared goal. You stop seeing their abstract demand as a legitimate obstacle and start seeing it for what it is: information about their internal state, but not a directive you can or should follow.

This doesn’t mean you become callous or dismissive. It means you become precise. You stop engaging in the swamp of “how we all feel about the thing” and focus on “what we are going to do about the thing.” You move the conversation from the internal and subjective to the external and observable.

What This Looks Like in Practice

Once you see the pattern, you can stop feeding it. Your responses change from trying to solve the feeling to clarifying the action. These are not magic phrases, but illustrations of how you can shift the conversation onto solid ground.

• Acknowledge the feeling, but pivot to action.

  “I hear that it doesn’t feel right to you yet. To move forward, we need to decide on the budget by noon. Let’s focus on the two options on the screen. Which is the stronger choice?” This line acknowledges their state without accepting responsibility for it. Then it firmly re-grounds the conversation in a tangible task with a deadline.

• Translate their abstraction into a concrete, binary choice.

  “When you say you need me to be ‘more supportive,’ I want to make sure I understand. For the purpose of this next step, would support look like me publicly endorsing your proposal in the team meeting, or would it look like me giving you an extra day to refine it? Let’s pick one.” This takes their vague demand and translates it into a testable action. It forces them out of the abstract and into a real-world commitment. If they refuse to choose, the pattern becomes obvious to everyone.

• Name the circular pattern gently.

  “I think we’ve discussed the overall feeling of alignment a few times now, and it seems we’re going in a circle. I’m concerned we’re going to run out of time before we make a decision. For now, I’m going to make the call to proceed with Option B.” This externalises the problem, it’s not “you are being difficult,” it’s “we are in a circle.” It states the consequence (running out of time) and then models the required behaviour: making a decision.

• State what you will do, rather than debating what they feel.

  “I can’t guarantee this approach will feel right to everyone, but I can guarantee that we will review the data together every Monday morning to track its impact.” This explicitly separates your actions (which you control) from their feelings (which you don’t). It offers a concrete, reliable process as a substitute for an unreliable feeling.