WEBVTT - My Team is Overworked - and I'm the Boss

0:00:03.560 --> 0:00:05.880
<v Speaker 1>My colleagues, We'll stop commenting on everything I get my

0:00:05.880 --> 0:00:09.360
<v Speaker 1>assist people and meeting. Why does my coworker keep taking

0:00:09.360 --> 0:00:12.240
<v Speaker 1>credit for all my ideas? Have any wisdom for me? Hi?

0:00:12.280 --> 0:00:15.720
<v Speaker 1>I'm Alison Green. Welcome to the Aska Manager podcast, where

0:00:15.760 --> 0:00:19.520
<v Speaker 1>I answer questions from listeners about life at work, everything

0:00:19.520 --> 0:00:21.640
<v Speaker 1>from what to say if you're allergic to your coworkers

0:00:21.640 --> 0:00:23.840
<v Speaker 1>perfume to what to do if you drink too much

0:00:23.840 --> 0:00:29.080
<v Speaker 1>at the company party. Let's get started. I hear from

0:00:29.120 --> 0:00:32.280
<v Speaker 1>a lot of people who feel overworked, that they're expected

0:00:32.320 --> 0:00:36.560
<v Speaker 1>to work unreasonable hours and their workload is just unmanageable.

0:00:37.200 --> 0:00:40.479
<v Speaker 1>Today's guest is approaching this issue from the other side.

0:00:40.720 --> 0:00:43.640
<v Speaker 1>She's a manager whose team seems to be working too much,

0:00:43.880 --> 0:00:46.519
<v Speaker 1>and she's wondering how she can help them get it

0:00:46.600 --> 0:00:49.680
<v Speaker 1>under control and work fewer hours. Hi, and welcome to

0:00:49.720 --> 0:00:52.880
<v Speaker 1>the show. Hi, thanks for having me. So you wrote

0:00:52.880 --> 0:00:55.680
<v Speaker 1>to me and you said you're a somewhat new manager

0:00:55.760 --> 0:00:58.720
<v Speaker 1>at a nonprofit and you've found that the dominant culture

0:00:58.760 --> 0:01:01.360
<v Speaker 1>on your team is why where people work all the time.

0:01:01.840 --> 0:01:05.160
<v Speaker 1>Despite your attempts to help people manage their workloads, you're

0:01:05.200 --> 0:01:08.959
<v Speaker 1>seeing people routinely working during vacations even when someone else

0:01:09.000 --> 0:01:11.760
<v Speaker 1>has been assigned to take care of their email for them,

0:01:11.800 --> 0:01:14.080
<v Speaker 1>and you see other people just never taking any time

0:01:14.120 --> 0:01:17.680
<v Speaker 1>off at all. Is that basically the situation. That's pretty

0:01:17.760 --> 0:01:21.000
<v Speaker 1>much it. And you mentioned that you're new to the job.

0:01:21.080 --> 0:01:24.000
<v Speaker 1>When did you come on board? So now I've been

0:01:24.040 --> 0:01:28.200
<v Speaker 1>here a year, I still feel new. Is the strange part.

0:01:28.319 --> 0:01:32.039
<v Speaker 1>I think because my team as a team predates me,

0:01:32.400 --> 0:01:36.360
<v Speaker 1>and our colleagues who work at our work site abroad

0:01:37.080 --> 0:01:40.120
<v Speaker 1>all predate me by many years. And so I still

0:01:40.200 --> 0:01:43.039
<v Speaker 1>I think feel like I've walked into a situation that

0:01:43.160 --> 0:01:46.600
<v Speaker 1>exists outside of my control. That makes perfect sense, Okay,

0:01:47.120 --> 0:01:50.040
<v Speaker 1>And in your email to me, you wrote, I'd like

0:01:50.120 --> 0:01:52.600
<v Speaker 1>to help change the culture, but I can't figure out

0:01:52.640 --> 0:01:57.080
<v Speaker 1>if I'm being ineffective, if I'm battling personalities that overwork

0:01:57.280 --> 0:02:02.160
<v Speaker 1>feeds like workaholics, people pleaser and over committers, if they

0:02:02.200 --> 0:02:05.280
<v Speaker 1>really are too overwork to define balance, or if I

0:02:05.280 --> 0:02:08.640
<v Speaker 1>am somehow creating an environment that reinforces the tendency to

0:02:08.720 --> 0:02:14.000
<v Speaker 1>overwork while paying lip service to wanting balance. I will

0:02:14.040 --> 0:02:16.919
<v Speaker 1>add one more possibility to that list. It could be

0:02:17.160 --> 0:02:20.840
<v Speaker 1>that the broader culture of your organization puts pressure on

0:02:20.880 --> 0:02:24.520
<v Speaker 1>people to work crazy hours, or that the last manager

0:02:24.560 --> 0:02:27.520
<v Speaker 1>on this team before you came in did, and so

0:02:27.600 --> 0:02:31.920
<v Speaker 1>people don't really believe that they can and should shift gears.

0:02:32.560 --> 0:02:35.440
<v Speaker 1>I think that's a big problem. Tell me a little

0:02:35.440 --> 0:02:38.200
<v Speaker 1>bit about the broader culture of the organization beyond just

0:02:38.280 --> 0:02:40.400
<v Speaker 1>your team. Are you seeing that kind of behavior on

0:02:40.440 --> 0:02:43.680
<v Speaker 1>other teams as well? I am. So we're the only

0:02:43.720 --> 0:02:47.720
<v Speaker 1>team in this country and everyone else is six hours

0:02:47.720 --> 0:02:50.840
<v Speaker 1>ahead of us. Um, we're a small group, and the

0:02:50.880 --> 0:02:54.720
<v Speaker 1>people abroad are a very big group, and they work

0:02:54.760 --> 0:02:59.640
<v Speaker 1>all the time. They work at our work site with

0:02:59.800 --> 0:03:03.360
<v Speaker 1>our clients, so and some of them live there, so

0:03:03.440 --> 0:03:06.200
<v Speaker 1>they don't have a break. Um. I mean they get

0:03:06.400 --> 0:03:09.160
<v Speaker 1>time off, but in the regular twenty for our cycle,

0:03:09.320 --> 0:03:13.000
<v Speaker 1>they're working or in that space all the time. The

0:03:13.080 --> 0:03:16.520
<v Speaker 1>other thing that I think we see is that because

0:03:16.919 --> 0:03:21.040
<v Speaker 1>we're all very mission driven people and our mission feels urgent,

0:03:22.080 --> 0:03:25.280
<v Speaker 1>there is this sense that if you can do something,

0:03:26.400 --> 0:03:28.919
<v Speaker 1>you will do something because you care about the mission

0:03:28.919 --> 0:03:31.160
<v Speaker 1>and you want to better the lives of our clients

0:03:31.200 --> 0:03:34.400
<v Speaker 1>as much as you can. Um. In addition, I think

0:03:35.200 --> 0:03:39.640
<v Speaker 1>the broader culture is also impacted by the time difference

0:03:40.920 --> 0:03:44.400
<v Speaker 1>that because so many of our working hours don't overlap.

0:03:44.680 --> 0:03:47.400
<v Speaker 1>There is kind of an impulse to want to be

0:03:47.480 --> 0:03:50.200
<v Speaker 1>available when your colleagues are, so I think the thing

0:03:50.200 --> 0:03:53.680
<v Speaker 1>that you're identifying about mission driven nonprofits is probably a

0:03:53.720 --> 0:03:56.200
<v Speaker 1>huge part of this. I spent my whole career in nonprofits,

0:03:56.200 --> 0:03:58.280
<v Speaker 1>and I know exactly what you're talking about. When you

0:03:58.320 --> 0:04:02.880
<v Speaker 1>feel like you're doing very important, crucial, urgent work, it's

0:04:02.920 --> 0:04:04.880
<v Speaker 1>hard to say, well, it's five o'clock, I'm going to

0:04:04.920 --> 0:04:08.120
<v Speaker 1>stop working for today When you know that if you

0:04:08.160 --> 0:04:09.840
<v Speaker 1>did put in more work, you could have a real

0:04:10.440 --> 0:04:14.080
<v Speaker 1>impact on people's lives or on an issue that you

0:04:14.320 --> 0:04:17.760
<v Speaker 1>care deeply about. It it's hard to work with other

0:04:17.800 --> 0:04:21.960
<v Speaker 1>people would consider regular hours in that context, and especially

0:04:22.400 --> 0:04:25.359
<v Speaker 1>I mean nonprofits fall prey to this all the time.

0:04:25.440 --> 0:04:28.279
<v Speaker 1>It can very quickly become that that is the culture there,

0:04:28.680 --> 0:04:31.320
<v Speaker 1>and people can start to feel like if they don't

0:04:31.320 --> 0:04:34.200
<v Speaker 1>work those sorts of hours that they either are less

0:04:34.240 --> 0:04:36.680
<v Speaker 1>committed or that look less committed, and they'll be judged

0:04:36.720 --> 0:04:38.880
<v Speaker 1>for it. Whether or not they really would be judged

0:04:38.880 --> 0:04:40.680
<v Speaker 1>for it. I mean, in many organizations they would be,

0:04:40.720 --> 0:04:42.680
<v Speaker 1>but but I think there are also ones where they

0:04:42.680 --> 0:04:45.880
<v Speaker 1>wouldn't be. But it's hard to know which one you're in. Yes,

0:04:46.360 --> 0:04:49.799
<v Speaker 1>I agree with you, And I think that that's also

0:04:49.920 --> 0:04:55.240
<v Speaker 1>the it's it becomes a way of of proving it

