The coworker who snapped

That sounds genuinely painful. Offering help and getting snapped at in front of everyone is the kind of moment that replays on a loop, and the fact that it’s still with you a day later says it landed hard. I’m glad you’re taking a beat before doing anything about it.

I can help you work out what you want to do here. First, can you walk me through the moment itself a little more? What exactly was happening when you jumped in, and what did she say, as close to word-for-word as you remember?

Thank you. That’s a clear picture. Let me reflect two different things back, because they’re doing different work in your head right now.

What happened: during her demo, something wasn’t loading, you offered a fix, and she said sharply, “I’ve got it. Can you please just let me finish?” in front of the team, then didn’t mention it afterward.

What you’ve concluded: that she thinks you’re incompetent and your input is worthless.

The first is something everyone in that room saw. The second is a story about what’s inside her head, and it’s a heavy conclusion to hang on one sharp sentence. Before we decide what to do, the first step of the Communication Protocol is Introspection: getting clear on your own side of this. Would you be willing to spend a few minutes there?

It might really be that simple. And if it is, you’ll handle it better with a settled head than a stewing one. Let me share something the system asks everyone to sit with at this stage:

“Fear, anger, shame, and frustration are all indicators of a problem. They are not the problem itself. If you hold onto them, you won’t be able to explore other perspectives or get a deeper understanding of your own. Can you see the shape and size of a forest from inside it? Not as well as you can if you were able to view it from a hilltop. Treat these feelings like notifications on a phone and let them go momentarily so you can see what they were trying to tell you.”

So let’s read the notification. When you replay that moment, the room going quiet, what’s the feeling that actually hits? Is it anger at Renee, or is there something else underneath it?

That’s an important discovery, and it took honesty to get there. The sting isn’t really the sentence. It’s the audience. What you’re feeling is closer to embarrassment than anger: being corrected in front of people whose opinion of you matters.

That reframes the apology, too. Ask yourself: if Renee sent you a private message right now saying “sorry about yesterday,” would the replaying stop? Or is what you actually want something more like being able to speak up in meetings without bracing for that to happen again?

That’s the real problem, named. Not “Renee owes me a ritual,” but “I want to feel safe offering help on this team.” An extracted apology wouldn’t give you that; a mumbled “sorry” delivered under pressure can even make things more guarded, not less. What restores safety is understanding: knowing what actually happened in that moment, so it stops being a landmine.

One more introspection question before we look at her side. That conclusion from earlier: “she thinks I’m incompetent.” Setting the sting aside for a moment: do you have any other evidence for that, from before yesterday?

So the evidence says this was one sharp moment inside an otherwise good working relationship, with someone who sought out your input two weeks ago. That matters for proportion: this is a small rupture, not a pattern, and it deserves a small, warm repair, not a formal confrontation.

This is where two of the system’s Wisdom Principles earn their keep. Good Faith asks you to assume she wasn’t out to humiliate you until you have real evidence otherwise. And you’ve just told me the evidence points the other way. Forgiveness isn’t saying the snap was fine; it’s declining to build a wall out of one bad moment. Neither one requires you to pretend it didn’t hurt.

Do you feel clear enough on your own side to spend a few minutes on hers?

You can’t know from where you sat. That’s exactly why the conversation is worth having. But you can loosen the “out of nowhere” story by imagining the moment from behind her screen. A few honest possibilities:

• She was mid-demo, in front of the team, and something broke. That’s a stressful spot even on a good day.
• Your suggestion, however well-meant, may have landed as “everyone is now watching someone fix my work for me.”
• She may have already known about the cache fix and been two seconds from doing it.
• Or the demo had nothing to do with it (a deadline, a rough morning, a bad week) and you caught the spillover.

Notice that none of these excuse the snap. She could have said “one sec, I’ve got it” without the edge. But every one of them is more likely than “she secretly thinks you’re incompetent,” given two weeks ago she asked for your input. What do you know about what’s on her plate right now?

So the fuller picture might be: her project, a moved-up deadline, a live demo to the whole team acting as her progress report, and it breaks on screen. Then a voice offers a fix in front of everyone. You meant “let me help”; under that much pressure it may have landed as “let me show you.”

