WEBVTT - How can I be a good manager?

0:00:03.560 --> 0:00:05.880
<v Speaker 1>My colleague, We'll stop commenting on everything I get my

0:00:05.880 --> 0:00:08.840
<v Speaker 1>assistant eyes at people and meeting. Why does my coworker

0:00:08.920 --> 0:00:11.240
<v Speaker 1>keep taking credit for all my ideas? Have any wisdom

0:00:11.280 --> 0:00:14.360
<v Speaker 1>for me? Hi? I'm Alison Green. Welcome to the Aska

0:00:14.400 --> 0:00:18.640
<v Speaker 1>Manager Podcast. Right answer questions from listeners about life at work,

0:00:19.120 --> 0:00:21.080
<v Speaker 1>everything from what to say if you're allergic to your

0:00:21.120 --> 0:00:23.599
<v Speaker 1>coworkers perfume to what to do if you drink too

0:00:23.680 --> 0:00:28.400
<v Speaker 1>much at the company party. Let's get started. Being a

0:00:28.440 --> 0:00:32.240
<v Speaker 1>good manager is hard. It's especially hard when you're new

0:00:32.280 --> 0:00:35.080
<v Speaker 1>to doing it, and managers often don't get a lot

0:00:35.080 --> 0:00:38.160
<v Speaker 1>of guidance, even though managing is usually a whole different

0:00:38.200 --> 0:00:41.520
<v Speaker 1>skill set from whatever they were doing previously. Our guest

0:00:41.600 --> 0:00:44.360
<v Speaker 1>today is a new ish manager who wants to make

0:00:44.400 --> 0:00:46.600
<v Speaker 1>sure she's doing a good job, and we're going to

0:00:46.640 --> 0:00:49.159
<v Speaker 1>talk through how she can make that happen. Hi, and

0:00:49.200 --> 0:00:52.599
<v Speaker 1>welcome to the show. Hi, Thank you so much so.

0:00:52.720 --> 0:00:55.160
<v Speaker 1>What you wrote to me is that you finished grad

0:00:55.200 --> 0:00:57.480
<v Speaker 1>school a couple of years ago, and you started a

0:00:57.480 --> 0:01:00.400
<v Speaker 1>company with a colleague and it's been more six assful

0:01:00.440 --> 0:01:03.160
<v Speaker 1>than you expected it to be. And now you have

0:01:03.400 --> 0:01:06.600
<v Speaker 1>three full time employees and some part time contractors. But

0:01:06.880 --> 0:01:09.319
<v Speaker 1>as you wrote before this, you had never had what

0:01:09.400 --> 0:01:11.959
<v Speaker 1>you would consider a real job, and suddenly you're a

0:01:12.000 --> 0:01:14.560
<v Speaker 1>manager and you're living in fear of being a bad one,

0:01:15.160 --> 0:01:17.480
<v Speaker 1>and you feel like things are good with your co founder,

0:01:17.560 --> 0:01:20.240
<v Speaker 1>but you're struggling with how to best manage your staff,

0:01:20.720 --> 0:01:24.120
<v Speaker 1>and you're not quite used to this boss employee dynamic

0:01:24.160 --> 0:01:27.720
<v Speaker 1>a by getting that all right, that's exactly right. And

0:01:27.800 --> 0:01:29.880
<v Speaker 1>you wrote when you first contacted me that some of

0:01:29.920 --> 0:01:33.920
<v Speaker 1>your biggest concerns are getting the balance right between being

0:01:33.959 --> 0:01:36.560
<v Speaker 1>a casual and fun place to work, but also making

0:01:36.600 --> 0:01:39.600
<v Speaker 1>sure that people respect you enough and understand that you're

0:01:39.600 --> 0:01:42.120
<v Speaker 1>making the final decisions. And you also want to be

0:01:42.160 --> 0:01:44.880
<v Speaker 1>sure that you're identifying any weaknesses that you might be

0:01:44.920 --> 0:01:48.720
<v Speaker 1>oblivious to, because it feels hard to get honest feedback,

0:01:48.800 --> 0:01:50.880
<v Speaker 1>especially from a small team, and you're not sure how

0:01:50.920 --> 0:01:54.200
<v Speaker 1>to solicit it, and more generally, just learning how to

0:01:54.240 --> 0:01:57.200
<v Speaker 1>be an effective manager. Does that all sound right? That's

0:01:57.200 --> 0:01:59.360
<v Speaker 1>all exactly right. Yeah. We work in like a tech

0:01:59.440 --> 0:02:02.360
<v Speaker 1>startup in a field where there's usually it's pretty casual

0:02:02.480 --> 0:02:05.400
<v Speaker 1>and fun, but obviously there's still lots of deadlines and

0:02:05.400 --> 0:02:07.080
<v Speaker 1>things that need to be done, and then we have

0:02:08.160 --> 0:02:10.240
<v Speaker 1>so far, really great staff, and I you know, it's

0:02:10.240 --> 0:02:12.480
<v Speaker 1>a very competitive field and I don't want to lose them,

0:02:12.480 --> 0:02:15.239
<v Speaker 1>So I'd hate to be oblivious to something terrible in

0:02:15.320 --> 0:02:18.760
<v Speaker 1>my managing style and then lose an employee. Yeah, well,

0:02:18.760 --> 0:02:20.520
<v Speaker 1>it's great that you're thinking about it, because so many

0:02:20.520 --> 0:02:23.160
<v Speaker 1>people don't even do that sort of reflection and then

0:02:23.160 --> 0:02:26.200
<v Speaker 1>we get lots of bad managers who people are writing about.

0:02:27.360 --> 0:02:30.360
<v Speaker 1>So before we jump into advice, tell me a little

0:02:30.360 --> 0:02:32.400
<v Speaker 1>bit about how things are going, Like, do you feel

0:02:32.480 --> 0:02:34.560
<v Speaker 1>like you're getting what you need from your staff and

0:02:34.720 --> 0:02:36.480
<v Speaker 1>just work get done the way you want it to

0:02:36.520 --> 0:02:39.320
<v Speaker 1>be done, and are you comfortable giving feedback that kind

0:02:39.360 --> 0:02:42.080
<v Speaker 1>of thing. I would say it's pretty good. Um, Like

0:02:42.120 --> 0:02:46.600
<v Speaker 1>the technical work is very strong. Sometimes it's hard to

0:02:47.800 --> 0:02:52.200
<v Speaker 1>know how to delegate exactly, how to how much responsibility

0:02:52.200 --> 0:02:55.600
<v Speaker 1>to give people was reasonable to expect in terms of

0:02:55.760 --> 0:02:59.040
<v Speaker 1>how fast someone should work. Um, for some of my staff,

0:02:59.040 --> 0:03:01.000
<v Speaker 1>they have the same skill, said it's me. So if

0:03:01.120 --> 0:03:03.640
<v Speaker 1>I kind of can bench mark like, oh, this should

0:03:03.639 --> 0:03:05.680
<v Speaker 1>take me two weeks, so maybe it will take them

0:03:05.680 --> 0:03:08.760
<v Speaker 1>similar a bit longer. But with some of my staff

0:03:08.800 --> 0:03:11.200
<v Speaker 1>are totally outside my field, it's it's really hard for

0:03:11.240 --> 0:03:13.280
<v Speaker 1>me to even assess what's reasonable or not, and I

0:03:13.320 --> 0:03:16.320
<v Speaker 1>find that hard. Yeah, it is hard. So I think

0:03:16.360 --> 0:03:19.519
<v Speaker 1>what might make sense is to start with a bunch

0:03:19.560 --> 0:03:23.440
<v Speaker 1>of general advice on managing in general, and then we

0:03:23.480 --> 0:03:27.200
<v Speaker 1>can dive into some of those more specific questions. If

0:03:27.240 --> 0:03:31.160
<v Speaker 1>that sounds good, that sounds great, Okay, Well let's start

0:03:31.240 --> 0:03:33.200
<v Speaker 1>with how do you even learn to be an effective

0:03:33.200 --> 0:03:36.160
<v Speaker 1>manager in the first place? And so I can't answer

0:03:36.160 --> 0:03:38.760
<v Speaker 1>this question without doing a plug for my book for managers,

0:03:38.920 --> 0:03:41.720
<v Speaker 1>which is called Managing to Change the World and Nonprofit

0:03:41.760 --> 0:03:44.960
<v Speaker 1>Manager's Guide to Getting Results. And as you can tell

0:03:45.000 --> 0:03:48.320
<v Speaker 1>from the title, it is primarily targeted to nonprofit managers,

0:03:48.360 --> 0:03:51.400
<v Speaker 1>but really, like of what's in there is going to

0:03:51.440 --> 0:03:54.080
<v Speaker 1>apply to managers in any sector, and it'll really walk

0:03:54.120 --> 0:03:57.440
<v Speaker 1>you through the nitty gritty of how you do some

0:03:57.480 --> 0:03:59.240
<v Speaker 1>of the stuff that we're about to talk about in

0:03:59.280 --> 0:04:02.640
<v Speaker 1>broader term. What I had found before writing it, well

0:04:02.760 --> 0:04:05.600
<v Speaker 1>co authoring it, I should say, is that a lot

0:04:05.640 --> 0:04:08.600
<v Speaker 1>of the management books that are out there are pretty theoretical,

0:04:08.960 --> 0:04:11.520
<v Speaker 1>but I think what managers often really want and need

0:04:11.720 --> 0:04:13.720
<v Speaker 1>is the real detail of it, Like what do I

0:04:13.760 --> 0:04:16.719
<v Speaker 1>say in this meeting and how exactly do I approach

0:04:16.760 --> 0:04:19.240
<v Speaker 1>this issue, and what does it sound like, and how

