Accusation Audit

Thinking Tools6.3 Implementing the Action PlanAlso known as Accusations Audit

Originated by Chris Voss (Never Split the Difference, 2016).

Lists every negative thing the other side might think or say, then states each one aloud at the start of the conversation, before they can.

Four negatives the client is holding, and what naming each one first does

At each of the account lead's turns, choose: name the negative before the client can, or move on and hope it stays buried. The client's reply shows, and the bar counts the objections cleared. Illustrative.

Account lead

Client's operations chief

Account lead

Client's operations chief

Select a stage to read it, or play the sequence.A cold open. The rollout slipped three months and support went quiet in month two. The chief opens flat: "We have forty minutes. Let's go through the renewal."First negative. She has not raised March yet, and it is the first charge on the account lead's list. Choose his opening line.Pick a move to see the reply.We did feel that. My people worked weekends for a date your team knew was fiction.Named first: she confirms it instead of building a case for it.Before any new modules, explain March.Left unsaid: it comes back at once, as her objection, and now she owns it.The date, conceded. The account lead admitted the charge in its harshest form, so the chief has nothing left to win by pressing it.Second negative. The tickets that sat for days in month two are the part her team talks about. Choose the next line.Pick a move to see the reply.Behind you, maybe. My dispatchers still remember the week of tickets nobody answered.A defense: it argues with a feeling she has not said aloud yet, so she says it now, louder.That's the part that hurt. We had trucks waiting on a screen that wouldn't load.Named first: she says which grievance matters most, and that is worth knowing.The real wound. She has named what she cares about. Whatever renewal offer comes later has to answer the support gap first.Third negative. She expects a pitch for more modules. Choose the line.Pick a move to see the reply.Honestly, yes. I assumed there'd be a slide.Named first: the suspicion is out, so she can stop waiting for the pitch.So the fix for your software is more of your software.Proves the suspicion she had not voiced, and every later offer looks like a pitch.No pitch coming. With the upsell named, she listens to what comes next as an offer, not a setup.Fourth negative. The last charge on the list: that the vendor will say her data caused the delay. Choose the line.Pick a move to see the reply.There it is. I wondered how long it would take.The accusation she expected, made for her: the meeting turns to who was at fault.Good. If you had, this meeting would be over.Named first: the one line that could have ended the meeting is now off the table.What renewal takes. With nothing left to defend, she says what renewal would need: a named support lead, credits for the delay, and a one-year term at a smaller scope.

