Difficult Conversation Prep How-to
Hard talks fail when they are only diagnosis. Prep the request and the support, not just the critique: impact, change needed, how you will support, and when you will check. This play is timed prep. Conversation length is separate.
Use it for performance gaps, broken commitments, teammate conflict you must mediate carefully, or a scope reset. It is manager practice and education, not legal advice, not a termination script, and not a substitute for HR when policy requires a partner.
Deep context: Difficult conversation scripts at work and Giving and receiving feedback. Cadence context: Weekly 1:1 operating cadence so hard topics are not once-a-year explosions.
Play card
| Field | Detail |
|---|---|
| Time box | 20–30 minutes of prep (before the live conversation) |
| Players | You (primary). The other person in the live talk. Optional HR partner when appropriate |
| Goal | One-page talking points: facts, impact, clear request, support offer, follow-up date |
| Done looks like | You can say the opening aloud in under two minutes without blame theater |
When to use
- Missed commitments that matter, after lighter feedback did not stick.
- Behavior with clear workplace impact (quality, reliability, collaboration).
- Conflict between teammates where you need a structured reset, not a group vent.
- Scope or priority reset that will disappoint someone and must be explicit.
When not to use (escalate instead)
Do not DIY when the topic is harassment, discrimination, retaliation risk, violence/threats, or anything your company routes to Employee Relations. Do not use this play to design a PIP or termination on your own. Follow policy and partner with HR. Education-only literacy: When to talk to HR vs manager, HR for humans, How HR works, and PIP explained for concepts, not DIY legal process.
Do not deliver serious performance actions only over chat if your company requires a live conversation. Do not record conversations where illegal or against policy.
Prep sheet template (fill in the time box)
Situation (neutral facts, dates, artifacts):
Behavior (observable: what someone did/didn’t do):
Impact (on customers, teammates, delivery, trust):
Request (specific change going forward):
Support (what you will provide: coaching, access, clarity, time):
Follow-up date / success signal:
Logistics (private room or video; buffer after; who else if any):
Desired outcome in one sentence:
Out of scope today (do not pile):
Insight check: If Support is blank, you wrote a prosecution brief. Rewrite until support is real.
Step-by-step prep moves
- Write raw facts (5 min). Pull emails, tickets, dates. Prefer artifacts over memory.
- Separate behavior from story (5 min). “Missed the Friday handoff twice” stays. “Doesn’t care” goes.
- Cut blame language (5 min). Delete always/never, mind-reading, and sarcasm. Keep impact.
- Define the ask and support (5 min). One primary request. One or two support moves you will actually do.
- Rehearse aloud (5–10 min). Say the opening once standing up. If you cannot finish without a speech, shorten.
- Schedule with care. Private setting. Enough time. Not Friday-at-5 unless urgency demands it. Put the follow-up on the calendar now.
Opening script (adapt, do not recite stiffly)
“I want to talk about [situation] and the impact it’s having. I’ll share what I’m seeing, what I need to change, and how I’ll support you. Then I want your view. My goal is [desired outcome], not a pile-on.”
If they derail into intent forever
“Intent matters, and we can talk about it. I still need the outcome to change: [request]. Let’s focus on what we’ll do differently by [date].”
If they get emotional or shut down
“We can pause for a minute. This is important, and I want you to be able to respond. Do you want a short break, or to continue with the request first?”
Stay present. Do not fill silence with three new issues. If they disclose something that belongs with HR or EAP, stop diagnosing and point to resources and policy.
Output artifact: talking points one-pager
Your finished prep is a single page you can glance at, not a novel. Include:
- Opening line
- Two to four fact bullets
- Impact in one short paragraph
- The request (one primary)
- Support you will give
- Follow-up date and what “better” looks like
- Parking lot for other issues
Document appropriately: Note date, topics at a high level, agreements, and follow-up in your private manager notes or company system as policy allows. Do not build a shadow legal memo or share widely. This play does not replace required documentation processes.
Sample (fictional, labeled sample): Sam repeatedly skipped the Tuesday handoff to Support, so tickets bounced. Manager prep request: own handoff checklist by next Tuesday; support = 30-minute walkthrough with Support lead; follow-up in one week. Opening stayed on missed handoffs, not “attitude.”
How 1:1 cadence helps
When weekly 1:1s already hold light feedback and commitments, difficult talks are less explosive. Use cadence for early course-corrects; use this prep when the topic needs a dedicated frame. Pair with Delegation without dumping when the root issue is unclear ownership.
Watch-outs
- Piling multiple issues: One primary request per conversation. Park the rest.
- Public feedback: Hard talks are private. Praise can be public; corrective feedback is not a meeting spectacle.
- Debating intent forever: Acknowledge, then return to observable change.
- Surprise PIPs: Formal processes follow company policy with HR. Do not ambush someone with a formal plan you never previewed in lighter form when policy expects progressive clarity.
- Chat-only serious actions: Prefer live conversation when stakes are high and policy requires it.
- Manager as investigator: If facts suggest misconduct in ER’s lane, stop freelancing.