The Moment Before You Respond
Every team says it values healthy conflict. But rarely do the people on the teams know what to do when someone drops something awkward into the conversation.
Like maybe a colleague questions your numbers in front of leadership, or sends a Slack message that reads as dismissive, or the team made an important decision without everyone in the room. What happens next either builds trust or drains it.
Most of us respond on autopilot. We defend, withdraw, or file the moment away as evidence for a story we’ve already been building about that person. None of that is a character flaw. It’s what people do when they don’t have a better process.
So here’s a better process. If you’re a member of any team (and almost all of us are), this process can help you be a better teammate.
Spot: What’s actually happening in me?
Before you respond, notice what’s going on inside you. Three questions help:
- What’s my story? You’ve probably already decided what the other person meant. Is that what they actually said, or what you heard?
- What’s my trigger? Something hit a nerve: your competence, your autonomy, being left out. Naming it takes away much of its power.
- What assumption am I making? About their intent, what they know, or why they did it. Most workplace conflict runs on unexamined assumptions.
Spotting doesn’t mean you’re wrong to be frustrated. It means you can see the situation more clearly before acting on it.
Own: What’s my part?
This is the hardest step and the one that matters most. Ask yourself honestly: what did I contribute? Maybe you weren’t clear about your expectations. Maybe you didn’t raise a concern when it was small. Maybe your tone in the last exchange set this one up.
Owning your part isn’t taking all the blame. It means you walk into the conversation as a participant rather than a prosecutor, and people can feel the difference right away.
Bridge: Who did we agree to be?
Only now do you engage, and you do it with a reference point. The strongest teams decide ahead of time who they want to be when conflict happens. Do they want to be direct? Curious? Fast to repair? When you’ve made that agreement together, a disagreement is a test of a commitment everyone already made, not a contest between two people.
Why this matters more than it seems
Plenty of teams learn frameworks like this in a workshop and never use them again. The difference comes when the process becomes recursive, meaning the team uses it in the moment, on real problems, until it becomes how they operate. A team that can disagree without damage decides faster, surfaces problems sooner, and spends far less energy managing tension it never talks about.
Healthy conflict is a skill. Teams can build it on purpose.
This is one piece of the Integrated Performance Blueprint, a six-week program we run that helps teams build the communication, decision-making, conflict, and accountability practices that hold up under pressure. Each week produces a working agreement your team keeps using long after the program ends. If your team could use this, reach out to me and I’ll walk you through how it works.
Leave a Reply