The Architecture of Delivery: Communication Strategies for Strategic Influence

In this episode, we explore why how we say something often matters more than what we say.

We unpack how tone and delivery can either build trust or quietly dismantle it, especially in high-stakes professional conversations. Rather than defaulting to blunt or defensive communication, we discuss practical shifts that foster collaboration, including leading with shared goals, using inclusive language like “we,” and asking open-ended questions that expand dialogue instead of shutting it down.

We also dive into one of the most underrated skills in leadership and relationships: choosing curiosity over defensiveness when challenged.

If you’ve ever felt your expertise was overlooked or your message didn’t land the way you intended, this conversation will show you how refining your delivery can transform you from being seen as a roadblock into a true strategic partner.

Transcript

SPEAKER_00 0:00

Have you ever been in a situation where um someone looked at a project you poured your absolute heart into? Or maybe just some task you finished at work and they told you just flat out that you were wrong.

SPEAKER_01 0:11

Oh, yeah. The worst feeling.

SPEAKER_00 0:13

Right. Not just wrong, but they delivered the feedback with this like blunt, borderline, rude edge that just it felt like a slap in the face.

SPEAKER_01 0:21

It really does.

SPEAKER_00 0:22

And as you stood there listening to them, this really uncomfortable realization kind of washed over you. Like technically they might actually be right.

SPEAKER_01 0:30

Yep. The facts are entirely on their side.

SPEAKER_00 0:32

Exactly. The facts are there. But despite knowing that, you just felt your entire body shutting down, your chest tightened, your jaw clenched, and you completely dismissed everything they were saying. You just rejected reality entirely because of the harsh packaging of their delivery.

SPEAKER_01 0:47

It is a profound and universal human glitch. We are entirely capable of throwing out incredibly valuable information simply because we despise the tone of the messenger.

SPEAKER_00 0:59

We really are.

SPEAKER_01 1:00

We sabotage our own projects or we ignore critical feedback just to protect our pride from a poorly delivered critique.

SPEAKER_00 1:07

And that highly relatable, incredibly frustrating phenomenon is our absolute focus today. So we are centering this deep dive entirely on a brilliant article by Matt Norman. It's titled, It's Not What You Say, It's How You Say It.

SPEAKER_01 1:21

Such a good piece.

SPEAKER_00 1:22

It really is. He takes this vague, often frustrating concept of, you know, good communication skills and forces us to look at the actual mechanical, psychological realities of how our words are processed by other people.

SPEAKER_01 1:34

It's a phenomenal piece of writing because it well, it strips away the corporate jargon and focuses purely on behavioral reality.

SPEAKER_00 1:42

Right. No buzzwords.

SPEAKER_01 1:43

Exactly. Norman demonstrates that communication isn't just an exchange of data, it was a complex mechanism that either accumulates trust over time or unfortunately evaporates it in an instant.

SPEAKER_00 1:54

And that is the mission for this deep dive. We are going to explore why your delivery matters on a biological level, how that trust evaporation actually happens, and most importantly, we are going to unpack the specific, actionable shifts you can make because we want to ensure your message actually survives the gauntlet of human emotion. Okay, let's unpack this. And um, we're starting with a rather candid personal admission from Matt Norman himself.

SPEAKER_01 2:18

Yeah, he opens the piece by putting himself right in the crosshairs. He details an interaction with a friend, um, someone he describes as having a personality that leans much more toward directness and skepticism than his own.

SPEAKER_00 2:31

So this friend looked at a project Matt had created, and instead of, you know, gently offering constructive feedback, they just bluntly told him it was wrong.

SPEAKER_01 2:39

Just straight up.

SPEAKER_00 2:40

Straight up. Like it it wouldn't work. The delivery was completely devoid of tact. And Matt writes that he immediately shut down. He backed away and distanced himself from this friend.

SPEAKER_01 2:49

Which is such a natural reaction.

SPEAKER_00 2:51

Right. But the turning point in the story is Matt's own self-awareness a few moments later, because he realized his intense resentment had absolutely nothing to do with whether the friend's technical assessment of the project was accurate.

SPEAKER_01 3:03

What's fascinating here is the core psychological dynamic at play. When delivery is harsh or abrupt, the receiver experiences a rapid, uncontrollable spike in defensive emotion.

SPEAKER_00 3:15

Like an instant flare-up.

SPEAKER_01 3:17

Exactly. We were talking about resentment, embarrassment, or sudden anger. And those emotions, they literally act as cognitive blinders.

SPEAKER_00 3:25

Wow.

SPEAKER_01 3:25

Yeah, the resentment blinds the listener to the actual content of the message. You could literally be handing someone the cure to a devastating disease, but if you deliver it in a package that makes them feel attacked or patronized or belittled, they will instinctively put up defensive walls.

SPEAKER_00 3:42

They won't even hear you. Trevor Burrus, Jr.

SPEAKER_01 3:43

Right. The content is rendered entirely powerless by the packaging.

SPEAKER_00 3:46

So isn't it a bit like serving a gourmet meal on a garbage lid?

SPEAKER_01 3:50

Aaron Powell Oh, that is a remarkably visceral image. But um yeah, incredibly accurate.

SPEAKER_00 3:56

Aaron Powell Like the food itself might be Michelin star quality. The ingredients are flawless, the culinary technique is flawless, the nutritional value is exactly what you need. But because of what is being served on this filthy, smelly piece of trash, no one in their right mind wants to consume it.

SPEAKER_01 4:12

No, of course not.

SPEAKER_00 4:13

In fact, you're actively repulsed by it. But it begs a bigger question: why are we wired this way? Why is it so incredibly hard for us to separate the objective message from the subjective tone of the messenger?

SPEAKER_01 4:24

Aaron Powell Well, it's because our brains are survival engines first and logic engines second.

SPEAKER_00 4:28

Okay, break that down for me.

SPEAKER_01 4:30

Long before we had complex language or spreadsheets or project management software, our ancestors relied heavily on tone, facial expression, and body language to assess immediate physical threats in their environment. Trevor Burrus, Jr.

SPEAKER_00 4:43

Like tiger or no tiger.

SPEAKER_01 4:45

Exactly. So when someone speaks to you aggressively today, your amygdala, which is the threat detection center of your brain, does not differentiate between a blunt friend and a physical predator. It fires up immediately and signals danger, we are under attack.

SPEAKER_00 5:00

So the brain hasn't updated its software for the modern office environment.

SPEAKER_01 5:04

Not at all.

SPEAKER_00 5:05

Your prefrontal cortex, you know, the logical analytical part of your brain that should be evaluating the data, essentially gets hijacked and shut down by this ancient emotional response.

SPEAKER_01 5:15

You are thrown straight into fight or flight mode. In that state, you are no longer processing facts or evaluating spreadsheets. You are entirely consumed with processing a perceived threat to your social standing, your autonomy, or your ego.

SPEAKER_00 5:28

The logical mind just goes offline completely.

SPEAKER_01 5:30

It does. It shuts down.

SPEAKER_00 5:32

That makes the trust evaporation trap so much more terrifying, honestly. If poor delivery can trigger a biological threat response and ruin a casual interaction between friends, it makes you wonder what happens when this dynamic occurs in a high-stakes corporate environment.

SPEAKER_01 5:47

Ooh, it gets messy.

SPEAKER_00 5:48

Right. A place where differing priorities, intense stress, and competing egos are literally built into the architectural framework of the business.

SPEAKER_01 5:57

That is precisely where Matt Norman takes the concept next. He brings us into the hyper-pressurized world of a real-world case study from his coaching practice. He introduces us to a client named Joe.

SPEAKER_00 6:09

Joe. And Joe leads the infrastructure team at a massive financial services company, which is a position that inherently carries immense, mostly unseen pressure.

SPEAKER_01 6:19

It is the definition of a thankless job. When everything works perfectly, nobody notices Joe.

SPEAKER_00 6:24

Of course not.

SPEAKER_01 6:25

But when one thing goes wrong, it is an international emergency.

SPEAKER_00 6:29

Because if you think about the foundational concern of Joe's role, his entire mandate is the stability and the security of the company's technical systems. He's the guardian in the gate, keeping the walls up and the lights on.

SPEAKER_01 6:41

He wants zero risk.

SPEAKER_00 6:42

Zero. He wants thorough testing, slow rollouts, and redundant backups. But then look at the people he reports to the president and the chief financial officer.

SPEAKER_01 6:52

Right. And their incentives exist on the complete opposite end of the spectrum.

SPEAKER_00 6:55

Exactly. The C-suite is incentivized by aggressive, relentless quarterly growth. They want to move incredibly fast, launch untested new products to beat competitors, slash operational costs, and push the envelope.

SPEAKER_01 7:08

They want speed.

SPEAKER_00 7:09

They want speed and cheap speed at that. So right away you have this intrinsic structural friction. These goals, obsessive stability on one hand, and aggressive cost-cutting growth on the other, are constantly colliding.

SPEAKER_01 7:22

Constantly.

SPEAKER_00 7:22

Which means Joe's everyday conversations with his executive team are naturally and fundamentally adversarial.

SPEAKER_01 7:29

And that adversarial baseline is where the stakes become incredibly high for someone in Joe's position. If Joe isn't meticulously careful about how he communicates his need for security and stability, he is going to be instantly categorized in the minds of the executives.

SPEAKER_00 7:45

Categorized as a roadblock, I imagine.

SPEAKER_01 7:47

Exactly, a roadblock.

SPEAKER_00 7:48

Like if he just walks into the boardroom sliding thick reports across the table and saying no to every new initiative because it presents a security vulnerability, the CFO isn't going to see him as a strategic partner.

SPEAKER_01 7:59

No, they'll see him as a frustrating hurdle, a cost center that just needs to be managed, minimized, or bypassed altogether so they can hit their growth targets.

SPEAKER_00 8:07

Just someone in the way.

SPEAKER_01 8:09

Right. Before Joe learned to adapt, those meetings likely involve him defensively dumping alarming data on the table, expecting the numbers to do the heavy lifting.

SPEAKER_00 8:18

Oh, just saying, look at the spreadsheet.

SPEAKER_01 8:20

Exactly. And the executives would just glaze over or push back harder, viewing his warnings as mere complaints.

SPEAKER_00 8:26

But let me play devil's advocate for a second here. Because Joe is the technical expert, right? He is the one who intimately understands the code, the server load limits, the catastrophic vulnerability risks.

SPEAKER_01 8:39

He is.

SPEAKER_00 8:40

Shouldn't his data and his expertise just speak for themselves? I mean, if the system is mathematically going to crash under a new product load, it's going to crash. Why does he have to play diplomat and massage the egos of the C-suite? Isn't the truth enough?

SPEAKER_01 8:53

It is the most common, tragic frustration of technical experts in every field across the globe.

SPEAKER_00 8:58

Really?

SPEAKER_01 8:59

Oh, absolutely. It's this profound belief that the truth, presented logically and backed by data, should be enough to win the argument. But Norman's conclusion, drawn from years of coaching high-level professionals, is that technical expertise on its own is never enough.

SPEAKER_00 9:14

Never enough.

SPEAKER_01 9:15

Never. Because data does not make decisions. Human beings make decisions.

SPEAKER_00 9:19

Oh, that's a great point.

SPEAKER_01 9:20

And human beings make decisions based on trust. Building relationship capital during tense, high stakes and negotiations is what actually distinguishes a valuable, indispensable partner from a mere technician.

SPEAKER_00 9:31

So a technician just points out the problem and expects the data to do the work. But a partner actually helps the stakeholders navigate the problem while actively preserving the relationship.

SPEAKER_01 9:40

Spot on.

SPEAKER_00 9:41

If Joe just walks in with a blunt, you can't do this attitude, he's basically serving his Michelin star data on a garbage lid. The CFO resents the delivery, rejects the data, and looks for a workaround.

SPEAKER_01 9:54

