Crucial Conversations

Thinking Tools6.3 Implementing the Action Plan

Developed by Kerry Patterson, Joseph Grenny, Ron McMillan, and Al Switzler (Crucial Conversations, 2002).

A method for conversations with high stakes, opposing views, and strong emotions: secure mutual purpose and respect, separate facts from stories, and speak tentatively while inviting challenge.

Raising three missed deadlines, one move at a time

At each of the manager's turns, pick a line: a dialogue move, or one of the two usual escapes, going quiet or going on the attack. The analyst's reply shows, and the bar tracks how safe he feels to say what is really going on. Illustrative.

Manager

Analyst

Manager

Analyst

Select a stage to read it, or play the sequence.The opening. The analyst's reconciliations were late for the last three month-end closes. Pick how the manager opens.Pick a move to see the reply.Things are fine. Busy, but fine.Silence: a hint he can wave off, so the problem stays unsaid.My attitude? Okay.Attack: a judgment of him, and his guard goes straight up.Sure. They haven't been great.Mutual purpose: a goal he shares, so the talk is safe to enter.He's in. He has agreed to look at the problem, not yet at his part in it.Facts first. Pick how the manager states the problem.Pick a move to see the reply.Not every month. March was on time.A generalization: he argues with the word every, not the problem.Yes. That's right.Facts: nothing to dispute, so the talk moves forward.No dispute. Facts stated plainly leave nothing to argue with. Now the manager has a story about why, and has to decide how to share it.The story. The manager suspects the close has fallen down his list. Pick how to say it.Pick a move to see the reply.That's not fair. You have no idea what my month looks like.A story told as fact: he defends himself against it.Not exactly. It's more that something else keeps jumping ahead of it.Tentative: the story is offered as a guess, so he corrects it.Something else. He has opened the door a little. The manager's next move decides whether he walks through it.Their view. Pick the manager's next line.Pick a move to see the reply.Sure. Will do.Silence: relief for both, and the cause never comes out.Right. Got it.Attack: he stops explaining and starts agreeing.The controller sends me audit requests every close week, and I've been doing those first.Asking for his facts: the real cause comes out, and it is not effort.His facts. The cause sits outside the analyst's control. Both of them now see the same problem.The close. Pick how the manager ends the conversation.Pick a move to see the reply.Me too.No decision: next month's close will look like the last three.Right. I'll forward the next request to you. Shall we check in on the fifth?Decisions, owners, and a date: the talk becomes a plan.A plan. The next close came in on time. The audit requests went through the manager for that week.

How safe he feels0of 5

  1. The opening (Manager). The analyst's reconciliations were late for the last three month-end closes. Pick how the manager opens.
    • No pressure, just checking in on how things are going generally. Things are fine. Busy, but fine. Silence: a hint he can wave off, so the problem stays unsaid.
    • We need to talk about your attitude toward deadlines. My attitude? Okay. Attack: a judgment of him, and his guard goes straight up.
    • I'd like us both to stop scrambling at month end. Can we look at the last three closes? Sure. They haven't been great. Mutual purpose: a goal he shares, so the talk is safe to enter.
  2. He's in (Analyst). He has agreed to look at the problem, not yet at his part in it.
  3. Facts first (Manager). Pick how the manager states the problem.
    • You've been late every single month. Not every month. March was on time. A generalization: he argues with the word every, not the problem.
    • The last three closes, your reconciliations came in two, three, and four days late. Yes. That's right. Facts: nothing to dispute, so the talk moves forward.
  4. No dispute (Analyst). Facts stated plainly leave nothing to argue with. Now the manager has a story about why, and has to decide how to share it.
  5. The story (Manager). The manager suspects the close has fallen down his list. Pick how to say it.
    • Clearly the close isn't a priority for you. That's not fair. You have no idea what my month looks like. A story told as fact: he defends himself against it.
    • I'm starting to wonder if the close has slipped down your list. Is that fair? Not exactly. It's more that something else keeps jumping ahead of it. Tentative: the story is offered as a guess, so he corrects it.
  6. Something else (Analyst). He has opened the door a little. The manager's next move decides whether he walks through it.
  7. Their view (Manager). Pick the manager's next line.
    • Okay, let's just both try harder next month. Sure. Will do. Silence: relief for both, and the cause never comes out.
    • Everyone's month is busy. The close comes first. Right. Got it. Attack: he stops explaining and starts agreeing.
    • Walk me through what jumps ahead of it. I'd like to understand your month. The controller sends me audit requests every close week, and I've been doing those first. Asking for his facts: the real cause comes out, and it is not effort.
  8. His facts (Analyst). The cause sits outside the analyst's control. Both of them now see the same problem.
  9. The close (Manager). Pick how the manager ends the conversation.
    • Good talk. Glad we cleared the air. Me too. No decision: next month's close will look like the last three.
    • So audit requests go through me in close week, and reconciliations are yours by day three? Right. I'll forward the next request to you. Shall we check in on the fifth? Decisions, owners, and a date: the talk becomes a plan.
  10. A plan (Analyst). The next close came in on time. The audit requests went through the manager for that week.

