In Brief
- Most hard conversations at work fail because both sides are protecting themselves, not the issue.
- The “skilled” version — polite, professional, hedged — is often the most avoidant.
- Both people unconsciously soften until the real issue is no longer on the table.
- The fix isn’t being tougher. It’s being more specific.
- Productive hard conversations name the thing, bring evidence, and stay open to being wrong.
Most hard conversations at work fail before either person opens their mouth.
You schedule it. You rehearse what to say. The other person senses it coming because they got an unusual calendar invite. Both of you walk in already braced. Both of you spend the first ten minutes circling the actual issue. By the end you’ve reached “alignment” that neither of you believes. A week later, nothing has changed.
This is the most common, most expensive, and least talked-about leadership failure in small business. And it has a name.
The pattern: both sides protect themselves
Chris Argyris spent thirty years studying why intelligent, well-intentioned people can’t have direct conversations with each other. His conclusion was unsettling. The reason isn’t a lack of skill. It’s that both parties are operating with the same hidden goal — protect myself from looking bad, losing the relationship, or feeling embarrassed.
He called this Model I thinking. Four operating principles run quietly underneath it:
- Stay in control of the conversation.
- Win, don’t lose.
- Suppress what you actually feel.
- Look rational at all times.
When two people both run on Model I, they can’t have a hard conversation. They can have a polished impression of one. They’ll be civil. They’ll nod. They’ll say “I hear you.” And neither of them will say what they came to say.
How the defensive routine actually works
Watch a hard conversation in slow motion.
You open with the softened version of what you mean. “I just wanted to chat about how things have been going.” You wait for them to volunteer the issue so you don’t have to name it. They don’t. They sense your softening and match it. “Yeah, things have been busy, but generally good.”
Now you’re on a fork. You either escalate — name the actual thing — or you stay soft and the conversation drifts. Most people stay soft. Because escalating feels rude, and they’ve trained themselves to be polite at work.
So you give a hint. They take the hint as a compliment plus a vague concern. They reassure you. You feel uncomfortable challenging the reassurance, so you accept it. The conversation ends with both of you feeling slightly worse than before, and neither of you having said what you came to say.
This is a defensive routine — an automatic pattern that protects both people from short-term discomfort at the cost of actually addressing anything.
The “skilled incompetence” trap
The unsettling part of Argyris’ research is that this pattern gets worse with experience, not better. He called it “skilled incompetence.” The more senior people become, the better they get at appearing to address things while actually avoiding them.
You’ve probably been in a meeting where someone delivered devastating feedback so smoothly that everyone agreed and nothing changed. That’s skilled incompetence. The conversation looked professional. The outcome was zero.
It also shows up as a gap between what leaders say they value and what they actually do — the difference between espoused theory and theory in use. Most managers will tell you they value direct feedback. Watch them in a real difficult conversation and you’ll see something else entirely.
In my PhD research with 19 Australian founders, one of the things that separated leaders who built lasting teams from leaders who didn’t was a willingness to be plain. As one founder put it, “You get answers from divergent mindset” — meaning the most useful conversations came from people who hadn’t yet learned to soften everything.
What it sounds like
The standard “hard conversation” template most managers use sounds like this:
“Look, I want to start by saying you’ve been doing some great work. I just wanted to check in about a few things. There’s no major concern, but I think we could maybe look at how the X project has been going. I don’t want to put too fine a point on it, but a few people have mentioned that maybe communication could be a bit clearer? I’m sure there’s lots of context I don’t have. What do you think?”
That paragraph is six sentences of hedging followed by a question that lets the person off the hook. Nothing concrete will be discussed. Nothing will change.
Compare it to:
“I want to talk about the X project. The thing I want to understand is why the Tuesday deadline moved without anyone telling me until Friday. That happened on three projects this quarter. I’d like to understand what’s driving it from your side, and then I want to agree what changes.”
Same person. Same intent. Completely different conversation. The second version names the thing, gives the evidence, doesn’t pre-blame, and asks for the other person’s view before deciding what to do.
That’s a Model II move. It’s not harder. It’s clearer.
What productive hard conversations actually do
Argyris described three things a Model II conversation does that a Model I conversation can’t.
Share valid information. Both people put the actual data on the table — the specific situation, the specific concern, the specific impact. No hints. No “people have been saying.”
Make free and informed choices. Both people have enough information to decide what to do. The conversation isn’t about getting agreement — it’s about understanding what’s true.
Build internal commitment. Whatever gets decided is owned by both, not imposed by one. The outcome holds because both people meant it, not because one of them performed agreement to end the discomfort.
You can’t get to those three outcomes through polite hedging. You get there by naming the thing.
How to fix it
Five moves change the pattern. None of them require being harder. All of them require being more specific.
1. Name the thing in the first sentence. Don’t bury it. The hedge-then-pivot opening is the most common reason these conversations stall. State what you want to discuss in plain language up front.
2. Bring the evidence with you. Be ready with two or three specific examples. Vague concerns are easy to deflect. Specific events are not. “On Tuesday the deadline moved” is harder to argue with than “communication has been off.”
3. Make your reasoning visible. Argyris called this saying what you’re thinking, including the part you’d normally hide. If you’ve been worried for two months, say so. If you’re nervous about the conversation, say so. Hidden reasoning is what makes the other person defensive.
4. Ask, then listen, then respond. Most managers ask the question and then mentally prepare their counter while the other person talks. Don’t. Listen for what you didn’t know. The point isn’t to win — it’s to find out what’s true.
5. End with what changes by when. Hard conversations that don’t produce a concrete next step might as well not have happened. Agree what one of you will do differently, starting when, and how you’ll check.
What to do this week
If there’s a conversation you’ve been postponing, write down two things before you have it.
First — what is the concrete behaviour, situation, or pattern you want to discuss? Write it in one sentence with specific examples.
Second — what’s the part of your thinking you’d normally hide? Why have you been avoiding this? What are you worried about?
Then have the conversation, and lead with both of those things in the first two minutes. You’ll find the rest of the conversation moves at twice the speed and produces twice the change.
If you’d like to see where these patterns are operating across your team, the workplace diagnostic can help you map the conversations that aren’t happening.
Hard conversations don’t have to feel hard. They feel hard when they’ve been postponed. They feel direct when they happen on time.
For the broader picture across all seven patterns, see What 19 Australian founders taught me about workplaces people don’t leave.
