# How to prepare what to say in a difficult conversation at work

Prepare a difficult work conversation with concrete facts, a clear request and room for a reply. Rehearse one change without scripting agreement.

[Canonical page](https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work)

Prepare the opening: name the specific issue, give the fact that makes it worth discussing, and state the request or boundary. Then leave room for the other person's account. You can prepare what you need to say without deciding their answer for them.

The other person needs to understand what happened and what you are asking for. A careful explanation can still receive a reasonable “no.” Rehearsal lets you inspect your message; it cannot settle the conversation in advance.

## Four anchors before the conversation

- **Point:** what is the main thing you need to say?
- **Evidence:** what specific fact supports it?
- **Boundary or request:** what do you need to change, stop, decide or agree?
- **Next:** what happens after this conversation?

Use short notes, not a script for both sides. Keep an observation separate from your interpretation: “Two checks arrived after the draft was ready” and “You don't respect my time” are different claims. If you do not know why something happened, leave that question open.

## A request the other person can answer

Here is a **fictional practice situation**, not a Ptichi observation. You and a colleague prepare a regular project update. Keep these facts fixed:

- Your draft is ready at 3 p.m.
- On Tuesday and Thursday, extra checks arrived after 3 p.m. and required another pass through the draft.
- You want to ask the colleague to collect changes by 2:30 p.m. for the next three updates, then review how that trial went.
- The colleague has not agreed. You do not yet know why the checks arrived later.
- Urgent changes may still need discussion; the proposed cutoff does not make them disappear.

The trial is an invented option for this example, not a proven workflow or a deadline rule.

A vague opening might sound like this:

> “Could we talk about the updates? On Tuesday and Thursday, extra checks came in after the draft was ready at three, so I had to go through it again. It would be good to get things a bit more organised for the next three updates and see how that goes.”

The issue and impact are present. The colleague still has to guess what “more organised” asks them to do.

A clearer opening makes the request answerable:

> “I'd like to agree when we collect changes for the update. On Tuesday and Thursday, extra checks came in after my draft was ready at three, so I had to go through it again. Could you collect changes by two-thirty for the next three updates, then we review the trial? We'd still discuss urgent changes. What would make that difficult from your side?”

This is an authored contrast, not a measured A/B result. The second opening states a proposal and asks about the colleague's situation. It does not claim that the colleague caused the whole problem, that the trial will work or that agreement already exists.

## Prepare a reply space, not a winning line

Decide what information could change your proposal. In the example, perhaps the colleague receives some checks only after 2:30. That is a possible reply to explore, not an established fact in the scenario. You might need another collection time, a different division of work or a decision from someone who owns the process.

Keep your authority clear:

| What you say | What it commits to |
| --- | --- |
| “Could we try collecting changes by 2:30?” | A request that still needs a response. |
| “We agreed to trial 2:30 for three updates.” | An agreement; say it only after that agreement exists. |
| “I can finish this pass today; a later change needs another pass.” | A statement about your own work, if it is accurate. It does not give you authority to reject every later change. |

If the person disputes a fact, return to what can be checked rather than adding an accusation. If they understand the request but decline it, the next question concerns reasons, alternatives and decision authority. Increasing the intensity of your voice does not create that authority.

For a question that catches you off guard, the [difficult-question guide](/goals/answer-difficult-question-at-work) covers answering the supported question while keeping unknowns visible.

## Rehearse the opening out loud

Use the fictional facts above, or a similarly small, non-confidential situation. Keep sensitive workplace details out of practice shared with another person. Say the opening aloud; optional playback uses a recorder you already have. The Ptichi website does not record.

### Take A

Give a natural first opening without reading the clearer example. Use the four anchors as notes. End at a point where the other person can respond; do not perform their imagined agreement.

### Listen

Check three things:

- Can you hear the concrete issue and the fact supporting it?
- Is the request specific enough to answer, or hidden inside “be more organised”?
- Does the ending allow a reply without turning the proposal into an agreed change?

You know the facts and what you meant. Your self-check shows what you notice, not what an unfamiliar listener would recover.

### Change one thing

Make the request explicit. Replace the vague request with the proposed action, its time and the three-update trial. Keep the issue, supporting facts, urgency limit and review step that were already in your first take.

If the first take also dropped a fact or invented agreement, repair those in a separate pass before comparing the request change. Do not call several repairs one adjustment. If the request was already clear, keep it; you do not need to manufacture a weak version to produce a winner.

### Take B

Say the opening again with that request change. Use your own words while preserving the facts and scope. If recording, keep the setup reasonably comparable. Stop where a genuine reply belongs.

### Compare

Which version makes it easier to tell what you are asking the colleague to do? Did the second version keep the proposal open, the facts intact and the urgent-change limit visible?

