Womansplain Back

This one is just the lines.

The explanation for why this happens is somewhere else. Here you get sentences you can put in your mouth before you need them.

The reason mansplaining works in the moment is not that you have no response. It is that you are trying to compose a good one while he keeps talking.

By the time you have it, the moment has closed. He has finished the tutorial, everyone has moved on and you have nodded through another explanation of the thing you built.

Do not try to be witty.

Be ready.

Delivery

Say these the way you would correct the date of a meeting.

Pleasant. Certain. Already moving on.

No apology before the sentence. No nervous laugh afterward. Do not add three paragraphs explaining that you understand he was only trying to help.

Say the line and stop.

The heat is what turns a correction into an incident. Once it becomes an incident, the conversation moves from what he did to how you responded.

Pleasant. Certain. Already moving on. Say it, stop and let it sit.

When he explains your own work to you

“I’m good on the background. I built this. Let’s go to the open question.”

“I know this one cold. We can skip ahead.”

“I wrote the spec, so I have the fundamentals. Take me to the part that is still undecided.”

“I designed the current version. What specifically are you proposing we change?”

You are not arguing about whether you are knowledgeable.

You are correcting a factual error about who knows what, then returning to the work.

When he is explaining something basic

“You can go a level up with me.”

“Assume I have the basics.”

“I’m familiar with that. Keep going.”

Or the shortest version:

“I know.”

Full sentence.

Warm tone.

Then move on.

The short version works often enough to keep. Sometimes he continues anyway. Now you have said you know and been ignored, which is more irritating than remaining silent.

Expect that possibility before using it. The line is not magic. It is a boundary delivered in three words.

When he creates a special beginner version for you

The main conversation is moving along. He turns toward you and starts a smaller, simpler conversation inside it.

Try:

“No need for the sidebar. I’m tracking the main discussion.”

“Let’s keep this with the group. I’m following.”

“I have the context. You can stay with the main point.”

“I don’t need a separate walkthrough.”

Say it once.

If he does it again later, returning to the same line may make the entire meeting about your response. At that point, use the deeper technical question or address the pattern privately afterward.

When he explains your idea back to you

“Right. That’s the point I raised earlier.”

“Yes, that’s the recommendation I opened with. Good, we agree.”

“Exactly. That’s why I proposed it.”

“Correct. That’s the approach I described a few minutes ago.”

No edge.

You are correcting the minutes.

The goal is not to embarrass him. It is to reconnect the idea to the person who introduced it before the room quietly forgets.

When he presents your idea as though he improved it

“That’s the same recommendation. What have you changed?”

“I’m hearing my original proposal. Is there a difference I missed?”

“Yes, that’s the direction I recommended. Let’s decide whether we’re adopting it.”

The question forces him to identify the new contribution without requiring you to accuse him of taking credit.

If there is a real difference, fine. Now the room can discuss it.

If there is not, the ownership has already been restored.

When he asks, “Does that make sense?”

“It does. Does my concern make sense to you?”

“It does. I’d take it further, actually.”

“Yes. The part I’m focused on is what happens when that assumption fails.”

“Yes. The basic model is clear. Here’s where it gets difficult.”

The strongest response is usually not “Yes, I understand.”

It is moving the conversation to the level where the actual problem lives.

He offered a comprehension check. You return with analysis.

When he repeats himself after you already answered

“I understood the first time. My answer is still the same.”

“I follow the point. I disagree with the conclusion.”

“We’re not stuck on comprehension. We disagree.”

“I understand what you’re saying. Repeating it will not change my answer.”

This one matters because disagreement is often treated as evidence that you did not understand.

Do not accept the premise.

You understood.

You still disagree.

When subtlety has failed

You can mirror the behavior back.

Same patient tone. Same unnecessary simplification.

“Let me make sure I have you. You’re saying [restate the basic point]. Yes, I had that. Here’s where it gets complicated.”

Use this sparingly.

It works because he can hear the behavior when it comes back in his direction. It also carries more cost than people admit.

This is the line that may be remembered later as you being sharp, condescending or difficult. Use it when the pattern is obvious, the softer correction has failed and the issue matters enough to justify the friction.

Not every annoying man deserves your most expensive sentence.

The quieter version is usually better

Go deeper.

No confrontation. No announcement that you know more. Answer at the level the work actually requires.

Name the tradeoff he missed.

Ask what happens under failure.

Identify the dependency.

Point out the second-order consequence.

Use the specific detail that only someone close to the work would know.

Do not perform complexity for the sake of winning. Use the real complexity already present.

There is nothing to complain about afterward. You contributed expertise to the meeting.

The room adjusts its understanding of who knows what without anyone having to announce the correction.

Go one level deeper without making the correction the subject of the meeting.

This is the version I use most.

Prevent the tutorial before it starts

Plant your expertise in the first two minutes of a new room.

“For context, I’ve owned this area for several years and built the current version, so I’ll take the deeper technical questions.”

“I led the design work here. The decision we need today is whether to keep the current approach or change the dependency.”

“I own this system. I’ll give the short background, then I want to focus on the unresolved risk.”

“I’ve been closest to this work, so I’ll walk us through the decision.”

Now the room has somewhere accurate to file you.

Expert.

Owner.

Decision maker.

There is much less space for a beginner tutorial to land once everybody knows you built the thing being discussed.

Establish the expertise in the first two minutes. Every other line is repair.

The repeat offender

Address the pattern once, privately and calmly.

“I’ve noticed you regularly walk me through things I already know. I don’t need the explanations. Let’s work as peers.”

Or:

“You often give me background after I’ve said I’m familiar with it. I need you to take me at my word and move to the substantive question.”

Do not bring a dozen examples unless he denies it. Start with the pattern and the change you want.

There are two common outcomes.

He is embarrassed, adjusts and becomes slightly awkward around you for a while. That usually passes.

Or he decides you made an issue out of something harmless and tells somebody else about it.

That can happen.

The private conversation is not risk-free just because you delivered it well. Decide whether the pattern is frequent enough, costly enough and important enough to address directly.

What not to say

Avoid lines that feel satisfying but create a larger problem.

“Are you seriously explaining my own job to me?”

Accurate, perhaps. Useful, rarely.

“Thanks for mansplaining that.”

Now the meeting is about the word mansplaining.

“I’ve been doing this longer than you.”

That turns expertise into a tenure contest and gives him somewhere easier to argue.

“Wow.”

Everyone hears the contempt. Nobody hears the correction.

The best line is usually the one that restores the level of the conversation and gives the room somewhere productive to go next.

Pick three

Do not try to remember every sentence on this page.

Choose three.

One for the basic explanation:

“You can go a level up with me.”

One for your own work:

“I built this. Let’s go to the open question.”

One for disagreement disguised as confusion:

“I understand. I disagree.”

Say them aloud several times.

The point is to have the sentence ready before your pulse rises and your brain starts searching for something clever.

Expect mixed results. Sometimes the line works immediately. Sometimes he continues. Sometimes the room notices. Sometimes it pretends not to.

A script that works every time does not exist.

The useful script is the one you can actually say while the moment is still open.

Do not be witty.

Be ready.

Pick three.