0:04:55.279 --> 0:04:57.800
<v Speaker 1>to yourself, you know. And I think that's part of it,

0:04:57.839 --> 0:05:01.680
<v Speaker 1>to the thing that we tell our yourselves about working

0:05:01.680 --> 0:05:04.159
<v Speaker 1>in a nonprofit and being paid less. Because you work

0:05:04.160 --> 0:05:06.640
<v Speaker 1>in a nonprofit, you make up for it and meaning,

0:05:06.680 --> 0:05:08.640
<v Speaker 1>and so you want that meaning to be as big

0:05:08.680 --> 0:05:11.760
<v Speaker 1>as it can be, you know. It drives itself somehow

0:05:11.760 --> 0:05:14.840
<v Speaker 1>that way too. Yeah, And it really I think working

0:05:14.839 --> 0:05:17.400
<v Speaker 1>on an important issue day in and day out can

0:05:17.440 --> 0:05:20.080
<v Speaker 1>take over your life in some ways. Like it's really

0:05:20.279 --> 0:05:22.159
<v Speaker 1>I don't know. I always found especially when I was

0:05:22.160 --> 0:05:23.880
<v Speaker 1>working like I used to work for an animal protection

0:05:23.960 --> 0:05:27.200
<v Speaker 1>charity where we were dealing with animal suffering and animal abuse,

0:05:27.400 --> 0:05:30.520
<v Speaker 1>and that gets into your head and it stays there

0:05:30.560 --> 0:05:33.120
<v Speaker 1>all the time. And it's that's a thing that it's

0:05:33.160 --> 0:05:36.760
<v Speaker 1>hard to not think, I don't know, it's hard to

0:05:36.760 --> 0:05:39.920
<v Speaker 1>get the balance right and and feel like you're fulfilling

0:05:39.920 --> 0:05:43.520
<v Speaker 1>your moral obligations, even though if you had a regular job,

0:05:43.560 --> 0:05:46.200
<v Speaker 1>you wouldn't question if you were fulfilling your moral obligations

0:05:46.240 --> 0:05:47.760
<v Speaker 1>by going to work at a bank and then coming

0:05:47.760 --> 0:05:51.000
<v Speaker 1>home at six o'clock. Yes, yeah, I think it's really

0:05:52.480 --> 0:05:54.640
<v Speaker 1>it's difficult. You know, you get so much meaning from it,

0:05:54.680 --> 0:05:59.359
<v Speaker 1>you get so much worth, um, and then you always

0:05:59.440 --> 0:06:01.640
<v Speaker 1>know you can see the gaps, or you can see

0:06:01.880 --> 0:06:03.400
<v Speaker 1>if I had done this better, we would have gotten

0:06:03.400 --> 0:06:05.400
<v Speaker 1>this money, If I had done this better, the clients

0:06:05.440 --> 0:06:10.120
<v Speaker 1>would have felt this. And those are those are tangible

0:06:10.160 --> 0:06:11.719
<v Speaker 1>and they can haunt you in a way, and I

0:06:11.760 --> 0:06:15.640
<v Speaker 1>think that drives it. Yes, absolutely well. Let me ask

0:06:15.680 --> 0:06:18.680
<v Speaker 1>you this, do you have a sense from your own

0:06:18.720 --> 0:06:22.440
<v Speaker 1>boss and from management of the organization above you in general?

0:06:23.400 --> 0:06:25.520
<v Speaker 1>Is there room if you were able to get through

0:06:25.560 --> 0:06:28.440
<v Speaker 1>to your team members and actually succeed in getting them

0:06:28.480 --> 0:06:31.920
<v Speaker 1>to work more reasonable hours. Is there room for that

0:06:32.320 --> 0:06:34.359
<v Speaker 1>for the organization to be okay with it, or is

0:06:34.440 --> 0:06:37.919
<v Speaker 1>your sense that maybe that would make waves. That's a

0:06:37.920 --> 0:06:43.440
<v Speaker 1>great question. Um. I think for some of my staff

0:06:44.279 --> 0:06:48.200
<v Speaker 1>there could be room for that, you know. UM. I

0:06:48.279 --> 0:06:53.279
<v Speaker 1>mentioned my letter that we recently grew our team and

0:06:54.120 --> 0:06:55.480
<v Speaker 1>part of the reason we did that is that we

0:06:55.520 --> 0:06:58.240
<v Speaker 1>had work that needed to be done, new work. And

0:06:58.320 --> 0:07:05.640
<v Speaker 1>I said to my board essentially that our existing sort

0:07:05.640 --> 0:07:08.480
<v Speaker 1>of person who gets everything dumped on them couldn't get

0:07:08.520 --> 0:07:11.960
<v Speaker 1>anything else dumped on them and that if we were

0:07:11.960 --> 0:07:13.960
<v Speaker 1>going to take on this project, we needed to hire

0:07:14.080 --> 0:07:17.120
<v Speaker 1>for it. And they heard me and they hired for it,

0:07:17.240 --> 0:07:18.920
<v Speaker 1>and so I was able to make space and get

0:07:18.920 --> 0:07:23.000
<v Speaker 1>the organization to make space in that way. But I mean,

0:07:23.040 --> 0:07:27.080
<v Speaker 1>I do think there are limits to that. Um. And

0:07:27.360 --> 0:07:30.560
<v Speaker 1>you know, in sort of a dated day way, do

0:07:30.680 --> 0:07:34.760
<v Speaker 1>I think that our colleagues overseas are going to stop

0:07:34.840 --> 0:07:39.800
<v Speaker 1>having needs at five AMR time? No, Like, that's just

0:07:39.880 --> 0:07:42.800
<v Speaker 1>the nature of the beast. Um. And I don't know

0:07:42.800 --> 0:07:45.000
<v Speaker 1>if I could convince my staff that it's okay not

0:07:45.120 --> 0:07:47.720
<v Speaker 1>to wake up at six am to check your phone

0:07:47.760 --> 0:07:50.840
<v Speaker 1>when you don't need to be getting up until seven. Yeah. Well,

0:07:50.880 --> 0:07:53.960
<v Speaker 1>the fact that they did respond with more staffing is

0:07:54.000 --> 0:07:58.480
<v Speaker 1>a really good sign, because a lot of organizations wouldn't

0:07:58.480 --> 0:08:01.560
<v Speaker 1>have So that's good. That indicates there's some degree of

0:08:01.600 --> 0:08:03.960
<v Speaker 1>reasonable airness at least. But I'm sure you're right that

0:08:04.000 --> 0:08:06.160
<v Speaker 1>there are limits to that. I mean, just that's like

0:08:06.200 --> 0:08:08.880
<v Speaker 1>the financial reality for most organizations that there will be

0:08:08.920 --> 0:08:11.440
<v Speaker 1>limits to that. UM. Let me ask you this. I mean,

0:08:11.440 --> 0:08:13.800
<v Speaker 1>you're talking about people needing things at five am here time?

0:08:14.680 --> 0:08:17.120
<v Speaker 1>Do they? I mean, is it urgent that they get

0:08:17.120 --> 0:08:19.280
<v Speaker 1>a response, then what what would happen if they didn't?

0:08:20.360 --> 0:08:23.200
<v Speaker 1>So this is something I think about a lot um.

0:08:23.240 --> 0:08:26.000
<v Speaker 1>So sometimes they do need a response then, and sometimes

0:08:26.200 --> 0:08:29.480
<v Speaker 1>they're writing it because they have the moment in their

0:08:29.520 --> 0:08:32.040
<v Speaker 1>work day to write it. And we have to be

0:08:32.080 --> 0:08:34.920
<v Speaker 1>able to triage right. We have to be able to

0:08:34.960 --> 0:08:37.400
<v Speaker 1>say this is urgent and you need me to do

0:08:37.440 --> 0:08:40.120
<v Speaker 1>this now, or I know something is urgent is going on,

0:08:40.200 --> 0:08:41.880
<v Speaker 1>I'm going to make sure I check my phone at

0:08:42.240 --> 0:08:44.080
<v Speaker 1>thirty before I go to bed, or wake up early

0:08:44.120 --> 0:08:47.360
<v Speaker 1>to check my phone because of this specific time sensitive need.

0:08:48.040 --> 0:08:51.160
<v Speaker 1>But most of the time it's not those things. And

0:08:51.240 --> 0:08:56.080
<v Speaker 1>I think recognizing that is is really important. And I

0:08:56.160 --> 0:08:59.679
<v Speaker 1>also kind of want to encourage a little bit of

0:09:00.320 --> 0:09:03.800
<v Speaker 1>self reliance on the part of some of my colleagues

0:09:04.280 --> 0:09:09.160
<v Speaker 1>overseas um that we don't always have the answer here,

0:09:09.360 --> 0:09:12.640
<v Speaker 1>and if it's the middle of the night, unless it's

0:09:13.320 --> 0:09:17.040
<v Speaker 1>a truly urgent matter, they shouldn't expect to get an

0:09:17.040 --> 0:09:21.040
<v Speaker 1>answer from us. And that's not because I, you know,

0:09:21.080 --> 0:09:23.160
<v Speaker 1>I don't want to be available when they need me.

0:09:23.200 --> 0:09:26.240
<v Speaker 1>It's more because I don't always know that it's a need,

0:09:27.080 --> 0:09:31.360
<v Speaker 1>um that there's somehow been a culture of learning to

0:09:31.480 --> 0:09:36.559
<v Speaker 1>rely on us for certain certain kinds of information as

0:09:36.559 --> 0:09:41.000
<v Speaker 1>opposed to feeling secure in your knowledge base. Yourself were

0:09:41.040 --> 0:09:45.080
<v Speaker 1>the fundraisers and they're the program people, but you know