0:04:19.240 --> 0:04:22.720
<v Speaker 1>do I structure conversations about someone's performance that sort of thing.

0:04:22.760 --> 0:04:25.800
<v Speaker 1>So the book really goes in detail on this is

0:04:25.839 --> 0:04:28.159
<v Speaker 1>exactly how you do it. So it might be worth

0:04:28.800 --> 0:04:32.720
<v Speaker 1>checking out as like a reference material. That sounds great,

0:04:32.880 --> 0:04:34.920
<v Speaker 1>but let's talk bigger themes and you can use that

0:04:34.960 --> 0:04:37.320
<v Speaker 1>as a reference later if you want to. So I

0:04:37.320 --> 0:04:39.520
<v Speaker 1>think the biggest thing that you want to do as

0:04:39.520 --> 0:04:42.320
<v Speaker 1>a manager, because everything else will stem from it, is

0:04:42.360 --> 0:04:45.640
<v Speaker 1>to be really clear in your own head on what

0:04:45.800 --> 0:04:48.880
<v Speaker 1>your job is, what you're there to do as a manager.

0:04:49.360 --> 0:04:51.200
<v Speaker 1>And I am going to argue that your fundamental job

0:04:51.240 --> 0:04:54.080
<v Speaker 1>as a manager is to make sure that your organization

0:04:54.240 --> 0:04:56.960
<v Speaker 1>gets the results that it needs. There's a lot that

0:04:57.000 --> 0:04:58.960
<v Speaker 1>goes into that, of course. I mean there's laying out

0:04:59.000 --> 0:05:02.240
<v Speaker 1>clear expectations, setting the right goals, and hiring their people

0:05:02.279 --> 0:05:05.640
<v Speaker 1>and developing them and giving them good feedback, and building

0:05:05.680 --> 0:05:08.200
<v Speaker 1>a culture that supports all of those things and is

0:05:08.240 --> 0:05:12.240
<v Speaker 1>somewhere that people want to work. But ultimately, those are

0:05:12.279 --> 0:05:15.600
<v Speaker 1>all means to an end, and that end is achieving

0:05:15.800 --> 0:05:18.159
<v Speaker 1>whatever it is that you're setting out to achieve, whatever

0:05:18.200 --> 0:05:19.880
<v Speaker 1>the goals of the company are. And the reason I'm

0:05:19.880 --> 0:05:23.200
<v Speaker 1>stressing that is that because a ton of managers lose

0:05:23.240 --> 0:05:25.880
<v Speaker 1>sight of it. They think that their job is just

0:05:25.920 --> 0:05:29.240
<v Speaker 1>to develop people or to keep their people happy, or

0:05:29.360 --> 0:05:31.599
<v Speaker 1>on the other end of the spectrum, that they're there

0:05:31.640 --> 0:05:34.960
<v Speaker 1>to just enforce rules or monitor people. And it is

0:05:35.000 --> 0:05:37.400
<v Speaker 1>important to develop people and keep your team happy and

0:05:37.480 --> 0:05:41.080
<v Speaker 1>monitor work. But those things aren't ends in themselves. You're

0:05:41.160 --> 0:05:44.440
<v Speaker 1>doing them because they're part of achieving the results that

0:05:44.480 --> 0:05:47.520
<v Speaker 1>you want. And again I'm belaboring this because if you

0:05:47.600 --> 0:05:50.359
<v Speaker 1>lose sight of it, you will find yourself prioritizing the

0:05:50.360 --> 0:05:53.320
<v Speaker 1>wrong things, like you'll find yourself avoiding making a decision

0:05:53.360 --> 0:05:56.680
<v Speaker 1>that will be unpopular, or shying away from a hard

0:05:56.720 --> 0:05:58.960
<v Speaker 1>conversation because you don't want to make someone unhappy, and

0:05:58.960 --> 0:06:02.320
<v Speaker 1>so forth. So that's point number one. Look at everything

0:06:02.320 --> 0:06:05.760
<v Speaker 1>through the lens of how it supports you achieving whatever

0:06:05.800 --> 0:06:09.159
<v Speaker 1>it is that you want to be achieving. From there,

0:06:09.200 --> 0:06:11.479
<v Speaker 1>I think I'm going to run through some of the

0:06:11.480 --> 0:06:14.400
<v Speaker 1>fundamentals that you want to be thinking about and doing

0:06:14.480 --> 0:06:16.640
<v Speaker 1>as a manager. And honestly, each of these could be

0:06:16.640 --> 0:06:18.640
<v Speaker 1>a book in itself, so I'm not going to get

0:06:18.760 --> 0:06:21.320
<v Speaker 1>terribly in depth on any of them. Unless you jump

0:06:21.400 --> 0:06:23.000
<v Speaker 1>in and tell me that you do want to go deeper,

0:06:23.240 --> 0:06:24.960
<v Speaker 1>and feel free to do that with any of these.

0:06:25.200 --> 0:06:27.680
<v Speaker 1>But otherwise, this is just kind of a list to

0:06:27.760 --> 0:06:29.919
<v Speaker 1>get you thinking about the areas that you want to

0:06:29.920 --> 0:06:33.440
<v Speaker 1>be paying special attention to. There's that sort of you

0:06:33.480 --> 0:06:35.839
<v Speaker 1>don't know what you don't know kind of things, So

0:06:35.839 --> 0:06:37.760
<v Speaker 1>so I would say look at this as a list

0:06:37.839 --> 0:06:40.359
<v Speaker 1>of areas to make sure that you're being thoughtful about.

0:06:41.560 --> 0:06:44.159
<v Speaker 1>So the first and maybe the biggest one is being

0:06:44.240 --> 0:06:48.160
<v Speaker 1>really clear with yourself and with your team about what

0:06:48.200 --> 0:06:50.080
<v Speaker 1>you want them to do and what it would look

0:06:50.080 --> 0:06:52.000
<v Speaker 1>like to do it successfully. And I know that sounds

0:06:52.040 --> 0:06:56.600
<v Speaker 1>really obvious, but people don't always do it very effectively,

0:06:56.640 --> 0:07:00.159
<v Speaker 1>and if you don't, it's really easy for you and

0:07:00.200 --> 0:07:01.880
<v Speaker 1>the people working with you to get pulled in a

0:07:01.880 --> 0:07:05.080
<v Speaker 1>bunch of different directions instead of figuring out what are

0:07:05.080 --> 0:07:08.920
<v Speaker 1>the most important things for us to achieve and focusing there. So,

0:07:10.080 --> 0:07:12.360
<v Speaker 1>for the organization as a whole and for each individual

0:07:12.440 --> 0:07:14.240
<v Speaker 1>person who works for you, you you want to get really

0:07:14.240 --> 0:07:17.560
<v Speaker 1>clear on what would a successful year look like. If

0:07:17.600 --> 0:07:19.160
<v Speaker 1>it's the end of the year and we're looking back

0:07:19.200 --> 0:07:21.600
<v Speaker 1>on the previous twelve months, what do we want to

0:07:21.640 --> 0:07:24.120
<v Speaker 1>have achieved for it to have been a successful year.

0:07:24.400 --> 0:07:27.360
<v Speaker 1>That way, by hashing that out and creating really clear

0:07:27.400 --> 0:07:30.560
<v Speaker 1>goals for that time period based on that, everyone's going

0:07:30.600 --> 0:07:32.360
<v Speaker 1>to be on the same page about what successful work

0:07:32.360 --> 0:07:33.720
<v Speaker 1>and their role looks like. And you're not going to

0:07:33.800 --> 0:07:36.600
<v Speaker 1>have people wondering, am I doing a good job? Am

0:07:36.600 --> 0:07:38.240
<v Speaker 1>I doing the things she wants me to be doing?

0:07:38.720 --> 0:07:41.280
<v Speaker 1>And you're not going to have people spending time on

0:07:41.440 --> 0:07:44.680
<v Speaker 1>things that ultimately are trumped by things that are more

0:07:44.720 --> 0:07:48.680
<v Speaker 1>important to you. Does that make sense? Definitely? Yeah? And

0:07:48.720 --> 0:07:51.280
<v Speaker 1>how does that? How do you balance like say an

0:07:51.280 --> 0:07:54.280
<v Speaker 1>employee where you don't really know how to do their jobs,

0:07:54.280 --> 0:07:57.080
<v Speaker 1>so you can explain what you want them to do,

0:07:57.120 --> 0:07:59.760
<v Speaker 1>but not exactly how you want them to do it. Yes,

0:08:00.040 --> 0:08:03.000
<v Speaker 1>So hopefully you've hired someone who has a track record

0:08:03.440 --> 0:08:05.640
<v Speaker 1>of getting those things done or getting things that are

0:08:05.720 --> 0:08:07.840
<v Speaker 1>very similar and done, so you have some reason to

0:08:07.880 --> 0:08:10.920
<v Speaker 1>put your trust in in their skills and their ability

0:08:11.000 --> 0:08:13.400
<v Speaker 1>to achieve those things. And then I would say talk

0:08:13.480 --> 0:08:16.640
<v Speaker 1>to them, you know, talk through I would explicitly ask

0:08:16.680 --> 0:08:19.720
<v Speaker 1>the question, what is reasonable for us to accomplish accomplish

0:08:19.800 --> 0:08:21.880
<v Speaker 1>this year? What I'm hoping is that we could do X,

0:08:21.960 --> 0:08:24.440
<v Speaker 1>Y and Z. What do you think is that realistic?

0:08:24.680 --> 0:08:27.360
<v Speaker 1>Is that enough? Is it not ambitious enough? And have

0:08:27.520 --> 0:08:30.480
<v Speaker 1>that conversation with them, and it should be kind of