If a willing listener is available, ask, “What happened, and what am I asking for?” Keep their answer before explaining your intended meaning. Do not show them the fact key first. Note whether they knew the situation or heard Take A: a repeat listener may already know the request. Preserve a partial or “I couldn't tell” answer.

Ask whether they would agree only as a separate question. Recovering the request does not show that it is workable or fair. The [listener-measurement article](/research/the-listener-is-part-of-the-measurement) explains why understanding, preference and acceptance need separate notes.

### Transfer

Try a different fictional situation: a shared document has two people giving conflicting instructions. You have not been given a final decision-maker. Ask the project lead to name one person who can resolve conflicts before your next revision, while inviting information about a review requirement you may be missing.

Prepare the issue, a specific example, your request and the next revision step in new wording. Naming a proposed decision-maker does not appoint them. This attempt tests another opening; it does not prove lasting learning or success in a real conversation.

## Guidance and our interpretation

Acas's [guide to challenging conversations](https://www.acas.org.uk/acas-guide-to-challenging-conversations-and-how-to-manage-them), published in July 2014, is written for employers and line managers. Its preparation sections emphasise establishing facts and checking the relevant process; its discussion framework includes listening to an explanation before deciding a way forward. This is practical UK workplace guidance, not an evaluation of this rehearsal.

**Our read:** prepare enough structure to make the issue and request inspectable, then leave room to learn something from the reply. The peer-work example and one-change exercise are Ptichi's editorial adaptation. A manager's decision-making role in the source does not give a peer the same authority. We do not know whether this exercise changes later workplace outcomes.

## When rehearsal is insufficient

Some difficult conversations require HR, legal, managerial or safety support. Rehearsal can clarify your message; it does not replace the appropriate professional process. This guide does not decide who has authority, which procedure applies or whether a conversation is safe to have.

An ordinary peer-work example is not a template for harassment, discipline, redundancy or a serious personal disclosure. Use the support appropriate to the actual situation. A clear opening is only one part of a conversation; you may need to correct your understanding, pause or seek help when new facts emerge.

## Continue with Ptichi

Bring one non-confidential opening to the free [pre-meeting rehearsal](/practice/practice-before-a-meeting), available without an account. Keep the issue, fact, request and next step in your notes. Say it once, make the request easier to recover if needed, then try another situation instead of memorising a perfect sentence.

The guide and web exercise are available now. Optional playback uses your own recorder; Ptichi's desktop application remains in development.

Interactive controls remain on the canonical page. This is a saved text representation, not a completed practice or a product result.

## Sources and limits

- [Challenging conversations and how to manage them](https://www.acas.org.uk/acas-guide-to-challenging-conversations-and-how-to-manage-them)
  Preparation based on concrete facts and listening to an explanation before deciding a way forward.
  July 2014 UK guidance for employers and line managers, including formal workplace conversations. Not current legal advice or a controlled study of peer requests, listener recovery, rehearsal, learning or Ptichi efficacy.

## Evidence and limits

- authored-example: This page includes a Ptichi-authored example built for explanation or rehearsal.
  It is an editorial example, not an observed-user result, experiment or proof that Ptichi improves speech.
- bounded-self-listening-exercise: This page includes a bounded listen-and-compare exercise that you can run with your own recorder.
  The exercise does not prove that Ptichi improves speech or that a second take will generalize to other listeners or situations.

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "@id": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work#article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work#webpage",
    "url": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work",
    "isPartOf": {
      "@id": "https://ptichi.com/#website"
    },
    "breadcrumb": {
      "@type": "BreadcrumbList",
      "@id": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work#breadcrumbs",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Ptichi",
          "item": "https://ptichi.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Goals",
          "item": "https://ptichi.com/goals"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "How to prepare what to say in a difficult conversation at work",
          "item": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work"
        }
      ]
    }
  },
  "articleSection": "Goals",
  "headline": "How to prepare what to say in a difficult conversation at work",
  "description": "Prepare a difficult work conversation with concrete facts, a clear request and room for a reply. Rehearse one change without scripting agreement.",
  "url": "https://ptichi.com/goals/prepare-for-a-difficult-conversation-at-work",
  "inLanguage": "en",
  "dateModified": "2026-10-04",
  "creditText": "Ptichi editorial",
  "publishingPrinciples": "https://ptichi.com/product/editorial-policy",
  "isPartOf": {
    "@id": "https://ptichi.com/#website"
  },
  "citation": [
    {
      "@type": "CreativeWork",
      "name": "Challenging conversations and how to manage them",
      "url": "https://www.acas.org.uk/acas-guide-to-challenging-conversations-and-how-to-manage-them"
    }
  ]
}
```