Objections cleared0of 4

  1. A cold open (Client's operations chief). The rollout slipped three months and support went quiet in month two. The chief opens flat: "We have forty minutes. Let's go through the renewal."
  2. First negative (Account lead). She has not raised March yet, and it is the first charge on the account lead's list. Choose his opening line.
    • Before the renewal: you probably feel we promised a March go-live we had no way to hit. We did feel that. My people worked weekends for a date your team knew was fiction. Named first: she confirms it instead of building a case for it.
    • Thanks for the time. Let's start with the renewal terms and the new modules. Before any new modules, explain March. Left unsaid: it comes back at once, as her objection, and now she owns it.
  3. The date, conceded (Client's operations chief). The account lead admitted the charge in its harshest form, so the chief has nothing left to win by pressing it.
  4. Second negative (Account lead). The tickets that sat for days in month two are the part her team talks about. Choose the next line.
    • Our support team has grown since spring, so that's behind us. Behind you, maybe. My dispatchers still remember the week of tickets nobody answered. A defense: it argues with a feeling she has not said aloud yet, so she says it now, louder.
    • It may seem like our support disappeared exactly when you needed it most. That's the part that hurt. We had trucks waiting on a screen that wouldn't load. Named first: she says which grievance matters most, and that is worth knowing.
  5. The real wound (Client's operations chief). She has named what she cares about. Whatever renewal offer comes later has to answer the support gap first.
  6. Third negative (Account lead). She expects a pitch for more modules. Choose the line.
    • You probably think I flew out here to sell you more modules. Honestly, yes. I assumed there'd be a slide. Named first: the suspicion is out, so she can stop waiting for the pitch.
    • We do have two modules that would fix most of what went wrong. So the fix for your software is more of your software. Proves the suspicion she had not voiced, and every later offer looks like a pitch.
  7. No pitch coming (Client's operations chief). With the upsell named, she listens to what comes next as an offer, not a setup.
  8. Fourth negative (Account lead). The last charge on the list: that the vendor will say her data caused the delay. Choose the line.
    • To be fair, the data migration did take longer than either of us planned. There it is. I wondered how long it would take. The accusation she expected, made for her: the meeting turns to who was at fault.
    • And you may expect us to blame the delay on your team's data. We won't. Good. If you had, this meeting would be over. Named first: the one line that could have ended the meeting is now off the table.
  9. What renewal takes (Client's operations chief). With nothing left to defend, she says what renewal would need: a named support lead, credits for the delay, and a one-year term at a smaller scope.

An example

A software firm's account lead flew out to a regional freight company for a renewal meeting four months after a rollout that went badly. Go-live slipped from March to June, support tickets sat for days in the second month, and the client's operations chief had told her own team the vendor was finished.

The night before, the account lead wrote down everything the chief was likely to think: we promised a date we could not hit, our support disappeared when it mattered, we are here to sell more modules, and we will blame the client's data. He opened the meeting by saying all four out loud, one after another, and then stopped talking.

The chief said the support gap was the part that had hurt, and that a word blaming her data would have ended the meeting. They spent the hour on what renewal would take. The account closed at a smaller scope for one year, with two months of service credits and a named support lead.

Why it works

An objection the other side raises is theirs to defend: they built the case, they said it out loud, and backing off it now costs them face. The same objection named first by you arrives already conceded, so there is nothing left to win by pressing it. Most people answer an honest admission by softening it ("it wasn't all your fault"), which moves them toward your side of the table.

The audit also drains the anticipation. A counterpart who has rehearsed four grievances listens badly until they are aired. Saying them early, in their strongest form, lets the conversation reach the actual terms. And it forces a discipline beforehand: you cannot name the negatives without first seeing yourself as they see you.

The thinking behind it

Chris Voss Chris Voss, a former FBI hostage negotiator, describes the accusation audit in Never Split the Difference (2016), written with the journalist Tahl Raz. It sits beside his other tools of tactical empathy, labeling emotions and asking calibrated how and what questions: before a hard conversation, list every bad thing the other side could say about you, and say it first, in plain words. The book draws on his field experience, not on controlled studies, and should be read as a practitioner's method.

How to run it

  1. List every negative. Write down each thing they could think or say about you, your offer, or your history, including the ones that sting.
  2. Keep the harsh versions. Phrase each in the words they would use, since a softened accusation sounds like spin.
  3. Phrase each as an acknowledgment. Use "you probably think" or "it may seem like" and name the charge without explaining it away.
  4. Say them first. Name them at the start of the conversation, before your agenda and before they raise any of them.
  5. Stop and wait. Let the silence work; the other side usually answers by correcting or shrinking one of the charges.
  6. Leave the defense out. Do not follow an acknowledgment with a reason, because "but" cancels it.
  7. Move to the terms. Once the air has cleared, turn to what a deal would need, starting with whatever they said hurt most.

Where it goes wrong

The first failure is the hidden defense. "You may think we overpromised, but the delay was partly your migration" is an argument with a polite opening, and the other side hears only the second half. If you notice a "but" in your list, cut everything after it.

The second is overreach: naming accusations nobody holds plants new ones, and a long list read aloud sounds like a performance. Keep to the charges you have real reason to expect, and say them in your own words.

The third is treating the audit as a fix. Naming the support gap buys a hearing, not forgiveness; if the next proposal has no answer to it, the trust bought in the first five minutes is gone by the end of the meeting.

When to use something else

  • Tactical Empathy. When the grievance is already out and the other side is talking, and the job is to label and mirror what they say in the moment.
  • Calibrated Questions. When the air is clear and you need the other side to work out how a deal could happen.
  • Premortem. When the objections to anticipate are your own team's plan failing, not a counterpart's grievances.

Where it sits in SOLVE eX

Go to the source

  • Never Split the Difference, 2016

Back to the catalog