0:08:30.480 --> 0:08:34.199
<v Speaker 1>a collaborative process if you've hired the right people. If

0:08:34.200 --> 0:08:36.480
<v Speaker 1>you've hired people who don't have those skills to do it,

0:08:36.520 --> 0:08:38.559
<v Speaker 1>that's a real problem if you don't have those skills either,

0:08:38.600 --> 0:08:40.680
<v Speaker 1>because then you can't can't train them. But I'm assuming

0:08:40.720 --> 0:08:42.960
<v Speaker 1>that you feel pretty confident. You said you're happy with

0:08:43.000 --> 0:08:47.120
<v Speaker 1>your team. Yes, yes, exactly, so yeah, I would just

0:08:47.120 --> 0:08:49.720
<v Speaker 1>have that conversation and it's it's completely okay. I mean,

0:08:49.760 --> 0:08:51.880
<v Speaker 1>I think sometimes especially when people are first managing, they

0:08:51.880 --> 0:08:55.160
<v Speaker 1>feel like people expect them to have all the answers. Actually,

0:08:55.200 --> 0:08:58.080
<v Speaker 1>it really enhances your credibility when you admit that you don't.

0:08:58.200 --> 0:09:01.120
<v Speaker 1>It's completely fine to sit down with someone and say,

0:09:01.400 --> 0:09:03.200
<v Speaker 1>I'm really going to be leaning on you to help

0:09:03.200 --> 0:09:05.720
<v Speaker 1>me figure this out because this is your area of expertise,

0:09:05.760 --> 0:09:09.679
<v Speaker 1>so let's talk through this and I think what you

0:09:09.760 --> 0:09:12.280
<v Speaker 1>want to have. And this touches on on your question

0:09:12.320 --> 0:09:14.920
<v Speaker 1>earlier about like, how do you know if you're not

0:09:15.000 --> 0:09:18.280
<v Speaker 1>an expert in their area that their timelines are reasonable?

0:09:18.440 --> 0:09:20.840
<v Speaker 1>And the quality of their work is reasonable. I think

0:09:21.440 --> 0:09:24.880
<v Speaker 1>you need to have a pretty good BS detector to

0:09:25.000 --> 0:09:28.959
<v Speaker 1>some extent. If you're if you're like Spidy, sense is

0:09:29.000 --> 0:09:31.800
<v Speaker 1>going off and telling you like this just doesn't sound

0:09:31.920 --> 0:09:36.559
<v Speaker 1>right to me. Don't dismiss that just because they are

0:09:36.600 --> 0:09:38.880
<v Speaker 1>more expert than you are. I would take that as

0:09:38.880 --> 0:09:41.600
<v Speaker 1>a flag that something's going on there and you should

0:09:41.600 --> 0:09:44.120
<v Speaker 1>sit down and dig into it. Maybe the thing that's

0:09:44.160 --> 0:09:46.400
<v Speaker 1>going on is that you just have some incorrect assumptions,

0:09:46.520 --> 0:09:48.960
<v Speaker 1>and by talking to them you can straighten that out.

0:09:49.320 --> 0:09:51.360
<v Speaker 1>But maybe there is something more going on. I mean,

0:09:51.360 --> 0:09:54.440
<v Speaker 1>one thing that I have found is that when I

0:09:54.480 --> 0:09:59.119
<v Speaker 1>am managing areas of work that aren't my area of expertise,

0:09:59.760 --> 0:10:03.360
<v Speaker 1>they're there's always small things that I do understand that,

0:10:03.480 --> 0:10:06.440
<v Speaker 1>Like I will understand like oh, that person is really

0:10:06.440 --> 0:10:09.040
<v Speaker 1>great at follow through, or they're not so great at

0:10:09.040 --> 0:10:12.360
<v Speaker 1>follow through, or the way they're explaining this to this

0:10:12.520 --> 0:10:14.560
<v Speaker 1>client like really doesn't make sense, and I don't think

0:10:14.600 --> 0:10:17.240
<v Speaker 1>that person is understanding it. There's like there's pieces like

0:10:17.320 --> 0:10:20.800
<v Speaker 1>that that you will be equipped to judge, and I

0:10:20.840 --> 0:10:24.199
<v Speaker 1>would put real weight on those because in my experience,

0:10:24.760 --> 0:10:28.760
<v Speaker 1>you can extrapolate pretty well the small pieces that you

0:10:28.840 --> 0:10:32.880
<v Speaker 1>are equipped to understand will usually lead you in the

0:10:32.920 --> 0:10:36.400
<v Speaker 1>right to action. Right that totally makes sense. I mean

0:10:36.440 --> 0:10:40.360
<v Speaker 1>not not entirely, of course, I don't want to overstate that,

0:10:40.640 --> 0:10:44.160
<v Speaker 1>but more often than not that will be the case.

0:10:44.480 --> 0:10:48.360
<v Speaker 1>And when you're having those conversations with people, when you're saying,

0:10:48.360 --> 0:10:49.800
<v Speaker 1>you know, help me figure this out. I want to

0:10:49.840 --> 0:10:52.640
<v Speaker 1>lean any for your expertise, you're going to get a

0:10:52.679 --> 0:10:57.079
<v Speaker 1>feel for how you know, do I trust what they're saying?

0:10:57.120 --> 0:10:59.640
<v Speaker 1>Does it make sense to me? Does it seem logically

0:10:59.679 --> 0:11:02.200
<v Speaker 1>sound owned to do it? Does their critical thinking here

0:11:02.240 --> 0:11:05.880
<v Speaker 1>seem on target? Or does it not? And that stuff

0:11:05.960 --> 0:11:07.520
<v Speaker 1>is all going to point you in a direction of

0:11:07.559 --> 0:11:10.839
<v Speaker 1>either Okay, yes, this person I can rely on this person.

0:11:11.160 --> 0:11:14.040
<v Speaker 1>They seem incredible, they know what they're doing, or oh,

0:11:14.080 --> 0:11:15.800
<v Speaker 1>it feels like there's a lot of red flags here.

0:11:17.000 --> 0:11:19.800
<v Speaker 1>Absolutely if it does turn out that you're seeing red

0:11:19.800 --> 0:11:23.400
<v Speaker 1>flags and you do think maybe this person isn't doing

0:11:23.440 --> 0:11:24.840
<v Speaker 1>what I need them to do or they're not right

0:11:24.880 --> 0:11:27.680
<v Speaker 1>for the role, but then you might be thinking like,

0:11:27.720 --> 0:11:30.600
<v Speaker 1>but it might even really equipped to assess that. That

0:11:30.960 --> 0:11:32.600
<v Speaker 1>is when you come back to the goals that we

0:11:32.600 --> 0:11:35.320
<v Speaker 1>were just talking about setting if you're really clear at

0:11:35.320 --> 0:11:37.719
<v Speaker 1>the outside of the year, the six month period, or

0:11:37.760 --> 0:11:40.440
<v Speaker 1>whatever time period you choose. If you're really clear, you

0:11:40.520 --> 0:11:43.000
<v Speaker 1>both get aligned and you both agree, this is what

0:11:43.000 --> 0:11:44.880
<v Speaker 1>we're going to achieve in this time period, this is

0:11:44.880 --> 0:11:47.559
<v Speaker 1>what success would look like. You're going to have really

0:11:47.559 --> 0:11:50.600
<v Speaker 1>good data on whether or not that's actually happening, right,

0:11:50.800 --> 0:11:53.760
<v Speaker 1>and then you can kind of assess did this happen

0:11:53.760 --> 0:11:55.880
<v Speaker 1>and if not, why not? And then that would give

0:11:55.880 --> 0:11:58.040
<v Speaker 1>you the kind of that information exactly. It makes it

0:11:58.200 --> 0:12:01.400
<v Speaker 1>really easy to assess performance. Let's pause here for a

0:12:01.400 --> 0:12:03.400
<v Speaker 1>short break and we'll come right back and keep talking.

0:12:12.520 --> 0:12:16.360
<v Speaker 1>So we were just talking about clarity for expectations for

0:12:16.400 --> 0:12:18.400
<v Speaker 1>a big chunk of time, like a year, but you

0:12:18.480 --> 0:12:20.920
<v Speaker 1>also want to be really clear about expectations on a

0:12:21.040 --> 0:12:24.440
<v Speaker 1>smaller level too, Like if you're assigning a project, you

0:12:24.440 --> 0:12:27.440
<v Speaker 1>want to take the time to really talk through whatever

0:12:27.559 --> 0:12:29.959
<v Speaker 1>is in your head about it. It's really easy as

0:12:29.960 --> 0:12:34.000
<v Speaker 1>a manager to to delegate very quickly. You know, three sentences,

0:12:34.040 --> 0:12:35.960
<v Speaker 1>can you take care of this for me? Here's the deadline.

0:12:36.679 --> 0:12:40.079
<v Speaker 1>But if you don't have a longer conversation, you're I mean,

0:12:40.120 --> 0:12:42.840
<v Speaker 1>obviously not everything requires a longer conversation. But it's if

0:12:42.840 --> 0:12:45.560
<v Speaker 1>it's a pretty major project and you don't really talk

0:12:45.600 --> 0:12:48.400
<v Speaker 1>it through, you're setting yourself in the staff person up

0:12:48.400 --> 0:12:50.280
<v Speaker 1>for frustration when they put a bunch of work in

0:12:50.440 --> 0:12:52.440
<v Speaker 1>and then it comes back to you and you say, oh,

0:12:52.440 --> 0:12:54.880
<v Speaker 1>this isn't really what I was talking about. That sucks

