WEBVTT 00:00:00.000 --> 00:00:04.120 So imagine you're deploying a flawless, beautifully 00:00:04.120 --> 00:00:07.620 architected system. I mean, the syntax is pristine, 00:00:07.740 --> 00:00:09.980 the logic is incredibly tight, and it's just 00:00:09.980 --> 00:00:12.240 humming along perfectly in your local environment. 00:00:12.279 --> 00:00:14.660 Right, the dream scenario. Exactly. But then 00:00:14.660 --> 00:00:17.079 the second you push it to a live production environment, 00:00:17.660 --> 00:00:20.339 the entire system just completely crashes. It 00:00:20.339 --> 00:00:22.899 falls apart. Oh, yeah. Which happens because 00:00:22.899 --> 00:00:25.120 that perfect code doesn't exist in a vacuum. 00:00:25.320 --> 00:00:28.160 Once it's deployed, it's forced to interact with 00:00:28.160 --> 00:00:32.600 this highly complex, really unpredictable ecosystem 00:00:32.600 --> 00:00:36.179 of legacy databases and third -party APIs. Meradic 00:00:36.179 --> 00:00:38.700 user input. Exactly. Users doing things you never 00:00:38.700 --> 00:00:40.740 planned for. And that is exactly what happens 00:00:40.740 --> 00:00:43.500 to brilliant tech leaders, like every single 00:00:43.500 --> 00:00:45.679 day. We spend our entire careers perfecting our 00:00:45.679 --> 00:00:47.700 personal code, right? Our hard technical skills, 00:00:47.859 --> 00:00:50.159 our certifications, our algorithmic thinking. 00:00:50.840 --> 00:00:52.920 But we often completely neglect the operating 00:00:52.920 --> 00:00:55.259 system required to actually deploy those skills 00:00:55.259 --> 00:00:59.179 into a messy human ecosystem. So today, our mission 00:00:59.179 --> 00:01:02.399 in this deep dive is to unlock the secret weapon 00:01:02.399 --> 00:01:04.819 for leadership in that unpredictable environment. 00:01:05.120 --> 00:01:07.650 And spoiler alert. It's not a new programming 00:01:07.650 --> 00:01:09.969 language. No, it is not a framework either. It 00:01:09.969 --> 00:01:13.909 is emotional intelligence or EQ. Right. And we 00:01:13.909 --> 00:01:16.930 are examining this through a really specific, 00:01:16.930 --> 00:01:20.090 highly revealing lens today. The source material 00:01:20.090 --> 00:01:22.269 for our deep dive comes from Michelle Bozeman. 00:01:22.430 --> 00:01:25.810 She is amazing. Oh, an absolute powerhouse. She 00:01:25.810 --> 00:01:30.030 has 30 years of IT experience, including roles 00:01:30.030 --> 00:01:33.510 as a director at Microsoft and a senior leader 00:01:33.510 --> 00:01:36.189 in AWS professional services. Wow. So she really 00:01:36.189 --> 00:01:39.290 knows the landscape. Intimately. And today, she 00:01:39.290 --> 00:01:42.010 runs TBW, which is an executive coaching firm 00:01:42.010 --> 00:01:44.129 specifically built for high -achieving women 00:01:44.129 --> 00:01:46.530 in tech. So she's sitting right on the front 00:01:46.530 --> 00:01:48.909 lines, seeing exactly why brilliant technical 00:01:48.909 --> 00:01:51.930 minds stall out, and more importantly, the specific 00:01:51.930 --> 00:01:54.230 mechanisms they use to leap forward. Okay, let's 00:01:54.230 --> 00:01:56.030 unpack this, because if you are a data -driven 00:01:56.030 --> 00:01:57.870 person listening right now, you might be, you 00:01:57.870 --> 00:01:59.489 know, rolling your eyes a little bit. The soft 00:01:59.489 --> 00:02:02.090 -skill stereotype. Yes. There's this persistent 00:02:02.090 --> 00:02:05.189 bias in tech that EQ is just corporate fluff. 00:02:05.329 --> 00:02:08.460 Like, it's just HR speak. But if you look at 00:02:08.460 --> 00:02:11.979 the McKinsey data Bozeman cites, it completely 00:02:11.979 --> 00:02:14.960 shatters that assumption. Leaders with high EQ 00:02:14.960 --> 00:02:17.259 scores are actually outperforming their revenue 00:02:17.259 --> 00:02:22.000 targets by 20%. Wait, 20 %? That's massive. It's 00:02:22.000 --> 00:02:24.159 a staggering variance. I mean, we usually attribute 00:02:24.159 --> 00:02:28.460 a 20 % revenue jump. to a massive new product 00:02:28.460 --> 00:02:31.039 launch or some seismic market shift, not to how 00:02:31.039 --> 00:02:33.280 a leader manages their own internal impulses, 00:02:33.280 --> 00:02:36.419 but that data point sets up a really critical 00:02:36.419 --> 00:02:39.620 tension in Bozeman's work. Because statistically, 00:02:39.870 --> 00:02:43.009 women naturally index very high on foundational 00:02:43.009 --> 00:02:46.310 EQ traits. They typically demonstrate much stronger 00:02:46.310 --> 00:02:49.870 baseline skills in reading nonverbal cues, active 00:02:49.870 --> 00:02:51.629 listening, and pathetic response. So they should 00:02:51.629 --> 00:02:53.650 be totally dominating the field, right? You would 00:02:53.650 --> 00:02:56.669 think so. Yet, in a highly technical, historically 00:02:56.669 --> 00:02:59.050 metric -obsessed environment, these natural strengths 00:02:59.050 --> 00:03:01.530 don't automatically translate to executive success. 00:03:01.849 --> 00:03:04.469 If they aren't managed strategically, they actually 00:03:04.469 --> 00:03:07.439 become hidden traps. Interesting. Okay, to understand 00:03:07.439 --> 00:03:09.639 why those traps happen, I think we first have 00:03:09.639 --> 00:03:13.560 to elevate our definition of EQ. Because we aren't 00:03:13.560 --> 00:03:16.219 just talking about being nice, right? No, not 00:03:16.219 --> 00:03:19.520 at all. Bozeman breaks EQ down into four operational 00:03:19.520 --> 00:03:21.740 pillars. Let's hear them. First, there's self 00:03:21.740 --> 00:03:25.300 -awareness, which is essentially real -time internal 00:03:25.300 --> 00:03:28.189 telemetry. It's your ability to read your own 00:03:28.189 --> 00:03:30.810 emotional logs before they trigger an outward 00:03:30.810 --> 00:03:33.050 reaction. Like checking your own system vitals. 00:03:33.349 --> 00:03:35.969 Exactly. Second is self -management. That's your 00:03:35.969 --> 00:03:38.629 runtime execution and impulse control. Third 00:03:38.629 --> 00:03:41.469 is social awareness. So your capacity to read 00:03:41.469 --> 00:03:43.729 the network traffic and room dynamics. Seeing 00:03:43.729 --> 00:03:45.889 what's happening around you. Right. And finally, 00:03:45.990 --> 00:03:48.030 relationship management, which is your ability 00:03:48.030 --> 00:03:51.189 to establish latency -free collaboration. When 00:03:51.189 --> 00:03:53.509 you define it in those operational terms, it 00:03:53.509 --> 00:03:55.909 makes perfect sense why Talent Smart found that 00:03:55.909 --> 00:03:58.389 90 % of top performers across all industries 00:03:58.389 --> 00:04:01.930 possess high EQ. 90 %? Yeah. In fact, when looking 00:04:01.930 --> 00:04:04.409 at leadership effectiveness specifically, EQ 00:04:04.409 --> 00:04:07.189 is proven to be twice as important as IQ and 00:04:07.189 --> 00:04:09.409 technical skills combined. Twice as important. 00:04:09.810 --> 00:04:12.449 That is wild. Well, I think of this way, you 00:04:12.449 --> 00:04:15.740 know. Your IQ and your coding proficiency, they 00:04:15.740 --> 00:04:18.399 represent your smartphone's hardware. It's the 00:04:18.399 --> 00:04:21.540 processor speed. It dictates your raw theoretical 00:04:21.540 --> 00:04:24.620 capability. Okay, I like this analogy. But EQ 00:04:24.620 --> 00:04:27.910 is the operating system. If you have a glitchy, 00:04:28.149 --> 00:04:30.790 unpatched OS, it honestly doesn't matter if you 00:04:30.790 --> 00:04:32.910 have the fastest microchip on the planet. Right, 00:04:32.970 --> 00:04:35.310 the system's still going to crash. Exactly. The 00:04:35.310 --> 00:04:38.310 hardware simply cannot route resources efficiently, 00:04:38.589 --> 00:04:41.410 especially when it's juggling multiple complex 00:04:41.410 --> 00:04:44.569 applications, which in our world means managing 00:04:44.569 --> 00:04:48.589 diverse engineering teams, navigating agile pivots, 00:04:48.689 --> 00:04:50.689 and resolving cross -departmental conflicts. 00:04:50.790 --> 00:04:52.949 What's really fascinating here is how the world's 00:04:52.949 --> 00:04:55.589 largest tech companies have independently proven 00:04:55.589 --> 00:04:57.930 that exact premise. Look at Google's project 00:04:57.930 --> 00:05:01.170 Aristotle. Oh, the perfect team study. Yes. They 00:05:01.170 --> 00:05:03.189 spent years trying to mathematically engineer 00:05:03.189 --> 00:05:06.230 the perfect, most productive team. They fed massive 00:05:06.230 --> 00:05:08.569 data sets into their models, educational backgrounds, 00:05:09.129 --> 00:05:11.170 coding proficiencies, personality types. Just 00:05:11.170 --> 00:05:13.329 looking for the ultimate combination of geniuses. 00:05:13.569 --> 00:05:16.129 Exactly. And the number one predictor of team 00:05:16.129 --> 00:05:20.149 success wasn't the raw hardware, it was psychological 00:05:20.149 --> 00:05:24.100 safety. which is a direct measurable byproduct 00:05:24.100 --> 00:05:26.680 of emotionally intelligent leadership. And there 00:05:26.680 --> 00:05:29.920 is actually a physical biological mechanism behind 00:05:29.920 --> 00:05:32.779 this that makes it so actionable because, you 00:05:32.779 --> 00:05:34.600 know, the immediate pushback is usually, well, 00:05:34.620 --> 00:05:37.139 my brain just doesn't work that way. I'm a logical 00:05:37.139 --> 00:05:40.199 person. My EQ is basically set in stone. Right. 00:05:40.360 --> 00:05:43.560 The I am who I am defense. Yeah. But the neuroscience 00:05:43.560 --> 00:05:45.879 completely invalidates that excuse. Totally. 00:05:46.040 --> 00:05:49.540 Yeah. Unlike IQ, which largely stabilizes and 00:05:49.540 --> 00:05:51.310 remains kind of static throughout your adult 00:05:51.310 --> 00:05:54.269 life, EQ is governed by neuroplasticity. Which 00:05:54.269 --> 00:05:56.649 means we can change it. Exactly. Every time you 00:05:56.649 --> 00:05:58.970 consciously choose a strategic response over 00:05:58.970 --> 00:06:02.470 like a reactive emotional impulse, you are physically 00:06:02.470 --> 00:06:04.529 thickening the neural pathways in your prefrontal 00:06:04.529 --> 00:06:06.910 cortex. Wow. You're actively building myelin 00:06:06.910 --> 00:06:09.029 around those new connections, which literally 00:06:09.029 --> 00:06:11.129 upgrades your operating system's code over time. 00:06:11.410 --> 00:06:13.610 It is a highly trainable physical adaptation. 00:06:13.930 --> 00:06:16.370 Which brings us to a really fascinating contradiction. 00:06:16.970 --> 00:06:20.660 If EQ is a trainable skill, and women naturally 00:06:20.660 --> 00:06:23.540 excel at the foundational telemetry of it, then 00:06:23.540 --> 00:06:26.060 women should be effortlessly dominating executive 00:06:26.060 --> 00:06:28.319 technical leadership. Right. But they aren't. 00:06:28.480 --> 00:06:31.379 Many are hitting a ceiling, or worse, completely 00:06:31.379 --> 00:06:35.360 burning out. And Bozeman identifies three specific 00:06:35.360 --> 00:06:38.720 systemic pitfalls responsible for this. So let's 00:06:38.720 --> 00:06:41.160 look at pitfall number one, over accommodation. 00:06:41.319 --> 00:06:43.980 Oh, boy. This is a scenario that many of you 00:06:43.980 --> 00:06:46.160 listening will recognize instantly. Oh, for sure. 00:06:46.279 --> 00:06:48.759 Think about the last high -stakes architecture 00:06:48.759 --> 00:06:50.899 review you led. Instead of simply delivering 00:06:50.899 --> 00:06:53.240 your analysis, you are likely running a massive 00:06:53.240 --> 00:06:56.040 background process. You're carefully modulating 00:06:56.040 --> 00:06:58.860 your tones so you sound confident, but not aggressive. 00:06:59.279 --> 00:07:01.680 You pre -qualify your insights with things like, 00:07:02.019 --> 00:07:04.600 uh, I might be missing some context here, but... 00:07:04.600 --> 00:07:07.480 The constant apologizing. Exactly. You might 00:07:07.480 --> 00:07:09.500 even catch yourself absorbing the blame when 00:07:09.500 --> 00:07:12.319 a deployment fails, even if the failure happened 00:07:12.319 --> 00:07:15.480 downstream from your code. You aren't just participating 00:07:15.480 --> 00:07:18.720 in the meeting, you are managing a second, entirely 00:07:18.720 --> 00:07:21.899 invisible job of monitoring how everyone in the 00:07:21.899 --> 00:07:24.339 room is perceiving your output. And that invisible 00:07:24.339 --> 00:07:27.839 job demands a massive amount of processing power. 00:07:28.459 --> 00:07:31.519 Bozeman refers to this as the authenticity tax. 00:07:31.660 --> 00:07:34.360 The authenticity tax? Yeah. The research indicates 00:07:34.360 --> 00:07:36.980 that women often spend up to 30 % of their mental 00:07:36.980 --> 00:07:39.899 resources just monitoring and adjusting their 00:07:39.899 --> 00:07:44.319 self -presentation. 30 %! just on managing how 00:07:44.319 --> 00:07:46.879 they look to others. Think about the sheer cognitive 00:07:46.879 --> 00:07:50.000 drain of that. 30 % of your available RAM is 00:07:50.000 --> 00:07:52.800 just dedicated to threat detection and tone modulation. 00:07:53.339 --> 00:07:55.959 Every ounce of mental energy spent hyper -analyzing 00:07:55.959 --> 00:07:58.339 your presentation is energy stripped directly 00:07:58.339 --> 00:08:01.040 away from complex problem solving and strategic 00:08:01.040 --> 00:08:02.860 innovation. But I want to push back a little 00:08:02.860 --> 00:08:05.279 on the idea that this is just a personal failing. 00:08:05.839 --> 00:08:08.100 The reason this happens isn't because women just 00:08:08.100 --> 00:08:10.519 lack confidence. No, not at all. Bozeman clearly 00:08:10.519 --> 00:08:14.180 points out the double bind. It is a very real, 00:08:14.420 --> 00:08:17.939 well -documented systemic trap. If you are highly 00:08:17.939 --> 00:08:20.779 assertive and direct in a tech environment, you're 00:08:20.779 --> 00:08:23.180 respected for your technical chops, but you get 00:08:23.180 --> 00:08:25.779 penalized socially. Right. You get labeled as 00:08:25.779 --> 00:08:28.879 difficult or abrasive. Exactly. But then, if 00:08:28.879 --> 00:08:31.439 you lean heavily into the empathetic collaborative 00:08:31.439 --> 00:08:33.919 side, you're penalized professionally. You're 00:08:33.919 --> 00:08:36.899 seen as too soft to make ruthless technical decisions. 00:08:37.120 --> 00:08:40.240 The classic catch -22. So this over -accommodation 00:08:40.240 --> 00:08:43.039 isn't a glitch. It's basically a necessary survival 00:08:43.039 --> 00:08:46.700 mechanism to navigate a flawed system. It absolutely 00:08:46.700 --> 00:08:49.519 begins as a survival mechanism, but it inevitably 00:08:49.519 --> 00:08:52.120 becomes a performance bottleneck. You just cannot 00:08:52.120 --> 00:08:54.379 operate at the executive level while paying a 00:08:54.379 --> 00:08:57.240 30 % tax on your cognition. So how do we bypass 00:08:57.240 --> 00:09:00.480 the tax? Well, the solution Bozeman proposes 00:09:00.480 --> 00:09:02.600 is not to just abandon all filters and become 00:09:02.600 --> 00:09:04.659 aggressively blunt. That just creates friction. 00:09:04.860 --> 00:09:08.299 The antidote is what she calls strategic authenticity. 00:09:08.659 --> 00:09:10.259 Strategic authenticity. Okay, what does that 00:09:10.259 --> 00:09:12.539 look like? This is the intentional alignment 00:09:12.539 --> 00:09:15.620 between your internal values and your external 00:09:15.620 --> 00:09:18.440 expression. You are expressing your genuine self, 00:09:18.820 --> 00:09:21.559 but doing it in a way that deliberately advances 00:09:21.559 --> 00:09:25.440 your objectives. And the ROI here is highly measurable. 00:09:25.620 --> 00:09:28.700 Do we have numbers on that? We do. Leaders who 00:09:28.700 --> 00:09:31.320 achieve this alignment and are rated as authentic 00:09:31.320 --> 00:09:34.059 by their teams actually outperform their peers 00:09:34.059 --> 00:09:38.100 by 22 % on leadership effectiveness metrics. 00:09:38.879 --> 00:09:41.639 Because authenticity removes the latency. It 00:09:41.639 --> 00:09:44.039 builds immediate trust and trust accelerates 00:09:44.039 --> 00:09:46.480 deployment. But how do you actually implement 00:09:46.480 --> 00:09:49.440 strategic authenticity? Bozeman provides three 00:09:49.440 --> 00:09:52.000 very concrete tools. The first is the emotional 00:09:52.000 --> 00:09:54.340 audit. Okay. This is just a two -minute process 00:09:54.340 --> 00:09:56.019 before a critical interaction where you check 00:09:56.019 --> 00:09:58.100 your internal telemetry. Yeah. Are you acting 00:09:58.100 --> 00:10:00.039 out of desire to solve the technical problem 00:10:00.039 --> 00:10:02.320 or are you acting out of a desire to manage someone 00:10:02.320 --> 00:10:04.379 else's perception of you? Oh, that's a great 00:10:04.379 --> 00:10:06.600 question to ask yourself. It stops unexamined 00:10:06.600 --> 00:10:08.740 anxiety from compiling into your behavior. Okay, 00:10:08.740 --> 00:10:11.779 what's the second tool? The second tool is value 00:10:11.779 --> 00:10:15.059 -aligned decision -making. You have to clearly 00:10:15.059 --> 00:10:17.799 define your non -negotiable leadership values 00:10:17.799 --> 00:10:21.000 and use them as your compass. Give me an example 00:10:21.000 --> 00:10:23.629 of how that plays out. Let's say a product manager 00:10:23.629 --> 00:10:26.269 is aggressively pushing for a Friday deployment 00:10:26.269 --> 00:10:28.570 of a feature, you know, hasn't cleared security 00:10:28.570 --> 00:10:32.490 protocols. If your core value is integrity of 00:10:32.490 --> 00:10:35.330 the system, you don't need to waste RAM worrying 00:10:35.330 --> 00:10:37.610 about whether pushing back makes you look difficult. 00:10:37.789 --> 00:10:40.049 You just lean on the value. Exactly. You anchor 00:10:40.049 --> 00:10:42.490 your response entirely on the value. You say, 00:10:42.610 --> 00:10:44.830 my priority is system stability, so we are holding 00:10:44.830 --> 00:10:47.700 this until Monday. The value makes the decision 00:10:47.700 --> 00:10:50.059 for you, completely removing the authenticity 00:10:50.059 --> 00:10:53.279 tax. I love that. And the third tool is authentic 00:10:53.279 --> 00:10:55.919 voice journaling. It sounds a bit abstract, but 00:10:55.919 --> 00:10:57.740 it's really just log analysis. Right. You track 00:10:57.740 --> 00:10:59.980 your weekly interactions, you note the meetings 00:10:59.980 --> 00:11:02.279 where you felt aligned and authoritative, and 00:11:02.279 --> 00:11:04.240 the ones where you felt yourself shrinking or, 00:11:04.240 --> 00:11:06.200 you know, over accommodating. You start looking 00:11:06.200 --> 00:11:08.960 for the bugs in your own log. Exactly. You start 00:11:08.960 --> 00:11:12.159 to spot the triggers. Maybe a specific stakeholder's 00:11:12.159 --> 00:11:14.799 communication style constantly forces you into 00:11:14.799 --> 00:11:17.340 a defensive posture. You can't write a patch 00:11:17.340 --> 00:11:19.960 for a bug until you identify the pattern in the 00:11:19.960 --> 00:11:23.000 logs. You are turning subjective feelings into 00:11:23.000 --> 00:11:26.740 actionable data. Overaccommodation is fundamentally 00:11:26.740 --> 00:11:29.500 an issue of how we filter our output to the world. 00:11:30.039 --> 00:11:32.220 But what happens when we reverse the flow of 00:11:32.220 --> 00:11:34.740 information? What happens when we stop worrying 00:11:34.740 --> 00:11:37.139 about what we are outputting and look at the 00:11:37.139 --> 00:11:39.360 emotional data we are downloading from our team? 00:11:39.539 --> 00:11:42.240 Oh, this leads us directly to pitfall two, the 00:11:42.240 --> 00:11:45.240 empathy burden. Right, because empathy is a phenomenal 00:11:45.240 --> 00:11:47.399 tool for building that psychological safety we 00:11:47.399 --> 00:11:49.639 discussed earlier. But it has a severe failure 00:11:49.639 --> 00:11:52.399 mode. It really does. A recent study found that 00:11:52.399 --> 00:11:55.360 68 percent of women leaders report experiencing 00:11:55.360 --> 00:11:58.460 compassion fatigue. 68%. And this isn't just 00:11:58.460 --> 00:12:01.559 regular tiredness, right? It is a profound systemic 00:12:01.559 --> 00:12:04.460 emotional exhaustion that occurs when a leader 00:12:04.460 --> 00:12:07.779 continuously absorbs and processes the stress, 00:12:08.159 --> 00:12:10.259 the anxieties, and emotional burdens of their 00:12:10.259 --> 00:12:12.799 team members. Here's where it gets really interesting, 00:12:12.860 --> 00:12:15.279 because the conventional wisdom is that being 00:12:15.279 --> 00:12:17.620 highly empathetic makes you a servant leader. 00:12:18.000 --> 00:12:21.399 Like, that's the ideal. Right. But Boseman reveals 00:12:21.399 --> 00:12:23.860 that acting as an emotional sponge actually creates 00:12:23.860 --> 00:12:26.840 a massive systemic risk, both to your career 00:12:26.840 --> 00:12:29.279 trajectory and to the organization itself. It 00:12:29.279 --> 00:12:31.720 fundamentally damages your operational capacity. 00:12:32.340 --> 00:12:34.679 When a leader functions as an endless emotional 00:12:34.679 --> 00:12:38.139 caretaker without firm boundaries, a shift happens 00:12:38.139 --> 00:12:40.580 in the organization's perception of them. How 00:12:40.580 --> 00:12:43.600 so? Well, in a hard skills environment, that 00:12:43.600 --> 00:12:47.159 deep unstructured empathy gets reframed negatively. 00:12:47.399 --> 00:12:50.519 You stop being seen as a strategic visionary, 00:12:50.700 --> 00:12:53.559 capable of leading a massive migration, and you 00:12:53.559 --> 00:12:56.679 start being viewed as, well, maternal. The maternal 00:12:56.679 --> 00:12:59.139 trap. Exactly. You become the team therapist, 00:12:59.600 --> 00:13:02.299 which drastically erodes your strategic authority. 00:13:02.600 --> 00:13:04.360 But honestly, the damage to the team is even 00:13:04.360 --> 00:13:07.159 worse. Right, because if you are the one constantly 00:13:07.159 --> 00:13:08.980 regulating the team's stress, you're essentially 00:13:08.980 --> 00:13:12.240 creating a centralized server for emotional processing. 00:13:12.320 --> 00:13:15.240 Yes. If you go offline, like if you take a vacation 00:13:15.240 --> 00:13:17.240 or move to a new project, the whole team crashes 00:13:17.240 --> 00:13:19.440 because they haven't built their own local capacity 00:13:19.440 --> 00:13:22.580 for resilience. Your compassion hasn't empowered 00:13:22.580 --> 00:13:25.759 them. It has inadvertently turned you into a 00:13:25.759 --> 00:13:27.940 single point of failure. That's a perfect way 00:13:27.940 --> 00:13:31.220 to describe it. A single point of failure. So 00:13:31.220 --> 00:13:34.440 to fix this, you don't suddenly become a cold, 00:13:34.740 --> 00:13:36.820 hyper -rational robot, right? Right. We still 00:13:36.820 --> 00:13:40.120 want to be human. Exactly. The solution is compassionate 00:13:40.120 --> 00:13:43.039 detachment. This means you care more strategically 00:13:43.039 --> 00:13:45.960 so that you can sustain that care over the long 00:13:45.960 --> 00:13:48.840 term. Studies actually show that leaders who 00:13:48.840 --> 00:13:52.139 implement compassionate detachment report a 40 00:13:52.139 --> 00:13:54.759 % reduction in emotional exhaustion. Wow, almost 00:13:54.759 --> 00:13:57.360 half. And it actually increases their team's 00:13:57.360 --> 00:13:59.419 independent problem -solving metrics at the same 00:13:59.419 --> 00:14:02.299 time. Because they're forcing the team to process 00:14:02.299 --> 00:14:04.679 their own emotions. Exactly. The mechanics of 00:14:04.679 --> 00:14:06.860 compassionate detachment are highly actionable. 00:14:07.480 --> 00:14:09.559 So step one, schedule your emotional support. 00:14:10.019 --> 00:14:12.799 You cannot be an open API that anyone can ping 00:14:12.799 --> 00:14:15.480 at any time of day to dump their stress. Boundaries 00:14:15.480 --> 00:14:18.259 are essential. Right. You need to establish predictable 00:14:18.259 --> 00:14:21.460 office hours for those deep supportive conversations. 00:14:22.440 --> 00:14:26.659 Step two, create firm boundaries. Bozeman highly 00:14:26.659 --> 00:14:30.139 recommends designating no emotional labor days. 00:14:30.620 --> 00:14:32.440 I love that concept. Yeah, these are specific 00:14:32.440 --> 00:14:35.019 days completely blocked off for deep architectural 00:14:35.019 --> 00:14:37.460 work and strategic planning, where your team 00:14:37.460 --> 00:14:40.379 knows you are offline for interpersonal troubleshooting. 00:14:40.860 --> 00:14:43.299 And step three is the actual mechanism of interaction. 00:14:43.440 --> 00:14:46.039 It's called the Observe Support Release Technique. 00:14:46.200 --> 00:14:48.700 Okay, walk us through that. So, when a developer 00:14:48.700 --> 00:14:51.039 comes to you completely overwhelmed by a failing 00:14:51.039 --> 00:14:54.279 build, you observe their frustration. and you 00:14:54.279 --> 00:14:57.080 offer appropriate structural support. Maybe you 00:14:57.080 --> 00:14:58.940 assign a secondary engineer to help them debug. 00:14:59.039 --> 00:15:01.720 You give them resources. Right. But then, you 00:15:01.720 --> 00:15:03.779 deliberately release the responsibility for their 00:15:03.779 --> 00:15:06.440 emotional state. You ask them, what patterns 00:15:06.440 --> 00:15:08.480 are you noticing in how you approach these high 00:15:08.480 --> 00:15:11.419 pressure bugs? By doing this, you force their 00:15:11.419 --> 00:15:13.639 prefrontal cortex to engage. You slip it back 00:15:13.639 --> 00:15:15.860 to them. Exactly. You're forcing them to build 00:15:15.860 --> 00:15:18.019 their own neural pathways for resilience rather 00:15:18.019 --> 00:15:20.240 than doing the emotional heavy lifting for them. 00:15:20.559 --> 00:15:22.960 You shift from being an emotional manager to 00:15:22.960 --> 00:15:26.000 an emotional capacity builder. I absolutely love 00:15:26.000 --> 00:15:28.679 that. That's a huge shift. So we've debugged 00:15:28.679 --> 00:15:32.200 our output with strategic authenticity. We've 00:15:32.200 --> 00:15:34.419 optimized our inputs with compassionate detachment. 00:15:34.899 --> 00:15:36.820 But there is a third vector we have to secure. 00:15:37.019 --> 00:15:39.120 The toughest one. Yeah. What happens when the 00:15:39.120 --> 00:15:41.700 critical data is pointed directly at us? How 00:15:41.700 --> 00:15:44.320 do we process negative feedback without it crashing 00:15:44.320 --> 00:15:46.700 our own system? Which triggers Bozeman's final 00:15:46.700 --> 00:15:50.600 challenge, pitfall three, perfectionism, and 00:15:50.600 --> 00:15:52.759 the certainty gap. OK, let's get into the data 00:15:52.759 --> 00:15:54.539 on this one. This is where the behavioral data 00:15:54.539 --> 00:15:57.620 gets incredibly stark. A Cornell University study 00:15:57.620 --> 00:16:00.840 found a massive discrepancy in how risk is processed. 00:16:01.470 --> 00:16:04.289 Women need an average certainty level of 80 % 00:16:04.289 --> 00:16:07.029 before making a decision or taking action. 80%. 00:16:07.029 --> 00:16:09.289 And what about men? Their male counterparts will 00:16:09.289 --> 00:16:12.210 confidently move forward with just 65 % certainty. 00:16:12.690 --> 00:16:15.259 Wow. I suppose if we are talking about, like, 00:16:15.379 --> 00:16:18.200 deploying a massive database migration, demanding 00:16:18.200 --> 00:16:20.759 80 % certainty is excellent engineering, you 00:16:20.759 --> 00:16:23.080 want high standards. Sure, in a techable context. 00:16:23.340 --> 00:16:26.919 But I can see how applying that same 80 % requirement 00:16:26.919 --> 00:16:29.139 to your own self -worth would be catastrophic. 00:16:29.940 --> 00:16:32.700 If your baseline requirement is perfection, then 00:16:32.700 --> 00:16:34.899 any piece of critical feedback isn't just a data 00:16:34.899 --> 00:16:37.820 point. It shatters the entire framework. You 00:16:37.820 --> 00:16:40.240 hit the exact mechanism of the problem. that 00:16:40.240 --> 00:16:43.679 impossibly high bar of perfectionism causes women 00:16:43.679 --> 00:16:46.779 to internalize criticism in a fundamentally different 00:16:46.779 --> 00:16:50.179 way. Boseman's research points out that women 00:16:50.179 --> 00:16:53.200 are 22 % more likely to attribute project failures 00:16:53.200 --> 00:16:56.399 or mistakes to their own internal character flaws 00:16:56.399 --> 00:16:59.139 rather than external environmental circumstances. 00:16:59.559 --> 00:17:02.379 That's heavy. It is. So when a manager says, 00:17:02.379 --> 00:17:05.059 you know, this feature lacks scalability, the 00:17:05.059 --> 00:17:07.180 perfectionist brain doesn't hear a technical 00:17:07.180 --> 00:17:10.289 critique. It hears, I am an imposter who doesn't 00:17:10.289 --> 00:17:12.349 belong in this role. It makes it personal. Exactly. 00:17:12.690 --> 00:17:15.569 It triggers an amygdala hijack. It fuels toxic 00:17:15.569 --> 00:17:18.910 rumination. And it paralyzes the rapid iteration 00:17:18.910 --> 00:17:21.190 that tech leadership actually requires. So we 00:17:21.190 --> 00:17:23.670 need a reliable algorithm for processing feedback 00:17:23.670 --> 00:17:26.630 without letting it corrupt our confidence. And 00:17:26.630 --> 00:17:29.569 Bozeman offers a brilliant structured framework 00:17:29.569 --> 00:17:32.789 for this called the 321 feedback method. Yes. 00:17:33.039 --> 00:17:35.720 Studies in cognitive behavioral therapy show 00:17:35.720 --> 00:17:37.900 that using highly structured approaches like 00:17:37.900 --> 00:17:40.779 this can reduce that paralyzing rumination by 00:17:40.779 --> 00:17:44.940 up to 60%. 60%. That's huge. It really is. So 00:17:44.940 --> 00:17:48.119 here is how you execute the 3 -2 -1 method. The 00:17:48.119 --> 00:17:50.220 next time you receive tough critical feedback, 00:17:50.779 --> 00:17:53.400 you grab a physical notebook. And we should specify 00:17:53.400 --> 00:17:55.759 why the physical act of writing is necessary 00:17:55.759 --> 00:17:57.660 here. Good point. Go ahead. When you receive 00:17:57.660 --> 00:18:00.069 criticism, Your amygdala, the threat detection 00:18:00.069 --> 00:18:03.170 center of your brain, fires up. By forcing yourself 00:18:03.170 --> 00:18:06.009 to physically write things down, you are demanding 00:18:06.009 --> 00:18:08.470 processing power from your prefrontal cortex. 00:18:08.630 --> 00:18:11.349 You're manually overriding the panic. Literally. 00:18:11.630 --> 00:18:13.829 You are rerouting the electrical activity in 00:18:13.829 --> 00:18:16.150 your brain away from panic and toward logical 00:18:16.150 --> 00:18:18.690 analysis. Exactly. It forces the system to cool 00:18:18.690 --> 00:18:21.849 down. So first, you identify the three. You write 00:18:21.849 --> 00:18:24.450 down three objective truths hidden within the 00:18:24.450 --> 00:18:26.730 feedback. You strip away the tone of the person 00:18:26.730 --> 00:18:29.289 who delivered it. You strip away your own defensiveness. 00:18:29.549 --> 00:18:32.970 And you extract three undeniable analytical facts. 00:18:33.289 --> 00:18:36.009 Right, just the raw data. Then second, you determine 00:18:36.009 --> 00:18:38.880 the two. You create two concrete actions based 00:18:38.880 --> 00:18:41.160 on those truths. Like, what is your actual deployment 00:18:41.160 --> 00:18:43.980 plan for tomorrow to address those facts? And 00:18:43.980 --> 00:18:47.000 finally, the one. This is the most critical step. 00:18:47.460 --> 00:18:50.440 You consciously choose one aspect of the feedback 00:18:50.440 --> 00:18:53.539 to let go of. Which is deeply counterintuitive 00:18:53.539 --> 00:18:56.140 for an overachiever. I mean, how could you just 00:18:56.140 --> 00:18:58.740 ignore a piece of feedback? It feels wrong, right? 00:18:58.819 --> 00:19:01.400 Yeah. But that is the mechanism that reclaims 00:19:01.400 --> 00:19:04.039 your power. You have to recognize that in any 00:19:04.039 --> 00:19:07.559 human ecosystem, some feedback is just corrupted 00:19:07.559 --> 00:19:09.900 data. Exactly. It might be purely subjective. 00:19:10.079 --> 00:19:12.740 It might be driven by office politics or it might 00:19:12.740 --> 00:19:15.680 contradict your core values. By actively choosing 00:19:15.680 --> 00:19:18.720 one piece of the feedback to discard, you shift 00:19:18.720 --> 00:19:21.740 from being a passive victim of criticism to an 00:19:21.740 --> 00:19:24.869 active curator of your own growth. Three objective 00:19:24.869 --> 00:19:28.390 truths, two concrete actions, one thing to send 00:19:28.390 --> 00:19:31.130 to the trash. It's a brilliant way to process 00:19:31.130 --> 00:19:34.009 data without letting it infect the host. It really 00:19:34.009 --> 00:19:37.009 is. Now, as you look at these three pitfalls... 00:19:36.839 --> 00:19:39.960 the authenticity attacks draining your RAM, the 00:19:39.960 --> 00:19:41.940 compassion fatigue turning you into a single 00:19:41.940 --> 00:19:44.839 point of failure, and the perfectionism causing 00:19:44.839 --> 00:19:48.740 you to internalize bad data, you realize they 00:19:48.740 --> 00:19:52.119 aren't isolated bugs. They are a deeply interconnected 00:19:52.119 --> 00:19:55.220 system. Yes. If we connect this to the bigger 00:19:55.220 --> 00:19:57.779 picture, you see how these vulnerabilities feed 00:19:57.779 --> 00:20:00.880 off each other. If you are exhausted from absorbing 00:20:00.880 --> 00:20:03.359 your team's emotional weight, your system is 00:20:03.359 --> 00:20:05.759 already strained. which means you're going to 00:20:05.759 --> 00:20:08.400 be far more sensitive and reactive to critical 00:20:08.400 --> 00:20:11.380 feedback. Like a domino effect. Exactly. And 00:20:11.380 --> 00:20:13.660 if you are constantly monitoring your tone to 00:20:13.660 --> 00:20:15.980 sound perfect, you have no bandwidth left to 00:20:15.980 --> 00:20:18.660 enforce boundaries. But the inverse is also true 00:20:18.660 --> 00:20:21.200 patching. Just one of these areas creates a powerful 00:20:21.200 --> 00:20:23.460 cascading upgrade across your entire operating 00:20:23.460 --> 00:20:26.079 system. And that interconnectedness is why Bozeman's 00:20:26.079 --> 00:20:28.619 implementation strategy is so important. If you 00:20:28.619 --> 00:20:30.359 are listening to this and thinking, you know, 00:20:30.359 --> 00:20:32.539 I suffer from all three of these traps, I need 00:20:32.539 --> 00:20:34.940 to completely overhaul my personality by Monday 00:20:34.940 --> 00:20:38.579 morning. Don't do it. Right. Stop. That is a 00:20:38.579 --> 00:20:41.680 guaranteed recipe for system failure. The research 00:20:41.680 --> 00:20:43.680 from the Center for Creative Leadership is clear. 00:20:44.349 --> 00:20:47.410 Leaders who focus on developing highly specific 00:20:47.410 --> 00:20:51.609 targeted EQ skills report a 34 % higher leadership 00:20:51.609 --> 00:20:55.430 effectiveness score in just six months. The operative 00:20:55.430 --> 00:20:58.509 word being specific. Yes. This is why Bozeman 00:20:58.509 --> 00:21:01.609 advocates for a simple 30 -day EQ action plan. 00:21:02.190 --> 00:21:04.670 Do not try to boil the ocean. Look at the mechanisms 00:21:04.670 --> 00:21:07.890 we just discussed and pick exactly one technique. 00:21:08.309 --> 00:21:11.250 Just one. Pick your battle. Exactly. Maybe you 00:21:11.250 --> 00:21:13.069 commit to doing a two -minute emotional audit 00:21:13.069 --> 00:21:15.569 before your wantly stand -up. Maybe you establish 00:21:15.569 --> 00:21:18.170 every Thursday as a no emotional labor day. Or 00:21:18.170 --> 00:21:20.250 maybe you just promise to use the 3 -2 -1 method 00:21:20.250 --> 00:21:22.470 the next time a code review gets heated. You 00:21:22.470 --> 00:21:24.490 pick one protocol and you run it consistently 00:21:24.490 --> 00:21:27.359 for 30 days to build that neural pathway. It 00:21:27.359 --> 00:21:29.559 is also really worth noting the broader context 00:21:29.559 --> 00:21:32.539 of Bozeman's work here. She is so deeply invested 00:21:32.539 --> 00:21:34.779 in closing the leadership gap for women in tech 00:21:34.779 --> 00:21:37.059 that she actually offered complimentary coaching 00:21:37.059 --> 00:21:39.460 sessions to her audience to help them define 00:21:39.460 --> 00:21:41.480 these six -month objectives. Which is amazing. 00:21:41.740 --> 00:21:44.940 It really underscores a vital reality. You cannot 00:21:44.940 --> 00:21:47.359 completely rewrite your operating system in a 00:21:47.359 --> 00:21:50.960 vacuum. Community, mentorship, and objective 00:21:50.960 --> 00:21:53.940 external feedback, those are the critical infrastructure 00:21:53.940 --> 00:21:57.400 required for this kind of permanent growth. So 00:21:57.400 --> 00:21:59.880 what does this all mean for you? Whether you 00:21:59.880 --> 00:22:02.200 are a seasoned executive architect designing 00:22:02.200 --> 00:22:05.319 global infrastructure or a senior engineer just 00:22:05.319 --> 00:22:07.579 stepping into your first management role, you 00:22:07.579 --> 00:22:09.980 have to stop viewing emotional intelligence as 00:22:09.980 --> 00:22:13.619 a secondary nice to have soft skill. In an industry 00:22:13.619 --> 00:22:16.619 obsessed with sprint velocities, output metrics, 00:22:16.779 --> 00:22:20.380 and hard data, your EQ is your ultimate competitive 00:22:20.380 --> 00:22:23.220 advantage. It is the operating system that allows 00:22:23.220 --> 00:22:26.140 your hard -earned technical brilliance to actually 00:22:26.140 --> 00:22:28.359 function at scale. I want to leave you with a 00:22:28.359 --> 00:22:30.220 completely new angle to mull over as we wrap 00:22:30.220 --> 00:22:32.519 up today. Let's hear it. We've spent this entire 00:22:32.519 --> 00:22:35.880 time talking about EQ as a vital optimizer for 00:22:35.880 --> 00:22:38.519 your technical skills, right? But consider the 00:22:38.519 --> 00:22:42.019 trajectory of our industry right now. As AI models 00:22:42.019 --> 00:22:44.759 become increasingly sophisticated, as they begin 00:22:44.759 --> 00:22:48.640 to reliably automate the actual coding, the architecture, 00:22:48.859 --> 00:22:52.200 and the raw hardware tasks of engineering, the 00:22:52.200 --> 00:22:55.640 value of pure technical execution is going to 00:22:55.640 --> 00:22:58.299 commoditize. Oh, wow. That's true. Right. When 00:22:58.299 --> 00:23:00.420 AI can write the code faster and more accurately 00:23:00.420 --> 00:23:03.279 than any human, how long will it be until your 00:23:03.279 --> 00:23:05.799 emotional intelligence isn't just a leadership 00:23:05.799 --> 00:23:08.380 advantage but literally the only metric that 00:23:08.380 --> 00:23:10.940 separates a human engineer? from the machines 00:23:10.940 --> 00:23:14.059 they are managing. What a profound thought. The 00:23:14.059 --> 00:23:16.000 hardware is becoming automated. The operating 00:23:16.000 --> 00:23:18.299 system is what makes us indispensable. We spent 00:23:18.299 --> 00:23:20.859 our entire careers optimizing our code to ensure 00:23:20.859 --> 00:23:23.700 it runs flawlessly in any environment. It is 00:23:23.700 --> 00:23:25.920 time we start applying that exact same level 00:23:25.920 --> 00:23:28.619 of rigorous engineering to ourselves. Thank you 00:23:28.619 --> 00:23:31.180 for joining us on this deep dive. Pick your one 00:23:31.180 --> 00:23:33.319 technique, deploy it this week, and we will catch 00:23:33.319 --> 00:23:34.019 you next time.