Warmth or Competence? How to Flip the Switch for Your Team

You walk into the break room to talk about yesterday's near-miss. You've got your facts straight. You know exactly what went wrong. You're ready to fix it.

And the room goes silent.

Not the good kind of silent, the uh-oh kind. Eyes down. Arms crossed. One guy suddenly very interested in his coffee cup.

Here's the thing: you said all the right words. But you used the wrong signal.

The Signal Matters More Than the Script

Most safety leaders know what to say. We've got the procedure memorized. We've been through the training. We know the five-step process for corrective conversations, the three-part model for incident debriefs, the approved language for stop-work authority.

But nobody ever taught us how to say it. And that "how" is everything.

Because your team isn't reading your PowerPoint. They're reading you. Your tone. Your pace. Your body language. The micro-signals that tell them whether you're here to help or here to blame.

Research from Harvard psychologist Amy Cuddy shows that when people evaluate you, they're asking two questions, usually subconsciously:

1. Can I trust this person? (Warmth)
2. Can I respect this person? (Competence)

And here's where it gets interesting: different people need those signals in different orders.

The Warmth-Competence Dial

Think of warmth and competence like a two-sided dial. You can turn it toward warmth (empathy, connection, understanding) or toward competence (expertise, authority, credentials). Most of us have a default setting, the one we naturally lean into when we're stressed or uncertain.

The problem? Your default setting probably works great for about half your team and falls completely flat with the other half.

Let me show you what I mean.

Guardians: Warmth First, Always

Guardians are your procedural thinkers. They follow the rules because the rules exist to protect people. They take safety personally.

When you approach a Guardian with a safety concern, lead with warmth. Not fake warmth, real human connection. Ask how they're doing. Acknowledge the stress they're under. Show them you see them as a person, not just a policy violation.

Then talk about the procedure.

If you flip that order, if you lead with "You didn't follow Step 4 of the lockout procedure", you've just told a Guardian that you don't trust them. And a Guardian who feels distrusted will shut down completely. They'll nod. They'll comply. But you've lost them.

I learned this the hard way early in my career. I walked up to a Guardian after an incident and immediately started with, "Tell me why you skipped the verification step."

She looked at me like I'd slapped her. Because to her, I had.

What I should have said: "Hey, I know yesterday was chaos. Walk me through what happened from your perspective." Warmth first. Competence later.

Analysts: Competence First, Respect Second

Analysts are the opposite. These are your systems thinkers, the people who want to understand the why behind every rule. They're not being difficult; they're being rational.

When you approach an Analyst, flip that dial hard toward competence. Show them your data. Explain the engineering rationale. Walk them through the logic.

If you lead with warmth, "I just want to make sure you're okay", an Analyst hears: This person doesn't think I can handle reality. They'll be polite. But they won't respect you.

I watched a safety manager lose an entire engineering team because he kept trying to "build relationships" before he'd earned their technical respect. Every meeting started with small talk. Every email had three paragraphs of pleasantries before getting to the point.

The Analysts tuned him out. They wanted competence. He gave them warmth. Mismatch.

Reading the Room (and the Person)

Here's where observation becomes critical. You can't dial in the right signal if you don't know who you're talking to.

And I'm not talking about personality tests or archetype assessments, though those help. I'm talking about reading behavior in real time.

Every person has a baseline. The way they normally talk, move, and engage. And when that baseline shifts, that's your signal.

When the Talkative Person Goes Quiet

You know that crew member who always has something to say? The one who jokes around, asks questions, challenges assumptions? That's their baseline.

Now imagine they walk into the morning briefing and say nothing. Head down. No eye contact. No commentary.

That's not "having a bad day." That's a red flag.

Something shifted. Maybe they witnessed something yesterday they're afraid to report. Maybe they made a mistake and they're terrified you'll find out. Maybe they're dealing with something at home that's affecting their focus at work.

Your job isn't to play therapist. Your job is to notice and respond appropriately.

Pull them aside. Not in front of the crew. Not in the office with the door closed (too formal, too scary). Somewhere neutral. And lead with warmth, real warmth.

"Hey, you seem off today. Everything okay?"

Give them space to talk. Or not talk. But let them know you noticed. That you care. That you're a safe person to come to if something's wrong.

When the Skeptic Suddenly Agrees

The opposite pattern is just as telling.

Skeptics challenge everything. That's their baseline. They're not being jerks; they're stress-testing ideas to make sure they hold up. A good Skeptic makes your safety program better by poking holes in your assumptions.

But if your Skeptic suddenly starts agreeing with everything you say? That's not growth. That's resignation.

They've stopped believing you'll listen. So they've stopped talking.

This is incredibly dangerous. Because the Skeptic who won't speak up is the Skeptic who won't stop a job when something feels wrong. They'll just go along. And people get hurt.

If you notice this shift, you have to rebuild trust. And trust with a Skeptic requires competence: demonstrated competence. Show them you actually fixed the thing they flagged last month. Prove that their input matters. Give them evidence that speaking up leads to change, not just more meetings.

The Adaptation Part (The "I" in VOICE)

Observation is useless without adaptation. Once you've read the person, you have to adjust your approach.

Let's say you're about to deliver corrective feedback to a Harmonizer: someone who values team cohesion above everything else. If you walk in with an authoritative, "Here's what you did wrong" tone, you've just triggered their fear of conflict. They'll agree to anything to make the discomfort stop. But they won't actually change.

Instead, dial toward warmth. Frame it as problem-solving together. "I noticed this happened yesterday, and I want to figure out how we can prevent it together. What do you think went wrong?"

You're still addressing the issue. But you're doing it in a way that doesn't activate their defenses.

Or let's say you're talking to an Enforcer: someone who respects authority and expects clear direction. Don't ask them what they think went wrong. They'll interpret that as weakness. Tell them what needs to change and why. Be direct. Be clear. Show confidence.

Same conversation. Different signal.

This Isn't Manipulation: It's Respect

Some people hear this and think, "Wait, so I'm supposed to fake different personalities depending on who I'm talking to?"

No.

You're supposed to meet people where they are. You're not changing your message. You're changing your delivery so your message actually lands.

Think of it like speaking different languages. If someone only speaks Spanish, and you only speak English, neither of you is wrong: but nothing gets communicated. Learning to adjust your tone, pace, and emphasis based on who's listening isn't manipulative. It's respectful.

It's recognizing that not everyone processes information the same way. Not everyone builds trust the same way. Not everyone feels safe the same way.

And if your goal is actually keeping people safe: not just covering your compliance checklist: then you owe it to them to communicate in a way they can actually hear.

Start Small

You don't have to master this overnight. Start with one thing:

Notice when someone's baseline shifts. When the quiet person suddenly gets chatty. When the skeptical person goes silent. When the confident person starts second-guessing everything.

Just notice.

Then ask yourself: What signal does this person need from me right now?

Warmth or competence. Connection or authority. Empathy or expertise.

Flip the dial. See what happens.

Because everyone has the right to feel and be safe.