0:12:54.920 --> 0:12:56.719
<v Speaker 1>for everyone. It's not a good use of people's time.

0:12:57.120 --> 0:12:59.600
<v Speaker 1>So I would say, really invest on the front end

0:12:59.760 --> 0:13:02.360
<v Speaker 1>in making sure that if you do have expectations in

0:13:02.400 --> 0:13:04.719
<v Speaker 1>your head about how something will go or what it

0:13:04.760 --> 0:13:06.800
<v Speaker 1>will look like when it comes back to you, that

0:13:06.880 --> 0:13:09.960
<v Speaker 1>you're very deliberate about sharing that with your staff so

0:13:10.000 --> 0:13:12.400
<v Speaker 1>that they're not trying to guess and they're not getting blindsided,

0:13:13.400 --> 0:13:16.920
<v Speaker 1>they're not finding out halfway through she had these expectations

0:13:16.920 --> 0:13:20.640
<v Speaker 1>that she didn't tell me about. Yes, absolutely, And then

0:13:20.679 --> 0:13:23.280
<v Speaker 1>you also want to apply that at another level too,

0:13:23.360 --> 0:13:26.640
<v Speaker 1>So not just long term goals, not just individual projects,

0:13:26.679 --> 0:13:30.320
<v Speaker 1>but also how people are operating in general, how you

0:13:30.360 --> 0:13:33.719
<v Speaker 1>expect them to approach their work. Like, just to give

0:13:33.720 --> 0:13:36.040
<v Speaker 1>you a random example, if you wouldn't like it if

0:13:36.080 --> 0:13:38.480
<v Speaker 1>they took more than like a day to return a

0:13:38.480 --> 0:13:41.200
<v Speaker 1>client's phone call, tell them that. Make sure they know

0:13:41.280 --> 0:13:45.960
<v Speaker 1>that what people tend to do is they don't make

0:13:46.040 --> 0:13:50.520
<v Speaker 1>those implicit expectations explicit, and so people don't meet those expectations,

0:13:50.559 --> 0:13:52.680
<v Speaker 1>and then they get really frustrated and they're wondering, like,

0:13:53.120 --> 0:13:55.000
<v Speaker 1>why is why is this person waiting days to return

0:13:55.000 --> 0:13:57.320
<v Speaker 1>a client's phone call? They should just know that they

0:13:57.320 --> 0:13:59.760
<v Speaker 1>should return it within a day. Well, maybe I mean

0:13:59.760 --> 0:14:01.720
<v Speaker 1>to thing in your context, maybe they should just know.

0:14:02.160 --> 0:14:04.360
<v Speaker 1>But you're setting everyone up for failure if you don't

0:14:04.400 --> 0:14:06.720
<v Speaker 1>just tell them. So you probably have a lot of

0:14:06.760 --> 0:14:11.000
<v Speaker 1>expectations in your head of like how we do things

0:14:11.040 --> 0:14:14.760
<v Speaker 1>here or how we definitely don't do things here, And

0:14:14.840 --> 0:14:18.080
<v Speaker 1>I would be very deliberate about pulling that stuff out

0:14:18.080 --> 0:14:20.560
<v Speaker 1>of your head, whatever it is, so that you can

0:14:20.560 --> 0:14:23.200
<v Speaker 1>share it with people and you don't end up you

0:14:23.360 --> 0:14:27.480
<v Speaker 1>and they don't end up frustrated. Yes, that definitely makes

0:14:27.560 --> 0:14:32.200
<v Speaker 1>good sense. Another thing kind of related to clear expectations

0:14:32.480 --> 0:14:36.200
<v Speaker 1>is feedback. So giving people feedback on their work is

0:14:36.800 --> 0:14:38.880
<v Speaker 1>really key part of your job. And that doesn't just

0:14:39.000 --> 0:14:42.840
<v Speaker 1>mean feedback when something goes wrong or needs to be changed.

0:14:43.400 --> 0:14:46.880
<v Speaker 1>It means kind of feedback all the time, feedback on

0:14:46.920 --> 0:14:49.080
<v Speaker 1>what's going well and what could be better, and how

0:14:49.120 --> 0:14:53.120
<v Speaker 1>someone could go from pretty good to really great. How

0:14:53.120 --> 0:14:56.880
<v Speaker 1>comfortable are you with giving feedback? Very comfortable with giving

0:14:56.920 --> 0:15:03.200
<v Speaker 1>positive feedback? We do lots of that, and negative I

0:15:03.240 --> 0:15:06.080
<v Speaker 1>think I find a little bit harder. Yeah, most people do.

0:15:06.360 --> 0:15:09.480
<v Speaker 1>Most people actually, I think most people start when they

0:15:09.480 --> 0:15:12.200
<v Speaker 1>start managing. There at one end of the spectrum or

0:15:12.240 --> 0:15:14.320
<v Speaker 1>the other. I think yours is the most common. Like,

0:15:14.360 --> 0:15:16.160
<v Speaker 1>it feels good to give praise, I can do that.

0:15:16.600 --> 0:15:19.080
<v Speaker 1>It's a little more awkward to give critical feedback. But

0:15:19.120 --> 0:15:21.200
<v Speaker 1>there are also people who do the reverse, who are

0:15:21.240 --> 0:15:24.880
<v Speaker 1>like super comfortable with the criticism and it doesn't care

0:15:25.040 --> 0:15:30.240
<v Speaker 1>the piece um. But it's really normal to feel a

0:15:30.280 --> 0:15:36.600
<v Speaker 1>little awkward about criticism. The easiest way to do it

0:15:36.640 --> 0:15:39.960
<v Speaker 1>is to get in the habit of giving feedback on

0:15:40.040 --> 0:15:42.880
<v Speaker 1>a really regular basis and to sort of build it

0:15:42.960 --> 0:15:46.320
<v Speaker 1>in two existing structures. So like, if you have regular

0:15:46.320 --> 0:15:49.720
<v Speaker 1>one and one meetings with your staff, have every time,

0:15:49.840 --> 0:15:53.080
<v Speaker 1>have part of those meetings be to debrief recent projects.

0:15:53.120 --> 0:15:55.440
<v Speaker 1>Like put it on the agenda. You can even call

0:15:55.520 --> 0:15:57.800
<v Speaker 1>it a debriefing because then it's not so scary like

0:15:57.880 --> 0:15:59.960
<v Speaker 1>feedback is. You're just talking about how a recent produ

0:16:00.040 --> 0:16:02.280
<v Speaker 1>jicked went. But if you make it a thing where

0:16:02.320 --> 0:16:05.000
<v Speaker 1>you're doing it every time and it's built into how

0:16:05.080 --> 0:16:08.040
<v Speaker 1>you operate, it won't be so hard to initiate when

0:16:08.120 --> 0:16:10.920
<v Speaker 1>you do have some serious criticism. You know, sometimes people

0:16:11.720 --> 0:16:14.200
<v Speaker 1>don't do that. They give praise and it's fine, and

0:16:14.200 --> 0:16:17.240
<v Speaker 1>then one day there's actually a serious issue they have

0:16:17.280 --> 0:16:20.000
<v Speaker 1>to talk about and they're like, oh no, and it

0:16:20.040 --> 0:16:22.560
<v Speaker 1>feels really dramatic, and they're calling someone into the conference

0:16:22.600 --> 0:16:24.360
<v Speaker 1>room and they've got a box of tissues there and

0:16:24.840 --> 0:16:27.920
<v Speaker 1>it feels like this big, serious thing. But it doesn't

0:16:27.960 --> 0:16:30.720
<v Speaker 1>have to be that. If you build it into your

0:16:30.720 --> 0:16:33.680
<v Speaker 1>existing structure so that you're always debriefing and you're always

0:16:33.720 --> 0:16:36.200
<v Speaker 1>talking about how things are going, it's going to be

0:16:36.280 --> 0:16:40.120
<v Speaker 1>so much less dramatic and stressful for everyone. Yes, that

0:16:40.160 --> 0:16:42.480
<v Speaker 1>makes total sense. And do you do you think it's

0:16:42.480 --> 0:16:45.120
<v Speaker 1>a good idea to do kind of the compliment sandwich

0:16:45.160 --> 0:16:47.080
<v Speaker 1>to have always kind of used that where you say, oh,

0:16:47.160 --> 0:16:48.720
<v Speaker 1>you know, you're doing these things well and this one

0:16:48.760 --> 0:16:52.200
<v Speaker 1>thing could use work, and then oh, here's some other

0:16:52.240 --> 0:16:54.160
<v Speaker 1>things you're doing well. Or do you think that's not

0:16:54.320 --> 0:16:56.160
<v Speaker 1>the best way to go? So I am not a

0:16:56.240 --> 0:16:58.360
<v Speaker 1>huge fan of the compliment sandwhich I know some people

0:16:58.440 --> 0:17:00.040
<v Speaker 1>like it. And find it really useful. And if you

0:17:00.080 --> 0:17:02.480
<v Speaker 1>feel like it's working for you and for your staff, great,

0:17:02.600 --> 0:17:05.160
<v Speaker 1>But i'll tell you why I don't love it. One

0:17:05.480 --> 0:17:08.440
<v Speaker 1>is sometimes people start to recognize what you're doing, and

0:17:08.520 --> 0:17:11.840
<v Speaker 1>so every time you praise them, they start bracing themselves

0:17:11.840 --> 0:17:14.160
<v Speaker 1>thinking like, oh no, what is she about to criticize?

0:17:14.600 --> 0:17:16.440
<v Speaker 1>So you don't want that, and you also don't want

0:17:16.440 --> 0:17:20.080
<v Speaker 1>people to feel like you're dealing with them by formula.

0:17:20.760 --> 0:17:23.600
<v Speaker 1>The thing is that sometimes it means the message can

0:17:23.600 --> 0:17:27.800
<v Speaker 1>be lost that the person either just here's the positive

0:17:27.800 --> 0:17:30.199
<v Speaker 1>stuff and doesn't think that the critical part is that

0:17:30.280 --> 0:17:32.119
<v Speaker 1>big of a deal because look, you just said all

0:17:32.160 --> 0:17:35.560
<v Speaker 1>this positive stuff about their work, or the opposite of

0:17:35.640 --> 0:17:38.720
<v Speaker 1>that happens. They just hear the criticism and they completely

0:17:38.800 --> 0:17:41.600
<v Speaker 1>forget the positive things that you said, And you don't

0:17:41.600 --> 0:17:43.240
<v Speaker 1>want that. You want to make sure that you're giving

0:17:43.280 --> 0:17:45.520
<v Speaker 1>them praise in a in a way that's really going

0:17:45.600 --> 0:17:49.520
<v Speaker 1>to register with them. So I think people turn to

0:17:49.560 --> 0:17:53.919
<v Speaker 1>the compliment sandwich because it feels a little better to

0:17:54.080 --> 0:17:58.440
<v Speaker 1>do it that way. Yeah, but I think you can

0:17:58.560 --> 0:18:01.639
<v Speaker 1>give criticism in a way that feels safe for the

0:18:01.640 --> 0:18:05.800
<v Speaker 1>person and that feels supportive and where it's clear that

0:18:05.880 --> 0:18:08.560
<v Speaker 1>you are not questioning their entire fit for the role.

0:18:09.359 --> 0:18:11.800
<v Speaker 1>And the part of the way to do it, something

0:18:11.840 --> 0:18:13.919
<v Speaker 1>that really will make it easier is if you do

0:18:14.040 --> 0:18:17.000
<v Speaker 1>normalize it, if it does become just a normal part

0:18:17.040 --> 0:18:19.040
<v Speaker 1>of the conversations that you're having when you check in

0:18:19.080 --> 0:18:21.720
<v Speaker 1>weekly or bi weekly or whatever it is, right and

0:18:21.760 --> 0:18:23.160
<v Speaker 1>not be like, oh, we need to have this big

0:18:23.280 --> 0:18:27.160
<v Speaker 1>talk exactly. And if you also are sure that you're

0:18:27.280 --> 0:18:30.080
<v Speaker 1>giving positive feedback and it sounds like you are, that's

0:18:30.080 --> 0:18:32.520
<v Speaker 1>going to help with that feeling that people will sometimes

0:18:32.560 --> 0:18:34.159
<v Speaker 1>get where they like you give them a piece of

0:18:34.160 --> 0:18:36.879
<v Speaker 1>criticism and they think their their whole job is in jeopardy. Now,

0:18:36.920 --> 0:18:38.439
<v Speaker 1>some people would think that no matter what you do.

0:18:38.480 --> 0:18:41.560
<v Speaker 1>But but in general, as long as you're giving more

0:18:41.640 --> 0:18:45.480
<v Speaker 1>praise than you are criticism, most people are going to

0:18:45.560 --> 0:18:47.919
<v Speaker 1>take that pretty well. If you're not giving more praise

0:18:48.080 --> 0:18:51.119
<v Speaker 1>than criticism, then I would look at is that a

0:18:51.119 --> 0:18:53.320
<v Speaker 1>problem with the way that you're managing or is it

0:18:53.359 --> 0:18:56.280
<v Speaker 1>a flag that maybe there's some pretty serious concerns about

0:18:56.280 --> 0:19:01.119
<v Speaker 1>the person's fit for the job? Right, Okay, let's see.

0:19:01.200 --> 0:19:05.080
<v Speaker 1>Another big area to think about is that a key

0:19:05.119 --> 0:19:07.760
<v Speaker 1>part of your job as a manager is to build

0:19:07.920 --> 0:19:10.280
<v Speaker 1>a great team. And I say that because you don't

0:19:10.280 --> 0:19:12.280
<v Speaker 1>want to be passive about it. You want to put

0:19:12.960 --> 0:19:16.000
<v Speaker 1>real energy into hiring good people and the flip side

0:19:16.000 --> 0:19:19.840
<v Speaker 1>of that addressing it when someone really isn't working out now,

0:19:19.920 --> 0:19:22.720
<v Speaker 1>doing that means being a place that good people want

0:19:22.720 --> 0:19:25.359
<v Speaker 1>to work so treating people well and being fair and

0:19:25.400 --> 0:19:28.560
<v Speaker 1>being open and compassionate while still holding a high bar

0:19:28.760 --> 0:19:31.479
<v Speaker 1>for the work that you're doing. UM when we started

0:19:31.480 --> 0:19:33.520
<v Speaker 1>out at the start of the show and I was like, Oh,

0:19:33.680 --> 0:19:36.360
<v Speaker 1>sometimes people think that managing is just all about supporting

0:19:36.359 --> 0:19:38.960
<v Speaker 1>their team. I'm not being dismissive of that. I think

0:19:39.040 --> 0:19:42.000
<v Speaker 1>supporting your team is really important. It's important for this

0:19:42.119 --> 0:19:44.960
<v Speaker 1>reason that it will help you attract and retain good

0:19:45.000 --> 0:19:46.959
<v Speaker 1>people if you're someone that people want to work for

0:19:47.080 --> 0:19:50.040
<v Speaker 1>in your company that people want to work in UM

0:19:50.040 --> 0:19:51.840
<v Speaker 1>And I mean, obviously it's the right thing to do.

0:19:51.880 --> 0:19:55.320
<v Speaker 1>I don't I don't mean to discount that, but ultimately

0:19:55.359 --> 0:19:59.200
<v Speaker 1>it's part of building a company that is going to

0:19:59.280 --> 0:20:01.439
<v Speaker 1>run really well over time. And part of that I

0:20:01.440 --> 0:20:04.880
<v Speaker 1>think is being really deliberate about the culture that you're creating.

0:20:05.119 --> 0:20:07.480
<v Speaker 1>And that's not really stuff like do you have a

0:20:07.480 --> 0:20:09.879
<v Speaker 1>foodsball table in the office. Although I know that it

0:20:09.920 --> 0:20:12.760
<v Speaker 1>gets talked about that way a lot, it's more that

0:20:13.800 --> 0:20:16.359
<v Speaker 1>the how we do things around here stuff that is

0:20:16.400 --> 0:20:19.160
<v Speaker 1>important to how the company functions. So it's stuff like

0:20:19.480 --> 0:20:21.800
<v Speaker 1>what kind of energy is in the office most days,

0:20:21.880 --> 0:20:24.480
<v Speaker 1>and how do people interact, and how do you handle

0:20:24.520 --> 0:20:27.080
<v Speaker 1>new ideas and how accountable to do people feel for

0:20:27.119 --> 0:20:30.919
<v Speaker 1>their work. It tends to not get culture tends to

0:20:30.920 --> 0:20:33.160
<v Speaker 1>not get a lot of attention with a small staff,

0:20:33.480 --> 0:20:35.919
<v Speaker 1>but it's something to have in your head to be

0:20:36.000 --> 0:20:38.600
<v Speaker 1>thinking about, especially if you keep growing and bringing new

0:20:38.600 --> 0:20:41.960
<v Speaker 1>people on. Yeah, it's something that's actually made us grow

0:20:42.000 --> 0:20:44.440
<v Speaker 1>a bit smaller on purpose, is because we're afraid to

0:20:45.040 --> 0:20:47.359
<v Speaker 1>double in size over night and we feel like our

0:20:47.359 --> 0:20:49.480
<v Speaker 1>culture may just kind of get away from us. Yeah,

0:20:49.600 --> 0:20:52.680
<v Speaker 1>growth is really hard, especially when you're going from from

0:20:52.720 --> 0:20:55.400
<v Speaker 1>pretty small to not quite as small. It's very very

0:20:55.400 --> 0:20:59.760
<v Speaker 1>common to find that the practices and systems or in

0:20:59.800 --> 0:21:02.879
<v Speaker 1>some case lack of practices and systems that that worked

0:21:02.920 --> 0:21:05.280
<v Speaker 1>for you at a small size they don't really translate

0:21:05.320 --> 0:21:07.000
<v Speaker 1>as you get bigger. And you think that's true of

0:21:07.520 --> 0:21:10.080
<v Speaker 1>culture too, and it just becomes all the more important

0:21:10.080 --> 0:21:13.480
<v Speaker 1>to be very deliberate about it. Yeah, that totally makes sense.

0:21:14.480 --> 0:21:17.000
<v Speaker 1>Let's go to another break here, and when we come back,

0:21:17.080 --> 0:21:29.679
<v Speaker 1>let's dig in more to the specific questions that you had. Okay,

0:21:29.720 --> 0:21:34.040
<v Speaker 1>we are back. So you mentioned in your letter to

0:21:34.119 --> 0:21:36.840
<v Speaker 1>me that you're concerned about getting the balance right between

0:21:36.920 --> 0:21:39.080
<v Speaker 1>being a casual and funt place to work, but also

0:21:39.119 --> 0:21:41.600
<v Speaker 1>making sure that people respect you enough that they understand

0:21:41.600 --> 0:21:44.240
<v Speaker 1>that you make the final decisions. How do you feel

0:21:44.240 --> 0:21:46.080
<v Speaker 1>like that's going so far. Does it feel like it's

0:21:46.240 --> 0:21:49.320
<v Speaker 1>more or less okay? Or have there been issues? I

0:21:49.359 --> 0:21:52.800
<v Speaker 1>feel like we we definitely are airing on the side

