Most dictation tools choke on technical language. Wispr Flow doesn't. It understands code syntax, framework names, and developer jargon — so you can dictate directly into your IDE and send without fixing.

Use it everywhere: Cursor, VS Code, Warp, Slack, Linear, Notion, your browser. Flow sits at the system level, so there's nothing to install per app. Tap and talk.

Developers use Flow to write documentation 4x faster, give coding agents richer context, and respond to Slack without breaking focus. 89% of messages go out with zero edits. Free on Mac, Windows, and iPhone.

Try Wispr Flow free

Accident, MD

Nobody wants to have difficult conversations.

We would rather send a passive-aggressive email. Schedule a meeting to "circle back." Leave a vague comment in a shared Google Doc that says "thoughts?" with no further context and pray the other person figures it out. We will go to extraordinary lengths, heroic, almost Olympic lengths, to avoid telling another human being something they need to hear.

And then we wonder why nothing changes.

Welcome to the art of difficult conversations. Where the feedback is real, the discomfort is temporary, and the alternative, which is saying nothing while quietly resenting everything, is somehow still the most popular option in corporate America.

Let us be honest about the epidemic first.

Most people avoid difficult conversations not because they lack the information, but because they lack the stomach. They are afraid of being disliked. Afraid of the other person's reaction. Afraid that naming the problem will somehow make it worse than the current situation, which is, to be clear, a problem that already exists and is getting worse by the day because nobody is naming it.

The math here is not complicated. A difficult conversation lasts twenty minutes. Avoidance lasts forever. You will spend more energy managing the anxiety of not having the conversation than you would have spent just having it. But sure. Let us schedule another team lunch and hope the tension resolves itself over catered sandwiches.

Spoiler: it will not. 

Before you open your mouth, you need a structure. Without one, difficult conversations have a predictable arc. They start with good intentions, drift into emotions, spiral into defensiveness, and end with someone saying "I just think communication could be better" before everybody agrees and absolutely nothing changes.

Enter the SBI Model: Situation, Behavior, Impact.

Developed by the Center for Creative Leadership, it has been around long enough that you have probably heard of it and forgotten it, which is on brand for how most professionals treat frameworks that would actually help them.

Here is how it works: 

•       Situation Anchor the conversation to a specific moment. Not "you always do this." Not "lately I have noticed." A real, dateable, locatable event. "In Tuesday's client meeting..." This matters because vague feedback is dismissible feedback. The second you say "always" or "never," the other person stops listening to your point and starts building a mental catalogue of every exception.

•       Behavior Describe what was observable. Not what you interpreted. Not what you felt. What happened, in terms a security camera could confirm. "You interrupted the client three times before they finished their question." Not "you were dismissive" -- that is a judgment. Not "you did not seem engaged" -- that is a mind read. What did they actually do? Stick to the footage.

•       Impact Now tell them what it cost. The client looked uncomfortable. The team lost confidence. The deal is now at risk. Impact is the reason the conversation is happening at all, and it is the piece most people skip because it feels confrontational. It is confrontational. That is the point. You are not here to make friends. You are here to make progress.

SBI works because it replaces accusation with observation. It removes the personality attack and leaves the behavior visible, addressable, and fixable. It gives the other person somewhere to go with the information other than straight into a defensive crouch.

Here is where most well-intentioned feedback-givers completely blow it.

They deliver the SBI with precision. They feel proud of themselves. And then, the moment the other person opens their mouth to respond, they stop listening and start preparing their rebuttal.

A difficult conversation is not a presentation. It is not a performance review you narrate while the other person sits there and receives. It is a two-way exchange, which means at some point you are going to hear something you did not expect. Maybe a context you did not have. Maybe a frustration that has been sitting unreported for six months. Maybe a completely valid explanation that reframes everything you thought you knew.

You have to be willing to be wrong. Not performatively. Actually willing. If you walk into a feedback conversation with a verdict already in hand, you are not having a conversation. You are delivering a sentence. And the other person will feel the difference immediately, which is why they will shut down, nod along, and change nothing.

Listen like the information matters. Because it does. 

We need to pause and address the feedback sandwich.

You know it. Compliment, criticism, compliment. Say something nice, say the real thing, say something nice again so everyone can pretend the middle part did not happen. This method was invented by someone who wanted to be liked more than they wanted to be effective, and it has been ruining feedback conversations ever since.

The problem with the sandwich is not kindness. Kindness is fine. The problem is that it trains people to hear compliments as warning sirens. The moment you open with "I really appreciate how much effort you put into this..." every experienced professional in your organization immediately braces for the "but" that is coming and stops processing everything before it.

The sandwich also dilutes the feedback. You spend the first thirty seconds softening the blow, fifteen seconds on the actual point, and thirty more seconds making the other person feel better. What lands is confusion. Was that a serious concern or just a minor note wrapped in a compliment?

Retire the sandwich. Say the thing. Be kind while you say it. Those two goals are not mutually exclusive, and the attempt to blend them into a three-layer construction has caused more workplace miscommunication than reply-all emails.

Three things that do not get said enough:

•       Timing matters. Feedback delivered in the heat of the moment is rarely feedback. It is reaction. Wait until you are regulated. Not until you have forgotten. Until you are calm. There is a difference.

•       Tone carries more than words. You can deliver a technically perfect SBI statement and still cause damage with the energy behind it. Condescension wrapped in correct language is still condescension. Check yourself before you check them.

•       Praise publicly. Correct privately. This is not optional. Giving critical feedback in front of an audience is not leadership. It is theater, and the audience does not forget the show. Pull people aside. Give them the dignity of a closed door. The goal is to change behavior, not to make an example.

Difficult conversations are not difficult because people are fragile.

They are difficult because we have built entire professional cultures around the idea that harmony is more valuable than honesty. That keeping the peace is leadership. That if we do not name the problem out loud, it somehow does not count.

It counts. It always counted. It was just counting silently while the team grew frustrated, the performance declined, and everyone kept scheduling lunches.

Have the conversation. Use the framework. Listen like it matters. And for the love of everything, put down the sandwich.

Skip Maloney writes for people who understand that the world doesn’t reward hesitation.

With over 30 years inside executive leadership, Skip has had a front-row seat to how power actually works inside companies, boardrooms, and careers. He has hired executives, fired executives, advised CEOs, and watched firsthand who rises, who stalls, and who disappears quietly.

He created Brace 4 Impact to tell the truth most professionals only learn after it’s too late.

This isn’t theory. It’s pattern recognition earned through decades of decision-making, risk-taking, and being around those who either adapted or became irrelevant.

Skip writes about career leverage, money, travel, health, leadership, risk, and the uncomfortable realities of modern ambition. His work sits at the intersection of business, psychology, and survival in an economy that no longer offers guarantees.

His philosophy is simple: nobody is coming to rescue you, and that’s the best possible news.

Because once you accept that, you become dangerous in the right ways.

Brace 4 Impact exists for builders, operators, and individuals who refuse to drift.

(Disclosure: Some links in this newsletter are affiliate links. If you purchase through them, I may earn a commission at no extra cost to you. I only recommend products and tools I personally use or believe provide value)

Follow me on: