WEBVTT 00:00:00.000 --> 00:00:03.379 Welcome to the debate. Today, we're diving into, 00:00:03.379 --> 00:00:06.219 well, what feels like an ever shifting target, 00:00:06.719 --> 00:00:09.300 professional email etiquette. Despite Slack, 00:00:09.660 --> 00:00:12.660 Teams, all of that, email is still fundamentally 00:00:12.660 --> 00:00:15.099 the authoritative backbone for so much formal 00:00:15.099 --> 00:00:17.600 business, legal stuff, international communication. 00:00:18.000 --> 00:00:20.719 Absolutely. And it's a space where the old norms 00:00:20.719 --> 00:00:23.100 are constantly getting pushed around by new tech, 00:00:23.480 --> 00:00:26.239 by global diversity, information overload. It's 00:00:26.239 --> 00:00:28.120 messy. We're not just talking about typos here, 00:00:28.120 --> 00:00:30.589 are we? It's really about the mechanics of trust 00:00:30.589 --> 00:00:33.649 and accountability. Exactly. And the core tension 00:00:33.649 --> 00:00:36.310 we want to unpack today is, well, it's pretty 00:00:36.310 --> 00:00:39.009 fundamental. Should professional email norms 00:00:39.009 --> 00:00:42.390 really prioritize accountability, structure, 00:00:42.789 --> 00:00:45.079 and clear documentation? you know, through things 00:00:45.079 --> 00:00:48.179 like mandatory read receipts, rigid CC structures, 00:00:48.600 --> 00:00:51.840 or should we lean more towards recipient autonomy, 00:00:52.520 --> 00:00:55.079 flexibility, depending on the context, and maybe 00:00:55.079 --> 00:00:57.899 reducing some of that communication anxiety that 00:00:57.899 --> 00:01:00.039 comes with tracking? And I'll be arguing for 00:01:00.039 --> 00:01:02.670 that flexibility. I think these really rigid 00:01:02.670 --> 00:01:05.409 demands, well, they fundamentally misunderstand 00:01:05.409 --> 00:01:08.469 that email is supposed to be asynchronous. And 00:01:08.469 --> 00:01:10.730 ironically, they can actually damage the professional 00:01:10.730 --> 00:01:13.489 trust we're trying to build. My focus is more 00:01:13.489 --> 00:01:15.689 on the human side, the communication overload 00:01:15.689 --> 00:01:19.129 aspect. And I'll take the other side. I'll argue 00:01:19.129 --> 00:01:22.650 for structure. Clear, established protocols, 00:01:22.989 --> 00:01:25.829 particularly those laid out in frameworks like 00:01:25.829 --> 00:01:28.489 Adrian Barker's professional global etiquette. 00:01:28.530 --> 00:01:31.480 Let's call it PGE for short. I think they're 00:01:31.480 --> 00:01:34.379 necessary, especially when you're managing complex 00:01:34.379 --> 00:01:37.599 multinational operations. Now, for this discussion, 00:01:37.840 --> 00:01:41.760 let's define PGE as a system that really values 00:01:41.760 --> 00:01:45.700 legal documentation, predictable response times, 00:01:46.219 --> 00:01:48.939 clear hierarchy, maybe sometimes over relationship 00:01:48.939 --> 00:01:52.900 history. Structure, I believe, guarantees efficiency 00:01:52.900 --> 00:01:55.400 and accountability, especially when the stakes 00:01:55.400 --> 00:01:58.209 are high. So my core argument... drawing from 00:01:58.209 --> 00:02:01.489 those PGE principles, is that structure ensures 00:02:01.489 --> 00:02:03.750 critical communications aren't just, you know, 00:02:03.769 --> 00:02:06.969 sent off into the void. They need to be demonstrably 00:02:06.969 --> 00:02:10.629 received, understood, and managed properly. Think 00:02:10.629 --> 00:02:13.509 about high -stakes situations, a contract negotiation, 00:02:13.930 --> 00:02:16.550 maybe a critical software patch, an urgent change 00:02:16.550 --> 00:02:19.469 to a global supply chain timeline. In those cases, 00:02:19.990 --> 00:02:23.169 confirmation isn't just nice, it's non -negotiable. 00:02:23.530 --> 00:02:26.469 Structure, things like using read receipts strategically, 00:02:26.729 --> 00:02:30.349 or having documented CC paths. It goes beyond 00:02:30.349 --> 00:02:33.289 simple politeness. It becomes a tool for, well, 00:02:33.789 --> 00:02:36.090 professional governance. It helps prevent the 00:02:36.090 --> 00:02:39.229 legal and operational mess that uncertainty can 00:02:39.229 --> 00:02:42.210 cause. Hmm. That's an interesting framing, though 00:02:42.210 --> 00:02:45.949 I'd put it differently. Look, the intent of preventing 00:02:45.949 --> 00:02:50.240 uncertainty? Yeah, that's laudable, sure. But 00:02:50.240 --> 00:02:52.879 imposing these structural demands often creates, 00:02:52.919 --> 00:02:55.680 I think, a bigger problem, this sort of crisis 00:02:55.680 --> 00:02:59.699 of autonomy and anxiety. Email, by its very nature, 00:03:00.039 --> 00:03:02.319 lets the recipient process information when they 00:03:02.319 --> 00:03:05.719 have the time and mental space, right? But forcing 00:03:05.719 --> 00:03:08.120 a read receipt, well, it instantly turns that 00:03:08.120 --> 00:03:10.479 asynchronous freedom into a kind of synchronous 00:03:10.479 --> 00:03:13.520 duty. It forces an immediate interaction, even 00:03:13.520 --> 00:03:16.139 if it's just a click. So if someone reads a message 00:03:16.139 --> 00:03:18.159 quickly on their phone, maybe between meetings, 00:03:18.500 --> 00:03:20.759 but they can't give a thoughtful reply for hours, 00:03:21.240 --> 00:03:23.580 the system marks them as seen, maybe implying 00:03:23.580 --> 00:03:26.400 they're unresponsive. You've essentially prioritized 00:03:26.400 --> 00:03:28.939 the documentation over thoughtfulness, and that 00:03:28.939 --> 00:03:31.360 can really hurt the relationship. Well, I'm not 00:03:31.360 --> 00:03:33.840 entirely convinced by that line of reasoning, 00:03:34.139 --> 00:03:37.259 because in critical business functions, accountability 00:03:37.259 --> 00:03:40.680 has to precede autonomy. Let's tackle the read 00:03:40.680 --> 00:03:44.280 -receipt dilemma head on. PGA actually advocates 00:03:44.280 --> 00:03:46.659 for these tools precisely because they help overcome 00:03:46.659 --> 00:03:49.099 the real logistical hurdles of global business, 00:03:49.460 --> 00:03:51.699 different time zones, tech glitches, sheer volume. 00:03:52.639 --> 00:03:55.500 And look, PGE doesn't necessarily demand an instant 00:03:55.500 --> 00:03:58.419 substantive reply. It often recommends an immediate 00:03:58.419 --> 00:04:02.000 documented acknowledgement. For instance, PGE 00:04:02.000 --> 00:04:04.979 might suggest a mandatory four -hour acknowledgement 00:04:04.979 --> 00:04:07.439 for certain high -priority external messages. 00:04:07.960 --> 00:04:10.500 That manages the client's expectation transparently. 00:04:10.750 --> 00:04:14.189 the accountability is or should be mutual. Okay, 00:04:14.349 --> 00:04:16.790 that's a compelling point about managing expectations, 00:04:17.370 --> 00:04:19.910 but have you really considered the inherent power 00:04:19.910 --> 00:04:22.910 dynamic these tools often introduce? I mean, 00:04:23.230 --> 00:04:25.350 let's be honest, it's pretty rare that tracking 00:04:25.350 --> 00:04:27.949 tools are used horizontally between equals, right? 00:04:28.410 --> 00:04:30.889 They almost always flow downhill from an executive 00:04:30.889 --> 00:04:33.689 to a subordinate, or maybe from a powerful client 00:04:33.689 --> 00:04:36.449 to a service provider. My position is that this 00:04:36.449 --> 00:04:39.170 tracking often functions, or at least feels like, 00:04:39.649 --> 00:04:42.149 surveillance imposed from above. And in certain 00:04:42.149 --> 00:04:44.970 cultural contexts, Japan's relationship -focused 00:04:44.970 --> 00:04:47.610 business world comes to mind, this kind of electronic 00:04:47.610 --> 00:04:50.389 tracking can imply a deep lack of trust. That's 00:04:50.389 --> 00:04:52.589 potentially far more damaging than, say, a four 00:04:52.589 --> 00:04:55.290 -hour delay in acknowledgement. Plus, there's 00:04:55.290 --> 00:04:57.649 the technical reality. Lots of email clients 00:04:57.649 --> 00:05:00.329 now let users just disable or ignore read receipts 00:05:00.329 --> 00:05:02.949 anyway. So the documentation you're seeking might 00:05:02.949 --> 00:05:05.930 not even be reliable. That's a substantive challenge, 00:05:05.930 --> 00:05:09.009 I grant you. But I'd argue the fault there lies 00:05:09.009 --> 00:05:12.370 not in the tool itself, but maybe in the failure 00:05:12.370 --> 00:05:15.230 to set up a clear communications charter from 00:05:15.230 --> 00:05:18.730 the start. If a client expects structured confirmation, 00:05:19.089 --> 00:05:21.970 that needs to be documented upfront, agreed upon. 00:05:22.430 --> 00:05:25.009 And the cultural variance you mentioned? Well, 00:05:25.110 --> 00:05:28.209 it cuts both ways. Sure, some cultures might 00:05:28.209 --> 00:05:31.439 see tracking as disrespectful. But PGE research 00:05:31.439 --> 00:05:34.639 also points out that other cultures, think Germany 00:05:34.639 --> 00:05:37.879 perhaps, actually value the detailed, verifiable 00:05:37.879 --> 00:05:40.519 accountability that receipts provide. For them, 00:05:40.740 --> 00:05:43.360 that clarity is a form of respect. So the goal 00:05:43.360 --> 00:05:45.759 isn't to ban the tool because it could be misused 00:05:45.759 --> 00:05:47.920 or because some clients can technically bypass 00:05:47.920 --> 00:05:51.019 it. It's about using it intentionally. A policy 00:05:51.019 --> 00:05:53.480 -driven, maybe even server -side confirmation, 00:05:53.899 --> 00:05:56.220 when it's agreed upon, gives you that necessary 00:05:56.220 --> 00:05:59.240 legal trail. Mm -hmm. We agree. Clarity is vital. 00:05:59.449 --> 00:06:01.790 But it's the burden imposed by these mandatory 00:06:01.790 --> 00:06:04.350 acknowledgments that creates friction. And that 00:06:04.350 --> 00:06:07.410 friction just gets multiplied, sometimes exponentially 00:06:07.410 --> 00:06:10.230 when we talk about volume. Which brings us, I 00:06:10.230 --> 00:06:12.870 think logically, to the whole reply -all epidemic. 00:06:13.610 --> 00:06:16.269 If one receipt adds friction, just imagine the 00:06:16.269 --> 00:06:18.529 cognitive load when a dozen people hit reply 00:06:18.529 --> 00:06:21.430 -all to a chain they barely need to be on. It's 00:06:21.430 --> 00:06:24.129 a massive source of inbox overload, right? All 00:06:24.129 --> 00:06:27.009 those gratuitous thanks or got -it messages distracting 00:06:27.009 --> 00:06:29.660 people, and who enforces the limits? Especially 00:06:29.660 --> 00:06:31.740 when things are moving fast, people are firing 00:06:31.740 --> 00:06:34.540 off replies from their phones. Okay, I wouldn't 00:06:34.540 --> 00:06:38.160 call Reply All an epidemic. I see it as a necessary 00:06:38.160 --> 00:06:41.439 component of transparency and frankly shared 00:06:41.439 --> 00:06:44.660 organizational memory. When decisions get made 00:06:44.660 --> 00:06:47.939 or scope changes or timeline shift, everyone 00:06:47.939 --> 00:06:50.879 who was initially in that loop needs to stay 00:06:50.879 --> 00:06:53.699 informed. The problem isn't the function itself. 00:06:54.100 --> 00:06:57.819 It's usually poor list management or just, well, 00:06:58.040 --> 00:07:01.300 poor professional judgment. And PGE specifically 00:07:01.300 --> 00:07:04.319 addresses this with governance, like a rule stating 00:07:04.319 --> 00:07:07.839 personal acknowledgements, got it, thanks, go 00:07:07.839 --> 00:07:11.240 only to the sender. Reply all is reserved strictly 00:07:11.240 --> 00:07:14.180 for information that actually changes the group's 00:07:14.180 --> 00:07:16.759 action plan or requires input from everyone. 00:07:17.459 --> 00:07:19.879 Structure, again, is what prevents the chaos. 00:07:20.300 --> 00:07:23.259 I'm sorry, but I just don't buy that the solution 00:07:23.259 --> 00:07:26.480 is simply better judgment. Because that judgment 00:07:26.480 --> 00:07:28.879 call happens under pressure. We're talking about 00:07:28.879 --> 00:07:31.699 people getting hundreds of emails a day. The 00:07:31.699 --> 00:07:34.100 mental effort needed to constantly filter and 00:07:34.100 --> 00:07:36.519 apply that kind of structural rule in real time 00:07:36.519 --> 00:07:39.439 is huge. And what happens when a conversation 00:07:39.439 --> 00:07:41.980 just goes off the rails? You know, when internal 00:07:41.980 --> 00:07:44.399 politics start playing out on the thread? The 00:07:44.399 --> 00:07:46.459 only way to really stop that isn't some abstract 00:07:46.459 --> 00:07:48.860 policy. It's usually a real -time intervention 00:07:48.860 --> 00:07:51.500 from someone, maybe a leader, who has to disrupt 00:07:51.500 --> 00:07:53.579 the chain and redirect it, saying something like, 00:07:53.720 --> 00:07:55.800 OK, let's take this offline, meeting invite to 00:07:55.800 --> 00:07:58.459 follow. The flexible approach sees the tool failing 00:07:58.459 --> 00:08:00.860 and steps in relationally, rather than just hoping 00:08:00.860 --> 00:08:04.300 a policy holds up. Well, I'd argue that redirection 00:08:04.300 --> 00:08:07.720 is a structural move, reinforcing the need for 00:08:07.720 --> 00:08:10.779 active management. And active management relies 00:08:10.779 --> 00:08:14.399 on visibility. Which brings us right to the ethics, 00:08:14.639 --> 00:08:19.120 the mechanics of CC versus BCC. Another area 00:08:19.120 --> 00:08:21.639 where transparency and structure kind of clash 00:08:21.639 --> 00:08:25.199 with potential political dynamics. Now, I staunchly 00:08:25.199 --> 00:08:29.100 defend CC as often a necessary means of professional 00:08:29.100 --> 00:08:32.379 inclusion and shared accountability. If I'm working 00:08:32.379 --> 00:08:35.299 on a major client project, CCing my supervisor 00:08:35.299 --> 00:08:37.720 ensures we have shared organizational knowledge. 00:08:38.100 --> 00:08:40.299 It prevents finger pointing later if the scope 00:08:40.299 --> 00:08:44.269 shifts or something goes wrong. And BCC, look, 00:08:44.309 --> 00:08:47.610 it also has legitimate structured uses, protecting 00:08:47.610 --> 00:08:51.370 privacy and mass emails, or maybe including administrative 00:08:51.370 --> 00:08:53.570 or legal staff who need the record but shouldn't 00:08:53.570 --> 00:08:56.210 be part of the active dialogue. I see the logic, 00:08:56.330 --> 00:09:00.090 but let me offer a different angle on CC. While 00:09:00.090 --> 00:09:03.789 you frame CCing a supervisor as shared accountability, 00:09:04.250 --> 00:09:06.929 let's be real. It's often perceived by the main 00:09:06.929 --> 00:09:10.250 recipient as an escalation. As soon as the boss 00:09:10.250 --> 00:09:12.929 is copied, the whole dynamic of the conversation 00:09:12.929 --> 00:09:16.110 shifts, doesn't it? It becomes less about solving 00:09:16.110 --> 00:09:19.169 a problem together and maybe more about documenting 00:09:19.169 --> 00:09:22.350 conflict or even showing off performance. That's 00:09:22.350 --> 00:09:25.529 the adversarial side of transparency. And as 00:09:25.529 --> 00:09:29.370 for BC, I'd argue its legitimate uses are frequently 00:09:29.370 --> 00:09:32.250 overshadowed by the, uh, more insidious ones. 00:09:32.710 --> 00:09:35.590 It's often used precisely to create hidden paper 00:09:35.590 --> 00:09:38.399 trails or for covert surveillance. If I'm having 00:09:38.399 --> 00:09:41.000 a serious business discussion, the basic principle 00:09:41.000 --> 00:09:43.419 of professional discourse suggests I should know 00:09:43.419 --> 00:09:46.840 who else is listening in. BCC kind of violates 00:09:46.840 --> 00:09:49.179 that needed presumption of openness. The argument 00:09:49.179 --> 00:09:52.000 that CC is inherently political sort of implies 00:09:52.000 --> 00:09:54.960 a lack of professional maturity within the organization, 00:09:55.139 --> 00:09:58.840 doesn't it? Proper PGE training emphasizes using 00:09:58.840 --> 00:10:01.539 these tools to include people who genuinely need 00:10:01.539 --> 00:10:04.539 the information to do their jobs, not as weapons. 00:10:04.940 --> 00:10:07.559 And we have to acknowledge the global complexity 00:10:07.559 --> 00:10:10.580 here. Adrian Barker's framework highlights massive 00:10:10.580 --> 00:10:13.159 cultural differences. A Western colleague might 00:10:13.159 --> 00:10:16.240 feel cc'd unnecessarily, see it as noise. But 00:10:16.240 --> 00:10:18.879 in a heavily regulated industry or certain cultures, 00:10:19.240 --> 00:10:21.559 it might be absolutely required for compliance 00:10:21.559 --> 00:10:24.399 or audit trails. The structure serves a necessary 00:10:24.399 --> 00:10:27.379 legal or operational purpose. We can't just throw 00:10:27.379 --> 00:10:29.919 out the tool because some individuals use it 00:10:29.919 --> 00:10:33.419 poorly or politically. Intent is crucial. I agree. 00:10:33.559 --> 00:10:36.240 But technology seems to be outpacing our best 00:10:36.240 --> 00:10:38.419 intentions sometimes, which leads us to maybe 00:10:38.419 --> 00:10:40.940 our final point, the relentless pressure that 00:10:40.940 --> 00:10:43.320 comes with mobile technology and what that means 00:10:43.320 --> 00:10:45.659 for etiquette moving forward. The simple fact 00:10:45.659 --> 00:10:48.519 that email is always there in our pockets, it 00:10:48.519 --> 00:10:51.279 encourages quick, sometimes unthoughtful responses. 00:10:51.700 --> 00:10:54.480 And critically, it sets this often unrealistic 00:10:54.480 --> 00:10:57.659 expectation among clients for immediate 24 -7 00:10:57.659 --> 00:11:00.120 replies, no matter the time zone or actual urgency. 00:11:00.360 --> 00:11:03.370 That's true. That pressure is real. But technology 00:11:03.370 --> 00:11:06.070 also gives us sophisticated countermeasures that 00:11:06.070 --> 00:11:08.490 can actually reinforce structured etiquette. 00:11:08.909 --> 00:11:11.529 Think about delayed send features. They let us 00:11:11.529 --> 00:11:13.429 write a response when it's convenient, maybe 00:11:13.429 --> 00:11:15.769 late at night, but schedule it to arrive during 00:11:15.769 --> 00:11:18.570 the recipient's actual business hours. That shows 00:11:18.570 --> 00:11:21.009 cultural sensitivity, respect for work -life 00:11:21.009 --> 00:11:23.850 balance, things explicitly recommended by PGE. 00:11:24.269 --> 00:11:27.629 Plus, PGE also emphasizes structuring the content 00:11:27.629 --> 00:11:31.129 itself. Front load the key action item for mobile 00:11:31.129 --> 00:11:34.070 readers who are just scanning. Use autoresponders 00:11:34.070 --> 00:11:36.210 that clearly state your response timeframes. 00:11:36.669 --> 00:11:39.309 Boundaries need structure to actually work. Sure, 00:11:39.490 --> 00:11:42.889 the tools exist, but I do question their psychological 00:11:42.889 --> 00:11:45.889 effectiveness sometimes. Once a client knows 00:11:45.889 --> 00:11:48.509 you can technically receive their urgent message 00:11:48.509 --> 00:11:52.279 anytime, Those structural boundaries, the autoresponder, 00:11:52.620 --> 00:11:55.080 the delayed send, can easily start to feel like 00:11:55.080 --> 00:11:58.120 bureaucratic hurdles rather than genuine professional 00:11:58.120 --> 00:12:00.980 courtesy. The underlying pressure for synchronous 00:12:00.980 --> 00:12:03.659 availability, even when the tech is asynchronous, 00:12:04.100 --> 00:12:06.779 kind of persists. And furthermore, we're seeing 00:12:06.779 --> 00:12:09.600 advanced email tracking software now, way beyond 00:12:09.600 --> 00:12:12.340 simple read receipts that can monitor how long 00:12:12.340 --> 00:12:15.419 an email was viewed, where links clicked. This 00:12:15.419 --> 00:12:18.419 pushes the debate from basic accountability into, 00:12:18.519 --> 00:12:21.360 potentially, detailed behavioral surveillance. 00:12:21.779 --> 00:12:24.379 And if that's not governed by autonomy and clear 00:12:24.379 --> 00:12:27.059 consent, it severely strains the relationship. 00:12:27.659 --> 00:12:30.100 You've hit on a crucial point there with advanced 00:12:30.100 --> 00:12:33.019 tracking. And that's precisely why PGE would 00:12:33.019 --> 00:12:35.720 focus on making any such tracking completely 00:12:35.720 --> 00:12:39.500 transparent. If there's a genuine legal or contractual 00:12:39.500 --> 00:12:42.460 need to know when information was consumed, then 00:12:42.460 --> 00:12:45.600 all parties must explicitly consent to a structural 00:12:45.600 --> 00:12:48.299 agreement defining exactly what's tracked and 00:12:48.299 --> 00:12:51.240 why. The choice isn't really between chaos and 00:12:51.240 --> 00:12:54.240 total rigidity. It's between unpredictable assumptions 00:12:54.240 --> 00:12:57.000 and transparent, agreed -upon documentation. 00:12:57.480 --> 00:12:59.799 Predictability, which comes from structure, I 00:12:59.799 --> 00:13:02.059 believe is the bedrock of strong international 00:13:02.059 --> 00:13:04.860 business relationships. And I still maintain 00:13:04.860 --> 00:13:07.100 that the bedrock of any sustainable business 00:13:07.100 --> 00:13:10.159 relationship is professional trust and autonomy. 00:13:10.679 --> 00:13:12.919 Flexibility allows communication to actually 00:13:12.919 --> 00:13:16.240 adapt to the messy reality of global hierarchies, 00:13:16.580 --> 00:13:19.500 specific client needs, cultural nuances. Rigid 00:13:19.500 --> 00:13:21.759 rules, I think, too often fail when they meet 00:13:21.759 --> 00:13:24.179 reality, leading to workarounds, frustration 00:13:24.179 --> 00:13:27.019 and resentment. Well, this discretion certainly 00:13:27.019 --> 00:13:30.799 illuminates that whether one leans towards structure 00:13:30.799 --> 00:13:34.820 or flexibility, The ultimate goal really has 00:13:34.820 --> 00:13:37.740 to be intentionality. We need to move beyond 00:13:37.740 --> 00:13:40.899 just defaulting to old habits or whatever the 00:13:40.899 --> 00:13:44.539 tech allows and really apply thoughtful judgment 00:13:44.539 --> 00:13:47.779 to every single professional interaction we have 00:13:47.779 --> 00:13:51.100 via email. I wholeheartedly agree. Our exploration 00:13:51.100 --> 00:13:53.500 today really underscores that every email we 00:13:53.500 --> 00:13:56.570 send is a strategic choice. Whether someone opts 00:13:56.570 --> 00:13:59.610 for the, let's say, high -formality path suggested 00:13:59.610 --> 00:14:03.169 by PGE or a more flexible, autonomy -first approach, 00:14:03.669 --> 00:14:05.970 that choice needs to be conscious. It needs to 00:14:05.970 --> 00:14:08.490 reflect the specific relationship, the operational 00:14:08.490 --> 00:14:11.070 context. Hopefully, this has given our listeners 00:14:11.070 --> 00:14:13.309 something to think about regarding their own 00:14:13.309 --> 00:14:16.230 communication habits and maybe the unseen pressures 00:14:16.230 --> 00:14:18.330 those habits place on colleagues and clients.