0:09:45.760 --> 0:09:48.760
<v Speaker 1>they know about both sides. That makes perfect sense. Let

0:09:48.760 --> 0:09:52.840
<v Speaker 1>me ask you this, do you trust your colleagues overseas

0:09:52.920 --> 0:09:55.319
<v Speaker 1>if you were to kind of explain to them, hey,

0:09:55.480 --> 0:09:58.160
<v Speaker 1>we have people who aren't getting sleep because they're getting

0:09:58.200 --> 0:10:00.040
<v Speaker 1>up at five am our time because they're worried it

0:10:00.160 --> 0:10:04.240
<v Speaker 1>needs something. Would you trust them to hear that context

0:10:04.360 --> 0:10:06.200
<v Speaker 1>and to say, well, let me actually back up and

0:10:06.200 --> 0:10:08.280
<v Speaker 1>tell you what I'm thinking. I wonder in this case,

0:10:09.080 --> 0:10:11.800
<v Speaker 1>if there is a way for you to have them

0:10:11.920 --> 0:10:15.000
<v Speaker 1>channel urgent stuff differently, Like if there could be a

0:10:15.000 --> 0:10:17.720
<v Speaker 1>particular phone number or a particular email address that is

0:10:17.800 --> 0:10:21.559
<v Speaker 1>for middle of the night urgent stuff. And I wonder

0:10:21.600 --> 0:10:23.720
<v Speaker 1>if you would trust them to have the right judgment

0:10:24.200 --> 0:10:27.120
<v Speaker 1>to decide what needs to go there and what doesn't.

0:10:27.240 --> 0:10:29.560
<v Speaker 1>Because if you could trust them to do that, you

0:10:29.600 --> 0:10:33.480
<v Speaker 1>could set up a channel that is just for truly

0:10:33.600 --> 0:10:36.920
<v Speaker 1>urgent stuff. And you could even have that set to

0:10:37.000 --> 0:10:38.880
<v Speaker 1>like a wake someone up if it needed to, or

0:10:38.920 --> 0:10:40.920
<v Speaker 1>you could have like one person who was charged with

0:10:41.000 --> 0:10:43.840
<v Speaker 1>checking it for everyone who may be agreed to work

0:10:44.480 --> 0:10:47.280
<v Speaker 1>a different those hours, like a different sort of shift almost.

0:10:47.360 --> 0:10:50.360
<v Speaker 1>But to make that work, you would have to trust

0:10:50.440 --> 0:10:53.880
<v Speaker 1>that your overseas colleagues would use it appropriately. So I

0:10:53.880 --> 0:10:57.320
<v Speaker 1>think this is a really great question. Um. What I

0:10:57.320 --> 0:10:59.520
<v Speaker 1>think I would love to do, just listening to what

0:10:59.559 --> 0:11:03.120
<v Speaker 1>you're saying, is to say, essentially, when it's urgent, what's

0:11:03.120 --> 0:11:05.280
<v Speaker 1>app me, and I'll make sure my what's up notifications

0:11:05.280 --> 0:11:07.960
<v Speaker 1>are always on. The qualm I would have about doing

0:11:08.000 --> 0:11:13.000
<v Speaker 1>that is that my boss is one of our overseas colleagues.

0:11:13.880 --> 0:11:19.040
<v Speaker 1>Our executive director is based overseas, and while he doesn't

0:11:19.160 --> 0:11:23.480
<v Speaker 1>think I should do what he does, he only sleeps

0:11:23.480 --> 0:11:26.920
<v Speaker 1>a handful of hours per night, And so I'm even

0:11:26.960 --> 0:11:29.560
<v Speaker 1>hesitant to say to him, you know, what, do you

0:11:29.600 --> 0:11:32.359
<v Speaker 1>mind not emailing me from these hours to these hours?

0:11:33.000 --> 0:11:38.280
<v Speaker 1>Because I want to sleep to sleep, But when I

0:11:38.320 --> 0:11:40.640
<v Speaker 1>know he doesn't, when I know he works himself way

0:11:40.720 --> 0:11:42.720
<v Speaker 1>too hard, and he doesn't want me to do to

0:11:42.800 --> 0:11:46.400
<v Speaker 1>myself what he does to himself. But you know, I

0:11:46.480 --> 0:11:50.040
<v Speaker 1>understand how overwork happens, right. I see the tendencies in

0:11:50.120 --> 0:11:53.920
<v Speaker 1>myself to not want to make waves there too. Let's

0:11:53.960 --> 0:11:56.040
<v Speaker 1>pass here for a quick break and we'll be right back.

0:12:03.600 --> 0:12:05.680
<v Speaker 1>I mean, it might be that you actually need someone

0:12:05.720 --> 0:12:08.319
<v Speaker 1>on your staff who works a weird schedule who can

0:12:08.360 --> 0:12:10.880
<v Speaker 1>handle those nighttime things. I don't know enough about the

0:12:10.880 --> 0:12:13.320
<v Speaker 1>context to know, but I don't want the solution to

0:12:13.400 --> 0:12:15.960
<v Speaker 1>be that we just move the whole burden over to you.

0:12:16.840 --> 0:12:19.040
<v Speaker 1>But I do think there's probably something there that if

0:12:19.080 --> 0:12:22.960
<v Speaker 1>you just have a specific emergency channel and people know

0:12:23.120 --> 0:12:24.920
<v Speaker 1>to use that, then they can go on emailing you

0:12:25.000 --> 0:12:27.760
<v Speaker 1>just like normal. But then then the other piece of

0:12:27.760 --> 0:12:29.280
<v Speaker 1>this is that you have to convince your staff to

0:12:29.280 --> 0:12:31.200
<v Speaker 1>stop waking up at five am to check their email.

0:12:31.640 --> 0:12:33.599
<v Speaker 1>But part of that will be that they know that

0:12:33.679 --> 0:12:37.240
<v Speaker 1>emergencies are getting handled through this other channel. Right, No,

0:12:37.360 --> 0:12:40.240
<v Speaker 1>I think you're I think you're definitely onto something there

0:12:40.320 --> 0:12:43.199
<v Speaker 1>that if we said, you know, WhatsApp is going to

0:12:43.280 --> 0:12:48.000
<v Speaker 1>be our emergency content means of contact, that we would

0:12:48.000 --> 0:12:50.240
<v Speaker 1>turn our notifiers off on our email or turn the

0:12:50.320 --> 0:12:54.000
<v Speaker 1>ding off on our email and and trusted after a

0:12:54.120 --> 0:12:56.720
<v Speaker 1>period of time. And I do think some of my

0:12:56.760 --> 0:13:01.520
<v Speaker 1>staff would respond to that and would trust it. You know,

0:13:01.559 --> 0:13:04.840
<v Speaker 1>I had one of my new staff was getting emails

0:13:04.880 --> 0:13:07.760
<v Speaker 1>on the weekend and was it was really nice. Was

0:13:07.960 --> 0:13:10.199
<v Speaker 1>new enough to this world that she said to me,

0:13:11.240 --> 0:13:12.520
<v Speaker 1>what do you want me to do when I get

0:13:12.559 --> 0:13:14.480
<v Speaker 1>emails from this person on the weekend? And I said,

0:13:14.480 --> 0:13:17.240
<v Speaker 1>don't respond to them until Monday. She said, okay, So

0:13:17.280 --> 0:13:19.200
<v Speaker 1>you know, she trusted that. I think some of my

0:13:20.000 --> 0:13:23.760
<v Speaker 1>older staff, my existing team from when I came in,

0:13:23.840 --> 0:13:29.439
<v Speaker 1>would I would have a little more trouble trusting the limitations. Yeah,

0:13:29.840 --> 0:13:34.200
<v Speaker 1>and sometimes it takes seeing it working for people to

0:13:34.280 --> 0:13:37.400
<v Speaker 1>begin trusting it. So it might mean that you have

0:13:37.440 --> 0:13:39.640
<v Speaker 1>to do a lot of coaching and reinforcing on the

0:13:39.720 --> 0:13:41.960
<v Speaker 1>system for the first few weeks, and also that you

0:13:42.000 --> 0:13:47.080
<v Speaker 1>have to really talk explicitly to people about why this

0:13:47.160 --> 0:13:50.160
<v Speaker 1>is okay. And also don't assume they'll just believe you.

0:13:50.600 --> 0:13:52.520
<v Speaker 1>They might be thinking, like you say, it's okay, but

0:13:52.559 --> 0:13:54.079
<v Speaker 1>I can think of all these times that it wouldn't

0:13:54.080 --> 0:13:56.480
<v Speaker 1>have been okay, And so it might really help to

0:13:56.920 --> 0:13:59.520
<v Speaker 1>walk through a bunch of concrete situations, like to say

0:13:59.520 --> 0:14:02.600
<v Speaker 1>to them, think back to the last three months, what

0:14:02.800 --> 0:14:04.920
<v Speaker 1>sorts of things came up that would have been a

0:14:04.960 --> 0:14:08.200
<v Speaker 1>problem if we were handling our workflow this way, and

0:14:08.240 --> 0:14:11.000
<v Speaker 1>then talk those through and if you can talk those

0:14:11.080 --> 0:14:14.040
<v Speaker 1>concrete worries through with them and say, okay, well, in

0:14:14.080 --> 0:14:17.440
<v Speaker 1>that situation, here's how we would handle that. Now, that

0:14:17.559 --> 0:14:20.880
<v Speaker 1>might be really key in putting some of their fears

0:14:20.880 --> 0:14:24.000
<v Speaker 1>to rest. I think that's a great idea. And I

0:14:24.040 --> 0:14:26.400
<v Speaker 1>think that also might be how I try to handle

