文字起こし 🔗
WEBVTT
00:00:25.692 --> 00:00:33.402
Here's an example of going from a tactical operational doer to a high level strategic leader.
00:00:34.002 --> 00:00:34.781
So here's the example.
00:00:34.781 --> 00:00:44.292
I was speaking with this individual, and this individual had received a request from their boss, and their boss had said, Hey, so and so, tell me what you want your org to look like.
00:00:44.472 --> 00:00:45.551
And so the individual.
00:00:45.911 --> 00:00:54.851
Went and prepared a very well designed and professional looking org chart on a slide deck and gave that back to the boss.
00:00:56.171 --> 00:01:14.121
And from the boss's overall response and reaction, it was clear that that wasn't quite what the boss was looking for, so then this individual and I were speaking and it became apparent that the org chart, while not wrong, was not the fulsome answer.
00:01:14.647 --> 00:01:18.367
The boss was looking for context for this.
00:01:19.326 --> 00:01:35.167
There were conversations before and around this request that made it apparent that the boss wasn't just asking for an org chart, so the context and the conversations were this boss came in and was trying to overhaul.
00:01:35.902 --> 00:01:45.921
This company, because the company was kind of archaic, old processes, old systems, old tools, stuck in an old mindset, very reactive.
00:01:46.311 --> 00:01:59.662
And this new boss was brought in to make this company cutting edge, to be at the forefront of the industry, to incorporate AI into what they were doing, to be a thought leader and to not be as reactive.
00:01:59.962 --> 00:02:03.921
And so the boss was going through to all the different main departments and saying.
00:02:04.287 --> 00:02:10.467
What do you need to revamp and overhaul and how, you know, tell me what you need to get us to that cutting edge.
00:02:10.856 --> 00:02:23.977
And all these very senior leaders were putting together proposals and going through all these different contingency plans and how this would interact with these teams and how this would interact with the other players in the market, et cetera, et cetera.
00:02:24.396 --> 00:02:30.366
And so the boss had gone through two main teams before this individual's team.
00:02:30.667 --> 00:02:33.967
And so when they got to this individual and said, what do you want your org to look like?
00:02:34.266 --> 00:02:38.227
And the individual gave them an org chart.
00:02:39.616 --> 00:02:42.676
It was kinda like head, head tilt, like, mm, what?
00:02:42.736 --> 00:02:45.917
No, no, I, I wanted a bit more from that.
00:02:46.456 --> 00:02:51.526
So in this individual's mind, it was, well, what do you want this org to look like?
00:02:51.796 --> 00:02:55.067
In kind of a literal sense was here's the org chart.
00:02:56.227 --> 00:03:04.896
I don't really think anything needs to change, per se,'cause it seems to be working okay now was kind of the gist and kind of the sentiment of the answer of the response.
00:03:05.407 --> 00:03:13.507
And in the discussion with this individual, I said, okay, let's think bigger picture, because I think a different question is being asked here.
00:03:13.507 --> 00:03:17.467
I think an org chart is part of the answer, but certainly not the entire answer.
00:03:17.736 --> 00:03:18.757
So we talked about.
00:03:19.727 --> 00:03:22.187
What is the vision for the overall company?
00:03:22.217 --> 00:03:30.977
This boss has a new vision for the company, and we talked about that, which was very well stated in, in presentations, in different meetings this individual had been in.
00:03:31.396 --> 00:03:37.606
And so this was pretty, this was pretty, you know, cutting edge AI thought leadership out in the industry.
00:03:37.907 --> 00:03:39.706
We're responding to our customers in a different way.
00:03:39.706 --> 00:03:41.387
We're responding to each other in a different way.
00:03:41.537 --> 00:03:43.516
All these different things that had been said.
00:03:44.731 --> 00:03:51.002
Okay, so the, to the individual, individual, how does your department feed into that vision?
00:03:52.111 --> 00:03:57.211
What does your department need to do to contribute to that vision and this specific department?
00:03:58.157 --> 00:04:15.407
Had a lot of interaction with the other teams and they were, uh, feeding the other teams a lot of information and then asking, receiving a lot of information from the other teams to assimilate that and produce data sets that the leadership team and the board could look at that were useful.
00:04:15.586 --> 00:04:23.672
And so this was, this was kind of the behind the scenes machine that had a lot of valuable intel and information if you collected and then.
00:04:24.076 --> 00:04:30.377
Sliced and diced data in different data sets for different constituents and groups to take action on.
00:04:30.677 --> 00:04:32.146
So this was a very powerful team.
00:04:32.177 --> 00:04:34.127
If, if it was done right and.
00:04:34.966 --> 00:04:37.966
We talked about connecting it to the overall vision of the company.
00:04:38.146 --> 00:04:42.557
We talked about the interaction that would be had with the other teams.
00:04:42.887 --> 00:04:46.906
We talked about the, you know, the vision for this department.
00:04:46.906 --> 00:04:47.836
What does it look like?
00:04:47.836 --> 00:04:48.797
What does it smell like?
00:04:48.797 --> 00:04:50.447
What does it, you know, taste like, all these different things.
00:04:50.447 --> 00:04:54.737
What does it sound like when you walk through the, this area of the.
00:04:55.151 --> 00:04:56.742
Of the building, what is, what should it sound like?
00:04:56.742 --> 00:04:57.641
All these different things.
00:04:57.641 --> 00:04:58.872
Just to paint the picture here.
00:04:59.382 --> 00:05:05.172
And this got us to a more robust and vibrant, okay, here's what we needed to be.
00:05:05.502 --> 00:05:10.872
And I had to nudge this person and kind of pull this out of the person.
Load full transcript
00:05:10.872 --> 00:05:18.762
'cause this person had been there for quite some time and they were a little bit stuck in the old, archaic way of doing things.
00:05:18.762 --> 00:05:20.141
Well Emily, we can't do that.
00:05:20.711 --> 00:05:22.812
'cause this is how these teams work together.
00:05:23.851 --> 00:05:26.762
It is now, but in the new vision, what does that look like?
00:05:27.302 --> 00:05:30.752
Uh, you know what, what needs to happen with this data set?
00:05:30.752 --> 00:05:31.622
Well, we can't pull that.
00:05:31.622 --> 00:05:32.521
'cause this system's old.
00:05:32.762 --> 00:05:34.052
It doesn't do that with the data.
00:05:34.711 --> 00:05:35.101
Okay.
00:05:35.101 --> 00:05:36.151
It doesn't do that now.
00:05:36.151 --> 00:05:37.622
But how can we do that in the future?
00:05:37.622 --> 00:05:41.101
If you could do anything with the data, what would that look like?
00:05:41.182 --> 00:05:52.822
And we went through an exercise of let's capture what's happening in the current state, And then let's vision cast the future state, which I think is what the boss is asking around what's the future state?
00:05:52.822 --> 00:05:53.872
What's the ideal state?
00:05:53.872 --> 00:05:58.072
If you could have anything for your department, what would that be?
00:05:58.492 --> 00:06:01.911
Because it's kind of a catalyst carte blanche moment right here.
00:06:01.911 --> 00:06:09.322
Maybe not like to, you know, billions of dollars, you know, to fund your department and all the changes, but it looks like there's some fresh blood here.
00:06:09.322 --> 00:06:11.992
It looks like there's some opportunities to ask for what you want.
00:06:12.262 --> 00:06:15.862
So create that vision for yourself and for your department.
00:06:16.161 --> 00:06:25.822
And when we did that, then this larger conversation and this larger vision, then informed.
00:06:26.346 --> 00:06:31.896
Multiple pieces of the answer and of the recommendation back to the boss.
00:06:32.346 --> 00:06:36.336
Some of it was updating systems and tools like, look, this thing is old and ancient.
00:06:36.757 --> 00:06:41.406
There are dozens of other systems and software that we could move to.
00:06:41.617 --> 00:06:42.877
It'll take an initiative.
00:06:42.877 --> 00:06:48.966
It'll take at least a quarter, if not two, to move all of our information over to this new one, but it's well worth it.
00:06:48.966 --> 00:06:50.226
That's the baseline.
00:06:50.706 --> 00:06:58.716
There was talk about, Hey, we need a communication plan for this team to be talking to other teams while we're all moving.
00:06:58.716 --> 00:06:59.016
Right?
00:06:59.016 --> 00:07:00.036
Everything's moving.
00:07:00.036 --> 00:07:03.997
We're all trying to revamp and overhaul our respective teams and departments.
00:07:04.237 --> 00:07:04.956
We don't want anything to get.
00:07:05.182 --> 00:07:06.021
To get dropped.
00:07:06.232 --> 00:07:09.291
So an interim communication plan was proposed as well.
00:07:09.291 --> 00:07:14.692
So like let's just keep in touch, like we're gonna do manual, keep in touches before we get this stuff automated.
00:07:14.901 --> 00:07:17.901
But as we roll this stuff out, we don't want anything to drop.
00:07:18.141 --> 00:07:23.362
And then part of that answer was indeed the org structure.
00:07:24.427 --> 00:07:37.326
So to support the new vision and like what this department could do and how it could thrive, and how it could be robust and what kind of amazing data we can inform our internal folks with, we can inform external vendors and constituents with.
00:07:37.627 --> 00:07:39.406
That would be really useful and valuable.
00:07:40.721 --> 00:07:45.612
From that, informed by that we do indeed need to do a reorg.
00:07:46.182 --> 00:07:50.831
And in this case we, you know, we're talking about pods versus functional areas.
00:07:50.831 --> 00:07:53.502
Do we wanna make this function into actual two roles?
00:07:53.682 --> 00:07:56.081
So then we split people off into those two functions.
00:07:56.382 --> 00:08:02.471
There were different contingency plans and options for, Hey, here's option A, B, and C for the org chart.
00:08:02.817 --> 00:08:07.166
I recommend option A for these reasons, but there's other ways to do this as well.
00:08:07.346 --> 00:08:08.726
I wanted to get those on the table.
00:08:09.086 --> 00:08:19.916
All of these three, option A, B, and C are in support of this new vision for where I think the department needs to be to support the overall company's goal and objective.
00:08:20.906 --> 00:08:22.947
So can you see the difference?
00:08:22.947 --> 00:08:26.156
Can you hear the difference of what do you want your org to look like?
00:08:26.547 --> 00:08:27.536
Here's the org chart.
00:08:28.161 --> 00:08:30.531
Versus Here's the vision for the department.
00:08:30.531 --> 00:08:35.692
If we're going this direction as a company, I'm so excited because this department has been underutilized.
00:08:35.692 --> 00:08:36.892
We can do this, this, and this.
00:08:36.951 --> 00:08:38.451
Here's what it would take to do that.
00:08:38.572 --> 00:08:42.442
I think out of the seven things that I would love to do, I know we can't do all of them now.
00:08:42.591 --> 00:08:46.011
I would pick these two, like if you can give me three, I can get you this.
00:08:46.131 --> 00:08:48.201
So saying, if you give me this and this and this.
00:08:48.572 --> 00:08:55.922
I will get you this part of the vision that is the conversation, that is the answer that I think this boss was looking for.
00:08:56.221 --> 00:09:03.841
Part of that was the recommendations for the new system and the new org structure and the interim communication process.
00:09:04.111 --> 00:09:12.361
But just handing this person, just handing the boss an org chart, Was not the high level strategic answer.
00:09:13.022 --> 00:09:19.111
It was an org chart, which is needed at some level, at some stage of this thing.
00:09:19.111 -->
00:09:22.532
But, but it, it wasn't, it was, it was a task.
00:09:22.562 --> 00:09:23.461
It was check, check.
00:09:23.881 --> 00:09:26.881
I have it on my to-do list to deliver this thing to the boss.
00:09:27.001 --> 00:09:27.991
I got it off my list.
00:09:27.991 --> 00:09:28.652
Now it's done.
00:09:29.312 --> 00:09:30.721
That's tactical.
00:09:31.111 --> 00:09:38.491
The larger conversation and connecting the dots is where the strategy piece comes in, is where you add value as a strategic leader.
00:09:39.032 --> 00:09:44.581
And part of this too, a big part of this for this individual was they were used to getting a more specific ask.
00:09:45.331 --> 00:09:49.292
If someone wanted something, they would detail, I want it like this.
00:09:49.292 --> 00:09:50.792
I'm looking for this, this, and this.
00:09:51.032 --> 00:09:52.412
It needs to be this, not that.
00:09:52.591 --> 00:09:53.672
Make sure you don't do that.
00:09:53.672 --> 00:09:56.552
They, they put parameters and put kind of guideposts around it.
00:09:56.942 --> 00:09:59.011
In this case, it was more like you tell me.
00:09:59.567 --> 00:10:00.947
You tell me what it should look like.
00:10:01.547 --> 00:10:06.706
That is also a big jump from tactical operational doer.
00:10:06.706 --> 00:10:09.287
I complete tasks to, oh.
00:10:09.902 --> 00:10:18.572
You want me to paint the outline of what this department should look like or could look like, or what I think it should look like?
00:10:18.572 --> 00:10:18.902
Right.
00:10:19.081 --> 00:10:21.032
That's a different, that's a whole different animal.
00:10:21.361 --> 00:10:22.951
It's not, I'm giving you the box.
00:10:22.951 --> 00:10:23.522
Fill the box.
00:10:23.522 --> 00:10:27.001
It's like you tell me the box, you tell me the parameters.
00:10:27.361 --> 00:10:28.621
Oh, okay.
00:10:29.101 --> 00:10:30.542
That takes more thought.
00:10:30.751 --> 00:10:31.652
That's not a check.
00:10:31.652 --> 00:10:31.981
Check.
00:10:31.981 --> 00:10:33.001
Cross off my list.
00:10:33.001 --> 00:10:36.692
That takes like, think about it, like where do you see the department?
00:10:37.231 --> 00:10:38.552
Where do you think it could get to?
00:10:39.001 --> 00:10:41.432
Where do you think it could add the most value?
00:10:41.552 --> 00:10:43.292
And maybe you're not doing that today.
00:10:43.292 --> 00:10:45.182
Maybe it's a brand new way to add value.
00:10:45.182 --> 00:10:47.341
So what can you conceive of?
00:10:47.341 --> 00:10:48.272
What can you imagine?
00:10:48.272 --> 00:10:51.481
What's your vision for your department that's higher level thinking?
00:10:51.481 --> 00:10:51.812
Right?
00:10:51.871 --> 00:10:56.912
And then they gotta back into and reverse engineer into, okay, how do we make this thing happen?
00:10:57.032 --> 00:10:59.402
Which does include tactical and practical things.
00:10:59.927 --> 00:11:02.356
Which does include operationalizing that strategy.
00:11:02.657 --> 00:11:03.826
So you have to have both.
00:11:03.947 --> 00:11:06.136
Sometimes you delegate, sometimes you do it yourself.
00:11:06.346 --> 00:11:16.427
There is that component, but first and foremost is the larger question, is connecting the dots is going okay.
00:11:16.697 --> 00:11:22.576
The boss has basically given me a blank slate and a blank check for what I wanna do with this department.
00:11:23.326 --> 00:11:27.886
I'm not just gonna hand them an org chart, I'm gonna have this larger conversation and.
00:11:28.922 --> 00:11:35.822
This individual ended up having conversations with their team, so their direct reports like, Hey, like what is your vision?
00:11:35.822 --> 00:11:36.782
What are your ideas?
00:11:36.961 --> 00:11:38.072
Having it at their level.
00:11:38.101 --> 00:11:39.662
'cause they're closer to some of the things.
00:11:40.076 --> 00:11:42.086
on a day-to-day level than this individual.
00:11:42.086 --> 00:11:48.206
And then incorporating and kind of sizzling all of that into, okay, and here's what I was thinking about and here's what I've heard the boss say.
00:11:48.297 --> 00:11:51.836
And here's what I've seen other people do when they're overhauling their departments.
00:11:51.866 --> 00:11:56.517
And here's some conversations I had with some other leadership team members over on the side here.
00:11:56.787 --> 00:12:00.206
I'm taking this all in, I'm taking the best parts of it.
00:12:00.356 --> 00:12:02.067
I'm discarding what's not useful.
00:12:02.277 --> 00:12:07.106
I am, I'm formulating this fulsome robust, vibrant answer.
00:12:07.856 --> 00:12:09.626
And then delivering that to the boss.
00:12:10.047 --> 00:12:24.267
And then maybe as a later part of that conversation, or maybe even a subsequent conversation, or maybe even 4, 5, 6, 7 conversations down the line, it becomes, and here's the specific or chart.
00:12:26.277 --> 00:12:27.147
Do you hear the difference?
00:12:27.147 --> 00:12:27.956
Do you see the difference?
00:12:28.037 --> 00:12:30.346
And sometimes it's interesting people go, Emily.
00:12:31.547 --> 00:12:33.826
They just don't see me as a strategic leader.
00:12:34.037 --> 00:12:35.506
They don't take me seriously.
00:12:35.986 --> 00:12:38.116
And sometimes that's on them.
00:12:38.147 --> 00:12:46.397
That's external reasoning, but sometimes it's because you are answering the question with an org chart, you're answering the question in a small way.
00:12:47.147 --> 00:12:51.826
It's not wrong, it's not inaccurate per se, but it's not the full answer.
00:12:52.517 --> 00:12:56.956
And a lot of times, bosses and people are looking for, oh, she gets it.
00:12:57.376 --> 00:12:58.996
She gets the big picture.
00:12:58.996 --> 00:13:00.197
She gets what we're trying to do.
00:13:00.376 --> 00:13:02.626
Oh, he's able to make that jump.
00:13:02.626 --> 00:13:08.206
He's able to say, we're firefighting this stuff right now, but in 18 months we've gotta get here.
00:13:08.687 --> 00:13:10.371
And I have ideas about how to get there.
00:13:11.027 --> 00:13:14.956
He does that, he's gonna come up and be a high level leader at this company.
00:13:15.856 --> 00:13:16.907
There's a difference.
00:13:16.996 --> 00:13:29.687
So I think think through for yourself, think through in the next week, in the next month, where can you be answering some questions in a more fulsome way versus just the, here's the org chart.
00:13:30.407 --> 00:13:34.216
And, and the org chart is symbolic in the sense of the small answer.
00:13:34.817 --> 00:13:39.616
So if you think back, you, maybe you can think backward too, in the last week, in the last month.
00:13:40.307 --> 00:13:42.407
Or even last quarter, like, oh, you know what?
00:13:42.706 --> 00:13:46.187
That's what was happening last quarter when I gave'em this thing.
00:13:46.307 --> 00:13:47.956
And they were kind of like, okay, whatever.
00:13:47.956 --> 00:13:51.197
We'll take that and then we'll come up with the answer ourselves.
00:13:51.197 --> 00:13:53.236
I guess that's kind of what was happening there.
00:13:53.236 --> 00:13:54.706
I didn't give'em the full answer.
00:13:55.126 --> 00:13:56.927
What might have that full answer look like?
00:13:57.346 --> 00:13:59.567
Can I do a follow up now or is it maybe too late?
00:13:59.807 --> 00:14:00.557
If it's too late?
00:14:00.586 --> 00:14:01.067
Okay.
00:14:01.216 --> 00:14:04.157
Going forward when I get these opportunities again.
00:14:04.652 --> 00:14:09.631
When I get these questions or requests or prompts again, how can I answer in a more fulsome way?
00:14:09.932 --> 00:14:11.881
How can I tie that to the big picture?
00:14:12.572 --> 00:14:16.201
Alright, so that can be your takeaway in the next week, in the next month for you.
00:14:16.381 --> 00:14:25.471
Keep an eye out, look for opportunities to move from a tactical operational doer to a more high level strategic leader.
00:14:25.591 --> 00:14:30.932
And one way to do that is to answer in a more fulsome way and put the big picture in place.
00:14:31.652 --> 00:14:35.491
Alright, hopefully that was helpful and I'll catch you next week on leveraging leadership.