An example

A finance manager at a distribution company had watched one analyst's reconciliations come in late for three month-end closes running. Twice she had hinted at it in a team meeting. The third time, the close slipped a day and the controller asked her what was going on.

Before the conversation she wrote down what she wanted: a clean close, an analyst she did not lose, and a working relationship after. She opened with that goal, then gave the facts (two, three, and four days late) and only then her guess at the cause, offered as a guess. He pushed back on the guess. She asked him to walk her through his month, and the cause came out: the controller sent audit requests every close week, and he had been doing those first.

They left with three decisions: audit requests during close week went through her, reconciliations were his by day three, and they would check in on the fifth. The next close came in on time.

Why it works

When stakes are high and feelings run strong, people drift to one of two escapes: they go quiet, hinting and hoping, or they attack, labeling and overstating. Both stop the flow of information, and the decision gets made on whatever each side already believed. The method keeps both people talking by managing safety, the sense that it is all right to say what you think.

Two moves do most of the work. Stating a shared purpose first tells the other person you are not out to beat them. Separating facts from the story you built on them lets the other side accept the facts and correct the story, instead of rejecting both. The manager's guess was wrong, and because she offered it tentatively, the analyst could say so and give her the real cause.

The thinking behind it

Kerry Patterson Kerry Patterson, a cofounder of VitalSmarts, was lead author of Crucial Conversations (2002), written with Joseph Grenny, Ron McMillan, and Al Switzler. The book defines its subject by three conditions together, high stakes, opposing opinions, and strong emotions, and sets out practices for keeping dialogue going when those conditions push people toward silence or attack. It is a practitioner's guide, not a research report.

How to run it

  1. Spot the conditions. High stakes, opposing views, and strong feelings together mean the usual reflexes will fail.
  2. Decide what you want. Name what you want for yourself, for them, and for the relationship, before you speak.
  3. Open with a shared purpose. Say the goal you both hold, so the other person knows you are not there to win.
  4. Give the facts first. State what happened in terms no one could dispute: dates, numbers, words said.
  5. Offer your story as a guess. Say what you have started to conclude, then ask whether it is fair.
  6. Ask for their facts and story. Invite their version and listen until you could repeat it back to them.
  7. Watch for silence or attack. When either side goes quiet or sharp, stop the content and restore safety by restating your purpose.
  8. Close with decisions. End with who does what by when, and a date to check.

Where it goes wrong

The tentative story turns into a technique. "I'm just wondering if you're lazy" is an accusation with a soft opening, and the other person hears the accusation. A story offered tentatively has to be one you would genuinely revise.

The second failure is mistaking calm for progress. A conversation that stays pleasant because nobody says the hard part has gone to silence, and the manager who walks out relieved has often avoided the fact that mattered. If you never stated the facts plainly, you did not have the conversation.

The third is the missing close. Dialogue that ends without owners and dates feels finished and changes nothing. Write the decisions down before you leave the room.

When to use something else

  • Nonviolent Communication. When the conflict is about needs between peers, and each side must learn to say what they need without blame.
  • Motivational Interviewing. When the facts are agreed and the person knows the problem, but is unsure whether to change.
  • After-Action Review. When the miss belongs to a team and the job is to learn from it together, not to address one person.

Where it sits in SOLVE eX

Go to the source

Back to the catalog