0:14:27.240 --> 0:14:33.360
<v Speaker 1>the checking email on vacation behavior, you know, which, Look,

0:14:33.400 --> 0:14:35.720
<v Speaker 1>if person wants to check in their email once a

0:14:35.800 --> 0:14:39.920
<v Speaker 1>day on vacation, I'm not really going to fight that.

0:14:39.920 --> 0:14:43.840
<v Speaker 1>That's in some ways their decision. Um. But I've had

0:14:45.000 --> 0:14:49.800
<v Speaker 1>more sort of egregious problems with that where I had

0:14:49.840 --> 0:14:51.560
<v Speaker 1>a staff member who has gone for a few weeks

0:14:51.560 --> 0:14:53.560
<v Speaker 1>on kind of a once in a lifetime opportunity, and

0:14:53.960 --> 0:14:57.560
<v Speaker 1>I was checking that staff member's email while they were gone,

0:14:57.560 --> 0:15:01.360
<v Speaker 1>and this was the agreed upon response. And I was

0:15:01.440 --> 0:15:05.720
<v Speaker 1>in the mailbox and I saw emails moving around around

0:15:05.840 --> 0:15:08.600
<v Speaker 1>me and going red and unread, and I knew they

0:15:08.600 --> 0:15:11.360
<v Speaker 1>were in there. Um. And on the one hand, I thought,

0:15:12.600 --> 0:15:14.800
<v Speaker 1>you have a really special opportunity. I really wish as

0:15:14.800 --> 0:15:18.640
<v Speaker 1>a person in your life that you would have this

0:15:18.680 --> 0:15:22.440
<v Speaker 1>opportunity to enjoy it. But also, I'm spending my work

0:15:22.440 --> 0:15:25.280
<v Speaker 1>time trying to do some of your work and you

0:15:25.440 --> 0:15:28.440
<v Speaker 1>doing it as well is not actually a good use

0:15:28.440 --> 0:15:31.960
<v Speaker 1>of anybody's time. Yeah. Did you ever have any version

0:15:32.000 --> 0:15:34.800
<v Speaker 1>of that conversation with them when they got back? Yeah?

0:15:34.840 --> 0:15:37.640
<v Speaker 1>So when they got back, I focused more on the

0:15:37.680 --> 0:15:40.320
<v Speaker 1>first one. I was very new at this point. I've

0:15:40.360 --> 0:15:45.000
<v Speaker 1>been the manager six weeks, um, and I really focused

0:15:45.000 --> 0:15:48.160
<v Speaker 1>on the you know, this is not I'm hoping to

0:15:48.240 --> 0:15:50.560
<v Speaker 1>build some kind of work life balance in here. And

0:15:50.640 --> 0:15:53.280
<v Speaker 1>it's really important to me that when you're gone, you

0:15:53.320 --> 0:15:55.160
<v Speaker 1>have the ability to be gone. And it's important for

0:15:55.160 --> 0:15:58.800
<v Speaker 1>all these reasons, including burnout and including your mental health

0:15:58.840 --> 0:16:00.920
<v Speaker 1>and the fact that you know you're a very valued

0:16:01.480 --> 0:16:03.680
<v Speaker 1>staff member and I want to keep you as long

0:16:03.720 --> 0:16:06.440
<v Speaker 1>as I can, and I can't do that if you

0:16:06.440 --> 0:16:08.720
<v Speaker 1>know you're going to end up feeling burnt out or

0:16:08.720 --> 0:16:12.320
<v Speaker 1>overburdened by work. But I think the second part about

0:16:12.520 --> 0:16:15.280
<v Speaker 1>staff time didn't really occur to me until I've been

0:16:15.320 --> 0:16:18.320
<v Speaker 1>working with them longer and realized that there was some

0:16:18.400 --> 0:16:21.560
<v Speaker 1>duplication of efforts there. Um and I have I haven't

0:16:21.600 --> 0:16:24.440
<v Speaker 1>had that conversation now that I think about it, And

0:16:24.800 --> 0:16:28.040
<v Speaker 1>that might be a a better avenue because it doesn't

0:16:28.040 --> 0:16:32.400
<v Speaker 1>appeal to their personhood, right, It appeals to their worker identity,

0:16:32.640 --> 0:16:35.760
<v Speaker 1>which is so strong anyway, I think that is worth saying.

0:16:35.760 --> 0:16:37.440
<v Speaker 1>I mean, I wouldn't go back. And if this happened

0:16:37.440 --> 0:16:40.320
<v Speaker 1>a year ago, obviously you don't want to, but like

0:16:40.520 --> 0:16:42.880
<v Speaker 1>if it happens, to bring it up again. But if

0:16:42.880 --> 0:16:46.920
<v Speaker 1>it happens again, definitely. And also you could say it preemptively.

0:16:46.960 --> 0:16:48.840
<v Speaker 1>If someone is going on vacation and you know that

0:16:48.880 --> 0:16:51.640
<v Speaker 1>they're likely to have that tendency, you could say, I

0:16:51.720 --> 0:16:53.760
<v Speaker 1>know that you're really dedicated and you might be tempted

0:16:53.800 --> 0:16:55.920
<v Speaker 1>to do this. Here is a reason that I'm asking

0:16:55.960 --> 0:16:58.040
<v Speaker 1>you not to, so it might be interesting to say

0:16:58.040 --> 0:17:00.560
<v Speaker 1>that ahead of time. The other thing you can do

0:17:00.680 --> 0:17:03.720
<v Speaker 1>is is maybe it's funny. I always tell people to

0:17:03.720 --> 0:17:05.719
<v Speaker 1>take this approach when they're talking to their manager. When

0:17:05.760 --> 0:17:07.520
<v Speaker 1>they want something from their manager and their word the

0:17:07.520 --> 0:17:10.840
<v Speaker 1>manager won't agree. I always say, ask for a limited

0:17:11.160 --> 0:17:14.160
<v Speaker 1>time experiment, because that's easier to get a yes too.

0:17:14.200 --> 0:17:16.520
<v Speaker 1>And I think there's a version of that that could

0:17:16.520 --> 0:17:19.120
<v Speaker 1>work for you here too, which is that I think

0:17:19.119 --> 0:17:20.920
<v Speaker 1>you might have better luck if you say to someone

0:17:21.440 --> 0:17:23.600
<v Speaker 1>who's about to go on vacation, who you know as

0:17:23.640 --> 0:17:26.760
<v Speaker 1>a workaholic, you could say you could talk about all

0:17:26.760 --> 0:17:29.960
<v Speaker 1>the reasons why this is important, and then you could say, um,

0:17:30.000 --> 0:17:32.040
<v Speaker 1>I know this might not be like a permanent change

0:17:32.080 --> 0:17:33.479
<v Speaker 1>that you want to make. I want to ask if

0:17:33.480 --> 0:17:35.680
<v Speaker 1>we can do it as an experiment this time, because

0:17:35.680 --> 0:17:37.120
<v Speaker 1>I think we can find a way to make it work.

0:17:37.640 --> 0:17:40.120
<v Speaker 1>Will you agree to see this trip as an experiment

0:17:40.160 --> 0:17:41.800
<v Speaker 1>and then we can see how it goes when you're back.

0:17:42.280 --> 0:17:44.520
<v Speaker 1>I think that's a good idea. I could definitely do that.

0:17:44.920 --> 0:17:46.960
<v Speaker 1>It's so much easier for people to commit to that

0:17:47.080 --> 0:17:49.480
<v Speaker 1>than to commit to what might feel like a really

0:17:49.480 --> 0:17:52.000
<v Speaker 1>fundamental change in the way that they relate to work.

0:17:52.600 --> 0:17:55.080
<v Speaker 1>Mm hmm, that's true. I want to go back to

0:17:55.119 --> 0:17:59.240
<v Speaker 1>something you said earlier about your boss never sleeping, because

0:17:59.800 --> 0:18:03.280
<v Speaker 1>I can understand why that would would unsettle you a bit.

0:18:03.320 --> 0:18:05.560
<v Speaker 1>And even if your boss has been very explicit about

0:18:05.600 --> 0:18:09.399
<v Speaker 1>not expecting that of you, I mean, our bosses model

0:18:09.800 --> 0:18:15.199
<v Speaker 1>stuff for us, and that's hard. Um My strong suspicion

0:18:15.440 --> 0:18:17.520
<v Speaker 1>is that if you have seen evidence in other ways

0:18:17.560 --> 0:18:20.479
<v Speaker 1>that your boss is a reasonable person, that they probably

0:18:20.480 --> 0:18:22.520
<v Speaker 1>do not, in fact expect you to only sleep three

0:18:22.520 --> 0:18:25.640
<v Speaker 1>hours and night too. But I think if you're ever

0:18:25.720 --> 0:18:28.439
<v Speaker 1>feeling weird about it. You could tackle that head on.

0:18:28.680 --> 0:18:31.000
<v Speaker 1>I mean, you could say, you know, I've been thinking

0:18:31.040 --> 0:18:32.920
<v Speaker 1>about these workload issues on my team. I'm trying to

0:18:32.920 --> 0:18:34.760
<v Speaker 1>find ways to make sure that people are actually coming

0:18:34.800 --> 0:18:37.840
<v Speaker 1>to work well arrested, because I want them not burning

0:18:37.880 --> 0:18:40.399
<v Speaker 1>out and I want to be able to retain people

0:18:40.520 --> 0:18:42.640
<v Speaker 1>in the long term and have them doing their best work.

0:18:42.800 --> 0:18:44.359
<v Speaker 1>I mean, you might not even need to explain all

0:18:44.359 --> 0:18:46.040
<v Speaker 1>that it might be. It might be obvious, but if

0:18:46.080 --> 0:18:48.120
<v Speaker 1>you feel like in your culture you need to explain

0:18:48.160 --> 0:18:51.320
<v Speaker 1>it and do um and then you could say, you know,

0:18:51.359 --> 0:18:54.520
<v Speaker 1>it hasn't escaped my notice that you sleep hardly at all,

0:18:54.800 --> 0:18:57.360
<v Speaker 1>and sometimes it can. I worry that it will make

0:18:57.560 --> 0:19:00.719
<v Speaker 1>me or other people on our team feel like they

0:19:00.760 --> 0:19:03.359
<v Speaker 1>don't really have standing to say, Hey, I really need

0:19:03.400 --> 0:19:04.960
<v Speaker 1>a full night's sleep, and I just want to check

0:19:05.000 --> 0:19:06.879
<v Speaker 1>that with you and make sure that I'm being crazy

0:19:06.960 --> 0:19:09.919
<v Speaker 1>in thinking this, and I suspect you will get reassurance.

0:19:10.320 --> 0:19:13.919
<v Speaker 1>I suspect so as well. And I I hadn't thought

0:19:14.160 --> 0:19:16.960
<v Speaker 1>until you said that about the impact that his schedule

0:19:18.200 --> 0:19:21.120
<v Speaker 1>and his habits probably have on my team, even though

0:19:21.440 --> 0:19:25.439
<v Speaker 1>they're insulated both by distance and now by me. Because

0:19:25.480 --> 0:19:29.160
<v Speaker 1>for a long time in the absence of my predecessor,

0:19:29.240 --> 0:19:33.600
<v Speaker 1>they were not reporting to him, but working more closely

0:19:33.640 --> 0:19:37.320
<v Speaker 1>directly with him. And I bet his habits and his

0:19:37.520 --> 0:19:40.399
<v Speaker 1>needs had a strong impact on them. And I you know,

0:19:40.440 --> 0:19:41.840
<v Speaker 1>I know you raised this at the beginning, but I

0:19:41.840 --> 0:19:46.080
<v Speaker 1>think you're probably I think you're probably right. UM. I

0:19:46.080 --> 0:19:48.080
<v Speaker 1>don't mean to sound a surprise. I think you're probably

0:19:48.119 --> 0:19:51.760
<v Speaker 1>right that that that probably had an impact on the

0:19:52.480 --> 0:19:56.080
<v Speaker 1>on the culture here too. And it also reminds me, frankly,

0:19:56.119 --> 0:19:59.040
<v Speaker 1>and this is something I wonder about. I know, as

0:19:59.080 --> 0:20:03.280
<v Speaker 1>a manager it's important to model what you want your

0:20:03.280 --> 0:20:07.000
<v Speaker 1>staff to do. UM. And I try to. I stick

0:20:07.200 --> 0:20:10.120
<v Speaker 1>very firmly to when I leave every day, in part

0:20:10.160 --> 0:20:15.640
<v Speaker 1>because I have a small child, but I do work

0:20:15.680 --> 0:20:18.760
<v Speaker 1>in the evenings, and I have told my team explicitly,

0:20:20.080 --> 0:20:22.800
<v Speaker 1>you know, I have to work sometimes in the evenings.

0:20:22.840 --> 0:20:24.600
<v Speaker 1>I have a little bit of a shorter day because

0:20:24.600 --> 0:20:27.199
<v Speaker 1>I have to be able to do daycare, etcetera. UM,

0:20:27.240 --> 0:20:29.040
<v Speaker 1>if you need the accommodations of these kinds, you know,

0:20:29.080 --> 0:20:31.080
<v Speaker 1>I'm happy to work with you on them too. But

0:20:31.200 --> 0:20:33.360
<v Speaker 1>if you get an email from me at night, it's

0:20:33.400 --> 0:20:35.359
<v Speaker 1>just because I'm getting the work done. I do not

0:20:35.440 --> 0:20:39.080
<v Speaker 1>expect you to respond to it, um, but I wonder

0:20:39.119 --> 0:20:43.200
<v Speaker 1>about the impact of those emails on on them, and

0:20:43.240 --> 0:20:45.399
<v Speaker 1>so I've tried to say something similar about the mode

0:20:45.400 --> 0:20:49.240
<v Speaker 1>of communication. You know that if I send you a

0:20:49.320 --> 0:20:52.480
<v Speaker 1>text in the evening, so it's not actually texting, but

0:20:52.600 --> 0:20:54.960
<v Speaker 1>some kind of message in the evening, that's you know,

0:20:55.000 --> 0:20:57.080
<v Speaker 1>that's how I'll communicates in the urgent. But please don't

0:20:57.240 --> 0:21:00.560
<v Speaker 1>respond to or feel that I am asking you to

0:21:00.640 --> 0:21:05.000
<v Speaker 1>respond to email. But it's a complicated situation because I

0:21:05.359 --> 0:21:06.800
<v Speaker 1>do have to get that work done to get my

0:21:06.840 --> 0:21:09.760
<v Speaker 1>work done, and as the head of this office, that

0:21:09.920 --> 0:21:12.960
<v Speaker 1>just is my responsibility. But I don't want it to

0:21:12.960 --> 0:21:15.840
<v Speaker 1>trickle down to my team. And as we're when we're

0:21:15.840 --> 0:21:18.240
<v Speaker 1>in busy periods of time and I am working, you know,

0:21:18.240 --> 0:21:20.560
<v Speaker 1>a number of nights during the week, I worry about

0:21:20.560 --> 0:21:24.879
<v Speaker 1>that impact. I used to send emails to my staff

0:21:25.040 --> 0:21:27.159
<v Speaker 1>really late at night, like two or three am, because

0:21:27.240 --> 0:21:29.159
<v Speaker 1>I am just like a weird night owl and I

0:21:29.200 --> 0:21:32.320
<v Speaker 1>am just highly productive at strange hours. And it took

0:21:32.320 --> 0:21:34.800
<v Speaker 1>me a long time to realize that I was freaking

0:21:34.880 --> 0:21:37.760
<v Speaker 1>people out because we're getting work emails from me at

0:21:37.760 --> 0:21:41.080
<v Speaker 1>two I am, and I I did two things. I

0:21:41.080 --> 0:21:44.760
<v Speaker 1>started being much more explicit with people, um about just

0:21:44.880 --> 0:21:47.280
<v Speaker 1>as you have that I'm just up and working then

0:21:47.280 --> 0:21:49.520
<v Speaker 1>because it's my choice, but I'm certainly not expecting anyone

0:21:49.560 --> 0:21:51.720
<v Speaker 1>to respond before they get into the office the next morning.

0:21:52.000 --> 0:21:54.800
<v Speaker 1>But also I had to start saving them as drafts

0:21:55.200 --> 0:21:58.359
<v Speaker 1>and sending them the next morning. Um yeah, because some

0:21:58.400 --> 0:22:00.639
<v Speaker 1>people just never believe it. I think, regardless of what

0:22:00.680 --> 0:22:03.320
<v Speaker 1>you say, um So, I mean there might be some

0:22:03.359 --> 0:22:06.119
<v Speaker 1>work around like that. Sometimes it doesn't make sense for

0:22:06.119 --> 0:22:08.040
<v Speaker 1>the work, especially if you're working with people in lots

0:22:08.080 --> 0:22:09.639
<v Speaker 1>of different times and you might not be able to

0:22:09.680 --> 0:22:11.159
<v Speaker 1>wait to send the email and you might need to

0:22:11.160 --> 0:22:13.879
<v Speaker 1>send it. Then I think probably for you, it's going

0:22:13.920 --> 0:22:17.560
<v Speaker 1>to be just a lot of explicit talking to people

0:22:17.680 --> 0:22:20.359
<v Speaker 1>and reminding them. And if you are really reinforcing, you know,

0:22:20.359 --> 0:22:23.639
<v Speaker 1>if it's one conversation, they might think you okay maybe

0:22:23.680 --> 0:22:26.919
<v Speaker 1>and then promptly forget about it. But if you're reinforcing it,

0:22:27.040 --> 0:22:29.119
<v Speaker 1>if you're talking about it in an ongoing basis, I

0:22:29.160 --> 0:22:31.120
<v Speaker 1>mean not every day, that's going to be weird, but

0:22:31.119 --> 0:22:33.440
<v Speaker 1>but you know, on an ongoing basis and it's coming

0:22:33.480 --> 0:22:36.080
<v Speaker 1>up and you're reminding people, I think it will start

0:22:36.119 --> 0:22:40.119
<v Speaker 1>to feel more real. And the other thing I would

0:22:40.119 --> 0:22:43.879
<v Speaker 1>say is I would lay all of this out for

0:22:43.920 --> 0:22:46.520
<v Speaker 1>your team and talk to them about it and say like,

0:22:46.560 --> 0:22:49.359
<v Speaker 1>here's what I'm seeing. These are the reasons that I

0:22:49.440 --> 0:22:51.080
<v Speaker 1>know are in play. So you don't want to sound

0:22:51.200 --> 0:22:52.920
<v Speaker 1>obviously like you're completely out of touch. You want to

0:22:52.960 --> 0:22:55.119
<v Speaker 1>make it clear you do recognize that this is the

0:22:55.119 --> 0:22:57.720
<v Speaker 1>culture and there are all of these pressures on them,

0:22:58.080 --> 0:23:01.680
<v Speaker 1>but that your sense is still that even within that context,

0:23:02.240 --> 0:23:05.080
<v Speaker 1>people are too connected to work when they don't need

