Phrases That Open Conversations Instead of Shutting Them Down

Before anyone rolls a die at an Operation Aetherfall session, every player gets a half-page printed card. Eleven phrases. One instruction: don't memorize these – when a disagreement starts, glance down and see if one fits. Adam White and I built the card because the hardest moment in any difficult conversation is the first sentence, and nobody drafts well while flooded.

The best phrases for difficult conversations at work all do the same job: they open the conversation instead of rendering a verdict. Six from that card carry most of the weight – "Help me understand...", "What problem are we trying to solve?", "I'm working from these assumptions – what are yours?", "Walk me through...", "The story I make up is...", and "That's not my experience..." What follows is why the first sentence sets the trajectory of everything after it, the mechanics of each phrase, the openers that read as attacks, and how to keep one phrase reachable when your pulse is up.

Why does the opening decide how the conversation ends?

A difficult conversation rarely goes wrong in the middle. It goes wrong in the first ten seconds, and the middle just plays out the opening. Here's the cascade. When someone feels attacked in a disagreement – idea dismissed, competence questioned, judgment overridden – the instinct is to fight back, shut down, or avoid. Once that instinct fires, they've stopped processing your argument. They're defending an identity. You answer their defensiveness with yours, information stops moving, and over time people quit raising things at all – which is where the real damage lives, because teams run on people sharing perceptions, concerns, and needs while there's still time to act on them. Most of the conflict types we've mapped on product teams escalate exactly this way: the opening reads as an attack, and the content never gets a hearing.

That's why "You're wrong about this" fails where "Here's what we learned that concerns us" works. The difference isn't tone – it's structure. The first delivers a verdict and invites a defense. The second delivers information and invites a conversation. The soft-startup research says the same thing from another angle: how a conversation begins predicts how it ends, with uncomfortable reliability.

You can't delete the defensive instinct, in yourself or anyone else. You can notice it. Catch the half-second where you think "I'm feeling defensive right now" and you've opened a small window of choice. A prepared phrase is the thing that fits through that window.

What should you say in a difficult conversation at work?

The six phrases below come from From Strong Ground, the language toolkit we built for Conflict Campaign; the full eleven-phrase card ships with the scenario kits. Adam's the licensed counselor. I'm a product manager, and the first time I read "the story I make up is" out loud, it felt like something you'd say in a therapist's office, not a sprint review. I've since said it in sprint reviews. It works better there than almost anything else I've tried.

When you want to...	Try saying...
Understand someone's reasoning	"Help me understand..."
Reframe toward the shared problem	"What problem are we trying to solve?"
Surface hidden assumptions	"I'm working from these assumptions – what are yours?"
Invite the full explanation	"Walk me through..."
Name your interpretation as an interpretation	"The story I make up is..."
Disagree without attacking	"That's not my experience..."

"Help me understand..." recasts the other person as an expert witness on their own reasoning rather than a defendant. Say your manager cuts the discovery work out of next quarter's plan. "You're cutting the one thing that de-risks the rest" opens a trial. "Help me understand what's driving the timeline" surfaces the board meeting behind the cut – a constraint you can actually plan around. This is the workhorse of disagreeing with someone above you because it presses on the information without pressing on the person.

"What problem are we trying to solve?" moves the argument off competing solutions and back onto the problem you're both paid to solve – interest-based problem framing compressed into one sentence. Two leads deadlock over shipping on the 15th versus adding a QA cycle; the question reveals both are protecting the same customer renewal, and now they're designing options instead of trading positions. One warning: delivery matters more here than anywhere else on the card. Asked with an edge, it's sarcasm. Ask it like you genuinely don't know the answer, because you probably don't.

"I'm working from these assumptions – what are yours?" discloses before it asks. You put your own reasoning on the table for inspection first, which makes the question nearly impossible to hear as an attack – and it models exactly the openness you're hoping to get back. Two engineers produce estimates two weeks apart and it starts turning into a credibility fight, until someone says it: one estimate assumes the current API, the other assumes the rewrite lands first. Ten minutes of assumption-swapping settles what an hour of arguing about the number couldn't.

"Walk me through..." asks for reasoning, not a defense. Something useful happens when people re-derive their own logic out loud: they often find the gap themselves, and when they do, it's their discovery – nobody has to lose. You're reviewing a design you're sure breaks under concurrent edits. "This breaks under concurrent edits" earns a rebuttal. "Walk me through what happens when two people edit at once" earns a pause, then either an answer you didn't have or a shared trip to the whiteboard.

"The story I make up is..." is the most vulnerable phrase on the card and the fastest defuser. It files your interpretation as an interpretation instead of as evidence. A colleague's gone quiet for a full sprint after the roadmap change, and the silence is breeding theories. "The story I make up is that you're unhappy with the direction and don't see the point in arguing" hands them something they can correct – "no, my kid's been sick" – or confirm. Either way, you're finally in the real conversation instead of the imagined one.

"That's not my experience..." is the card's disagreement move. It adds a data point without ranking it above theirs, and it renders no verdict on the other person – so there's nothing to defend against. A teammate declares that users never read release notes. "That's not my experience – the last time we rewrote ours, tickets about new features dropped" keeps your data in play without knocking theirs off the table. The conversation becomes about why your experiences differ. Which is where the useful information was hiding anyway.

Which openers shut a conversation down?

Some openers do the reverse job: they announce an attack before any information arrives.

"We need to talk." delivers threat and withholds content. The other person spends every minute between now and the meeting rehearsing defenses against charges you haven't named, so by the time you sit down you're on round three of a fight that hasn't started. Name the topic instead: "I want to talk about the launch date – do you have twenty minutes today?"

"With all due respect..." has never once preceded respect. It flags the attack while claiming immunity for it, and everyone in the room knows it. Its cousin "no offense, but..." works the same way. The disclaimer is the tell.

"You're wrong about this." seats the defendant before presenting any evidence. Even when you're right – especially when you're right – it converts someone who could quietly update their thinking into someone defending their standing in front of witnesses.

The common structure across all three: judgment travels first and information travels second. The six phrases above run the same freight in the opposite order.

How do you make a phrase available under stress?

Knowing a phrase while calm and reaching it while flooded are different skills, and only the second one changes your week. Three moves close the gap.

Pick one phrase, not six. Under stress you'll get roughly one retrieval attempt, so match the phrase to your pattern. If you go quiet when you disagree, take the assumptions phrase. If you argue, take "what problem are we trying to solve?" If you stew over ambiguous behavior, take "the story I make up is."

Bind it to a cue with an if-then plan. Not "I'll communicate better" – something with the shape we push pilot participants toward: "If I feel the urge to stay quiet when I disagree with a decision in a meeting, I will say 'I'm working from different assumptions – can I share them?'" The feeling is the trigger; the phrase is the response. Specific if-then plans roughly double training transfer – from about 30 percent to about 67 – and sharing the plan with someone raises follow-through from roughly 43 percent to 76. Tell a colleague which phrase you're practicing. Ask them to check in two weeks later.

Then rehearse somewhere cheap. Say the phrase out loud, alone in the car if you have to, until it stops sounding like a script. In our pilot sessions the card sits on the table through four hours of fictional disagreements, and the debrief asks the question I'd ask about your practice too: did anyone use one of those phrases – or something like it? "Or something like it" is the point. The card is scaffolding. Once "help me understand" has turned into your own sentence in your own words, you've stopped borrowing it.

You can't draft a whole conversation in advance. You can draft the first sentence – and the first sentence is most of the conversation.