Precisely. To survive and thrive in that role, Joe had to fundamentally change his approach. He had to learn how to bridge that massive gap between technical reality and executive ambition.

SPEAKER_00 10:05

So let's look at how Joe managed to bridge that gap. Norman lays out a framework of communication shifts that he and Joe worked on together to transform these interactions.

SPEAKER_01 10:14

But tactical stuff.

SPEAKER_00 10:14

Yeah, the real tactics. And the first shift requires a complete reversal of our natural instincts in an argument. Instead of launching into defensive opinions or listing dense technical facts, Norman advised Joe to start by naming the shared problem right out of the gate.

SPEAKER_01 10:29

It is a master stroke in disarming an adversarial conversation. You have to actively, verbally demonstrate to the other person that you are sitting on the same side of the table.

SPEAKER_00 10:39

Make them feel safe.

SPEAKER_01 10:41

Right. Think about the standard dynamic. The CFO demands a new feature launch by Friday. The infrastructure leader immediately thinks about server load and blurts out, we can't do that, the bandwidth isn't there, the API isn't tested, and we need a massive budget increase for cloud storage.

SPEAKER_00 10:57

And instantly the CFO's threat detection system fires up. All they hear is a subordinate telling them no while simultaneously demanding more money.

SPEAKER_01 11:06

Exactly.

SPEAKER_00 11:07

But Norman highlights a specific, incredibly clever pivot Joe made. Here's where it gets really interesting. Joe goes to pitch the CFO on a delay, but he opens the conversation by saying, while none of us wants to increase our tech budget right now, we need to ensure system reliability.

SPEAKER_01 11:23

Look at the psychological architecture of that sentence.

SPEAKER_00 11:25

It's brilliant because he disarms the executive by acknowledging the CFO's primary overarching pain point first. He leads with the budget.

SPEAKER_01 11:33

He addresses the elephant in the room.

SPEAKER_00 11:35

Right. Joe knows the CFO loses sleep over spending money. By explicitly stating none of us wants to increase the budget, Joe is essentially holding up a mirror and saying, I see the world through your eyes. I validate your core concern.

SPEAKER_01 11:51

And the tension in the room immediately drops. That threat response we talked about earlier is completely deactivated. Exactly. Only after establishing that psychological safe harbor does Joe introduce his own need, which is system reliability. You are signaling to the executive, I am not your enemy, I am carrying your priorities along with my own. It completely changes the tone of the ensued negotiation from a battle into a puzzle.

SPEAKER_00 12:18

That sets a collaborative foundation, but it's what Joe does next that really steers the ship. Norman points out a critical flaw in how we ask questions. Like we rarely think about the grammatical structure of our inquiries, but Norman argues that swapping out specific verbs changes the entire paradigm.

SPEAKER_01 12:33

Language matters so much here.

SPEAKER_00 12:35

It really does. He advises swapping words like have or do for what or how.

SPEAKER_01 12:40

The mechanics of our questions dictate the entire flow of the conversation. When you start a question with words like is, does, are, or do, you are functionally trapping the conversation in a very tight corner. How so? You are forcing the other person to be a binary gatekeeper.

SPEAKER_00 12:57

Wait, so by starting with something like, do you approve this budget? You're essentially handing the CFO a giant yes or no button.

SPEAKER_01 13:05

A giant button, yes.

SPEAKER_00 13:06

And if they're already stressed, territorial, and mandated to cut costs, they are always going to smash the NO button because it's the safest, easiest option. It requires zero mental effort to say no.

SPEAKER_01 13:17

Exactly the issue. You approve this budget, shuts the door. But words like what or how act as conversational skeleton keys.

SPEAKER_00 13:25

Oh, I like that.

SPEAKER_01 13:26

They expand understanding and demand a nuanced, thoughtful response. So in the article, instead of asking that binary trap question, Joe alters his approach and asks the CFO, what are your key priorities regarding this system upgrade?

SPEAKER_00 13:39

It forces the executive to actually think.

SPEAKER_01 13:41

If we connect this to the bigger picture, um, asking a what or how question completely reframes the relationship. You are no longer a subordinate begging a gatekeeper for permission.