0:21:52.840 --> 0:21:57.200
<v Speaker 1>of a fun, happy place to work, and we certainly

0:21:57.320 --> 0:21:59.840
<v Speaker 1>have done good work and have good feedback on our clients,

0:22:00.000 --> 0:22:02.640
<v Speaker 1>and so that part's going really well. But I think

0:22:02.680 --> 0:22:05.440
<v Speaker 1>sometimes deadlines aren't taken as seriously as they could be.

0:22:06.119 --> 0:22:08.399
<v Speaker 1>How do you handle deadlines? Like if someone misses a deadline,

0:22:08.400 --> 0:22:12.080
<v Speaker 1>what happens? Like, say, when it happened recently, I had

0:22:12.080 --> 0:22:14.879
<v Speaker 1>a conversation with someone about getting something done by a

0:22:14.920 --> 0:22:17.359
<v Speaker 1>certain date, and then when that date came up, I

0:22:17.359 --> 0:22:20.000
<v Speaker 1>asked her how it was going, and she said basically like, oh,

0:22:20.040 --> 0:22:21.600
<v Speaker 1>she might be able to get part of it done

0:22:21.680 --> 0:22:25.080
<v Speaker 1>by the end of the day, and I was a

0:22:25.119 --> 0:22:26.760
<v Speaker 1>little unsure how to deal with that, to be honest,

0:22:26.800 --> 0:22:28.880
<v Speaker 1>because I I just said something like, oh, I thought

0:22:28.920 --> 0:22:31.240
<v Speaker 1>you knew that this was a deadline and that if

0:22:31.240 --> 0:22:33.120
<v Speaker 1>you couldn't meet it, you would at least let me know.

0:22:34.119 --> 0:22:37.200
<v Speaker 1>And uh, yeah, So that that's something I've been struggling

0:22:37.200 --> 0:22:39.080
<v Speaker 1>a little bit with, is how do I I mean,

0:22:39.119 --> 0:22:41.280
<v Speaker 1>I made a pretty clear that you know, we need

0:22:41.320 --> 0:22:43.760
<v Speaker 1>to meet the deadlines a bit better, but I'm not

0:22:43.800 --> 0:22:46.879
<v Speaker 1>really sure exactly what what I should have done differently,

0:22:46.880 --> 0:22:48.840
<v Speaker 1>because I'm pretty sure it's something to do with my management,

0:22:48.920 --> 0:22:51.520
<v Speaker 1>is why that happened, And I don't know exactly what

0:22:51.640 --> 0:22:54.080
<v Speaker 1>it was. How clear were you when you first set

0:22:54.080 --> 0:22:57.959
<v Speaker 1>the deadline? Sometimes people I think that they have communicated

0:22:58.000 --> 0:23:00.760
<v Speaker 1>to deadline clearly, but in reality they've it's come across

0:23:00.800 --> 0:23:03.040
<v Speaker 1>as more of a suggestion like it would be great

0:23:03.080 --> 0:23:05.919
<v Speaker 1>if you could do this by Tuesday, but the person

0:23:06.040 --> 0:23:08.800
<v Speaker 1>hears that as well, Tuesday would be great, but Friday

0:23:08.800 --> 0:23:11.760
<v Speaker 1>would be fine too. So do you do you remember

0:23:11.800 --> 0:23:14.920
<v Speaker 1>how clear you were? I feel like I was fairly clear,

0:23:15.000 --> 0:23:17.240
<v Speaker 1>but I also know that I gave her a bunch

0:23:17.240 --> 0:23:20.760
<v Speaker 1>of other things to do after that that we're less urgent,

0:23:20.960 --> 0:23:23.640
<v Speaker 1>but she may have interpreted them as well, I should

0:23:23.640 --> 0:23:26.320
<v Speaker 1>be working on these now instead or in addition to

0:23:26.520 --> 0:23:28.760
<v Speaker 1>so the deadline now was a little bit less important.

0:23:28.800 --> 0:23:31.399
<v Speaker 1>I don't think I explicitly said, but wait and do

0:23:31.480 --> 0:23:35.120
<v Speaker 1>these things after How much time was there between when

0:23:35.160 --> 0:23:37.000
<v Speaker 1>you first made the assignment and when it was due

0:23:38.280 --> 0:23:41.920
<v Speaker 1>about a week okay, so enough time that she could

0:23:41.920 --> 0:23:44.000
<v Speaker 1>have come back to you and said, hey, I'm I

0:23:44.080 --> 0:23:47.000
<v Speaker 1>have concerned about my ability to meet this deadline. Definitely,

0:23:47.560 --> 0:23:50.040
<v Speaker 1>So I think a couple of things. You might be right.

0:23:50.080 --> 0:23:52.120
<v Speaker 1>It really might just be it was like this one time,

0:23:52.119 --> 0:23:53.800
<v Speaker 1>fluke and she just had a bunch of other things

0:23:53.800 --> 0:23:56.640
<v Speaker 1>going on. But I suspect you're bringing it up because

0:23:56.640 --> 0:23:58.800
<v Speaker 1>it feels like more of a pattern. So I think

0:23:58.800 --> 0:24:01.640
<v Speaker 1>a couple of things. One, do be very clear when

0:24:01.720 --> 0:24:04.480
<v Speaker 1>you're setting deadlines, and you might be um, but make

0:24:04.480 --> 0:24:07.000
<v Speaker 1>sure that it's not sounding like a suggestion. Make sure

0:24:07.080 --> 0:24:08.760
<v Speaker 1>it's you know, I will need this by the end

0:24:08.800 --> 0:24:10.320
<v Speaker 1>of the day, you know what. I would even be

0:24:10.400 --> 0:24:12.080
<v Speaker 1>more explicit because the end of the day can be

0:24:12.119 --> 0:24:15.320
<v Speaker 1>interpreted as five o'clock or eleven o'clock at night. So

0:24:15.720 --> 0:24:18.359
<v Speaker 1>let me back up. I would say, Um, you know,

0:24:18.400 --> 0:24:20.920
<v Speaker 1>I need this by five pm on Tuesday. Do you

0:24:20.920 --> 0:24:22.919
<v Speaker 1>think you'll be able to do that? So you're getting

0:24:22.920 --> 0:24:26.720
<v Speaker 1>their commitment to it. And then if the deadline comes

0:24:26.720 --> 0:24:28.840
<v Speaker 1>and the person is being kind of wishy washy, you

0:24:28.840 --> 0:24:30.679
<v Speaker 1>know the conversation that you had or she was like, oh,

0:24:30.760 --> 0:24:33.840
<v Speaker 1>I don't know if it's going to happen. Um, two things.

0:24:34.240 --> 0:24:37.280
<v Speaker 1>In the moment, you can say, oh, I really do

0:24:37.400 --> 0:24:39.960
<v Speaker 1>need it by the end of today. What can Is

0:24:39.960 --> 0:24:42.119
<v Speaker 1>there anything you can move around to make that happen,

0:24:42.520 --> 0:24:45.320
<v Speaker 1>so that your intent is very clear. You're not being

0:24:45.359 --> 0:24:47.800
<v Speaker 1>loosey goosey about this deadline. You're making it very clear

0:24:47.800 --> 0:24:50.080
<v Speaker 1>that you really do need it. In some cases the

0:24:50.080 --> 0:24:51.560
<v Speaker 1>person might be able to pull that off and in

0:24:51.600 --> 0:24:56.919
<v Speaker 1>other cases maybe not. Either way, though, afterward, have a

0:24:56.920 --> 0:25:00.720
<v Speaker 1>conversation about it, because this is how you get deadlines

0:25:00.760 --> 0:25:03.359
<v Speaker 1>taken seriously in your culture. You don't just kind of

0:25:03.440 --> 0:25:05.840
<v Speaker 1>let it go and feel annoyed about it. You talk

0:25:05.880 --> 0:25:08.639
<v Speaker 1>about it, and that means sitting down with her. And

0:25:08.960 --> 0:25:10.880
<v Speaker 1>it doesn't have to be like a whole special meeting

0:25:10.920 --> 0:25:12.239
<v Speaker 1>just for this. It can be the next time you

0:25:12.240 --> 0:25:15.119
<v Speaker 1>have like a weekly check in or something. But you say, hey,

0:25:15.200 --> 0:25:17.560
<v Speaker 1>I know we had talked about having project X do

0:25:17.720 --> 0:25:22.080
<v Speaker 1>on Tuesday. What happened there? And that's it. That's all

0:25:22.119 --> 0:25:24.480
<v Speaker 1>you need to say. What happened there? Those are your

0:25:24.520 --> 0:25:29.280
<v Speaker 1>magic words for accountability, because what it's doing is, well,

0:25:29.280 --> 0:25:32.959
<v Speaker 1>it's doing a few things. Most importantly, it's communicating this

0:25:33.040 --> 0:25:35.200
<v Speaker 1>is actually a problem that we're going to talk about.

0:25:35.240 --> 0:25:37.440
<v Speaker 1>I'm concerned that it didn't happen, and it's a big

0:25:37.560 --> 0:25:40.080
<v Speaker 1>enough issue that we're talking about why it played out

0:25:40.160 --> 0:25:43.080
<v Speaker 1>that way. But also you're giving the person a chance

0:25:43.320 --> 0:25:45.719
<v Speaker 1>to give you information that you might not have. You know,

0:25:45.800 --> 0:25:49.200
<v Speaker 1>maybe what happened is you gave her three other projects

0:25:49.200 --> 0:25:52.680
<v Speaker 1>that had sooner deadlines, or um, maybe she was really sick,

0:25:52.800 --> 0:25:54.560
<v Speaker 1>or she was learning from home when her power went out,

