STATE is the five-step framework from Crucial Conversations for navigating moments when stakes are high, opinions differ, and emotions are strong. Most crucial conversations fail not because the people in them lack skill, but because one or both sides move into silence (masking, avoiding, withdrawing) or violence (controlling, labeling, attacking). STATE gives you a sequence that keeps the conversation in the room.

When to use STATE

Use STATE when a conversation has all three elements: high stakes, differing opinions, and strong emotions. The signal you need it is usually one person going quiet or one person going loud.

A performance conversation with someone who becomes defensive
A peer disagreement that has stopped being about the work
A disagreement with a manager about a direction you think is wrong
A difficult conversation that has been avoided for too long and is now charged
Any moment where you feel the urge to either withdraw or force

How to use it

Share facts. Start with observable data, not interpretation. "The deadline moved three times and the client mentioned it on our last call" is a fact. "You're not prioritizing this" is a story.
Tell your story. Share the conclusion you drew from the facts, tentatively. "I started to think this project might not be a priority for you."
Ask for others' paths. Invite the other person's view before defending yours. "I want to make sure I'm reading the situation right — what's going on from your side?"
Talk tentatively. Use hedged language when stating your interpretation — "it seems like," "I wonder if" — so there is room for the other person to correct a wrong reading.
Encourage testing. Make it safe to disagree. "I might be wrong about this — push back if you see it differently."

Example

Them

(after you raise a difficult topic) I really don't know why you're making this a big deal.

On your HUD

I'm not trying to make it a big deal — I want to make sure I have the right picture.
The last three milestones slipped, and I started wondering whether there's something about the project that's harder than it looks from the outside.
What's going on from your side? I might be missing something.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Skipping to your story without sharing the facts first. Your interpretation delivered without the observable foundation lands as accusation, not curiosity.
Forgetting to invite their path. STATE without the Ask step is a lecture with softer language. The question is what makes it a conversation.
Hedging so heavily you lose the point. "Talking tentatively" does not mean burying the message. The facts and the story still need to land.

Where it comes from

Patterson, Grenny, McMillan & Switzler, Crucial Conversations (2002, 3rd ed. 2021)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.