SPEAKER_00 13:53

Right. You're not just asking for a stamp.

SPEAKER_01 13:55

You are a high-level consultant asking a stakeholder to collaborate.

SPEAKER_00 13:59

Right.

SPEAKER_01 14:00

When you ask what are your priorities, you force the CFO to articulate their vision and step into the messiness of the problem-solving process with you.

SPEAKER_00 14:09

You're pulling them onto your side of the table again. You're making them co-offer the solution. And at the same time, you're gathering incredibly valuable intelligence about what actually matters to them, which you can then use to tailor your technical solutions later.

SPEAKER_01 14:23

It it is deeply strategic empathy.

SPEAKER_00 14:25

Okay. So opening up a conversation by validating shared stakes and using what oh questions to invite collaboration is a powerful way to start. But you know, let's be realistic about corporate environments.

SPEAKER_01 14:35

Things get heated.

SPEAKER_00 14:36

The pushback is inevitably going to come. People are going to disagree, timelines are going to clash, and egos are going to flare up. Opening well is one thing, but how do we manage the actual language and emotional temperature when we are actively under fire?

SPEAKER_01 14:51

That brings us to the psychological nuances of navigating friction. And it starts with a subtle but massive linguistic shift, moving your language from IU to we is.

SPEAKER_00 15:16

Why is that?

SPEAKER_01 15:17

Because it alters the brain's perception of in-group versus out-group dynamics. If you walk into a tense meeting and say something like, I need you to approve this timeline, it instantly registers as a demand.

SPEAKER_00 15:28

Yeah, that makes sense.

SPEAKER_01 15:29

It creates this invisible adversarial line in the sand. There is I over here with my needs and you over there acting as the obstacle.

SPEAKER_00 15:37

It triggers those territorial defense mechanisms again. Because saying, I need you to do this implies a transfer of burden. It feels like an obligation or a heavyweight being abruptly placed on the receiver's shoulders.

SPEAKER_01 15:49

But if you intentionally alter the pronouns, the entire cognitive categorization shifts. Instead of a demand, you say, Let's develop a plan for how we can approach this collaboratively.

SPEAKER_00 16:01

Let's develop a plan. Wow. It forces the executive brain to re-categorize the IT guy from annoying internal vendor to co-founder.

SPEAKER_01 16:11

Yes. You are linguistically binding your fates together.

SPEAKER_00 16:14

Because we implies shared risk, shared reward, and shared consequences.

SPEAKER_01 16:17

Precisely.

SPEAKER_00 16:18

When the CFO hears we and us, their subconscious processes that you are down in the trench with them, sharing the mud, not just shouting unrealistic orders from the outside.

SPEAKER_01 16:28

It is a simple, elegant tweak to make before you speak. Catching yourself before you say I and you and intentionally swapping in we and you's builds an invisible bridge over adversarial waters.

SPEAKER_00 16:38

Which brings us to the final shift Norman outlines. And I have to be completely honest here. While the pronoun shift is easy to understand, this final one feels like the hardest thing in the world to actually execute in real life.

SPEAKER_01 16:51

Oh, without a doubt.

SPEAKER_00 16:52

When the pushback hits its peak, Norman says you must choose curiosity over defensiveness.

SPEAKER_01 16:57

It is undoubtedly the hardest step, but it is the crucible where trust is truly won or lost.

SPEAKER_00 17:03

The rule here is that when your data is challenged or your expertise is questioned, you cannot take the bait. You have to resist the overwhelming, burning biological urge to justify yourself.

SPEAKER_01 17:15

Then we all have that urge.

SPEAKER_00 17:16

Well, we all know that feeling. Someone looks at your meticulous spreadsheet and says, This timeline is ridiculous, and your immediate reaction is to start rapid-firing excuses like Well, we were just trying to do this because of X, Y, and Z. And if you look at cell D4, the justification reflex.

SPEAKER_01 17:30

Yeah. It is a powerful instinct.

SPEAKER_00 17:32