0:25:54.640 --> 0:25:57.280
<v Speaker 1>or who knows. There could be reasons. So you don't

0:25:57.320 --> 0:25:59.320
<v Speaker 1>want to just launch into a lecture. You want to

0:25:59.359 --> 0:26:01.280
<v Speaker 1>make sure that you're hearing the person out and getting

0:26:01.280 --> 0:26:03.960
<v Speaker 1>their perspective, and frankly, you don't even need the lecture

0:26:04.080 --> 0:26:08.040
<v Speaker 1>at that point, just the what happened is usually enough

0:26:08.040 --> 0:26:11.760
<v Speaker 1>of the conversation. Now, if it keeps happening, you don't

0:26:11.800 --> 0:26:14.280
<v Speaker 1>want to just keep having but what happened conversation week

0:26:14.280 --> 0:26:17.639
<v Speaker 1>after week. That would be not good if it becomes

0:26:17.640 --> 0:26:20.400
<v Speaker 1>a pattern. Then you talk about the pattern, and then

0:26:20.400 --> 0:26:23.360
<v Speaker 1>the conversation is, Hey, I'm concerned, there's this pattern. You've

0:26:23.359 --> 0:26:26.440
<v Speaker 1>missed a bunch of deadlines recently. What's going on? Oh, look,

0:26:26.560 --> 0:26:30.000
<v Speaker 1>it's actually a version of what happened, but you're talking

0:26:30.040 --> 0:26:34.119
<v Speaker 1>about the pattern at that point. But for the one time,

0:26:34.359 --> 0:26:37.160
<v Speaker 1>what happened is usually enough. And sometimes I think managers

0:26:37.200 --> 0:26:39.160
<v Speaker 1>feel like, am I supposed to be like coming down

0:26:39.240 --> 0:26:41.480
<v Speaker 1>harder on the person? And what would that even look like?

0:26:41.960 --> 0:26:44.840
<v Speaker 1>But really, like, these are adults, they're presumably good at

0:26:44.880 --> 0:26:47.639
<v Speaker 1>their jobs. You hired them because you trusted them. What

0:26:47.800 --> 0:26:52.960
<v Speaker 1>happened is a respectful way to address it and convey

0:26:53.000 --> 0:26:55.560
<v Speaker 1>your concern about it. Now, if they're not people who

0:26:55.560 --> 0:26:57.720
<v Speaker 1>you trust to do your job, that's a totally different issue.

0:26:57.800 --> 0:27:01.520
<v Speaker 1>But but it sounds like they are. They are. Definitely. Yeah,

0:27:01.560 --> 0:27:04.560
<v Speaker 1>let me ask you this. A lot of new managers

0:27:04.840 --> 0:27:10.080
<v Speaker 1>feel kind of awkward about having authority and exercising authority.

0:27:10.080 --> 0:27:14.280
<v Speaker 1>It just feels weird. Do you feel weird about it? Yes? Definitely, Yeah,

0:27:14.760 --> 0:27:17.679
<v Speaker 1>so super normal. I think it feels weird for like,

0:27:18.560 --> 0:27:20.400
<v Speaker 1>I mean, a minimum of one year, and I think

0:27:20.440 --> 0:27:24.199
<v Speaker 1>for most people a few years. The interesting thing, and

0:27:24.240 --> 0:27:25.960
<v Speaker 1>I think it really helps to remember it, is that

0:27:26.000 --> 0:27:29.160
<v Speaker 1>if you have decent employees, they probably don't feel weird

0:27:29.200 --> 0:27:31.479
<v Speaker 1>about it at all, Like it's normal to have a boss.

0:27:31.680 --> 0:27:34.000
<v Speaker 1>It probably feels like a completely normal, matter of fact

0:27:34.040 --> 0:27:36.679
<v Speaker 1>thing that you have authority over them. You probably have

0:27:36.720 --> 0:27:39.040
<v Speaker 1>a bigger hang up about it than in they do.

0:27:39.920 --> 0:27:42.199
<v Speaker 1>I think that's true. And Label had bobs before and

0:27:42.240 --> 0:27:45.720
<v Speaker 1>had managers before, so I think for them it's very normal. Yeah. So,

0:27:45.800 --> 0:27:47.600
<v Speaker 1>and like if you think about, well, you said you

0:27:47.600 --> 0:27:49.200
<v Speaker 1>haven't had a real job history. I was going to say,

0:27:49.240 --> 0:27:50.920
<v Speaker 1>if you think about times when you've had a boss,

0:27:50.960 --> 0:27:53.520
<v Speaker 1>you probably didn't feel really awkward about the fact that

0:27:53.520 --> 0:27:55.960
<v Speaker 1>they had authority. Um, but but yeah, in their shoes,

0:27:55.960 --> 0:27:59.240
<v Speaker 1>they probably don't feel weird. So it's not weird unless

0:27:59.240 --> 0:28:02.280
<v Speaker 1>you make it weird. And you can make it weird,

0:28:02.400 --> 0:28:07.960
<v Speaker 1>are being noticeably uncomfortable about it, or like really holding

0:28:07.960 --> 0:28:10.679
<v Speaker 1>off on addressing issues or dancing around it like that

0:28:10.720 --> 0:28:13.880
<v Speaker 1>thing I was talking about about presenting things as suggestions

0:28:13.880 --> 0:28:17.080
<v Speaker 1>when they're really not suggestions is a really common trap

0:28:17.160 --> 0:28:21.560
<v Speaker 1>when someone doesn't feel comfortable with authority. It's easier to say, well,

0:28:21.600 --> 0:28:23.400
<v Speaker 1>Tuesday would be great if you can get to it,

0:28:24.000 --> 0:28:27.600
<v Speaker 1>rather than a more authoritative I need this by Tuesday, right,

0:28:27.600 --> 0:28:30.040
<v Speaker 1>which is actually so much more actionable, so right, And

0:28:30.080 --> 0:28:32.800
<v Speaker 1>it's better for the person you're managing to let them

0:28:32.840 --> 0:28:35.639
<v Speaker 1>know what you need so that they can meet those expectations.

0:28:36.160 --> 0:28:38.640
<v Speaker 1>So really, the more matter of fact you can be

0:28:38.680 --> 0:28:41.640
<v Speaker 1>about having authority, the more comfortable everyone will be. But

0:28:41.720 --> 0:28:44.120
<v Speaker 1>you do have to fake it for for a while.

0:28:44.200 --> 0:28:47.160
<v Speaker 1>It's not going to come naturally. Just like totally pretend

0:28:47.200 --> 0:28:49.120
<v Speaker 1>that you feel comfortable with it, and at some point

0:28:49.160 --> 0:28:51.000
<v Speaker 1>you will look around and realize that you do, but

0:28:51.080 --> 0:28:54.880
<v Speaker 1>it takes a while. That makes sense, I think to like,

0:28:55.400 --> 0:28:58.040
<v Speaker 1>most of the time you want to be taking a

0:28:58.040 --> 0:29:01.280
<v Speaker 1>pretty collaborative approach with the all that you manage. You know,

0:29:01.320 --> 0:29:03.360
<v Speaker 1>you respect their opinions and their input and you want

0:29:03.400 --> 0:29:05.719
<v Speaker 1>to hear from them and and then you'll do your

0:29:05.720 --> 0:29:07.720
<v Speaker 1>own job, which is using that input from them to

0:29:07.800 --> 0:29:12.080
<v Speaker 1>make decisions. But you can be collaborative, like I think

0:29:12.120 --> 0:29:14.880
<v Speaker 1>sometimes when people start managing, they have this idea in

0:29:14.920 --> 0:29:17.520
<v Speaker 1>their head that they're supposed to be like the boss,

0:29:17.640 --> 0:29:20.640
<v Speaker 1>like really rigid and just like delivering these orders, and

0:29:21.240 --> 0:29:24.640
<v Speaker 1>you can be collaborative with people because you do have

0:29:24.720 --> 0:29:27.320
<v Speaker 1>the authority to use when you need to. So if

0:29:27.360 --> 0:29:29.160
<v Speaker 1>you do need to step in at some point and say,

0:29:29.280 --> 0:29:30.760
<v Speaker 1>you know, hey, I actually want us to do this

0:29:30.800 --> 0:29:32.720
<v Speaker 1>a little bit differently, or we're going to go in

0:29:32.720 --> 0:29:35.360
<v Speaker 1>a different direction, you have the authority to say that,

0:29:35.440 --> 0:29:39.000
<v Speaker 1>but you don't need to be like exuding that authority

0:29:39.080 --> 0:29:41.200
<v Speaker 1>all the time. You can just treat them like a

0:29:41.200 --> 0:29:44.120
<v Speaker 1>normal colleague most of the time, right, Okay, Well, that's

0:29:44.120 --> 0:29:45.800
<v Speaker 1>good to know because that's that tends to be what

0:29:45.840 --> 0:29:49.160
<v Speaker 1>we do good. And I think you had asked about

0:29:49.240 --> 0:29:51.960
<v Speaker 1>like making it clear that even though you have a

0:29:52.000 --> 0:29:54.280
<v Speaker 1>pretty casual culture, there are times when you'll be making

0:29:54.800 --> 0:29:57.720
<v Speaker 1>the final decision, and I think just be a matter

0:29:57.760 --> 0:30:01.239
<v Speaker 1>of fact about that too, to be clear about your

0:30:01.240 --> 0:30:04.400
<v Speaker 1>decision making structure, because where people run into problems with

0:30:04.440 --> 0:30:07.480
<v Speaker 1>this is when they're so collaborative that they say things

0:30:07.560 --> 0:30:10.680
<v Speaker 1>that signal that a decision is a group decision when

