WEBVTT 00:00:00.000 --> 00:00:02.299 Okay, so if you're a retail executive listening 00:00:02.299 --> 00:00:04.379 to this, maybe you've tried to roll out video 00:00:04.379 --> 00:00:08.099 training on the sales floor. And maybe, maybe 00:00:08.099 --> 00:00:11.000 it haven't gone quite as planned. Yeah, more 00:00:11.000 --> 00:00:14.039 than maybe, I'd guess. It's a really common frustration. 00:00:14.590 --> 00:00:17.190 You know video works, especially for your younger 00:00:17.190 --> 00:00:19.769 associates, your Gen Z staff. Right, they expect 00:00:19.769 --> 00:00:22.550 it. But then you launch and it's all buffering, 00:00:22.629 --> 00:00:25.769 freezing, inconsistent playback. Store managers 00:00:25.769 --> 00:00:27.969 are tearing their hair out. And here's where 00:00:27.969 --> 00:00:30.989 it gets, well, predictable maybe. You put in 00:00:30.989 --> 00:00:33.670 the support ticket, describe the poor playback, 00:00:33.990 --> 00:00:36.109 and the training vendor almost always points 00:00:36.109 --> 00:00:38.429 the finger back at you. It must be your store 00:00:38.429 --> 00:00:40.729 network. We hear that all the time. Exactly, 00:00:40.850 --> 00:00:43.399 that's the standard reply. But look, this is 00:00:43.399 --> 00:00:45.340 the core idea we need to tackle in this deep 00:00:45.340 --> 00:00:47.399 dive today. If this is happening everywhere, 00:00:47.859 --> 00:00:50.140 if maybe 5 % of your stores are struggling, but 00:00:50.140 --> 00:00:53.079 you hear the same story from execs at other retail 00:00:53.079 --> 00:00:55.619 chains, then it's not just your network. Then 00:00:55.619 --> 00:00:57.740 the vendor is selling something that doesn't 00:00:57.740 --> 00:00:59.520 actually work for the environment it's meant 00:00:59.520 --> 00:01:02.380 for, like a half -baked solution. Precisely. 00:01:02.600 --> 00:01:04.879 They're pushing a real -time streaming model 00:01:04.879 --> 00:01:07.540 that frankly just isn't built for the realities 00:01:07.540 --> 00:01:10.180 of a secure retail store network. It's fundamentally 00:01:10.180 --> 00:01:13.129 incompatible at scale. So our mission today is 00:01:13.129 --> 00:01:15.310 to get past that blame game. We're looking at 00:01:15.310 --> 00:01:18.030 the sources, diving into why this technical conflict 00:01:18.030 --> 00:01:21.450 happens between what everyone expects from video 00:01:21.450 --> 00:01:24.650 now and, you know, the constraints of these older 00:01:24.650 --> 00:01:27.450 secure retail networks. And crucially, we're 00:01:27.450 --> 00:01:30.069 looking at the how. How do you actually fix this 00:01:30.069 --> 00:01:32.469 delivery problem securely and at scale? All right. 00:01:32.489 --> 00:01:35.390 Let's start with why video is so critical. Section 00:01:35.390 --> 00:01:38.359 one. The video imperative. I mean, it's just 00:01:38.359 --> 00:01:39.840 one of the best training tools we have, isn't 00:01:39.840 --> 00:01:43.000 it? Visual, engaging, fast. Absolutely. The data 00:01:43.000 --> 00:01:45.180 backs it up consistently. People learn and retain 00:01:45.180 --> 00:01:47.140 information better, especially complex stuff. 00:01:47.239 --> 00:01:49.859 When they see it, static text modules, they just 00:01:49.859 --> 00:01:51.659 don't cut it anymore for a lot of tasks. And 00:01:51.659 --> 00:01:53.879 the expectation level, particularly from younger 00:01:53.879 --> 00:01:55.780 staff. Oh, completely different. If you grew 00:01:55.780 --> 00:01:58.719 up on YouTube, TikTok, Instagram, video isn't 00:01:58.719 --> 00:02:01.040 just nice to have for learning. It's baseline. 00:02:01.400 --> 00:02:03.780 It's how information gets consumed and remembered. 00:02:03.980 --> 00:02:06.260 We see that, right? When you show a process or 00:02:06.260 --> 00:02:09.680 a product feature on video, comprehension, retention, 00:02:10.460 --> 00:02:12.939 it just goes way up compared to reading a manual. 00:02:13.099 --> 00:02:15.520 Huge difference. And that consistency matters 00:02:15.520 --> 00:02:17.659 so much when you've got thousands of people across 00:02:17.659 --> 00:02:20.039 hundreds of stores needing the same message. 00:02:20.199 --> 00:02:22.180 And the weird thing is making the video content 00:02:22.180 --> 00:02:24.960 itself, that's gotten way easier. you know, with 00:02:24.960 --> 00:02:27.759 AI tools helping out. Yeah, production's faster, 00:02:28.060 --> 00:02:30.860 cheaper. You can create really targeted, even 00:02:30.860 --> 00:02:33.479 store -specific little videos incredibly quickly 00:02:33.479 --> 00:02:36.060 now, like a quick update on a new display setup. 00:02:36.879 --> 00:02:39.780 An hour, maybe? So you can make amazing content. 00:02:39.879 --> 00:02:42.650 Sure. But then you hit the wall. That's the disconnect. 00:02:43.069 --> 00:02:45.189 The expensive disconnect. You've got great content. 00:02:45.449 --> 00:02:47.810 But the delivery mechanism, getting it reliably 00:02:47.810 --> 00:02:50.430 onto those tablets, the handhelds, the POS systems 00:02:50.430 --> 00:02:52.990 associates actually use. It fails. It buffers. 00:02:52.990 --> 00:02:55.430 It stalls. What does the associate do? They close 00:02:55.430 --> 00:02:57.490 it. Of course they do. Who wouldn't? And that 00:02:57.490 --> 00:02:59.830 missed opportunity. It's not just about training. 00:03:00.110 --> 00:03:02.590 It's inconsistent messaging. It's mistakes on 00:03:02.590 --> 00:03:05.050 the floor. It's a team that starts seeing training 00:03:05.050 --> 00:03:07.710 as this annoying, broken thing. OK. That leads 00:03:07.710 --> 00:03:09.610 straight into the technical side. Section two. 00:03:09.919 --> 00:03:13.879 The barriers. Why is it so hard? Why can't a 00:03:13.879 --> 00:03:16.840 huge retailer stream a simple five -minute video 00:03:16.840 --> 00:03:20.919 smoothly? It feels like it should work. It feels 00:03:20.919 --> 00:03:22.319 like it should, but you have to understand the 00:03:22.319 --> 00:03:25.039 environment. These stores, especially devices 00:03:25.039 --> 00:03:27.060 connected to payment systems, they must be secure. 00:03:27.500 --> 00:03:29.500 That's where PCI compliance comes in. Right, 00:03:29.699 --> 00:03:32.919 PCI DSS. The payment card industry data security 00:03:32.919 --> 00:03:35.219 standard, non -negotiable if you're taking credit 00:03:35.219 --> 00:03:37.879 cards. Absolutely. And that standard dictates 00:03:37.879 --> 00:03:40.340 a lot about the network environment. High security, 00:03:40.900 --> 00:03:44.000 encrypted connections, specifically HTTPS, strict 00:03:44.000 --> 00:03:47.120 access controls. All vital for protecting customer 00:03:47.120 --> 00:03:49.530 financial data. Okay, essential for security. 00:03:49.949 --> 00:03:52.229 But what does that do to video streaming? Well, 00:03:52.229 --> 00:03:54.849 it basically creates a direct conflict. Those 00:03:54.849 --> 00:03:57.689 very security measures, particularly HTTPS encryption, 00:03:58.250 --> 00:04:00.689 they kind of dismantle the efficiency needed 00:04:00.689 --> 00:04:03.430 for smooth, high -volume video streaming across 00:04:03.430 --> 00:04:05.729 a shared network. Let's get granular there, because 00:04:05.729 --> 00:04:07.270 this feels like the crux of it. You mentioned 00:04:07.270 --> 00:04:10.569 caching earlier. What is caching and why is HTTPS 00:04:10.569 --> 00:04:14.199 the enemy here? Okay, so caching... Simply put, 00:04:14.340 --> 00:04:16.379 it's like keeping a temporary copy of frequently 00:04:16.379 --> 00:04:18.899 accessed stuff, maybe an image on a webpage, 00:04:19.600 --> 00:04:22.560 or, crucially, chunks of a video closer to the 00:04:22.560 --> 00:04:24.959 user, maybe on a local server, maybe on the device 00:04:24.959 --> 00:04:27.100 itself. So if 10 people want the same thing, 00:04:27.180 --> 00:04:28.959 they grab the local copy instead of everyone 00:04:28.959 --> 00:04:31.540 going back to the main source. Makes sense. Faster, 00:04:31.680 --> 00:04:35.670 less network traffic. Exactly. But HTTPS... Well, 00:04:35.910 --> 00:04:38.430 its job is security through encryption. It creates 00:04:38.430 --> 00:04:40.810 a private secure tunnel between one user and 00:04:40.810 --> 00:04:44.009 the server. That connection is unique, ephemeral. 00:04:44.430 --> 00:04:46.850 It's not designed to be shared or reused easily. 00:04:47.569 --> 00:04:50.170 Ah. So that secure tunnel, vital for protecting 00:04:50.170 --> 00:04:52.490 data, prevents that efficient local copying the 00:04:52.490 --> 00:04:54.290 caching of the video stream across the store. 00:04:54.410 --> 00:04:56.709 Pretty much. Because each connection is private 00:04:56.709 --> 00:04:59.009 and encrypted end -to -end for that specific 00:04:59.009 --> 00:05:01.550 user, you can't easily have a shared cache that 00:05:01.550 --> 00:05:04.420 everyone pulls from. So. Let's picture this. 00:05:04.579 --> 00:05:07.019 Morning rush. 20 associates need to watch the 00:05:07.019 --> 00:05:08.819 new five -minute product video before hitting 00:05:08.819 --> 00:05:11.920 the floor because of HTTPS and the lack of effect 00:05:11.920 --> 00:05:15.100 of caching. Each of those 20 devices is trying 00:05:15.100 --> 00:05:18.660 to pull down its own separate real -time encrypted 00:05:18.660 --> 00:05:21.660 stream from the corporate server, all at the 00:05:21.660 --> 00:05:25.639 same time, all over the same shared secure store 00:05:25.639 --> 00:05:28.540 Wi -Fi or wired network. Which just completely 00:05:28.540 --> 00:05:31.259 swamps the network. Instant bandwidth saturation. 00:05:32.029 --> 00:05:35.629 buffering, errors, total frustration. And you 00:05:35.629 --> 00:05:38.250 see this pattern consistently. Which brings us 00:05:38.250 --> 00:05:40.550 back to that executive talking point. The vendor 00:05:40.550 --> 00:05:43.189 blaming the network. Right. When maybe only 5 00:05:43.189 --> 00:05:46.129 % of stores report a major issue, it's easy for 00:05:46.129 --> 00:05:48.329 corporate to think, OK, it's just those few locations. 00:05:48.550 --> 00:05:51.209 But if the pattern is industry -wide. Then it's 00:05:51.209 --> 00:05:53.829 not the store's fault. It's the model. The real 00:05:53.829 --> 00:05:56.069 -time streaming model is the half -baked solution 00:05:56.069 --> 00:05:59.170 for this specific environment. Exactly. Standard 00:05:59.170 --> 00:06:00.990 streaming technology wasn't designed for the 00:06:00.990 --> 00:06:03.829 constraints of a mass -scale PCI -compliant retail 00:06:03.829 --> 00:06:06.670 operation. It fundamentally slashes. But hang 00:06:06.670 --> 00:06:08.750 on, quick challenge. Why not just throw more 00:06:08.750 --> 00:06:10.649 bandwidth at the stores? Internet pipes are cheaper 00:06:10.649 --> 00:06:12.610 now, aren't they? Couldn't that solve it? That's 00:06:12.610 --> 00:06:14.389 a really common question. And honestly, it's 00:06:14.389 --> 00:06:16.750 where a lot of money gets wasted. Because it's 00:06:16.750 --> 00:06:19.529 not just about the total size of the pipe. It's 00:06:19.529 --> 00:06:22.170 about the delivery architecture within that secure 00:06:22.170 --> 00:06:24.569 environment. OK. You could double, even triple. 00:06:24.750 --> 00:06:27.949 the store's internet speed. But if every single 00:06:27.949 --> 00:06:31.730 video playback still requires a separate, non 00:06:31.730 --> 00:06:35.550 -cached, encrypted HTTPS download happening in 00:06:35.550 --> 00:06:38.230 real time. You just hit the same bottleneck again 00:06:38.230 --> 00:06:40.649 as soon as enough people try to watch concurrently. 00:06:40.810 --> 00:06:43.189 You haven't fixed the underlying architectural 00:06:43.189 --> 00:06:46.050 conflict. Precisely. You can't fix an architecture 00:06:46.050 --> 00:06:48.430 problem just by making the pipe bigger. It's 00:06:48.430 --> 00:06:50.569 like trying to fix traffic jams by only widening 00:06:50.569 --> 00:06:52.829 the highway entrance ramp doesn't solve the merging 00:06:52.829 --> 00:06:54.699 problem. That really refra - frames the whole 00:06:54.699 --> 00:06:57.240 issue. It's not about speed or content quality. 00:06:57.680 --> 00:07:00.339 It's the delivery method itself that's broken 00:07:00.339 --> 00:07:02.399 for retail. Which means we have to fundamentally 00:07:02.399 --> 00:07:05.339 rethink how this video training gets onto those 00:07:05.339 --> 00:07:07.779 secure devices. We need to move away from real 00:07:07.779 --> 00:07:09.899 time streaming. Okay, so that leads us to section 00:07:09.899 --> 00:07:13.259 three, rethinking delivery. What is the fix, 00:07:13.600 --> 00:07:15.959 according to the sources? Well, the core finding 00:07:15.959 --> 00:07:18.970 is shifting the model entirely. Our sources point 00:07:18.970 --> 00:07:21.490 to solutions like the INCITE platform as a really 00:07:21.490 --> 00:07:23.730 good example of how this is done right. It hinges 00:07:23.730 --> 00:07:26.470 on local storage. Local storage, meaning the 00:07:26.470 --> 00:07:28.490 video file actually lives on the device itself. 00:07:28.750 --> 00:07:31.470 Yes, exactly. The playback happens directly from 00:07:31.470 --> 00:07:34.529 the device's memory. The beauty of this is it 00:07:34.529 --> 00:07:36.970 completely bypasses the bottleneck of trying 00:07:36.970 --> 00:07:39.610 to stream over that congested secure network 00:07:39.610 --> 00:07:42.149 in real time. When the associate hits play... 00:07:42.149 --> 00:07:44.189 It's instant, because the content is already 00:07:44.189 --> 00:07:47.480 there, ready to go. No reliance on the live network 00:07:47.480 --> 00:07:50.360 connection for playback. Okay, immediate executive 00:07:50.360 --> 00:07:53.620 questions pop into my head. One, security. Isn't 00:07:53.620 --> 00:07:55.660 storing potentially sensitive internal training 00:07:55.660 --> 00:07:59.959 videos locally a risk? Two, cost. Do we suddenly 00:07:59.959 --> 00:08:03.060 need super expensive devices with massive storage? 00:08:03.259 --> 00:08:05.279 Both fair and critical points. The security piece 00:08:05.279 --> 00:08:07.459 is paramount. This isn't just downloading an 00:08:07.459 --> 00:08:10.300 MP4 file. The architecture relies on a patented 00:08:10.300 --> 00:08:13.040 end -to -end encrypted delivery and storage process. 00:08:13.199 --> 00:08:15.459 How does that work? How does the video get there 00:08:15.459 --> 00:08:17.699 securely without causing problems during business 00:08:17.699 --> 00:08:20.300 hours? It's designed around the store's operational 00:08:20.300 --> 00:08:23.540 rhythm. The content download happens securely 00:08:23.540 --> 00:08:26.740 overnight during non -peak hours when the network 00:08:26.740 --> 00:08:30.420 is quietest. Ah, OK. And crucially, the system 00:08:30.420 --> 00:08:33.679 uses controlled bandwidth throttling. It sips 00:08:33.679 --> 00:08:36.440 the bandwidth it needs very carefully, ensuring 00:08:36.440 --> 00:08:39.120 it never interferes with critical overnight processes 00:08:39.120 --> 00:08:42.919 like POS updates, inventory syncs, anything like 00:08:42.919 --> 00:08:45.179 that. It's designed to be invisible operationally. 00:08:45.539 --> 00:08:48.039 So the next morning, associates clock in, pick 00:08:48.039 --> 00:08:50.379 up their device, and the necessary training videos 00:08:50.379 --> 00:08:53.320 are just there, encrypted, secure, and ready. 00:08:53.620 --> 00:08:56.340 That's the goal. Instant access, zero buffering. 00:08:56.409 --> 00:08:58.750 And this approach scales really well, too. For 00:08:58.750 --> 00:09:01.070 bigger stores than department stores, big box 00:09:01.070 --> 00:09:03.210 retailers, you might have hundreds of devices. 00:09:03.470 --> 00:09:05.129 Yeah, how does that work? You're not downloading 00:09:05.129 --> 00:09:07.570 to hundreds individually overnight, surely? No, 00:09:07.610 --> 00:09:09.570 for larger environments, the architecture uses 00:09:09.570 --> 00:09:12.570 localized content servers. Think of them as secure 00:09:12.570 --> 00:09:15.350 on -site mini -hubs or nodes. That node takes 00:09:15.350 --> 00:09:17.889 the single secure overnight download from corporate. 00:09:18.330 --> 00:09:20.490 Then, it efficiently and securely distributes 00:09:20.490 --> 00:09:22.809 the content to all the registered devices within 00:09:22.809 --> 00:09:25.769 that store using the local network. Ah, so the 00:09:25.769 --> 00:09:27.549 distribution inside the store doesn't need the 00:09:27.549 --> 00:09:30.009 main internet pipe. It's local traffic. Exactly. 00:09:30.190 --> 00:09:32.490 It drastically reduces the wide area network 00:09:32.490 --> 00:09:35.830 strain. That single node manages local delivery. 00:09:36.009 --> 00:09:38.909 Again, the whole process, the download to the 00:09:38.909 --> 00:09:41.549 node, the distribution to devices, the storage, 00:09:41.649 --> 00:09:44.090 it's all handled through that patented secure 00:09:44.090 --> 00:09:47.330 encrypted method. Meaning you maintain full PCI 00:09:47.330 --> 00:09:49.429 compliance throughout. You're not compromising 00:09:49.429 --> 00:09:52.230 security for performance. Correct. You get both. 00:09:52.710 --> 00:09:54.850 You eliminate the performance headache of streaming 00:09:54.850 --> 00:09:57.129 while adhering to the strict security standards. 00:09:57.169 --> 00:09:59.309 You're no longer forced to choose. This really 00:09:59.309 --> 00:10:01.250 does change the game. Training shifts from being 00:10:01.250 --> 00:10:04.470 this unreliable, often frustrating task to just 00:10:04.470 --> 00:10:07.139 being a dependent utility, like electricity. 00:10:07.440 --> 00:10:09.460 It's just there. It works when you need it. Which 00:10:09.460 --> 00:10:11.960 brings us to the impact on workflow and results. 00:10:12.539 --> 00:10:15.299 Section four. If playback is instant and reliable, 00:10:15.679 --> 00:10:17.779 how does that change things on the floor? It 00:10:17.779 --> 00:10:20.279 enables something really powerful. IBC training 00:10:20.279 --> 00:10:23.159 in between customer training. IBC training. I 00:10:23.159 --> 00:10:25.500 like that. Explain that. It means learning can 00:10:25.500 --> 00:10:28.220 happen in those small natural gaps in the retail 00:10:28.220 --> 00:10:31.500 day. Maybe an associate has 90 seconds while 00:10:31.500 --> 00:10:34.460 waiting for a customer query response or two 00:10:34.460 --> 00:10:36.440 minutes while restocking a shelf. Instead of 00:10:36.440 --> 00:10:38.600 needing a dedicated off -the -floor half -hour 00:10:38.600 --> 00:10:41.980 block. Exactly. They can pull up a quick targeted 00:10:41.980 --> 00:10:44.639 micro learning video, maybe a product feature 00:10:44.639 --> 00:10:47.399 refresh, a quick compliance reminder right there 00:10:47.399 --> 00:10:49.960 in the moment on the device they already have 00:10:49.960 --> 00:10:52.659 in their hand. It weaves training into the workflow. 00:10:52.840 --> 00:10:55.799 Making it much less disruptive. Far less. And 00:10:55.799 --> 00:10:57.840 the user experience is designed to match what 00:10:57.840 --> 00:11:00.659 they're used to on their phones. The platform 00:11:00.659 --> 00:11:02.799 remembers exactly where they left off in a video. 00:11:03.059 --> 00:11:05.320 Oh, like the Netflix prompt? Continue watching. 00:11:05.700 --> 00:11:08.159 Precisely that. If they get interrupted mid -video, 00:11:08.500 --> 00:11:11.100 or even switch devices, it picks up right where 00:11:11.100 --> 00:11:14.559 they stopped. That seamlessness is huge for reducing 00:11:14.559 --> 00:11:16.940 friction. People are far more likely to finish 00:11:16.940 --> 00:11:19.519 the training. Which drives completion rates up. 00:11:19.600 --> 00:11:22.460 Dramatically. We see completion rates jump because 00:11:22.460 --> 00:11:24.840 associates aren't abandoning videos out of frustration. 00:11:25.179 --> 00:11:28.200 They can dip in and out easily. So what are the 00:11:28.200 --> 00:11:30.740 bottom line business results retailers see when 00:11:30.740 --> 00:11:34.039 they adopt this kind of secure local delivery 00:11:34.039 --> 00:11:37.259 model? OK, a few key things consistently emerge. 00:11:38.019 --> 00:11:41.019 First. Much higher associate engagement with 00:11:41.019 --> 00:11:43.960 training materials. That leads directly to more 00:11:43.960 --> 00:11:46.580 consistent product knowledge and procedural execution 00:11:46.580 --> 00:11:50.039 across all stores. Consistency is gold in retail. 00:11:50.440 --> 00:11:53.279 Makes sense. What else? Second, a massive drop 00:11:53.279 --> 00:11:55.340 in support tickets coming from the field about 00:11:55.340 --> 00:11:58.460 training access. Sore managers get that time 00:11:58.460 --> 00:12:00.879 back. They're not troubleshooting network issues 00:12:00.879 --> 00:12:03.559 or video players anymore. And presumably you 00:12:03.559 --> 00:12:05.679 don't have to dumb down the video quality anymore. 00:12:05.840 --> 00:12:08.879 Not at all. Because playback is local, it's completely 00:12:08.879 --> 00:12:10.820 unaffected by network conditions or how many 00:12:10.820 --> 00:12:13.120 other people are watching. You can deliver crisp, 00:12:13.500 --> 00:12:16.139 clear, high -definition, even 4K training content 00:12:16.139 --> 00:12:19.159 if you want. The experience is premium. It really 00:12:19.159 --> 00:12:21.179 does sound like it transforms training from a 00:12:21.179 --> 00:12:24.620 headache into just... a reliable tool. It empowers 00:12:24.620 --> 00:12:26.840 the workforce, giving them the information they 00:12:26.840 --> 00:12:29.279 need exactly when they need it without any technical 00:12:29.279 --> 00:12:31.580 drama. It becomes part of the daily rhythm accessible 00:12:31.580 --> 00:12:34.519 and actually helpful. Okay, wrapping this up. 00:12:35.220 --> 00:12:38.899 The core takeaway seems crystal clear. Retailers, 00:12:39.240 --> 00:12:41.700 you do not have to choose between effective high 00:12:41.700 --> 00:12:44.679 quality video training and the absolute necessity 00:12:44.679 --> 00:12:47.379 of network security. The solution isn't about 00:12:47.519 --> 00:12:50.500 incrementally faster streaming, it's an architectural 00:12:50.500 --> 00:12:53.659 shift, moving away from that fragile, real -time 00:12:53.659 --> 00:12:56.559 model. For its secure, encrypted, local storage 00:12:56.559 --> 00:12:58.679 and playback. It's fundamentally changing how 00:12:58.679 --> 00:13:00.720 the video gets there. Right. It's like upgrading 00:13:00.720 --> 00:13:02.740 from, I don't know, dial -up internet to having 00:13:02.740 --> 00:13:04.940 the file already downloaded on your hard drive. 00:13:05.480 --> 00:13:08.090 Instant access. And this isn't just about training 00:13:08.090 --> 00:13:10.470 videos, is it? It feels bigger. It really is. 00:13:10.610 --> 00:13:13.029 It's about enabling a more modern way for retail 00:13:13.029 --> 00:13:15.929 organizations to communicate with, update, and 00:13:15.929 --> 00:13:18.629 empower their frontline teams consistently and 00:13:18.629 --> 00:13:21.470 reliably. It makes the network work for the store 00:13:21.470 --> 00:13:24.669 operations, not against them. OK, so final provocative 00:13:24.669 --> 00:13:26.330 thought for everyone listening, especially those 00:13:26.330 --> 00:13:29.149 retail leaders. We know reliable, seamless video 00:13:29.149 --> 00:13:31.870 is basically table stakes for today's associates 00:13:31.870 --> 00:13:33.970 and certainly for tomorrow's leaders you want 00:13:33.970 --> 00:13:36.230 to attract and retain. It's their expectation. 00:13:36.399 --> 00:13:39.139 built from their consumer tech experiences. So 00:13:39.139 --> 00:13:42.309 the question to ponder is this. As you're planning 00:13:42.309 --> 00:13:45.330 your next tech refresh, maybe new POS systems, 00:13:45.490 --> 00:13:48.090 new handheld network upgrades, are you only thinking 00:13:48.090 --> 00:13:51.169 about transaction speed? Or are you also building 00:13:51.169 --> 00:13:53.990 in the architectural foundation, the device memory, 00:13:54.230 --> 00:13:56.690 the secure local delivery infrastructure needed 00:13:56.690 --> 00:13:58.750 to finally make high impact communication and 00:13:58.750 --> 00:14:01.049 training consistent? Because if you keep reinforcing 00:14:01.049 --> 00:14:03.649 the old incompatible architecture, you're potentially 00:14:03.649 --> 00:14:05.950 locking yourself into another cycle of frustration 00:14:05.950 --> 00:14:08.169 and disengagement for the very people who will 00:14:08.169 --> 00:14:10.490 be leading your business in the future. Investing 00:14:10.490 --> 00:14:13.649 in that delivery architecture today? Well, that's 00:14:13.649 --> 00:14:14.289 building for tomorrow.