Confrontation Isn't the Enemy...Silence Is

People tend to avoid confrontation at all costs and would rather try to “keep the peace” with silence than confront something head on. Plot twist: the hidden cost of staying quiet is always far more expensive than speaking up.

‍
If you've led, or been part of, a team this situation is probably familiar: something's off with a teammate, a deliverable isn't quite right, a dynamic feels awkward and it seems easier to let it slide rather than to speak up. This is for that moment.

‍
Before we get too far, what even is confrontation? "Confront" comes from the Latin word confrontare meaning "with the forehead," or to stand face-to-face. It didn't originally mean fight, it meant presence. Merriam-Webster still draws the line clearly: to confront is "to bring face to face"; conversely to avoid is "to keep away from, shun." One is presence. The other is absence; and absence isn't neutral, it negatively compounds.

‍
The Resentment Cycle

‍
When we choose not to confront things, there’s a great chance we find ourselves within the Resentment Cycle. Here are the four stages:

•Silence – You notice the issue. You say nothing.
•Assumption – In the silence, you fill in the gaps about intent, character, and whether it'll happen again.
•Resentment – The story you've told yourself hardens. You're no longer annoyed at the behavior; you're now annoyed with the person.
•Explosion or Exit – The built up pressure and frustration has to go somewhere. It comes out sideways, later, and messier than it needed to, or you decide it’s easier to just leave.

‍
Here’s an example of how quickly this issue compounds. A peer starts showing up ten minutes late to scrum. You think it’s not worth "making a big deal of." So, you choose silence. Two weeks later you notice a slower Slack reply and a missed meeting. Now assumption creeps in… maybe they're checked out, maybe they don't respect the team's time. By week four, you're short with them in a conversation over something unrelated, and they have no idea why. What could've been a 90-second "hey, I noticed you've been late to our meetings recently, is everything okay?" in week one is now a misunderstanding leading to unspoken tension because of an assumed "lack of care or respect" by week four.

‍
Two Tools You Can Use

‍
With that slippery slope in mind, we need to always try to interrupt the cycle at step one before assumption sets by confronting the issue or concern. Here are two practical tools you can use to help confront something.

‍
S.T.A.R. (Situation, Truth, Ask, Resolve) best used for factual issues:
"You were 20 minutes late to the last two customer calls. (situation) That's landed on me having to stall or apologize, and it's made me question if having you in charge of customer-facing work is the best choice. (truth) I need you on time, or a heads-up beforehand. If this keeps happening, we'll need to assign someone else to lead these calls." (resolve)

‍
This is a way to communicate with a teammate about a specific issue or instance that is detrimental to the team. By preemptively putting together your four points you can concisely communicate with your teammate and confront this issue before it gets out of hand.

‍
F.B.I. by Simon Sinek (Feeling, Behavior, Impact) best used for relational issues:
"During scrum I've been feeling shut out. (feeling) In the last two meetings, you cut me off before I finished making my point. (behavior) It's made me hesitant to speak up at all, which isn't good for either of us.” (impact)

‍
This approach is highly effective when you are trying to gain understanding as well as confront an issue. By approaching an issue with this method, and leading with curiosity rather than conviction, you may find that more often than not it’s a miss understanding rather than actual conflict but the point is to confront the issue and resolve it before you end up in the Resentment Cycle.

‍
Either of these two approaches turns "confrontation" back into what the word originally meant: showing up, forehead to forehead, present and honest… not a fight.

‍
Why It Matters at Beast Code

‍
At Beast Code, our priorities are People, Product, Profit… in that order. A team where small frictions get named early is a team that trusts each other more, not less. Avoidance feels like kindness in the moment, but it quietly erodes the exact thing it's trying to protect… the relationship, the trust, the psychological safety we're all striving to build within our teams. Real care looks like showing up early, before the story in your head becomes the only story that exists.

‍
If there's something you've been sitting on, sweeping under the rug, or avoiding… confront it this week! Take one of these methods and write out your concern if you need to so you communicate clearly with your teammate but don’t fall into the trap that silence or avoidance is the best bet. Love yourself and your teammates enough to show up, be present face-to-face, challenge one another to grow and improve, and never let an issue fester into resentment, confront it!

‍