0:30:10.680 --> 0:30:12.840
<v Speaker 1>they don't actually mean that. So you just want to

0:30:12.880 --> 0:30:15.880
<v Speaker 1>be upfront and transparent, like you might say at the

0:30:15.920 --> 0:30:18.680
<v Speaker 1>start of the discussion, you know, I'm figuring out how

0:30:18.680 --> 0:30:20.840
<v Speaker 1>we're going to handle X, and I'd love to get

0:30:20.840 --> 0:30:23.640
<v Speaker 1>your input as they make the decision. Yes, I think

0:30:23.720 --> 0:30:26.840
<v Speaker 1>that's the balance I need to strike better. Yeah, so

0:30:26.880 --> 0:30:30.560
<v Speaker 1>you're like welcoming and inviting their input, but you're using

0:30:30.600 --> 0:30:33.640
<v Speaker 1>that input because you're making the decision. Or you could say, like,

0:30:33.880 --> 0:30:35.680
<v Speaker 1>I need to make a decision about X, I'd love

0:30:35.680 --> 0:30:38.840
<v Speaker 1>any thoughts you have on it, or like if something

0:30:38.920 --> 0:30:41.680
<v Speaker 1>is sensitive, you might even be more explicit about it,

0:30:41.720 --> 0:30:43.760
<v Speaker 1>like you could say, hey, I want to note that

0:30:43.800 --> 0:30:45.280
<v Speaker 1>we're not going to decide this as a group, but

0:30:45.320 --> 0:30:48.720
<v Speaker 1>I do want to get everyone's input and advice. And

0:30:48.760 --> 0:30:50.920
<v Speaker 1>then if you do make a decision that is different

0:30:50.960 --> 0:30:53.760
<v Speaker 1>from what people wanted, just explain why you ended up

0:30:53.760 --> 0:30:56.600
<v Speaker 1>there and be clear that you did consider their input

0:30:56.640 --> 0:30:59.440
<v Speaker 1>and your thinking and why you ultimately went in a

0:30:59.440 --> 0:31:01.960
<v Speaker 1>different direct, because most people are going to feel respected

0:31:02.000 --> 0:31:04.480
<v Speaker 1>if it's clear that you heard them out and you

0:31:04.560 --> 0:31:07.320
<v Speaker 1>took their inputs seriously, even if you ultimately made a

0:31:07.320 --> 0:31:12.440
<v Speaker 1>different choice. Yeah, excellent. Now you also mentioned you want

0:31:12.480 --> 0:31:14.480
<v Speaker 1>to be sure that you're spotting any weaknesses that you

0:31:14.560 --> 0:31:16.959
<v Speaker 1>have and that it's hard to get candid feedback from

0:31:17.000 --> 0:31:20.160
<v Speaker 1>people you're managing, which is very true. One of the

0:31:20.160 --> 0:31:21.720
<v Speaker 1>best ways to do it is to just create a

0:31:21.760 --> 0:31:25.080
<v Speaker 1>culture where people feel safe talking to you, that they

0:31:25.160 --> 0:31:27.200
<v Speaker 1>know that they won't be penalized in some way for

0:31:27.280 --> 0:31:31.120
<v Speaker 1>being candid. Honestly, it's hard to do because some people

0:31:31.640 --> 0:31:33.840
<v Speaker 1>have had bosses in the past who did penalize them

0:31:33.840 --> 0:31:36.000
<v Speaker 1>for being candid, or they grew up in a family

0:31:36.080 --> 0:31:40.160
<v Speaker 1>that like really reinforced that posses through the enemy. Some

0:31:40.200 --> 0:31:42.719
<v Speaker 1>people just won't be that candid with managers, but a

0:31:42.720 --> 0:31:45.440
<v Speaker 1>lot of people will if you demonstrate that it's safe

0:31:45.440 --> 0:31:47.520
<v Speaker 1>for them to do it. But you can also make

0:31:47.520 --> 0:31:50.640
<v Speaker 1>a point of asking probing questions every so often, like

0:31:50.720 --> 0:31:53.440
<v Speaker 1>periodically asking people how things are going, and what would

0:31:53.440 --> 0:31:56.800
<v Speaker 1>make their jobs easier, if there's anything that you personally

0:31:56.840 --> 0:32:00.120
<v Speaker 1>could be doing differently, and that kind of thing. And

0:32:00.160 --> 0:32:02.360
<v Speaker 1>if you have created an environment where it's safe for

0:32:02.400 --> 0:32:05.040
<v Speaker 1>people to speak openly and you ask those questions and

0:32:05.080 --> 0:32:09.080
<v Speaker 1>you make it clear you really want the answers, you'll hear, well,

0:32:09.120 --> 0:32:12.680
<v Speaker 1>you'll hear some of it, you still because there's power

0:32:12.760 --> 0:32:16.480
<v Speaker 1>dynamics there. But the other thing is to develop relationships

0:32:16.520 --> 0:32:18.959
<v Speaker 1>with other people, people who you don't manage, who you

0:32:19.040 --> 0:32:21.880
<v Speaker 1>trust to be straight with you. So maybe that's your

0:32:21.920 --> 0:32:24.960
<v Speaker 1>co founder. Maybe it's colleagues and other companies so you

0:32:24.960 --> 0:32:27.360
<v Speaker 1>can bounce things off of. Maybe it's like a mentor

0:32:27.480 --> 0:32:30.680
<v Speaker 1>type figure. But the idea is to diversify to figure.

0:32:30.880 --> 0:32:33.080
<v Speaker 1>You're probably never going to hear everything there is to

0:32:33.160 --> 0:32:35.320
<v Speaker 1>hear from your own staff, but that if you work

0:32:35.320 --> 0:32:38.600
<v Speaker 1>on developing good, trusting relationships across the range of people,

0:32:38.800 --> 0:32:42.680
<v Speaker 1>your chances go up. Right. That makes sense, not just

0:32:42.760 --> 0:32:48.080
<v Speaker 1>relying on them to tell me their deepest, darkest feelings exactly. Oh,

0:32:48.160 --> 0:32:51.960
<v Speaker 1>and this is really important. Part of making people feel

0:32:52.000 --> 0:32:55.239
<v Speaker 1>safe sharing input with you is to demonstrate that you

0:32:55.280 --> 0:32:57.880
<v Speaker 1>don't shoot the messenger. And I know we all think like, oh,

0:32:57.920 --> 0:33:00.120
<v Speaker 1>I would never shoot the messenger, but like people do it.

0:33:00.440 --> 0:33:02.720
<v Speaker 1>A lot of people do it. So if people who

0:33:02.760 --> 0:33:06.520
<v Speaker 1>you manage see you get angry or like visibly frustrated

0:33:06.560 --> 0:33:09.040
<v Speaker 1>when you get bad news or you hear something you

0:33:09.080 --> 0:33:11.560
<v Speaker 1>don't like or agree with, they are never going to

0:33:11.600 --> 0:33:14.240
<v Speaker 1>give you honest feedback about their own weaknesses. It's just

0:33:14.280 --> 0:33:16.640
<v Speaker 1>not worth that risk. And you're always kind of on

0:33:16.840 --> 0:33:20.040
<v Speaker 1>stage as a manager, like people are watching your reactions

0:33:20.080 --> 0:33:23.000
<v Speaker 1>to all kinds of things, even if you don't feel

0:33:23.040 --> 0:33:26.239
<v Speaker 1>like you're in an official moment of managing, and so

0:33:26.320 --> 0:33:29.160
<v Speaker 1>if you react badly to bad news, there goes your

0:33:29.200 --> 0:33:31.440
<v Speaker 1>chances of candidate and put down the road. So never

0:33:31.440 --> 0:33:35.560
<v Speaker 1>shoot the messenger if you want real feedback that makes sense. Well,

0:33:35.600 --> 0:33:37.960
<v Speaker 1>hopefully this was helpful. Thank you so much for coming on.

0:33:38.760 --> 0:33:42.320
<v Speaker 1>It really was. Thank you so much. Thanks for listening

0:33:42.360 --> 0:33:44.320
<v Speaker 1>to the Asking Manager podcast. If you'd like to come

0:33:44.320 --> 0:33:46.320
<v Speaker 1>on the show to talk through your own question, email

0:33:46.320 --> 0:33:49.120
<v Speaker 1>it to podcast at Asking Manager dot org, or you

0:33:49.120 --> 0:33:51.360
<v Speaker 1>can leave a recording of your question by calling eight

0:33:51.400 --> 0:33:55.360
<v Speaker 1>five five six work. That's eight five five T six

0:33:55.480 --> 0:33:58.160
<v Speaker 1>nine seven five. You can get more ask a Manager

0:33:58.200 --> 0:34:00.240
<v Speaker 1>at ask a Manager dot org or in my book

0:34:00.280 --> 0:34:03.880
<v Speaker 1>Ask a Manager how to navigate clueless colleagues, lunch stealing bosses,

0:34:03.920 --> 0:34:05.880
<v Speaker 1>and the rest of your life at work. They Ask

0:34:05.880 --> 0:34:08.120
<v Speaker 1>a Manager show is a partnership with How Stuff Works

0:34:08.160 --> 0:34:10.360
<v Speaker 1>and is produced by Paul Deckett. If you liked what

0:34:10.400 --> 0:34:12.560
<v Speaker 1>you heard, please take a minute to subscribe, rate, and

0:34:12.600 --> 0:34:16.040
<v Speaker 1>review the show on Apple Podcasts, Spotify or Google Play.

0:34:16.320 --> 0:34:18.160
<v Speaker 1>I'm Alison Green and I'll be back next week with

0:34:18.200 --> 0:34:19.280
<v Speaker 1>another one of your questions.