WEBVTT

1
00:00:04.200 --> 00:00:06.960
<v Speaker 1>Helping leaders motivate their people to a higher level of

2
00:00:07.000 --> 00:00:11.119
<v Speaker 1>performance through strong human relations, team building, and goal achieving.

3
00:00:11.560 --> 00:00:14.960
<v Speaker 1>This is the seven minute Leadership Podcast with your host

4
00:00:15.279 --> 00:00:16.879
<v Speaker 1>Paul Fellovaledo.

5
00:00:21.280 --> 00:00:24.960
<v Speaker 2>Hello everyone, and welcome to this seven minute leadership podcast.

6
00:00:25.000 --> 00:00:28.440
<v Speaker 2>It's episode four oh four, and let me ask you

7
00:00:28.559 --> 00:00:32.840
<v Speaker 2>a quick question. What happens to your business, your team,

8
00:00:33.159 --> 00:00:36.640
<v Speaker 2>or your day when the Internet goes out? What if

9
00:00:36.719 --> 00:00:40.320
<v Speaker 2>the network is down? What if your dispatch software crashes

10
00:00:41.320 --> 00:00:45.200
<v Speaker 2>or your payment system stops responding. What if your scheduling

11
00:00:45.240 --> 00:00:50.520
<v Speaker 2>tools disappear or your cloud storage locks you out. Now

12
00:00:50.560 --> 00:00:54.280
<v Speaker 2>here's the real question. Are you ready for your next

13
00:00:54.560 --> 00:01:01.079
<v Speaker 2>tech failure? Technology runs everything today, from communication to payroll,

14
00:01:01.759 --> 00:01:05.719
<v Speaker 2>from reporting to real time operations, but we're so used

15
00:01:05.760 --> 00:01:08.920
<v Speaker 2>to it working that we forget one hard truth. Every

16
00:01:09.000 --> 00:01:13.719
<v Speaker 2>system will eventually fail, maybe for ten minutes, maybe for

17
00:01:13.799 --> 00:01:17.920
<v Speaker 2>ten hours, or maybe for ten days, but it will happen,

18
00:01:18.000 --> 00:01:21.560
<v Speaker 2>and when it does, it won't be convenient. So this

19
00:01:21.680 --> 00:01:25.959
<v Speaker 2>episode is not about doom and gloom. It's about leadership readiness.

20
00:01:26.079 --> 00:01:31.040
<v Speaker 2>It's about having a plan before the blinking cursor disappears

21
00:01:31.599 --> 00:01:36.599
<v Speaker 2>and panic sets in. So here are several leadership checkpoints

22
00:01:36.640 --> 00:01:40.959
<v Speaker 2>to get your team ready for the next inevitable tech failure.

23
00:01:41.760 --> 00:01:46.680
<v Speaker 2>Checkpoint number one, know what tech you depend on. This

24
00:01:46.760 --> 00:01:49.840
<v Speaker 2>sounds obvious, but many leaders can't name the full list

25
00:01:49.879 --> 00:01:54.599
<v Speaker 2>of platforms tools in digital systems, their operation depends on

26
00:01:54.959 --> 00:01:59.640
<v Speaker 2>inventory your digital assets, what programs run your payroll, your customer,

27
00:01:59.719 --> 00:02:05.159
<v Speaker 2>serve your files, your critical communication? Because if one system fails,

28
00:02:05.200 --> 00:02:09.360
<v Speaker 2>what else is affected? You can't prepare for impact if

29
00:02:09.400 --> 00:02:14.479
<v Speaker 2>you don't know what's vulnerable. Checkpoint number two. Identify your

30
00:02:14.560 --> 00:02:19.000
<v Speaker 2>single points of failure. If your entire business grinds to

31
00:02:19.080 --> 00:02:22.800
<v Speaker 2>a halt when one Wi Fi router goes down, that's

32
00:02:22.879 --> 00:02:26.280
<v Speaker 2>a problem. If only one person knows how to restart

33
00:02:26.319 --> 00:02:30.840
<v Speaker 2>the system after a crash, that's another problem. Single points

34
00:02:30.919 --> 00:02:35.199
<v Speaker 2>of failure are where minor issues turn into full blown chaos.

35
00:02:35.759 --> 00:02:39.560
<v Speaker 2>A great leader always has a plan B, and sometimes

36
00:02:39.599 --> 00:02:45.599
<v Speaker 2>even a plan C. Checkpoint number three create a tech

37
00:02:45.719 --> 00:02:49.199
<v Speaker 2>down game plan. Does your team know what to do

38
00:02:49.280 --> 00:02:51.840
<v Speaker 2>when the screen goes dark? I'm not talking about just

39
00:02:51.919 --> 00:02:56.800
<v Speaker 2>calling it. I'm talking about who communicates what to whom,

40
00:02:57.159 --> 00:03:01.639
<v Speaker 2>what manual processes take over, what gets delayed in what

