The Mistake of Thinking a Conversation Is a One-Time Event

The meeting door clicks shut behind him, and you let out a breath you didn’t realise you’d been holding. It was a hard conversation, but it went well. You were clear, you were firm, you laid out the new expectations and the consequences. He nodded, said he understood, and even seemed a little relieved. You lean back in your chair, cross that task off your list, and feel the familiar, fleeting sense of resolution. A week later, you see it: the same missed deadline, the same vague excuse dropped into Slack, the same passive-aggressive sign-off on an email to the client. The knot in your stomach tightens and a single, frustrated question forms in your mind: “Why do I have to have the same conversation over and over again?”

The exhaustion you feel in that moment isn’t just about the repeated problem; it’s from the collapse of a deeply held, and deeply flawed, assumption. You treated the conversation as a discrete event, a transaction of information. You said the right words, they heard the words, and therefore the behaviour should change. But a difficult conversation is never a single event. It’s the opening of a process. The real mistake isn’t what you said in the room; it’s believing that what happens in the room is enough.

What’s Actually Going On Here

When a behaviour persists after you’ve clearly addressed it, it’s rarely because the person didn’t understand you. It’s because the behaviour is perfectly adapted to the system it lives in. The conversation is a single point of pressure you’re applying, but the rest of their environment, the team’s workflow, the company’s reward structure, the client’s demands, is a constant, invisible force pushing them back to the old way.

Think of the team member who consistently submits rushed, error-filled work. You have the talk about “taking more ownership” and “improving attention to detail.” But the team’s workflow rewards speed above all else. The person who gets their piece done first unblocks three other people, receiving a subtle hero-status, while the person who takes an extra day to do it right is seen as a bottleneck. You delivered a message about quality, but the system screams for speed. Your 30-minute conversation is one data point; the system provides a hundred data points every day telling them to do the opposite.

This is made worse when our feedback is abstract. A manager tells a report, “I need you to take more ownership.” That phrase feels clear to the manager, but to the employee, it’s a puzzle. Does it mean generating new ideas? Flagging risks earlier? Setting their own deadlines? Without a concrete, observable definition, the employee will default to their old habits because at least those are known and predictable. They aren’t ignoring you; they are navigating a fog you helped create.

What People Usually Try (and Why It Backfires)

Faced with a problem that won’t go away, we tend to reach for a few logical-seeming tools that only reinforce the pattern. You’ve probably done at least one of these.

• The Re-Briefing. You call another meeting and have the same conversation, but with more intensity. You might say, “I want to be crystal clear this time,” using sharper language and a more serious tone. This backfires because it assumes the problem was a lack of clarity. It wasn’t. The real issue is the gap between intention and execution, and raising the stakes just adds shame and defensiveness, making it even harder for them to ask for help where they’re actually stuck.

• The Paper Trail. You shift from coaching to documenting. Your emails now start with, “As per our conversation on Tuesday…” You begin logging instances to build a case for HR. This backfires by immediately transforming a performance issue into a legalistic, adversarial process. The person’s focus shifts from “how do I fix this?” to “how do I protect myself?” Trust evaporates, and any chance of a genuine solution disappears with it.

• The Strategic Withdrawal. You get frustrated and pull back. You stop assigning them critical tasks or you just start fixing their mistakes yourself because it’s faster. You think you’re mitigating risk, but you’re actually doing something far worse: you’re teaching them that their problematic behaviour is survivable. The system simply routes around them, the pressure to change vanishes, and the habit becomes permanently entrenched.

The Move That Actually Works

The most effective move is to stop seeing the conversation as the solution. The conversation is just the diagnosis. The solution is the structured follow-up that you design together. The goal isn’t to get them to agree with you in the room; the goal is to establish a shared, observable reality and a lightweight process for checking in on it.

This means reframing the initial conversation from a verdict to a starting line. You are not delivering a final judgment; you are co-creating a new set of expectations and, crucially, a plan to support them. Your job shifts from being the enforcer to being the architect of a support system.

This works because it acknowledges the truth: changing a habit is difficult and rarely linear. People don’t fail because they are defiant; they fail because the old way is easier, more practiced, and better supported by the surrounding environment. By building a follow-up process, you are creating a temporary, alternative environment, a scaffold, that supports the new behavior until it’s strong enough to survive on its own. It replaces the pressure of a single, high-stakes event with the manageable cadence of iterative, low-stakes check-ins.

What This Sounds Like

These are not scripts, but illustrations of how to operationalise this shift. Notice how each one sets up the next conversation.

• At the end of the initial talk: “Okay, we’re aligned on what ’taking ownership’ actually means for this role. I know changing habits is hard, so let’s not pretend this will be a perfect switch. Let’s put 15 minutes on the calendar for next Thursday just to check in on where this is feeling easy and where it’s getting stuck.”

  • Why it works: It normalises imperfection and defines the purpose of the follow-up as support, not surveillance. It makes the next conversation safe.

• At the start of the check-in: “Last week, we talked about getting ahead of client deadlines. Talk me through how that went with the Acme project. What was one moment where you were able to do it, and one moment where the old habit took over?”

  • Why it works: This isn’t a “did you succeed or fail?” question. It’s an after-action review. It gathers data on specific moments, treating setbacks as information, not as moral failures.

• When you see a problem: “I noticed the report went out with the same data errors we talked about. Before I jump to conclusions, can you walk me through your process this time? Where in the workflow is this breaking down?”

  • Why it works: It separates the person from the behaviour and frames the problem as a systemic breakdown, not a personal failing. It invites them to be a fellow detective looking at a process problem, rather than a suspect under interrogation.

• To connect it to the system: “It sounds like you only get the final data from the analytics team an hour before the deadline. That makes it nearly impossible for anyone to do a thorough review. Let’s talk to their lead together.”

  • Why it works: It demonstrates that you see the wider context and are willing to take action to change the system, making you an ally instead of just a critic.