0:23:05.119 --> 0:23:09.000
<v Speaker 1>to be, and ask for their input about what might help,

0:23:09.040 --> 0:23:11.600
<v Speaker 1>because there might be obstacles to solving this that you

0:23:11.640 --> 0:23:14.600
<v Speaker 1>don't even realize, and hearing their perspective would probably be

0:23:14.640 --> 0:23:17.720
<v Speaker 1>really helpful. Yeah, I think that's a good idea. I

0:23:18.200 --> 0:23:21.479
<v Speaker 1>don't know that I've done that enough lately, And and

0:23:21.520 --> 0:23:23.640
<v Speaker 1>I think one of the things that has made me

0:23:24.880 --> 0:23:28.200
<v Speaker 1>worry about it in coming into a sort of already

0:23:28.200 --> 0:23:32.520
<v Speaker 1>existing structure and culture is that what if their jobs

0:23:32.520 --> 0:23:34.560
<v Speaker 1>are just a lot harder than I realized and it's

0:23:34.600 --> 0:23:37.680
<v Speaker 1>really taking them this amount of time, in which case

0:23:38.560 --> 0:23:40.399
<v Speaker 1>are they going to tell me that, you know, are

0:23:40.440 --> 0:23:43.000
<v Speaker 1>they going to be upfront about it? Are they going

0:23:43.040 --> 0:23:45.840
<v Speaker 1>to end up feeling bad or inefficient about the way

0:23:45.880 --> 0:23:47.919
<v Speaker 1>they're doing their work. There's a point at which I

0:23:47.960 --> 0:23:50.080
<v Speaker 1>start to worry about looking like I don't know what

0:23:50.200 --> 0:23:52.280
<v Speaker 1>their lives are like, and actually not knowing what their

0:23:52.320 --> 0:23:54.880
<v Speaker 1>lives are like. We'll pause here for a quick word

0:23:54.920 --> 0:24:05.480
<v Speaker 1>from a sponsor and then we'll come right back. When

0:24:05.520 --> 0:24:07.360
<v Speaker 1>you see, people are working long hours, So what kind

0:24:07.400 --> 0:24:09.440
<v Speaker 1>of hours are we talking about, Like in an average week,

0:24:09.440 --> 0:24:13.040
<v Speaker 1>what do you think people are working? Um, I think

0:24:13.440 --> 0:24:15.000
<v Speaker 1>so it's hard to me. It's hard for me to

0:24:15.040 --> 0:24:18.639
<v Speaker 1>actually know because I do leave the office because I

0:24:18.680 --> 0:24:21.200
<v Speaker 1>have to, so I don't always know when they leave.

0:24:21.920 --> 0:24:26.280
<v Speaker 1>But I have, for example, a staff member who basically

0:24:26.320 --> 0:24:29.960
<v Speaker 1>doesn't have internet at home. UM. It's just it's a

0:24:30.040 --> 0:24:33.520
<v Speaker 1>very bad connection, and I will regularly get emails from

0:24:33.560 --> 0:24:38.040
<v Speaker 1>him at seven thirty at night. UM. And I realized

0:24:38.200 --> 0:24:40.720
<v Speaker 1>right that if you work in consulting, the day of

0:24:40.720 --> 0:24:43.680
<v Speaker 1>seven thirty at night is joyous. But if you work

0:24:44.240 --> 0:24:47.840
<v Speaker 1>for a nonprofit and you're making what you make at

0:24:47.840 --> 0:24:51.480
<v Speaker 1>a nonprofit, and you're doing this regularly and also not

0:24:51.600 --> 0:24:55.280
<v Speaker 1>taking any of your paid time off, this is a problem,

0:24:55.320 --> 0:24:57.840
<v Speaker 1>or at least I feel like it's a problem. I

0:24:57.880 --> 0:25:03.000
<v Speaker 1>have another staff member who I think starts working her

0:25:03.040 --> 0:25:07.200
<v Speaker 1>work week on Sunday morning every weekend, and I'm getting

0:25:07.240 --> 0:25:12.800
<v Speaker 1>emails from six am two thirty am off and on

0:25:12.800 --> 0:25:17.600
<v Speaker 1>on the weekdays. Okay, yeah, I so yeah. I think

0:25:17.640 --> 0:25:19.320
<v Speaker 1>one of the issues that you want to get a

0:25:19.359 --> 0:25:23.800
<v Speaker 1>handle on here is is the workload forcing them into

0:25:23.840 --> 0:25:28.320
<v Speaker 1>this and do they legitimately feel like if they pulled back,

0:25:29.240 --> 0:25:31.760
<v Speaker 1>they would miss deadlines and important things would go undone.

0:25:31.840 --> 0:25:35.120
<v Speaker 1>Because if that is the case, then the solution isn't

0:25:35.160 --> 0:25:37.879
<v Speaker 1>just telling them, hey, workless, um. In that case, you

0:25:37.920 --> 0:25:40.000
<v Speaker 1>would have to take a bigger picture, look at the

0:25:40.000 --> 0:25:42.919
<v Speaker 1>workload and figure out do you need to cut projects,

0:25:42.960 --> 0:25:44.679
<v Speaker 1>do you need to bring it more staff, do you

0:25:44.680 --> 0:25:47.159
<v Speaker 1>need to backburner things? There would need to be some

0:25:47.240 --> 0:25:50.280
<v Speaker 1>solution that's outside of their control, but hopefully is in

0:25:50.320 --> 0:25:54.359
<v Speaker 1>your control. So it might be worth sitting down individually

0:25:54.359 --> 0:25:57.240
<v Speaker 1>with people or at least the ones where, like definitely

0:25:57.280 --> 0:25:59.399
<v Speaker 1>the person who seems to be working all day Sunday, UM,

0:26:00.040 --> 0:26:02.040
<v Speaker 1>lose the ones where you think that the problem seems

0:26:02.040 --> 0:26:05.880
<v Speaker 1>the most pronounced, and explain that you are concerned about

0:26:05.880 --> 0:26:07.639
<v Speaker 1>how high the workload seems to be and that you

0:26:07.680 --> 0:26:11.399
<v Speaker 1>want to get more nuanced understanding of exactly what's on

0:26:11.440 --> 0:26:14.439
<v Speaker 1>their point so that you're better able to figure out solutions,

0:26:14.560 --> 0:26:18.160
<v Speaker 1>and then maybe have them walk you through what's going

0:26:18.200 --> 0:26:22.480
<v Speaker 1>on at a pretty nitty gritty level. So maybe like

0:26:22.520 --> 0:26:24.760
<v Speaker 1>take ask them to walk you through what they're juggling

0:26:24.760 --> 0:26:27.720
<v Speaker 1>this week and how long things are taking and why.

0:26:28.160 --> 0:26:29.840
<v Speaker 1>When you do it, you want to be careful not

0:26:29.880 --> 0:26:31.360
<v Speaker 1>to put people in the defense of like you don't

0:26:31.359 --> 0:26:33.520
<v Speaker 1>want them to feel like you're questioning whether they're efficient

0:26:33.720 --> 0:26:35.920
<v Speaker 1>enough or not, So you you need to be really

0:26:35.960 --> 0:26:39.600
<v Speaker 1>explicit that you're seeking to understand, not looking for It's

0:26:39.600 --> 0:26:41.640
<v Speaker 1>not like a gotcha, you're not looking for a problem

0:26:41.640 --> 0:26:43.600
<v Speaker 1>with the way that they work. But if you get

0:26:43.600 --> 0:26:46.200
<v Speaker 1>really into the weeds, I think you'll be better equipped

0:26:46.200 --> 0:26:49.600
<v Speaker 1>to judge, oh, yes, this is just an insanely high workload,

0:26:49.880 --> 0:26:52.639
<v Speaker 1>or maybe it's not. But you also might realize when

0:26:52.640 --> 0:26:55.320
<v Speaker 1>you do that that there are some obvious places where

0:26:55.359 --> 0:26:57.240
<v Speaker 1>you could cut back. Like to give you an example

0:26:57.240 --> 0:26:59.439
<v Speaker 1>of what I mean, if you really dig into it,

0:26:59.480 --> 0:27:02.400
<v Speaker 1>you might really lies someone is putting hours every week

0:27:02.400 --> 0:27:05.200
<v Speaker 1>into something that actually doesn't need to be that high

0:27:05.200 --> 0:27:08.320
<v Speaker 1>of a priority, or that they're putting hours into getting

0:27:08.320 --> 0:27:10.720
<v Speaker 1>something perfect when they could put in twenty of the

0:27:10.760 --> 0:27:13.040
<v Speaker 1>time and have it be good enough. But maybe they

0:27:13.040 --> 0:27:16.040
<v Speaker 1>don't know that because it's never been discussed. Um or

0:27:16.080 --> 0:27:18.160
<v Speaker 1>you might find there some kind of like system problem,

0:27:18.200 --> 0:27:20.520
<v Speaker 1>like maybe someone can't move something forward until they get

0:27:20.520 --> 0:27:23.359
<v Speaker 1>input from another team and that other team is constantly

0:27:23.359 --> 0:27:25.880
<v Speaker 1>a roadblock, or or who knows. I mean, we can't

0:27:25.880 --> 0:27:27.480
<v Speaker 1>predict it. But I think if you dig in with

0:27:27.520 --> 0:27:30.919
<v Speaker 1>an eye toward thinking about whether things have to be

0:27:30.960 --> 0:27:33.600
<v Speaker 1>done the way they're happening now, or whether there might

0:27:33.640 --> 0:27:35.960
<v Speaker 1>be shortcuts that would be okay for people to take,

0:27:36.080 --> 0:27:38.359
<v Speaker 1>or even whole projects that could be put on the

