WEBVTT 00:00:00.540 --> 00:00:02.600 You know, if you are listening to this right 00:00:02.600 --> 00:00:04.700 now, there is like a really good chance you're 00:00:04.700 --> 00:00:07.440 a retail executive. And if that's true, I mean, 00:00:07.559 --> 00:00:11.800 you have absolutely lived this specific nightmare. 00:00:11.900 --> 00:00:14.560 Oh, yeah. The classic rollout nightmare. Right. 00:00:15.140 --> 00:00:17.960 So you and your leadership team, you just spent, 00:00:17.960 --> 00:00:20.199 what, three months locked in a conference room. 00:00:20.480 --> 00:00:24.260 You hammered out this brilliant, just bulletproof. 00:00:24.440 --> 00:00:27.719 corporate strategy. And the slide deck is completely 00:00:27.719 --> 00:00:30.920 flawless. Flawless. The rollout plan is meticulous. 00:00:31.300 --> 00:00:33.560 You hit send on that massive communication out 00:00:33.560 --> 00:00:35.579 to all the stores and you're feeling like you 00:00:35.579 --> 00:00:37.399 just solved retail, you know. You're popping 00:00:37.399 --> 00:00:40.899 the champagne. Exactly. But then, like a month 00:00:40.899 --> 00:00:43.640 later, you walk onto an actual store floor and 00:00:43.640 --> 00:00:46.479 it is as if that memo never existed. Yeah, the 00:00:46.479 --> 00:00:48.719 displays are wrong. They're wrong. The Associates 00:00:48.719 --> 00:00:51.000 are using the old greeting, and your brilliant 00:00:51.000 --> 00:00:53.259 strategy is just nowhere to be found. It's the 00:00:53.259 --> 00:00:55.200 universal retail heartbreak, really. I mean, 00:00:55.240 --> 00:00:57.880 you look around, you see the strategy just hasn't 00:00:57.880 --> 00:01:01.000 translated to frontline execution, and the immediate 00:01:01.000 --> 00:01:03.200 executive reaction is usually just frustration. 00:01:03.380 --> 00:01:06.099 Yeah, for sure. You know, the assumption is that 00:01:06.099 --> 00:01:07.620 the Associates just aren't paying attention, 00:01:07.959 --> 00:01:10.079 or worse, they just don't care. Right. You wonder, 00:01:10.159 --> 00:01:12.400 like, did they even read it? Are they just actively 00:01:12.400 --> 00:01:14.900 ignoring us at headquarters? Well, according 00:01:14.900 --> 00:01:17.000 to a really compelling white paper we're diving 00:01:17.000 --> 00:01:20.480 into today from Multimedia Plus, which is titled, 00:01:20.900 --> 00:01:23.819 Why Associates Stop Trusting Corporate Communication, 00:01:24.680 --> 00:01:27.620 the answer is yes, they are ignoring you. It's 00:01:27.620 --> 00:01:30.620 entirely your fault. Yeah. OK, let's unpack this 00:01:30.620 --> 00:01:33.019 because the central thesis here is just a massive 00:01:33.019 --> 00:01:35.780 paradigm shift. It really is. It totally shifts 00:01:35.780 --> 00:01:38.280 the blame from the floor back to the corporate 00:01:38.280 --> 00:01:41.379 office. Because the core idea in this source 00:01:41.379 --> 00:01:44.480 is that associates do not ignore corporate messages 00:01:44.480 --> 00:01:47.420 because they're inherently resistant to information 00:01:47.420 --> 00:01:50.299 or, you know, just stubborn. Right. They ignore 00:01:50.299 --> 00:01:52.219 them because their lived experience on the floor 00:01:52.219 --> 00:01:54.219 has taught them that the information coming from 00:01:54.219 --> 00:01:57.540 corporate is likely irrelevant. or outdated or 00:01:57.540 --> 00:01:59.459 completely disconnected from their day -to -day 00:01:59.459 --> 00:02:02.299 reality, which means this breakdown isn't happening 00:02:02.299 --> 00:02:06.000 because of like one single poorly worded memo. 00:02:06.760 --> 00:02:10.259 It's a slow erosion, right? Trust is being chipped 00:02:10.259 --> 00:02:12.919 away piece by piece over months or even years. 00:02:13.139 --> 00:02:15.319 Yeah, it's a cumulative effect. We have to look 00:02:15.319 --> 00:02:18.240 at what every single... piece of communication 00:02:18.240 --> 00:02:21.599 actually represents to the person receiving it. 00:02:21.879 --> 00:02:23.639 The white paper points out that every time corporate 00:02:23.639 --> 00:02:26.259 sends a message to an associate, it carries this 00:02:26.259 --> 00:02:28.879 implied promise. An implied promise. Exactly. 00:02:29.259 --> 00:02:31.219 And that promise is simply, this information 00:02:31.219 --> 00:02:33.539 matters to you and will help you do your job. 00:02:33.759 --> 00:02:36.560 But if I'm an executive, I'm thinking I don't 00:02:36.560 --> 00:02:39.620 have the bandwidth. to curate 50 different versions 00:02:39.620 --> 00:02:41.719 of one update just to make sure it's perfectly 00:02:41.719 --> 00:02:43.939 tailored. Like, I have a business to run. I need 00:02:43.939 --> 00:02:46.300 to get the message out today to everyone. And 00:02:46.300 --> 00:02:48.199 I just have to trust them to filter out what 00:02:48.199 --> 00:02:50.780 they need. And that is the exact mindset that 00:02:50.780 --> 00:02:53.639 breaks the implied promise. Wow. OK. When you 00:02:53.639 --> 00:02:56.000 force the associate to be the filter, they start 00:02:56.000 --> 00:02:58.039 building this defensive layer of skepticism. 00:02:58.719 --> 00:03:01.319 The source provides some painfully specific examples 00:03:01.319 --> 00:03:03.439 of how this plays out in the real world. Oh, 00:03:03.500 --> 00:03:05.780 yeah. Those examples were rough. Right. So think 00:03:05.780 --> 00:03:08.900 about an associate working in, like, a small 00:03:08.900 --> 00:03:12.039 standard format store in a mall. Suddenly, they 00:03:12.039 --> 00:03:16.479 receive a massive, highly detailed visual merchandising 00:03:16.479 --> 00:03:19.460 update that only applies to a three -story flagship 00:03:19.460 --> 00:03:22.039 location. Totally useless to them. Completely. 00:03:22.759 --> 00:03:25.680 Or consider a really sensitive HR policy change 00:03:25.680 --> 00:03:27.919 that is strictly meant for store managers, but 00:03:27.919 --> 00:03:31.099 oops, it gets blasted out to the entire part 00:03:31.099 --> 00:03:34.180 -time seasonal workforce by mistake. Or a regional 00:03:34.180 --> 00:03:37.039 promotion meant entirely for the West Coast showing 00:03:37.039 --> 00:03:39.520 up in the inbox of an associate working in Boston. 00:03:39.919 --> 00:03:42.379 It's just infuriating. Honestly, thinking about 00:03:42.379 --> 00:03:44.120 it, it's exactly like being trapped in one of 00:03:44.120 --> 00:03:47.180 those massive corporate reply -all email chains. 00:03:47.219 --> 00:03:49.319 Oh, the worst. That has absolutely nothing to 00:03:49.319 --> 00:03:51.000 do with your department. At first, you read them, 00:03:51.020 --> 00:03:52.759 right? Trying to figure out if you missed something 00:03:52.759 --> 00:03:55.840 important. But by the 15th email about a jammed 00:03:55.840 --> 00:03:58.379 printer on the third floor, you just start auto 00:03:58.379 --> 00:04:00.449 -deleting everything without even gl - at the 00:04:00.449 --> 00:04:02.750 subject line. You have to. Yeah, you literally 00:04:02.750 --> 00:04:05.969 train yourself to ignore the noise, just to survive 00:04:05.969 --> 00:04:08.930 the workday. And what's fascinating here is what 00:04:08.930 --> 00:04:11.509 that pattern signals to the front line. It creates 00:04:11.509 --> 00:04:14.990 this massive us versus them divide. Oh, that's 00:04:14.990 --> 00:04:17.730 absolutely. To the associate, a constant stream 00:04:17.730 --> 00:04:20.370 of irrelevant messages says, loud and clear, 00:04:20.730 --> 00:04:23.129 that the corporate team has zero understanding 00:04:23.129 --> 00:04:26.290 of their actual role, their specific location, 00:04:26.290 --> 00:04:28.810 or just the physical realities of standing on 00:04:28.810 --> 00:04:31.589 a sales for eight hours. It adds friction to 00:04:31.589 --> 00:04:33.870 their day. Right. Every irrelevant message means 00:04:33.870 --> 00:04:35.970 they have to stop serving a customer, open the 00:04:35.970 --> 00:04:38.170 alert, read it, try to interpret it, realize 00:04:38.170 --> 00:04:40.769 it's completely useless, and then try to regain 00:04:40.769 --> 00:04:43.910 their focus. So the bleeding stops with precision. 00:04:44.269 --> 00:04:46.509 Like the baseline requirement has to be absolute 00:04:46.509 --> 00:04:49.290 surgical targeting by role, location, department, 00:04:49.389 --> 00:04:52.310 and language. But I'll push back on the reality 00:04:52.310 --> 00:04:54.689 of this. OK, go ahead. I've seen what happens 00:04:54.689 --> 00:04:56.910 when corporate realizes their messages are being 00:04:56.910 --> 00:05:00.079 ignored. Their first instinct is rarely to get 00:05:00.079 --> 00:05:02.759 more precise. Their first instant is usually 00:05:02.759 --> 00:05:05.519 to turn up the volume, to say the exact same 00:05:05.519 --> 00:05:07.980 thing, just louder and more often across way 00:05:07.980 --> 00:05:10.160 more channels. Yeah, the old, if they didn't 00:05:10.160 --> 00:05:12.300 hear it the first time, let's just yell it, strategy. 00:05:12.439 --> 00:05:14.639 Exactly. If lack of relevance is the first way 00:05:14.639 --> 00:05:16.959 corporate loses trust, well, this is the second. 00:05:17.680 --> 00:05:20.279 They try to fix a quality problem with quantity. 00:05:20.540 --> 00:05:22.439 But hold on, doesn't retail actually require 00:05:22.439 --> 00:05:25.160 repetition? Like, you can't just launch a new 00:05:25.160 --> 00:05:27.439 strategic priority, say, hey, here is the new 00:05:27.439 --> 00:05:30.620 customer greeting once in January and expect 00:05:30.620 --> 00:05:32.879 it to hold up in November. You have to keep brand 00:05:32.879 --> 00:05:35.399 standards top of mind. Well, the source makes 00:05:35.399 --> 00:05:37.620 a vital distinction to address that exact point. 00:05:38.259 --> 00:05:40.600 Reinforcement and duplication are not the same 00:05:40.600 --> 00:05:43.319 thing. OK, break that down. Reinforcement is 00:05:43.319 --> 00:05:46.779 a business necessity. Duplication is just noise. 00:05:47.839 --> 00:05:50.139 Associates instantly recognize when a message 00:05:50.139 --> 00:05:52.100 has simply been recycled. Oh, for sure. They 00:05:52.100 --> 00:05:54.939 can spot it a mile away. Right. If you send the 00:05:54.939 --> 00:05:57.360 exact same announcement, using the same corporate 00:05:57.360 --> 00:05:59.620 speak with no new guidance, and you don't even 00:05:59.620 --> 00:06:01.319 acknowledge that they've seen this before, you're 00:06:01.319 --> 00:06:03.819 offering zero new value, it just makes headquarters 00:06:03.819 --> 00:06:06.139 look totally disconnected and desperate. The 00:06:06.139 --> 00:06:08.839 way paper highlights a compounding problem here, 00:06:08.879 --> 00:06:11.399 that just sounds like an absolute nightmare for 00:06:11.399 --> 00:06:14.339 the store level. It happens when multiple corporate 00:06:14.339 --> 00:06:17.259 silos communicate about the exact same initiative, 00:06:17.319 --> 00:06:19.639 but they do it completely independently of one 00:06:19.639 --> 00:06:22.100 another. Oh, it is rampant in large organizations. 00:06:22.819 --> 00:06:24.939 So operations sends out a directive about a new 00:06:24.939 --> 00:06:28.459 product launch. Then, like two days later, learning 00:06:28.459 --> 00:06:30.519 and development sends out a mandatory training 00:06:30.519 --> 00:06:33.120 module about the same launch. Right. And then 00:06:33.120 --> 00:06:35.579 marketing sends out a promotional memo detailing 00:06:35.579 --> 00:06:38.459 the signage for that launch. So technically the 00:06:38.459 --> 00:06:40.579 information might all be accurate, but to the 00:06:40.579 --> 00:06:43.579 associate, it doesn't feel like one cohesive 00:06:43.579 --> 00:06:46.199 strategy at all. It feels like three separate, 00:06:46.620 --> 00:06:48.779 totally overwhelming demands hitting them from 00:06:48.779 --> 00:06:50.720 different departments. Which is why the rule 00:06:50.720 --> 00:06:53.779 has to be that repetition only works if it adds 00:06:53.779 --> 00:06:57.079 value. A follow -up cannot just be a carbon copy. 00:06:57.259 --> 00:06:59.939 It has to have something fresh. Exactly. It must 00:06:59.939 --> 00:07:01.970 include something new. Give them a practical 00:07:01.970 --> 00:07:04.550 example of the new behavior working in a real 00:07:04.550 --> 00:07:06.569 store. Give them a new selling technique. Give 00:07:06.569 --> 00:07:09.110 them answers to frequently asked questions that 00:07:09.110 --> 00:07:11.050 have bubbled up since the initial announcement. 00:07:11.430 --> 00:07:13.410 You have to respect their time enough to give 00:07:13.410 --> 00:07:16.029 them an actual reason to open that second message. 00:07:16.189 --> 00:07:19.230 Yeah. And this is where the source mentions that 00:07:19.230 --> 00:07:22.149 technology platforms like Insight are stepping 00:07:22.149 --> 00:07:25.500 in to sort of centralize this chaos. Wait, let's 00:07:25.500 --> 00:07:27.519 clarify that for the listener really quick. When 00:07:27.519 --> 00:07:29.459 we talk about a platform like Insight, what does 00:07:29.459 --> 00:07:31.560 that actually look like for the frontline worker? 00:07:31.779 --> 00:07:33.879 Like, are we talking about a portal on the back 00:07:33.879 --> 00:07:37.699 office computer or an app on their phone? Think 00:07:37.699 --> 00:07:40.360 of it as a unified, branded environment. It's 00:07:40.360 --> 00:07:43.360 usually accessed via a mobile device or a store 00:07:43.360 --> 00:07:45.720 tablet that the associate carries with them right 00:07:45.720 --> 00:07:48.610 on the floor. Oh, okay. So it's right there with 00:07:48.610 --> 00:07:50.889 them. Right. Instead of operations, marketing, 00:07:51.069 --> 00:07:53.230 and L &D all bombarding the store through these 00:07:53.230 --> 00:07:55.629 different methods, a platform like Insight acts 00:07:55.629 --> 00:07:58.149 as a single gateway. It brings task management, 00:07:58.569 --> 00:08:01.129 multimedia training, and corporate communications 00:08:01.129 --> 00:08:04.750 all into one interface. Nice. So instead of three 00:08:04.750 --> 00:08:08.310 disconnected emails, the associate gets one cohesive, 00:08:08.610 --> 00:08:11.040 purposeful brief from the brand. Okay, that makes 00:08:11.040 --> 00:08:13.259 visualizing the solution much easier. So let's 00:08:13.259 --> 00:08:16.060 say a retail executive gets this all right. The 00:08:16.060 --> 00:08:18.980 message is perfectly targeted, it's highly relevant, 00:08:19.319 --> 00:08:21.480 and it's delivered through a unified platform. 00:08:21.920 --> 00:08:25.160 Problem solved. Wow. Not necessarily, because 00:08:25.160 --> 00:08:27.259 we have to talk about the tyranny of bad timing. 00:08:27.920 --> 00:08:30.360 I mean, even a perfectly crafted message is going 00:08:30.360 --> 00:08:33.440 to fail entirely if it hits the store at the 00:08:33.440 --> 00:08:35.990 absolute wrong moment. This is a huge blind spot 00:08:35.990 --> 00:08:38.429 for headquarters because corporate environments 00:08:38.429 --> 00:08:41.370 and store environments operate on entirely different 00:08:41.370 --> 00:08:43.889 biological clocks, so to speak. That's a great 00:08:43.889 --> 00:08:45.690 way to put it. Corporate teams are sitting at 00:08:45.690 --> 00:08:48.309 desks, right? They're actively monitoring screens, 00:08:48.350 --> 00:08:50.970 waiting for updates and emails. Store associates 00:08:50.970 --> 00:08:53.149 are in constant motion. They're managing foot 00:08:53.149 --> 00:08:56.190 traffic, unloading pallets, de -escalating customer 00:08:56.190 --> 00:08:59.029 complaints, and executing physical tasks. The 00:08:59.029 --> 00:09:01.250 examples on the white paper are just wind -sinducing 00:09:01.250 --> 00:09:04.590 for anyone who has ever worked a floor set. Imagine 00:09:04.590 --> 00:09:07.330 a detailed visual merchandising update arriving 00:09:07.330 --> 00:09:09.610 at the store after the team has already spent 00:09:09.610 --> 00:09:12.169 six hours completing the display based on the 00:09:12.169 --> 00:09:14.870 old instructions. You've just guaranteed hours 00:09:14.870 --> 00:09:17.730 of physical rework. The associates aren't going 00:09:17.730 --> 00:09:20.149 to praise corporate for the update. They are 00:09:20.149 --> 00:09:23.309 going to curse them for being out of touch. Seriously? 00:09:23.639 --> 00:09:27.620 Or consider a massive, highly detailed training 00:09:27.620 --> 00:09:30.279 program dropped into the system right in the 00:09:30.279 --> 00:09:33.399 middle of a high traffic holiday weekend. You 00:09:33.399 --> 00:09:36.179 are putting the associate in an impossible position. 00:09:36.240 --> 00:09:38.879 Yeah, total lose -lose. They either ignore the 00:09:38.879 --> 00:09:41.179 training to help the customer or they ignore 00:09:41.179 --> 00:09:43.460 the customer to complete the training. Timing 00:09:43.460 --> 00:09:46.460 communicates respect. When headquarters schedules 00:09:46.460 --> 00:09:48.940 their communication around the operational realities 00:09:48.940 --> 00:09:51.720 of the store, like the peak traffic periods, 00:09:52.240 --> 00:09:53.940 the opening and closing routines, the shipment 00:09:53.940 --> 00:09:56.179 delivery windows, they demonstrate that they 00:09:56.179 --> 00:09:58.360 actually understand. what it takes to run a store. 00:09:58.620 --> 00:10:00.700 And it's not just when the message arrives. It's 00:10:00.700 --> 00:10:03.200 the chaotic web of where it lives. Without a 00:10:03.200 --> 00:10:05.500 centralized platform, the fragmentation of channels 00:10:05.500 --> 00:10:08.360 is just staggering. Oh, it's everywhere. An associate 00:10:08.360 --> 00:10:10.559 might get information through a company email, 00:10:11.139 --> 00:10:14.320 a secure messaging app on a zebra device, a dusty 00:10:14.320 --> 00:10:16.919 printed binder sitting in the break room, and 00:10:16.919 --> 00:10:19.360 whatever their shift manager half remembers during 00:10:19.360 --> 00:10:21.960 a morning huddle. So what does this all mean 00:10:21.960 --> 00:10:25.340 for the frontline worker? Well, it means they 00:10:25.340 --> 00:10:27.799 are forced to play detective. just to do their 00:10:27.799 --> 00:10:31.240 jobs. They have to waste their shift cross -referencing 00:10:31.240 --> 00:10:35.019 information. Does the email sent yesterday supersede 00:10:35.019 --> 00:10:37.899 the printed binder from last week? Did the store 00:10:37.899 --> 00:10:40.139 manager get an even newer version on a conference 00:10:40.139 --> 00:10:43.379 call? Is this update a suggestion? Or is it a 00:10:43.379 --> 00:10:45.779 mandatory compliance task? And that detective 00:10:45.779 --> 00:10:48.220 work severely weakens operational confidence. 00:10:48.700 --> 00:10:50.580 Associates shouldn't have to launch an investigation 00:10:50.580 --> 00:10:52.740 into a message's accuracy before they can act 00:10:52.740 --> 00:10:55.100 on it. If they have to guess which source is 00:10:55.100 --> 00:10:57.700 the real source of truth, execution is just always 00:10:57.700 --> 00:10:59.639 going to be inconsistent. Let's keep building 00:10:59.639 --> 00:11:01.940 this out. Let's assume you fixed the timing, 00:11:02.399 --> 00:11:04.559 eliminated the fragmented channels, and targeted 00:11:04.559 --> 00:11:06.679 the message perfectly. OK. You still have to 00:11:06.679 --> 00:11:08.799 ensure the associate actually understands the 00:11:08.799 --> 00:11:11.840 underlying why. of the task, and corporate has 00:11:11.840 --> 00:11:14.960 to measure the right outcomes. Yes, because communication 00:11:14.960 --> 00:11:17.840 without context doesn't feel like guidance. It 00:11:17.840 --> 00:11:19.799 feels like a command. Complete this training 00:11:19.799 --> 00:11:22.860 module. Move this display three feet to the left. 00:11:23.240 --> 00:11:26.039 Start saying this specific phrase to every customer. 00:11:26.399 --> 00:11:28.929 It is entirely transactional. And when you strip 00:11:28.929 --> 00:11:31.490 away the context, they might know what to do, 00:11:31.509 --> 00:11:34.190 but they have absolutely no idea why it matters. 00:11:35.049 --> 00:11:37.350 Research actually shows that associates remain 00:11:37.350 --> 00:11:40.730 engaged when they understand how their specific 00:11:40.730 --> 00:11:43.809 localized tasks connect to the broader purpose 00:11:43.809 --> 00:11:45.809 of the brand. That makes total sense. The white 00:11:45.809 --> 00:11:47.929 paper suggests every piece of communication must 00:11:47.929 --> 00:11:50.570 explicitly answer four questions. Why does this 00:11:50.570 --> 00:11:52.929 matter? What do I need to do? When does it need 00:11:52.929 --> 00:11:55.210 to happen? And where can I get help if something 00:11:55.210 --> 00:11:57.799 goes wrong? If you don't give them the why. You 00:11:57.799 --> 00:11:59.980 cannot be surprised when they give you the absolute 00:11:59.980 --> 00:12:03.320 bare minimum on the what. But that brings up 00:12:03.320 --> 00:12:07.179 a massive friction point for executives. Measurement. 00:12:07.440 --> 00:12:09.299 How does corporate traditionally prove to the 00:12:09.299 --> 00:12:11.919 board that our rollout was successful? They use 00:12:11.919 --> 00:12:14.279 read receipts and completion rates. The classic 00:12:14.279 --> 00:12:16.720 compliance metrics. Here's where it gets really 00:12:16.720 --> 00:12:19.720 interesting though. Relying on read receipts 00:12:19.720 --> 00:12:22.519 to gauge actual understanding is completely flawed. 00:12:23.259 --> 00:12:25.419 Think about every time you download a new software 00:12:25.419 --> 00:12:28.440 update. You scroll to the absolute bottom of 00:12:28.440 --> 00:12:30.940 a 40 page terms and conditions, pop up in two 00:12:30.940 --> 00:12:33.600 seconds, and click I agree without reading a 00:12:33.600 --> 00:12:36.440 single syllable. We all do it. Exactly. The system 00:12:36.440 --> 00:12:39.460 logged your completion rate at 100%. But you 00:12:39.460 --> 00:12:41.379 couldn't tell me a single thing you just agreed 00:12:41.379 --> 00:12:44.080 to. This raises an important question for any 00:12:44.080 --> 00:12:46.259 executive listening. What are you actually trying 00:12:46.259 --> 00:12:49.620 to measure? Read receipts only monitor compliance. 00:12:49.919 --> 00:12:52.139 They prove someone clicked a button. They do 00:12:52.139 --> 00:12:54.590 not prove comprehension. But if I'm an executive, 00:12:54.789 --> 00:12:56.649 I have to report something up the chain, right? 00:12:57.289 --> 00:12:59.710 If I abandon completion rates, what metrics am 00:12:59.710 --> 00:13:01.789 I supposed to use to prove my team is actually 00:13:01.789 --> 00:13:03.889 doing their job? Well, you don't abandon metrics. 00:13:03.970 --> 00:13:07.049 You evolve them. The mindset has to shift from, 00:13:07.389 --> 00:13:10.929 did associates click complete? To, did the communication 00:13:10.929 --> 00:13:13.769 actually work? The source details how a platform 00:13:13.769 --> 00:13:16.350 like Insight uses short, integrated knowledge 00:13:16.350 --> 00:13:18.950 checks and question -level analytics. This turns 00:13:18.950 --> 00:13:21.129 measurement into a discovery tool rather than 00:13:21.129 --> 00:13:23.049 a surveillance tool. Walk us through how that 00:13:23.049 --> 00:13:25.570 changes the dynamic. Okay, so if you push a new 00:13:25.570 --> 00:13:28.389 policy and your analytics show that 60 % of your 00:13:28.389 --> 00:13:31.250 stores are failing a specific question about 00:13:31.250 --> 00:13:33.570 the return window, that doesn't mean you have 00:13:33.570 --> 00:13:36.070 thousands of bad associates. Right. It means 00:13:36.070 --> 00:13:39.029 your corporate communication was confusing or 00:13:39.029 --> 00:13:42.230 maybe the phrasing was ambiguous. Real -time 00:13:42.230 --> 00:13:45.389 analytics allow corporate to identify weak content 00:13:45.389 --> 00:13:48.350 and proactively fix the message rather than waiting 00:13:48.350 --> 00:13:50.590 three months and punishing the store managers 00:13:50.590 --> 00:13:53.950 for low compliance. It changes the entire relationship 00:13:53.950 --> 00:13:56.610 from a dictatorship to a dialogue. You are basically 00:13:56.610 --> 00:13:58.929 auditing your own communication strategy in real 00:13:58.929 --> 00:14:01.090 time. Okay, we are rounding the corner here. 00:14:01.190 --> 00:14:03.529 Let's bring this all together. How does a retail 00:14:03.529 --> 00:14:05.710 executive take these insights and immediately 00:14:05.710 --> 00:14:07.730 apply them? Because as the source makes very 00:14:07.730 --> 00:14:10.370 clear, you cannot fix broken trust with just 00:14:10.370 --> 00:14:12.850 another corporate memo about improving communication. 00:14:13.230 --> 00:14:15.889 No, you definitely can't. The trust has to be 00:14:15.889 --> 00:14:18.090 rebuilt through the experience of the communication 00:14:18.090 --> 00:14:20.789 itself. The white paper provides an executive 00:14:20.789 --> 00:14:23.779 playbook with eight standards. But rather than 00:14:23.779 --> 00:14:26.259 just reading a list, let's look at the operational 00:14:26.259 --> 00:14:28.879 friction of actually doing this. Because implementing 00:14:28.879 --> 00:14:31.899 these standards requires real structural changes 00:14:31.899 --> 00:14:34.100 at headquarters. OK, let's group them. The first 00:14:34.100 --> 00:14:36.159 bucket is what we could call the precision engine. 00:14:36.559 --> 00:14:39.340 This includes standard one, target every message. 00:14:39.659 --> 00:14:43.059 Standard three, make priorities obvious. And 00:14:43.059 --> 00:14:45.779 standard four, design for the front line. Design 00:14:45.779 --> 00:14:47.659 for the front line means abandoning the corporate 00:14:47.659 --> 00:14:50.820 PDF entirely. Good riddance. Right. You have 00:14:50.820 --> 00:14:53.620 to use concise language, mobile friendly formats, 00:14:53.820 --> 00:14:56.899 and short video examples. You are designing for 00:14:56.899 --> 00:14:59.600 someone who has maybe three uninterrupted minutes 00:14:59.600 --> 00:15:01.879 between customer interactions, not someone sitting 00:15:01.879 --> 00:15:05.000 at a desk with a cup of coffee. Yeah. And making 00:15:05.000 --> 00:15:06.799 priorities obvious means the associate should 00:15:06.799 --> 00:15:09.279 know instantly if an alert is just informational, 00:15:09.480 --> 00:15:12.139 highly recommended, or an urgent compliance issue. 00:15:12.399 --> 00:15:14.480 But the real friction at headquarters happens 00:15:14.480 --> 00:15:17.480 in the second bucket, which we'll call the empathy 00:15:17.480 --> 00:15:21.460 loop. This includes Standard 2, coordinate the 00:15:21.460 --> 00:15:24.580 corporate calendar, Standard 5, respect store 00:15:24.580 --> 00:15:28.340 timing, Standard 6, add value with follow -ups, 00:15:29.000 --> 00:15:32.570 and Standard 8, close the feedback loop. Coordinating 00:15:32.570 --> 00:15:34.889 the corporate calendar is incredibly difficult 00:15:34.889 --> 00:15:37.669 in a silent business. Oh, I bet. It requires 00:15:37.669 --> 00:15:40.929 operations, marketing, and L &D to actually sit 00:15:40.929 --> 00:15:44.389 down, look at a unified calendar, and negotiate 00:15:44.389 --> 00:15:46.629 their rollouts so they don't collide on the store 00:15:46.629 --> 00:15:49.929 floor. It forces corporate departments to compromise 00:15:49.929 --> 00:15:52.639 for the sake of the associate. I can just imagine 00:15:52.639 --> 00:15:54.820 the turf wars in those meetings, you know, like 00:15:54.820 --> 00:15:56.879 my promotional rollout is more important than 00:15:56.879 --> 00:15:59.100 your compliance training. But if they don't fight 00:15:59.100 --> 00:16:01.840 that battle at headquarters, they're just exporting 00:16:01.840 --> 00:16:04.100 that chaos to the 19 -year -old associate on 00:16:04.100 --> 00:16:06.600 the floor. Exactly. And the most challenging 00:16:06.600 --> 00:16:09.000 standard for corporate egos is closing the feedback 00:16:09.000 --> 00:16:11.700 loop. When frontline associates use these platforms 00:16:11.700 --> 00:16:14.220 to render questions or point out that a new display 00:16:14.220 --> 00:16:16.580 physically doesn't fit in a standard store layout, 00:16:17.080 --> 00:16:19.340 you have to acknowledge their input. You can't 00:16:19.340 --> 00:16:21.529 just ignore it. No, and more importantly, you 00:16:21.529 --> 00:16:24.809 must communicate what you changed as a result 00:16:24.809 --> 00:16:27.350 of their feedback. That is the only way to prove 00:16:27.350 --> 00:16:29.669 this isn't just a one -way surveillance system. 00:16:29.809 --> 00:16:32.370 Which brings us back to why relying on a unified 00:16:32.370 --> 00:16:35.649 technology platform is so critical. Executing 00:16:35.649 --> 00:16:38.409 that level of coordination, targeting, and feedback 00:16:38.409 --> 00:16:41.690 manually across thousands of stores is virtually 00:16:41.690 --> 00:16:44.409 impossible. You need an environment that handles 00:16:44.409 --> 00:16:46.909 the logistics so executives can actually focus 00:16:46.909 --> 00:16:49.429 on the strategy. It allows an executive to turn 00:16:49.450 --> 00:16:53.049 chaotic corporate noise into frontline operational 00:16:53.049 --> 00:16:55.509 confidence. So to summarize our journey today, 00:16:55.950 --> 00:16:58.429 corporate communication is not and should never 00:16:58.429 --> 00:17:01.330 be measured by the sheer volume of messages sent 00:17:01.330 --> 00:17:04.130 from headquarters. It is measured entirely by 00:17:04.130 --> 00:17:06.150 whether your frontline associates believe those 00:17:06.150 --> 00:17:08.250 messages are actually worth receiving. And to 00:17:08.250 --> 00:17:10.309 the retail executives listening, just remember 00:17:10.309 --> 00:17:12.829 that your frontline teams are the literal face 00:17:12.829 --> 00:17:15.410 of your brand. When execution suffers because 00:17:15.410 --> 00:17:18.329 of disconnected, noisy communication, it is the 00:17:18.329 --> 00:17:20.369 customer experience that takes the direct hit. 00:17:20.690 --> 00:17:23.250 The stakes are incredibly high. We're going to 00:17:23.250 --> 00:17:24.950 leave you with a final thought today, something 00:17:24.950 --> 00:17:27.309 to really chew on during your next leadership 00:17:27.309 --> 00:17:30.029 meeting. We've spent this entire time talking 00:17:30.029 --> 00:17:33.230 about how bad communication causes associates 00:17:33.230 --> 00:17:37.130 to ignore corporate. But what if the opposite 00:17:37.130 --> 00:17:40.009 is also true? Is this a good point? Look at your 00:17:40.009 --> 00:17:42.430 absolute highest performing stores right now. 00:17:42.589 --> 00:17:45.529 The ones just crushing their sales goals and 00:17:45.529 --> 00:17:48.799 customer satisfaction metrics. If you really 00:17:48.799 --> 00:17:51.559 look closely at how they operate, is it possible 00:17:51.559 --> 00:17:54.000 that your best store managers are succeeding 00:17:54.000 --> 00:17:56.940 precisely because they are acting as a shield? 00:17:57.680 --> 00:18:00.019 What if they are intentionally filtering out 00:18:00.019 --> 00:18:02.779 and ignoring 80 % of your corporate communication 00:18:02.779 --> 00:18:05.359 just to give their associates the peace and quiet 00:18:05.359 --> 00:18:07.700 they need to actually sell? And if your most 00:18:07.700 --> 00:18:09.640 successful locations are the ones ignoring you 00:18:09.640 --> 00:18:11.579 the most, what does that say about the true value 00:18:11.579 --> 00:18:14.200 of your communication strategy? That is a terrifying 00:18:14.200 --> 00:18:17.000 question for an executive to ask. It might be 00:18:17.000 --> 00:18:19.210 the most necessary. That's our deep dive for 00:18:19.210 --> 00:18:20.849 today. Thanks for joining us and we'll catch 00:18:20.849 --> 00:18:21.369 you next time.