But Norman insists you have to stop that reflex dead in its tracks. In the example from the article, if the CFO aggressively pushes back on a timeline Joe proposed, Joe does not start listing all the technical reasons his timeline is realistic.

SPEAKER_01 17:46

No, he doesn't.

SPEAKER_00 17:47

Instead, he takes a breath, absorbs the hit, and asks the question. He says, those are concerns worth discussing. Walk me through your ideal timeline.

SPEAKER_01 17:56

It is brilliant conversational jujitsu.

SPEAKER_00 17:58

But how do you actually do that? When your hard work is questioned, your immediate biological instinct, going back to the amygdala, is to defend it. Your heart rate spikes, your face flushes, you feel the adrenaline. You're under attack. You desperately want to prove you are competent and right. How do you override that deeply ingrained evolutionary instinct in the heat of a boardroom argument?

SPEAKER_01 18:18

You have to fundamentally change your internal definition of what a conversation is.

SPEAKER_00 18:21

Okay, explain that.

SPEAKER_01 18:22

Well, when we feel defensive, we view the conversation as a zero-sum battle to be won. The subconscious logic is if I justify my actions and prove my data, I win. If I admit a flaw or ask a question, I lose status.

SPEAKER_00 18:37

Right. Nobody wants to lose.

SPEAKER_01 18:39

But you have to realize that justifying yourself in the face of an angry executive is like hitting a brick wall. All the forward momentum stops, you just end up bruised, and the other person digs their heels in deeper. Defensiveness only breeds more defensiveness.

SPEAKER_00 18:55

So by asking a genuine question instead, you're essentially stepping off the tracks while the train is coming.

SPEAKER_01 19:01

Yes. Great analogy.

SPEAKER_00 19:03

You aren't blocking their aggressive energy with your ego. You are stepping aside and redirecting that critical energy into constructive planning.

SPEAKER_01 19:10

Exactly. When Joe says, walk me through your ideal timeline, he isn't conceding defeat or saying his own timeline was wrong. He is forcing the CFO to actually think through the logistical nightmare of a shorter timeline themselves.

SPEAKER_00 19:22

That is the genius of it. By asking them to explain their ideal scenario, they might suddenly realize on their own why your original timeline was the right one all along. They bump into the constraints naturally rather than having you lecture them about the constraints.

SPEAKER_01 19:36

People are rarely convinced by your logic. They are convinced by their own logic. Curiosity facilitates that self-discovery. Wow. The information hasn't changed. The data Joe possesses is exactly the same. But by weaving these shifts together, validating shared stakes, using expansive questions, employing inclusive pronouns, and remaining relentlessly curious, the delivery transforms an adversary into an ally.

SPEAKER_00 20:03

So what does this all mean? When we zoom out and look at the totality of Matt Norman's insights, it paints a very clear picture. Whether you are a highly specialized IT director negotiating with a ruthless CEO, or you're just talking to a blunt friend about a weekend side project, how you deliver your message is the ultimate deciding factor in your success.

SPEAKER_01 20:23

It really is the deciding factor.

SPEAKER_00 20:24

Your technical skills, your raw intelligence, and having the mathematically correct data, those things might get you into the room. But your communication skills, your ability to manage your tone, your phrasing, and your own ego, that is what keeps you at the table.

SPEAKER_01 20:38

It highlights the profound difference between being right and being effective.

SPEAKER_00 20:42

That's a great way to put it.

SPEAKER_01 20:44

You can be the most correct person in the entire building. But if your delivery evaporates trust, your correctness is entirely useless. Which is why Matt Norman ends his piece with a very direct challenge that every professional needs to take to heart. He asks, How are you auditing the way you say things?

SPEAKER_00 21:03

It's a powerful prompt to carry into your next meeting or, you know, your next difficult conversation. Next time you feel that friction, take a second to audit your words. Are you building a wall or are you building a bridge?

SPEAKER_01 21:15

And this raises an important question for you to mull over. What if the absolute highest level of technical mastery isn't about knowing all the answers at all? What if true mastery is simply possessing the profound emotional discipline to ask a what or how question at the exact moment you are desperate to prove you are right?