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.720
<v Speaker 1>performance through strong human relations, team building, and goalajiving. This

3
00:00:11.919 --> 00:00:16.359
<v Speaker 1>is the seven Minute Leadership Podcast with your host Paul Fellovledo.

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

5
00:00:25.199 --> 00:00:29.600
<v Speaker 2>It's episode three ninety and today we're talking about something

6
00:00:30.039 --> 00:00:33.159
<v Speaker 2>that might sting a little, but it's one of the

7
00:00:33.200 --> 00:00:39.880
<v Speaker 2>most important leadership blind spots out there. Stop being a bottleneck.

8
00:00:40.719 --> 00:00:45.439
<v Speaker 2>We're going to break down how managers unintentionally slow things

9
00:00:45.479 --> 00:00:50.359
<v Speaker 2>down and more importantly, how to fix it. First, let's

10
00:00:50.399 --> 00:00:56.320
<v Speaker 2>talk about the bottleneck problem. Every business has goals, every

11
00:00:56.399 --> 00:01:02.960
<v Speaker 2>team has momentum, and every process has friction. But when

12
00:01:02.960 --> 00:01:07.879
<v Speaker 2>the friction is you, the manager or leader, that's a problem.

13
00:01:08.439 --> 00:01:11.480
<v Speaker 2>You may not mean to slow things down. You're not

14
00:01:11.680 --> 00:01:16.560
<v Speaker 2>trying to stall innovation, miss deadlines, or even frustrate your team.

15
00:01:16.640 --> 00:01:23.840
<v Speaker 2>But if your team is constantly waiting on you to approve, decide, delegate,

16
00:01:24.599 --> 00:01:30.000
<v Speaker 2>or weigh in, you are the bottleneck. And bottlenecks don't

17
00:01:30.000 --> 00:01:35.519
<v Speaker 2>always look like indecision or micromanagement. Sometimes they're disguised as

18
00:01:35.840 --> 00:01:40.079
<v Speaker 2>wanting to get it perfect before giving the green light,

19
00:01:41.040 --> 00:01:45.120
<v Speaker 2>or always needing to be the final voice in the room,

20
00:01:45.560 --> 00:01:50.599
<v Speaker 2>or taking days to respond to emails because you're too busy,

21
00:01:51.560 --> 00:01:54.480
<v Speaker 2>or hoarding knowledge, or refusing to teach others how to

22
00:01:54.519 --> 00:01:58.239
<v Speaker 2>do what you do. If any of that sounds familiar,

23
00:01:58.599 --> 00:02:01.760
<v Speaker 2>it's time to get honest with yourself, not to beat

24
00:02:01.799 --> 00:02:06.840
<v Speaker 2>yourself up, but to adjust. Here are three signs that

25
00:02:06.920 --> 00:02:09.919
<v Speaker 2>you are the bottleneck and you might be slowing things down.

26
00:02:10.759 --> 00:02:15.879
<v Speaker 2>Number one, your team constantly asks did you hear back

27
00:02:15.879 --> 00:02:19.199
<v Speaker 2>from them yet? If your name is the common thread

28
00:02:19.240 --> 00:02:24.360
<v Speaker 2>in the delay, that's a red flag. Number two, projects

29
00:02:24.639 --> 00:02:28.680
<v Speaker 2>stall at your desk. You start things but they don't finish,

30
00:02:29.159 --> 00:02:33.680
<v Speaker 2>or you assign things but never check back. In Number three,

31
00:02:33.759 --> 00:02:36.120
<v Speaker 2>you feel like you're the only one who knows how

32
00:02:36.120 --> 00:02:39.879
<v Speaker 2>to do it, so instead of teaching, you keep doing

33
00:02:39.960 --> 00:02:46.719
<v Speaker 2>it yourself. Sound familiar. That's how leaders unintentionally become the ceiling.

34
00:02:47.360 --> 00:02:52.000
<v Speaker 2>Your team's capacity is now tied directly to your availability.

35
00:02:52.960 --> 00:02:57.159
<v Speaker 2>And let's be real, it's not always ego. Sometimes leaders

36
00:02:57.199 --> 00:03:02.919
<v Speaker 2>become bottlenecks because they're overwhelmed, they think they're protecting the team,

37
00:03:03.319 --> 00:03:05.719
<v Speaker 2>They don't trust that others will get it done the

38
00:03:05.879 --> 00:03:10.080
<v Speaker 2>right way, or they've never learned how to build a