41
00:03:01.800 --> 00:03:06.439
<v Speaker 2>becomes priority. This is your digital version of a fire drill.

42
00:03:06.719 --> 00:03:11.479
<v Speaker 2>Everyone should know the steps before the emergency starts. Checkpoint

43
00:03:11.560 --> 00:03:16.439
<v Speaker 2>number four. Train your people to think analog. It sounds

44
00:03:16.479 --> 00:03:19.240
<v Speaker 2>weird to say that in twenty twenty five, but your

45
00:03:19.240 --> 00:03:22.599
<v Speaker 2>team still needs to know how to operate without a

46
00:03:22.639 --> 00:03:26.000
<v Speaker 2>screen in front of them. Can your receptionist take notes

47
00:03:26.080 --> 00:03:29.400
<v Speaker 2>by hand if the scheduling software is down? Can a

48
00:03:29.439 --> 00:03:34.719
<v Speaker 2>manager track time manually? If the punching system fails? Can

49
00:03:34.759 --> 00:03:39.280
<v Speaker 2>dispatch shift to radios or phones if the CAD system crashes.

50
00:03:39.960 --> 00:03:43.919
<v Speaker 2>The more your people know how to handle low tech workarounds,

51
00:03:44.520 --> 00:03:49.000
<v Speaker 2>the more they'll stay calm and productive under pressure. And

52
00:03:49.080 --> 00:03:54.159
<v Speaker 2>here's checkpoint five. Have backup channels for communication. If you

53
00:03:54.240 --> 00:03:58.080
<v Speaker 2>rely on email or chat apps and your network drops,

54
00:03:58.199 --> 00:04:00.919
<v Speaker 2>how will you reach your team. You need a backup

55
00:04:00.960 --> 00:04:06.000
<v Speaker 2>way to stay in contact, group texts, emergency contact lists,

56
00:04:06.680 --> 00:04:12.800
<v Speaker 2>even a walkie TALKIEFRS radio type system. Communication is the

57
00:04:12.840 --> 00:04:15.319
<v Speaker 2>first thing to break down in a tech crisis and

58
00:04:15.400 --> 00:04:20.240
<v Speaker 2>the first thing that needs to be restored. Checkpoint number six.

59
00:04:20.920 --> 00:04:25.839
<v Speaker 2>Protect your data. If your business isn't backing up regularly

60
00:04:26.199 --> 00:04:30.639
<v Speaker 2>and securely, your one lightning strike away from disaster. You

61
00:04:30.759 --> 00:04:36.959
<v Speaker 2>need off site, cloud and even local backups. Redundancy isn't paranoia,

62
00:04:37.040 --> 00:04:41.680
<v Speaker 2>Its preparation, and it's your insurance policy when things go sideways.

63
00:04:42.279 --> 00:04:47.079
<v Speaker 2>Make sure someone checks this system weekly, not yearly. Weekly

64
00:04:48.319 --> 00:04:53.600
<v Speaker 2>checkpoint seven. Run regular failure scenarios. Don't wait for a

65
00:04:53.680 --> 00:04:58.480
<v Speaker 2>disaster to test your readiness. Pick a random hour once

66
00:04:58.519 --> 00:05:01.040
<v Speaker 2>a quarter and simulate a Wi Fi outage or run

67
00:05:01.079 --> 00:05:05.240
<v Speaker 2>a tabletop exercise where your payment system goes down. Let

68
00:05:05.319 --> 00:05:09.600
<v Speaker 2>your team work through it, watch how they respond, debrief afterwards,

69
00:05:10.120 --> 00:05:16.399
<v Speaker 2>and find the cracks before they become craters. So technology

70
00:05:16.480 --> 00:05:20.560
<v Speaker 2>is amazing until it's not, and when it's not, your

71
00:05:20.639 --> 00:05:24.160
<v Speaker 2>leadership is what your team will depend on, not the software,

72
00:05:24.759 --> 00:05:29.959
<v Speaker 2>not the signal. You. Leaders who prepare for failure never

73
00:05:30.279 --> 00:05:33.399
<v Speaker 2>fully fail. They adapt, they respond, and they guide their

74
00:05:33.439 --> 00:05:37.680
<v Speaker 2>teams with calm under pressure. So before your next tech

75
00:05:37.879 --> 00:05:41.519
<v Speaker 2>crash hits, have the talk, build the plan, and test

76
00:05:41.560 --> 00:05:45.800
<v Speaker 2>the system, because once the screen goes black, it's already

77
00:05:45.800 --> 00:05:49.839
<v Speaker 2>too late. This has been the seven minute Leadership podcast,

78
00:05:50.160 --> 00:05:51.399
<v Speaker 2>and I thank you for listening.

79
00:05:51.680 --> 00:05:55.600
<v Speaker 1>For more Paul Fell of Alito Podcasts, visit paulfellowalito dot

80
00:05:55.639 --> 00:05:56.480
<v Speaker 1>com