0:27:38.400 --> 0:27:42.439
<v Speaker 1>back burner temporarily or forever, or or you might come

0:27:42.440 --> 0:27:45.720
<v Speaker 1>away thinking, Okay, yeah, this is a really insanely high

0:27:45.720 --> 0:27:48.720
<v Speaker 1>workload and there aren't any obvious easy ways to lighten

0:27:48.760 --> 0:27:52.280
<v Speaker 1>anyone's burden here. But even that last thing, I mean,

0:27:52.280 --> 0:27:54.760
<v Speaker 1>that's the hardest one to handle. But that at least

0:27:54.760 --> 0:27:57.800
<v Speaker 1>tells you the solution isn't that I just keep nudging

0:27:57.800 --> 0:27:59.960
<v Speaker 1>people to work less. The solution has to be something

0:28:00.080 --> 0:28:04.080
<v Speaker 1>in that you're working out with your management, right. I

0:28:04.119 --> 0:28:05.879
<v Speaker 1>think if you do that, you'll come away with more

0:28:05.920 --> 0:28:08.800
<v Speaker 1>information about what's going on. And also that's a good

0:28:08.840 --> 0:28:11.160
<v Speaker 1>time to ask people for input too, And you might

0:28:11.240 --> 0:28:15.480
<v Speaker 1>even ask them whether they can identify places where they

0:28:15.600 --> 0:28:17.479
<v Speaker 1>or other people could be cutting back, because they might

0:28:17.480 --> 0:28:20.879
<v Speaker 1>have opinions that they've kept to themselves about a program

0:28:20.880 --> 0:28:23.720
<v Speaker 1>not having much impact or not being worth the energy

0:28:23.760 --> 0:28:26.359
<v Speaker 1>that gets put into it, or a process being really

0:28:26.400 --> 0:28:29.399
<v Speaker 1>onerous that maybe the old manager didn't want to change

0:28:29.400 --> 0:28:31.560
<v Speaker 1>and so everyone's just kept doing it, or or who

0:28:31.600 --> 0:28:34.840
<v Speaker 1>knows what. But I think having those conversations and explicitly

0:28:34.880 --> 0:28:38.440
<v Speaker 1>asking for that can maybe draw some of that out.

0:28:38.480 --> 0:28:40.600
<v Speaker 1>If there is anything like that, I think that's a

0:28:40.640 --> 0:28:44.120
<v Speaker 1>great idea. If that's not something I had thought of about,

0:28:44.360 --> 0:28:46.520
<v Speaker 1>you know, are there places they see that can be

0:28:47.120 --> 0:28:50.680
<v Speaker 1>simplified or that aren't having impact? And I do think

0:28:50.720 --> 0:28:54.080
<v Speaker 1>that just because of the particularities or a situation, it

0:28:54.120 --> 0:28:59.160
<v Speaker 1>took them sort of many months to trust that when

0:28:59.200 --> 0:29:01.880
<v Speaker 1>I said, you know, I'm concerned about the amount you're working,

0:29:02.080 --> 0:29:05.240
<v Speaker 1>it wasn't in any way having to do with their

0:29:05.280 --> 0:29:08.600
<v Speaker 1>performance or that I wasn't sort of lowering them into

0:29:08.640 --> 0:29:11.200
<v Speaker 1>a trap where I was going to yell at them. Um.

0:29:11.240 --> 0:29:12.880
<v Speaker 1>But I think I've been here long enough now that

0:29:12.920 --> 0:29:16.680
<v Speaker 1>they they feel a little more secure. Um, and so

0:29:16.720 --> 0:29:18.240
<v Speaker 1>this might be a good time to have to start

0:29:18.280 --> 0:29:21.800
<v Speaker 1>having those conversations. Yeah, I like that a lot. And

0:29:21.840 --> 0:29:24.800
<v Speaker 1>I think also it might be there's so many things

0:29:24.840 --> 0:29:26.200
<v Speaker 1>that could be at play here, and I think you're

0:29:26.200 --> 0:29:27.600
<v Speaker 1>going to get to most of them if you do

0:29:27.680 --> 0:29:30.280
<v Speaker 1>this kind of really digging into it. But another one

0:29:30.400 --> 0:29:33.680
<v Speaker 1>could be and this is so common in nonprofits where

0:29:33.680 --> 0:29:36.320
<v Speaker 1>there's like this ethos of if something seems like a

0:29:36.320 --> 0:29:38.520
<v Speaker 1>worthy project, let's just find a way to fit it in.

0:29:39.040 --> 0:29:41.680
<v Speaker 1>So you could have a team of horribly overworked people

0:29:41.680 --> 0:29:44.240
<v Speaker 1>who aren't saying no to anything new that comes up

0:29:44.400 --> 0:29:47.880
<v Speaker 1>because something their played is full. Something new comes up,

0:29:47.920 --> 0:29:49.800
<v Speaker 1>it feels like it would be worthy and have a

0:29:49.880 --> 0:29:53.120
<v Speaker 1>valuable impact, and so they just take it on without

0:29:53.200 --> 0:29:55.200
<v Speaker 1>looking for, well, what are we going to cut to

0:29:55.240 --> 0:29:58.400
<v Speaker 1>make room for this? Um. That happens in every sector,

0:29:58.480 --> 0:30:00.280
<v Speaker 1>but oh my god, it happens in non off it

0:30:00.480 --> 0:30:03.360
<v Speaker 1>so much so you might need to do some work

0:30:03.400 --> 0:30:07.040
<v Speaker 1>on resetting your team's culture in that regard and training

0:30:07.080 --> 0:30:09.760
<v Speaker 1>people that when they or your team as a whole

0:30:09.800 --> 0:30:12.680
<v Speaker 1>is taking on something new. You talk about where the

0:30:12.680 --> 0:30:14.520
<v Speaker 1>time for it is going to come from that. The

0:30:14.560 --> 0:30:17.360
<v Speaker 1>assumption isn't just oh, you'll pile this on top of

0:30:17.400 --> 0:30:20.720
<v Speaker 1>the already overwhelming pile that you already have. That you'll

0:30:20.760 --> 0:30:22.600
<v Speaker 1>talk about what to cut or what to push back

0:30:23.000 --> 0:30:25.640
<v Speaker 1>to make room for it. And that is something that

0:30:25.880 --> 0:30:27.520
<v Speaker 1>very much has to come from you. They're gonna have

0:30:27.560 --> 0:30:30.160
<v Speaker 1>to see you asking that question every time and then

0:30:30.200 --> 0:30:33.600
<v Speaker 1>backing it up by actually helping them cut things so

0:30:33.600 --> 0:30:35.320
<v Speaker 1>that they know that you really mean it and it's

0:30:35.360 --> 0:30:39.520
<v Speaker 1>not just lip service. Yes, I I agree so much.

0:30:39.560 --> 0:30:42.840
<v Speaker 1>And I'm just thinking about the once or twice where

0:30:42.880 --> 0:30:45.920
<v Speaker 1>I've had someone say to me when of my teams say,

0:30:46.040 --> 0:30:48.080
<v Speaker 1>can you help me figure out how to prioritize this?

0:30:48.640 --> 0:30:52.240
<v Speaker 1>And I see that as this window into I don't

0:30:52.240 --> 0:30:54.280
<v Speaker 1>know how I'm going to get this done? How do

0:30:54.320 --> 0:30:56.280
<v Speaker 1>you want to get this done? Like? What do you

0:30:56.280 --> 0:30:59.080
<v Speaker 1>want me to not do? So I do this? Which

0:30:59.120 --> 0:31:02.200
<v Speaker 1>I think is great right that someone's coming and saying

0:31:02.200 --> 0:31:03.880
<v Speaker 1>that to me, But I think I probably do need

0:31:03.920 --> 0:31:07.680
<v Speaker 1>to give that opening a lot more um And I

0:31:07.720 --> 0:31:09.160
<v Speaker 1>think that was at least the beauty of having this

0:31:09.200 --> 0:31:12.120
<v Speaker 1>new staff members start who was able to take projects

0:31:12.600 --> 0:31:16.840
<v Speaker 1>off of our let's say are most burdened, do you remember. Yeah,

0:31:16.960 --> 0:31:19.360
<v Speaker 1>And I might even start, just like make a little

0:31:19.360 --> 0:31:22.440
<v Speaker 1>note for yourself that every time something new comes up

0:31:22.480 --> 0:31:25.640
<v Speaker 1>that someone is taking on, maybe for the next few months,

0:31:25.640 --> 0:31:27.680
<v Speaker 1>say to them, what do we need to cut to

0:31:27.680 --> 0:31:28.960
<v Speaker 1>make room for this? Or what do we need to

0:31:28.960 --> 0:31:31.440
<v Speaker 1>push back to make room for this? Because they might

0:31:31.440 --> 0:31:33.880
<v Speaker 1>not even give you the opening on their own, because

0:31:33.920 --> 0:31:37.440
<v Speaker 1>they might not even be thinking that that is a possibility. Yeah,

0:31:37.760 --> 0:31:41.440
<v Speaker 1>I think that's true. I think the the expectation and

0:31:41.520 --> 0:31:44.320
<v Speaker 1>just the feeling around here, especially because how mission driven

0:31:44.360 --> 0:31:46.280
<v Speaker 1>we are, is if this is the thing we need

0:31:46.320 --> 0:31:49.160
<v Speaker 1>to do to make possible what we need to make

0:31:49.200 --> 0:31:51.720
<v Speaker 1>possible for the clients, then we'll find a way to

0:31:51.720 --> 0:31:56.680
<v Speaker 1>do it. And I know that I'm not always as

