Manager's Toolkit #10: Stop Avoiding That Conversation: The COIN Method for Managers Who Hate Confrontation
A simple four-step framework that turns awkward workplace conversations into productive discussions without torching relationships in the process.
You know that conversation you’ve been putting off for three weeks?
The one about Sarah’s late arrivals. Or the email tone that’s rubbing everyone up the wrong way. Or the fact that someone’s “collaborative approach” actually means they never make a decision without checking with seven people first.
Yeah, that one.
Most managers avoid difficult conversations because we don’t have a good way to structure them. We either word-vomit everything we’re thinking, or we tiptoe around the issue so carefully that the other person leaves thinking everything’s fine.
Neither works.
I’ve found the COIN method gives you just enough structure to stay on track without sounding like you’re reading from a script. It’s not magic. But it does make hard conversations less awful.
What is COIN?
Four steps. That’s it.
C - Context: Set up the conversation
O - Observation: Share what you’ve noticed
I - Impact: Explain the effect
N - Next steps: Agree what happens now
Let me break each one down with actual examples you can steal.
C - Context
This is where you tell someone why you’re having this chat. Don’t spring it on them in the corridor. Don’t sandwich it between “how was your weekend” and “fancy a coffee.”
Be direct about what’s coming.
What it sounds like:
“I wanted to talk about the client meeting yesterday. I noticed something that I think we should discuss.”
“Can we chat about the project timelines? I’ve got some concerns about how we’re tracking.”
“I need to raise something about team communication. Do you have 15 minutes now, or should we grab a room?”
The goal is simple. No surprises. No ambushes. Just clarity about what’s about to happen.
Some people try to soften this bit so much it becomes meaningless. “I wondered if maybe we could possibly have a quick chat about something small that might not be important but...”
Stop. You’re making it worse.
O - Observation
This is what you saw or heard. Not what you think. Not what you assume. What actually happened.
Stick to facts. Avoid interpretation. The second you say “you don’t care about deadlines” instead of “the last three reports were submitted late,” you’ve lost them.
What it sounds like:
“In yesterday’s meeting, when the client asked about timeline, you said you’d need to check with the team before committing.”
“I’ve noticed the daily stand-ups have run over 30 minutes for the past week.”
“The feedback form from the workshop had four comments about the pace being too fast.”
Notice what’s missing? “You always...” or “You never...” or “Everyone thinks...”
Those words start arguments, not conversations.
If you can’t point to a specific thing that happened, you’re not ready to have this conversation yet.
I - Impact
Now you explain why it matters. Not in a corporate word-salad way. Just the actual consequences.
This is where most managers either go too soft or too harsh. Too soft sounds like “it’s not a big deal but...” Too harsh sounds like “you’re destroying team morale.”
Find the middle ground. Explain what happened because of the behaviour.
What it sounds like:
“When we couldn’t give the client a clear answer, they pushed back the contract review by two weeks.”
“The longer stand-ups mean the developers are starting their focused work at 10am instead of 9am, which is cutting into delivery time.”
“Some attendees left early, and two people mentioned in the feedback that they felt lost by the afternoon session.”
See how this connects the observation to a real outcome? You’re not saying “this is bad because I say so.” You’re showing the ripple effect.
Sometimes the impact is about the person themselves. “When you take on every task that comes your way, you end up working until 8pm most nights, and I’m worried about burnout.” That’s valid too.
N - Next Steps
This is where you both work out what changes. Not where you tell them what to do. Not where you hope they magically figure it out.
You’re looking for agreement on something concrete.
What it sounds like:
“For the next client meeting, can we agree you’ll come with a proposed timeline we’ve already discussed as a team?”
“Let’s try keeping stand-ups to 15 minutes. If someone needs longer to discuss something, we’ll schedule a separate chat.”
“For the next workshop, what if we build in a 10-minute break every hour and add some recap slides between sections?”
The key word is “what” or “how” - not “you need to” or “you should.”
If they suggest the solution, they’re more likely to actually do it. Ask “what do you think would help here?” before you jump in with your answer.
And make it specific. “Be more professional” means nothing. “Reply to client emails within 24 hours” means something.
Putting it together
Here’s what a full conversation might sound like:
“I wanted to talk about how we’re managing the project updates. In the last two weeks, the client has emailed me directly three times asking for information that should have come from you. This makes it look like there’s confusion about who’s leading the account, and it’s eating into time I need for other projects. Going forward, can we set up a weekly check-in where you update me on client communication, so I know what’s been covered? That way, if they do reach out to me, I’ll know what’s already been said.”
Not perfect. A bit clunky in places. But it gets the job done.
What if it goes wrong?
Sometimes people get defensive. They interrupt. They blame someone else. They cry (yeah, that happens).
When it does, pause. Ask questions. “Help me understand your perspective on this.” “What’s your take on what happened?” “Is there something I’m missing here?”
You’re not backing down. You’re just giving them space to process.
If emotions run high, it’s okay to suggest a break. “I can see this is difficult. Should we take 10 minutes and come back to this?” is perfectly reasonable.
Don’t just push through and hope for the best.
Why this works
The COIN method works because it separates facts from feelings. You’re not attacking character. You’re addressing behaviour.
It also keeps both of you focused. When you have a structure, you’re less likely to ramble or bring up six other unrelated issues because you’re already having a difficult conversation anyway.
And it respects the other person. You’re not dictating solutions. You’re explaining the problem and working together to fix it.
Will every conversation go smoothly? Of course not. Some people will push back. Some will need multiple conversations. Some will nod along and then change nothing.
But you’ll have done your bit. You’ll have been clear, fair, and direct. That’s all you can control.
The conversation you’re avoiding won’t get easier next week. It’ll just get harder. So grab the COIN method, take a breath, and have the chat.
Your future self will thank you.