Same eight words from you, two completely different experiences of them. That gap between what you meant and what she received is exactly what a short conversation can close. And given the size of this, I’d keep it small: not a meeting, not a “we need to talk.” Five minutes over coffee, this week while it’s still fresh. How does that feel as a scale?

Good instincts on both counts. The opener should do three things: name the moment plainly, own your piece without groveling, and hand her the floor. Something like:

“Hey, do you have five minutes? I wanted to circle back on the demo yesterday. When I jumped in with the cache thing, I was trying to help, but I realized after that interrupting your demo in front of everyone probably wasn’t the moment. It also stung a bit to get shut down like that. I’d rather clear the air than have it be weird.”

Notice what that does: it’s honest about your hurt (“it stung”) without demanding anything. You’re not asking for an apology; you’re opening a door she can walk through. In my experience of how these go, that opener gets a genuine “oh no, I’m sorry, I was so stressed” far more often than any demand would. Would you like to practice it? I can play Renee, including a version where she’s still prickly, so the first time you say it out loud isn’t the real one.

Then stay gently curious for one more beat instead of retreating. A brush-off is often just embarrassment on her side. She may not love how she sounded either. You could follow with:

• “It’s not a big deal, agreed. I just noticed I’ve been hesitant to speak up since, and I didn’t want that to calcify.”
• “Fair enough. Was the timing of it the problem, or would you generally rather drive your demos solo? Genuinely asking. I’ll follow your lead.”

That second question matters: you might learn something real about how she likes to work, which is worth more to you than any apology. And if she brushes it off and still nothing changes, you’ve lost five minutes and gained information. What would make this feel worth it to you, if the word “sorry” never comes?

That’s a genuinely good solution. And notice it’s something an apology could never have delivered. The system asks that agreements be actionable and testable, but proportion matters: this is a five-minute repair, so the agreement should be tiny. Something like:

The agreement: In her demos, you hold suggestions unless she asks, and she has an easy way to ask, like “anyone seen this before?” If something seems urgent, you drop it in the meeting chat instead of speaking over her.

The test: next demo, you both know the rule and nobody has to guess.

The review: none needed, honestly. If it works, you’ll both just feel it. If meetings still feel tense in a couple of weeks, that’s your signal to check in again.

It’s small, it’s concrete, and it directly answers the thing you actually wanted: knowing you’re safe to contribute, and knowing when. Does that feel proportionate to you, or does any part of it feel like more ceremony than the moment deserves?

Your conversation prep summary

The problem (observable): During Renee’s demo yesterday, you offered a fix (“try clearing the cache”) and she said sharply, “I’ve got it. Can you please just let me finish?” in front of the team. No word about it since.

Your side (from Introspection): The sting is mostly embarrassment that it happened in front of everyone, plus a new hesitance to speak up in meetings. The wish for an apology turned out to be a wish to feel safe and respected offering help. One sharp moment; no other evidence she doubts you: she asked for your input two weeks ago.

Her side (held in good faith): Her project, a moved-up Friday deadline, a demo-as-progress-report that broke on screen. Your help may have landed as being publicly fixed at her lowest moment. None of this excuses the snap; all of it makes it human.

The setting: Five minutes over coffee this week. Not a summit.

Opening: “Hey, do you have five minutes? I wanted to circle back on the demo yesterday. When I jumped in with the cache thing, I was trying to help, but I realized after that interrupting your demo in front of everyone probably wasn’t the moment. It also stung a bit to get shut down like that. I’d rather clear the air than have it be weird.”

If she brushes it off:

1. “Agreed it’s not a big deal. I just noticed I’ve been hesitant to speak up since, and I didn’t want that to calcify.”
2. “Was the timing the problem, or would you rather drive your demos solo? Genuinely asking. I’ll follow your lead.”

The small agreement (propose, don’t impose): You hold suggestions during her demos unless she asks; urgent things go in the meeting chat. If meetings still feel tense in a couple of weeks, check in again.

One thing to leave behind: The demand for an apology. If one comes, receive it graciously. If it doesn’t, you’ll still walk away with the thing you actually wanted.

Good luck, and if you’d like, come back afterward and tell me how it went.