0:31:56.720 --> 0:31:59.280
<v Speaker 1>good as I could be about modeling that in my

0:31:59.320 --> 0:32:01.680
<v Speaker 1>own workload. I mean, I think I do it a

0:32:01.680 --> 0:32:03.320
<v Speaker 1>good deal all the time, but I think for my

0:32:03.360 --> 0:32:06.000
<v Speaker 1>own insecurities or whatever reason, I don't do it all

0:32:06.040 --> 0:32:09.400
<v Speaker 1>the time that I should um to my bosster, to

0:32:09.480 --> 0:32:13.560
<v Speaker 1>my board, and so giving them explicitly the opportunity is

0:32:13.600 --> 0:32:16.800
<v Speaker 1>going to be important. Yeah, And I think to you,

0:32:16.840 --> 0:32:19.040
<v Speaker 1>I mean, we all sort of inadvertently fall into this

0:32:19.120 --> 0:32:21.880
<v Speaker 1>thing where we assume that if someone is asking us

0:32:21.880 --> 0:32:24.560
<v Speaker 1>to do something, they must expect us to make the time,

0:32:25.240 --> 0:32:27.200
<v Speaker 1>and they must know all the other things that are

0:32:27.240 --> 0:32:29.360
<v Speaker 1>on there our plate, and if they're putting this on

0:32:29.400 --> 0:32:31.560
<v Speaker 1>there too, we're just expected to handle all of it.

0:32:31.640 --> 0:32:34.719
<v Speaker 1>But so often we train people to think that because

0:32:35.000 --> 0:32:39.600
<v Speaker 1>we don't speak up right, right, I agree? Is it

0:32:39.720 --> 0:32:42.160
<v Speaker 1>helpful to talk about, like, if you do take a

0:32:42.200 --> 0:32:45.480
<v Speaker 1>look at this and you realize it's just an insanely

0:32:45.680 --> 0:32:48.280
<v Speaker 1>crushing workload and there isn't a lot that people can

0:32:48.320 --> 0:32:50.440
<v Speaker 1>do about it, Is it helpful to talk a little

0:32:50.480 --> 0:32:54.240
<v Speaker 1>bit about what to do if that is what you realize. Yes,

0:32:54.360 --> 0:32:57.400
<v Speaker 1>because I think that might be the case, and in

0:32:57.440 --> 0:33:01.120
<v Speaker 1>at least one situation. Okay, so if you do what

0:33:01.160 --> 0:33:03.280
<v Speaker 1>we were talking about earlier, you sit down with people,

0:33:03.480 --> 0:33:05.560
<v Speaker 1>you have them really walk you through like this week

0:33:05.640 --> 0:33:07.280
<v Speaker 1>or this month, and you try to really get a

0:33:07.320 --> 0:33:11.000
<v Speaker 1>feel for how much time does stuff take, and you

0:33:11.040 --> 0:33:12.840
<v Speaker 1>take out all the stuff where you realize, oh, here's

0:33:12.840 --> 0:33:15.200
<v Speaker 1>an inefficient and an inefficiency we could cut this out,

0:33:15.520 --> 0:33:18.440
<v Speaker 1>and then you're left with still this whole pile of work.

0:33:19.160 --> 0:33:22.520
<v Speaker 1>So I think ideally you would do that for everyone

0:33:22.520 --> 0:33:24.520
<v Speaker 1>on your team or close to everyone on your team,

0:33:24.520 --> 0:33:26.280
<v Speaker 1>so that you have this whole long list of all

0:33:26.360 --> 0:33:28.040
<v Speaker 1>the stuff that has to be done and roughly how

0:33:28.120 --> 0:33:31.680
<v Speaker 1>much time stuff takes. And then so I would take

0:33:31.720 --> 0:33:35.080
<v Speaker 1>that information and then I would write out a reasonable

0:33:35.080 --> 0:33:38.040
<v Speaker 1>work allocation for each people, So taking all the stuff

0:33:38.080 --> 0:33:40.320
<v Speaker 1>from that long, that big pile of work and assigning

0:33:40.360 --> 0:33:43.400
<v Speaker 1>to each person in order of how important things are

0:33:43.920 --> 0:33:46.800
<v Speaker 1>each of those items, and then stop when each person

0:33:46.880 --> 0:33:49.480
<v Speaker 1>has a list that represents a full workload. So maybe

0:33:49.480 --> 0:33:51.080
<v Speaker 1>for you guys, it's not forty hours a week. Maybe

0:33:51.120 --> 0:33:52.920
<v Speaker 1>it's forty five, maybe it's fifty. I don't know what

0:33:53.320 --> 0:33:54.720
<v Speaker 1>number it is that you want to get to, but

0:33:54.960 --> 0:33:57.120
<v Speaker 1>it's probably less than what it is now, whatever that

0:33:57.200 --> 0:34:01.080
<v Speaker 1>number is, stop your list when each per since is full,

0:34:01.400 --> 0:34:03.800
<v Speaker 1>and then see what is left over. And if you

0:34:03.880 --> 0:34:05.960
<v Speaker 1>have a bunch of stuff left over that did not

0:34:06.040 --> 0:34:08.239
<v Speaker 1>fit at anyone's plate, and I suspect that you will,

0:34:09.000 --> 0:34:10.880
<v Speaker 1>then there is your list of the stuff that your

0:34:10.920 --> 0:34:14.080
<v Speaker 1>team doesn't actually have time to do but is cramming

0:34:14.080 --> 0:34:17.480
<v Speaker 1>in anyway, and and there's your problem. So at that point,

0:34:17.640 --> 0:34:19.680
<v Speaker 1>you could reshuffle some of the things on that list.

0:34:19.719 --> 0:34:21.839
<v Speaker 1>You could take some things off and put some things on.

0:34:22.280 --> 0:34:23.759
<v Speaker 1>You could decide that some are going to come off

0:34:23.800 --> 0:34:27.399
<v Speaker 1>the list altogether. But at some point you might need

0:34:27.480 --> 0:34:30.000
<v Speaker 1>and I suspect you will find that you're probably at

0:34:30.000 --> 0:34:31.920
<v Speaker 1>this point you would need to bring your own boss

0:34:31.920 --> 0:34:34.960
<v Speaker 1>into the conversation. Like if you were contemplating cutting things entirely,

0:34:35.080 --> 0:34:36.799
<v Speaker 1>or if you're realizing, Okay, if we're going to do

0:34:36.840 --> 0:34:38.720
<v Speaker 1>all this, we need more people to get it done,

0:34:39.239 --> 0:34:41.560
<v Speaker 1>that's the point where you'd bring your own Boston. But

0:34:41.560 --> 0:34:43.879
<v Speaker 1>but when you did that, you would have this very

0:34:43.960 --> 0:34:46.440
<v Speaker 1>stark written illustration of what the problem was. So it

0:34:46.440 --> 0:34:49.440
<v Speaker 1>wouldn't just be this amorphous like, oh, people feel overworked.

0:34:49.880 --> 0:34:51.840
<v Speaker 1>It would be here's what people can get done in

0:34:51.880 --> 0:34:54.280
<v Speaker 1>forty five hours a week, and here's all the stuff

0:34:54.400 --> 0:34:57.480
<v Speaker 1>that is still happening on top of that. I think

0:34:57.520 --> 0:35:01.279
<v Speaker 1>that's incredibly helpful. Good it. Well, So do you feel

0:35:01.280 --> 0:35:03.400
<v Speaker 1>like you have some next steps to try to tackle this?

0:35:03.920 --> 0:35:06.000
<v Speaker 1>I do. I feel like I have a couple of

0:35:06.080 --> 0:35:08.160
<v Speaker 1>great next steps. Thanks for talking that through with me.

0:35:08.320 --> 0:35:10.359
<v Speaker 1>Thank you so much for coming on the show. It

0:35:10.400 --> 0:35:13.200
<v Speaker 1>was great to be here. This was a really helpful conversation.

0:35:14.440 --> 0:35:16.759
<v Speaker 1>Thanks for listening to the asking manager podcast. If you'd

0:35:16.760 --> 0:35:18.080
<v Speaker 1>like to come on the show to talk through your

0:35:18.080 --> 0:35:21.359
<v Speaker 1>own question, email it to podcast at Asking Manager dot org.

0:35:21.719 --> 0:35:23.520
<v Speaker 1>Or you can leave a recording of your question by

0:35:23.520 --> 0:35:26.799
<v Speaker 1>calling eight five five four T six work. That's eight

0:35:26.840 --> 0:35:29.839
<v Speaker 1>five five f T six nine seven five. You can

0:35:29.880 --> 0:35:32.040
<v Speaker 1>get more ask a Manager at ask a Manager dot

0:35:32.120 --> 0:35:34.160
<v Speaker 1>org or in my book Ask a Manager How to

0:35:34.280 --> 0:35:37.200
<v Speaker 1>navigate clueless colleagues, lunch stealing bosses, and the rest of

0:35:37.200 --> 0:35:39.440
<v Speaker 1>your life at work. The Ask a Manager shows a

0:35:39.480 --> 0:35:42.360
<v Speaker 1>partnership with How Stuff Works and is produced by Paul Deckett.

0:35:42.640 --> 0:35:44.240
<v Speaker 1>If you liked what you heard, please take a minute

0:35:44.239 --> 0:35:47.400
<v Speaker 1>to subscribe, rate, and review the show on Apple Podcasts,

0:35:47.440 --> 0:35:50.239
<v Speaker 1>Spotify or Google Play. I'm Alison Green and I'll be

0:35:50.280 --> 0:36:00.360
<v Speaker 1>back next week with another one of your questions. M H.