39
00:03:10.080 --> 00:03:15.759
<v Speaker 2>self sustaining team. This is where good intention meets bad outcome.

40
00:03:16.719 --> 00:03:20.199
<v Speaker 2>So how do you fix it? Here are four practical

41
00:03:20.240 --> 00:03:23.280
<v Speaker 2>ways to stop being a bottleneck and start being a

42
00:03:23.400 --> 00:03:29.199
<v Speaker 2>flow through leader. Number one, give away authority, not just tasks.

43
00:03:29.800 --> 00:03:34.639
<v Speaker 2>Don't just delegate the doing, delegate the deciding. If everything

44
00:03:34.759 --> 00:03:39.319
<v Speaker 2>still needs your signature, your inbox becomes the choke point.

45
00:03:39.960 --> 00:03:44.080
<v Speaker 2>Empower others to make the call, then support them publicly.

46
00:03:45.080 --> 00:03:49.520
<v Speaker 2>Number two, set deadlines for yourself. If a team member

47
00:03:49.560 --> 00:03:53.400
<v Speaker 2>needs a decision from you, don't make them chase you down.

48
00:03:53.719 --> 00:03:57.680
<v Speaker 2>Set a personal deadline, put it on your calendar and

49
00:03:57.800 --> 00:04:03.080
<v Speaker 2>meet it. Number three build systems not silos. If everything

50
00:04:03.159 --> 00:04:07.199
<v Speaker 2>you know lives only in your head, your absence stalls

51
00:04:07.240 --> 00:04:13.319
<v Speaker 2>the machine, document the process, train your people, make yourself optional,

52
00:04:14.319 --> 00:04:18.360
<v Speaker 2>and number four audit your decision touch points. Ask yourself,

53
00:04:18.399 --> 00:04:21.279
<v Speaker 2>do I really need to be involved in this step?

54
00:04:21.480 --> 00:04:25.519
<v Speaker 2>If not, get out of the way. Create fewer approvals,

55
00:04:26.399 --> 00:04:30.920
<v Speaker 2>simplify the chain of command. And here's a test that

56
00:04:31.000 --> 00:04:35.160
<v Speaker 2>you can try next week. Pick one project, step back,

57
00:04:35.279 --> 00:04:40.439
<v Speaker 2>remove yourself as the go to person. Instead, assign ownership

58
00:04:40.480 --> 00:04:43.720
<v Speaker 2>to someone else and let them lead it front to back.

59
00:04:44.319 --> 00:04:48.120
<v Speaker 2>Will they do it exactly like you probably not. Will

60
00:04:48.160 --> 00:04:51.399
<v Speaker 2>they make a few mistakes, maybe, but will they grow

61
00:04:51.439 --> 00:04:55.399
<v Speaker 2>and move the ball forward? Absolutely. Your job isn't to

62
00:04:55.439 --> 00:04:58.439
<v Speaker 2>be the smartest person in the room. It's to build

63
00:04:58.480 --> 00:05:00.680
<v Speaker 2>a room full of people who don't need you to

64
00:05:00.800 --> 00:05:06.920
<v Speaker 2>be in it every second. So if your team is

65
00:05:07.000 --> 00:05:10.279
<v Speaker 2>waiting on you, then you're not leading, your limiting. You're

66
00:05:10.399 --> 00:05:13.600
<v Speaker 2>the reason the anchor is stuck in the mud. It

67
00:05:13.680 --> 00:05:17.240
<v Speaker 2>should never be that way. It's not a character flaw.

68
00:05:17.480 --> 00:05:20.759
<v Speaker 2>It's a fixable pattern if you're willing to fix it.

69
00:05:20.959 --> 00:05:26.480
<v Speaker 2>Because leadership isn't about holding on, It's about letting go strategically,

70
00:05:27.079 --> 00:05:32.240
<v Speaker 2>responsibly and with trust. So let your team breathe, let

71
00:05:32.279 --> 00:05:35.800
<v Speaker 2>them move. You'll get more done, they'll feel more valued,

72
00:05:36.399 --> 00:05:39.160
<v Speaker 2>and you will learn more respect. And that's what great

73
00:05:39.240 --> 00:05:43.040
<v Speaker 2>leadership looks like. This has been the seven Minute Leadership

74
00:05:43.079 --> 00:05:44.879
<v Speaker 2>Podcast and I thank you for listening.

75
00:05:45.120 --> 00:05:49.920
<v Speaker 1>For more Paul Fell of Alito Podcasts, visit paulfellowalito dot com.