Most people walk into a difficult conversation already knowing how it's going to go. They've decided what happened, what it means, and often what they're going to say — before the other person has said a word.
That approach rarely goes well, and it's one of the most common reasons new managers avoid these conversations entirely, or have them badly when they finally can't put it off any longer.
Clarify, Situation, Behaviour, Impact, Agree
C.S.B.I.A. is a simple five-step structure for having these conversations with clarity instead of assumption. It works because it delays your conclusion until after you've actually gathered the information to support one.
Name the topic, then ask for their side before you say a word of your own. Not "here's what happened," but "walk me through what happened from your side." This single step prevents most of the damage a badly-run conversation causes — you might be missing context that changes everything.
State what you actually observed — specific and factual, not a verdict on who they are as a person. "You missed the deadline on Tuesday" is a situation. "You're not reliable" is a verdict. Only one of those is useful, or fair.
Describe the specific action, not the general pattern you've built up in your head. Specificity keeps the conversation about one identifiable thing that can actually change, rather than a vague sense of dissatisfaction that's hard to act on.
Explain why it actually matters — to the team, the customer, the numbers. Not as a threat, but as context. Most people change behaviour faster once they understand the real consequence, rather than just being told a rule was broken.
Leave with a specific next step and a date attached to it — not just a good feeling. "I'll try to do better" isn't an agreement. "I'll send the report by 5pm every Friday, starting this week" is one.
Why Skipping the First Step Undoes Everything After It
The most common mistake isn't getting the later steps wrong. It's skipping Clarify entirely and walking straight into Situation with a conclusion already formed. Once someone senses they're being told what happened rather than asked, the rest of the conversation becomes about defending themselves rather than actually solving the problem.
Asking first costs almost nothing and prevents a specific, recurring failure mode: confidently confronting someone about something that turns out to have a reasonable explanation you didn't know about.
Why the Structure Matters More With Someone You Know Well
Ironically, this framework matters most exactly when it feels least necessary — with people you already know, whose history with you makes the conversation feel like it doesn't need much structure. That familiarity is exactly what makes it easy to skip Clarify and jump straight to your existing assumption about what's going on, since you feel like you already understand this person well enough to skip the question.
A Structure, Not a Script
This isn't meant to sound rehearsed or robotic in the room. It's a sequence to think through beforehand, so the conversation itself can stay natural while still covering everything that actually needs to be said — in an order that gives the other person a fair chance to explain, before you've already decided what the explanation is.
Every promotion requires a new version of you. Part of that version has learned to walk into hard conversations with a question ready, not a verdict.