TRANSCRIPT 🔗
WEBVTT
00:00:05.069 --> 00:00:09.930
Good stories provide opportunities for both simulation and inspiration.
00:00:10.489 --> 00:00:15.305
I'm Matt Abrahams and I teach strategic communication at Stanford Graduate School of Business.
00:00:15.615 --> 00:00:21.524
Welcome to this bonus Quick Thinks episode of Think Fast, Talk Smart, the podcast.
00:00:22.255 --> 00:00:31.855
During my recent interview with Dan Heath, he offered a masterclass in what makes for a great story by not only telling a great story, but helping me analyze it.
00:00:33.965 --> 00:00:43.390
I want to come back to storytelling because one of the things that really impresses me in your work
is, not only do you talk about story and analyze story, but you're actually a really good storyteller.
00:00:43.669 --> 00:00:58.510
Can you give us a little insight into your process for one, thinking about the stories that you tell in your books and when you
speak on your podcast, but also the process about how to craft and deliver those stories, because that's equally as powerful?
00:00:58.510 --> 00:01:03.940
It is the heart of what I do and what takes the most time out of everything I work on as a writer.
00:01:03.940 --> 00:01:13.080
So maybe what I should do, let me just tell a story from the book and then talk a little bit about, just gesticulate at it, and tell, tell what my intentions were in using it.
00:01:13.350 --> 00:01:19.820
So the very first story in Reset is about the receiving area at the Northwestern Memorial Hospital.
00:01:19.850 --> 00:01:24.690
So this is the part of the hospital that takes in packages, gets them delivered to their ultimate destination.
00:01:25.249 --> 00:01:32.729
And at the point when the story starts, it takes them an average of three days to get packages delivered within the hospital.
00:01:33.140 --> 00:01:42.079
The UPS might get some medicine across the country in a day or two, and then to get the package from the basement to like the third floor, it takes another three days.
00:01:42.079 --> 00:01:46.039
So it's just crazy, but it's been crazy as long as anyone can remember.
00:01:46.710 --> 00:01:48.679
It is something that everyone's adapted to.
00:01:48.679 --> 00:01:49.729
They're not dumb people.
00:01:49.769 --> 00:01:50.919
They're not lazy people.
00:01:51.220 --> 00:01:55.359
They have just always lived in a system where it takes three days to get these packages out.
00:01:55.590 --> 00:01:57.640
So, this is expensive.
00:01:57.899 --> 00:02:00.550
They're having medications expire in the box.
00:02:00.550 --> 00:02:05.270
They're having people over order because they want to dodge this chaos of the receiving area.
00:02:05.270 --> 00:02:11.039
They have people trying to make side deals with FedEx drivers to come directly to the third floor and bypass the receiving area.
00:02:11.590 --> 00:02:14.899
So into this mess comes a new person named Paul Suett.
00:02:15.165 --> 00:02:18.804
And if we just freeze there for a second, so what is this story doing?
00:02:18.804 --> 00:02:25.134
Number one, just observe that there is nothing naturally compelling about this topic area, right?
00:02:25.134 --> 00:02:29.655
There's not, there's no sex, there is no violence, there are no celebrities.
00:02:30.015 --> 00:02:42.690
It is the most boring imaginable domain and yet there are universal themes here that kind of get us on the
hook like, these were the pariahs of the .Hospital all the sudden implicitly were rooting for them, right?
00:02:42.930 --> 00:02:45.989
And then this new guy comes in and you wonder what is he gonna do?
00:02:46.010 --> 00:02:47.819
There's, there's a detective story element.
00:02:47.839 --> 00:02:50.070
What is he gonna do to untangle this mess?
00:02:50.570 --> 00:02:52.279
Yeah, you build that curiosity.
00:02:52.700 --> 00:02:57.549
But also when you were describing the problem, you didn't just itemize the different things.
00:02:57.559 --> 00:02:59.149
You actually really reinforced it.
00:02:59.149 --> 00:03:02.829
I love the point where you said, hey, UPS can do it in a day or two.
00:03:03.149 --> 00:03:06.720
That really adds a magnifier to what's coming.
00:03:06.720 --> 00:03:08.790
So I appreciated that part.
00:03:09.209 --> 00:03:10.609
So Paul Suett comes in.
00:03:10.619 --> 00:03:11.659
He's our protagonist.
00:03:11.690 --> 00:03:13.969
We talked about simulation and inspiration, right?
00:03:13.969 --> 00:03:16.040
So now we're walking in Paul Suett's shoes.
00:03:16.440 --> 00:03:19.230
First thing he does is he says, what problems can I solve for you?
00:03:19.465 --> 00:03:20.735
What's getting in your way?
00:03:21.114 --> 00:03:35.465
And so the team's giving him a laundry list of complaints and obstacles, some of them quite mundane, like, well, the wheels on the carts
that we push around are sometimes real stuck and jangly, so Suett says instantly, we'll get you new carts, new wheels, whatever you need.
00:03:35.475 --> 00:03:37.874
He's trying to just show them that he's on their team.
00:03:37.885 --> 00:03:40.755
He's not the know it all coming in to quote unquote fix things.
00:03:41.350 --> 00:03:43.700
And he invites them into the detective work.
00:03:43.700 --> 00:03:48.029
So every day for an hour, a day, twelve days in a row, they stop what they're doing.
00:03:48.170 --> 00:03:54.540
And they just walk the line from where the packages come in, through all the stations, to the eventual destination.
00:03:54.809 --> 00:03:55.889
They're noticing things.
00:03:55.920 --> 00:03:57.369
What's delaying operations.
00:03:57.369 --> 00:03:58.339
What's blocking us.
00:03:58.709 --> 00:04:07.100
The number one thing that pops out of this process is they have unwittingly used batch processes where they are not needed.
00:04:07.440 --> 00:04:08.680
We all use batch process.
00:04:08.730 --> 00:04:13.570
Nobody runs a single sock in the washer and dryer, and nobody runs a single
Load full transcript
spoon in the dishwasher.
00:04:13.570 --> 00:04:17.329
So we get the value of batch processes, but they were doing this to a fault.
00:04:17.340 --> 00:04:24.610
So the idea was let's wait until a bunch of packages build up on the receiving dock, and then we'll do the scanning into inventory all at once.
00:04:24.660 --> 00:04:25.900
Like that'll be quote unquote.
00:04:26.045 --> 00:04:26.604
efficient.
00:04:27.215 --> 00:04:34.085
But what Suett helped them realize is that there was no natural, organic reason to have these delays.
00:04:34.135 --> 00:04:44.244
That, as he said, the system should flow like a river, and we should be able to take a package and have it flow along, and we should be removing friction, removing obstacles from its way.
00:04:44.614 --> 00:04:46.614
And so it's like this aha experience.
00:04:46.634 --> 00:04:48.984
They set about completely changing the way they work.
00:04:49.294 --> 00:04:53.755
Within twelve weeks, they're delivering ninety percent of the packages in one day.
00:04:54.079 --> 00:04:58.349
Something nobody thought imaginable, much less practical.
00:04:58.590 --> 00:05:01.530
People start visiting the receiving area to learn what they've done.
00:05:01.679 --> 00:05:09.210
And so again, if you zoom out of the story for a second, there is zero of natural intrinsic value in any of these details.
00:05:09.239 --> 00:05:13.530
I mean, I said the phrase batch processes and you didn't immediately go to sleep, right?
00:05:13.569 --> 00:05:15.960
Which is, that's the power of story, right?
00:05:15.960 --> 00:05:22.430
Is once we see a protagonist and a challenge and some stakes that matter, like, we're in it.
00:05:22.710 --> 00:05:27.450
But with that batch processing, you did something I think which is very masterful, is you didn't define it.
00:05:27.480 --> 00:05:32.290
You didn't say, here's what a batch process is, because many people know what it is, but they don't know that term.
00:05:32.719 --> 00:05:34.990
But you just said, we don't wash one sock.
00:05:35.000 --> 00:05:37.390
We don't put one spoon in the dishwasher.
00:05:37.690 --> 00:05:42.910
That was a great way of explaining something without actually breaking it down and saying, now I'm explaining it.
00:05:43.195 --> 00:05:48.205
You do a great job of hooking us in and diagnosing and describing for us what you do.
00:05:48.495 --> 00:05:50.585
I'm curious, how do you find these stories?
00:05:50.595 --> 00:05:52.135
How did you find Paul Suett?
00:05:52.154 --> 00:05:53.574
Did you know him?
00:05:53.574 --> 00:05:54.844
Did somebody point you to him?
00:05:54.845 --> 00:05:56.335
Did you, were you in that hospital?
00:05:56.345 --> 00:05:57.775
How did you find that story?
00:05:58.034 --> 00:06:06.065
This is the most frustrating and rewarding aspect of the work is the majority of the way I spend my time as a writer is finding stories like that.
00:06:06.280 --> 00:06:09.490
I spend a lot of time figuring out, what am I trying to say to the reader?
00:06:09.600 --> 00:06:12.800
How am I going to arm them with principles to make their life or their work better?
00:06:12.800 --> 00:06:13.660
That's part one.
00:06:13.990 --> 00:06:23.849
And then part two is, how can I hang those principles on stories that are more compelling than me just yammering on about systems and operations and so forth?
00:06:24.400 --> 00:06:26.039
And it is like panning for gold.
00:06:26.039 --> 00:06:27.659
I mean, you've probably experienced this too.
00:06:27.729 --> 00:06:31.445
There is no reliable process for finding great stories.
00:06:31.445 --> 00:06:33.745
It is just, you got to go shake the trees every day.
00:06:33.745 --> 00:06:35.905
And then the next day you wake up and you do it again.
00:06:36.205 --> 00:06:49.085
This particular story was written up in a business school case, and there was a very heavy operation spin on it, but
there was so much that was interesting in the details that my team and I, we decided to re-report the whole thing.
00:06:49.085 --> 00:06:55.414
So I, one of my colleagues actually flew to Evanston and met with Paul Suett and saw the operations and took pictures.
00:06:55.414 --> 00:07:00.085
And in that case, it was like taking a different spin on a story someone else had already spotted.
00:07:00.405 --> 00:07:07.815
And in a lot of other cases in the book, it was just a byproduct of you have ten conversations to get down to that one story that really connects.
00:07:08.595 --> 00:07:19.855
I like, though, that you start with an idea, a goal of what you're trying to achieve, and the goal is to really
help people and to clearly explain it, and then find stories and other tools that can help get that across.
00:07:20.014 --> 00:07:26.445
And I think a lot of people skip that step, and they just try to jump to the information without having a clear goal up front.
00:07:26.970 --> 00:07:33.500
Yeah, for me stories are just like a vessel to get messages across in a reader friendly way.
00:07:33.510 --> 00:07:42.699
So it's like what that Northwestern story did for me at the start of the book was it just it brought to bear a bunch of themes that even people that are not in hospital receiving areas can recognize.
00:07:42.729 --> 00:07:45.770
What is it like to be part of a system that's stuck?
00:07:46.149 --> 00:07:52.140
And what is it like to endure subpar performance, but feel like you're powerless to affect it?
00:07:52.354 --> 00:07:57.465
And, you know, and have other people in the hospital judge you, you know, the pariahs of the hospital was a quote that came out.
00:07:57.615 --> 00:08:09.014
And what is it like to be able to undo that by finding leverage points in complicated systems and seeing how things can change actually surprisingly quickly if you find the right places to push.
00:08:09.440 --> 00:08:11.890
So it really sets expectations for what's to come.
00:08:12.070 --> 00:08:18.419
Not just in terms of what you'll be talking about in the book, but how the reader or listener will be engaged.
00:08:18.429 --> 00:08:23.799
And how we set our audiences expectations up front can really make a big difference.
00:08:24.329 --> 00:08:33.580
One of the things that frustrates me so much is speakers or people who run meetings who start by saying, I
want this to be very engaging and get you all involved, and then they talk at you for forty-five minutes.
00:08:33.620 --> 00:08:38.710
What you do in your books and in this example is you get us engaged from the get go.
00:08:39.155 --> 00:08:40.684
And that brings us along with you.
00:08:41.814 --> 00:08:46.564
Thank you for joining us for a Quick Thinks episode of Think Fast, Talk Smart, the podcast.
00:08:46.875 --> 00:08:55.984
To learn more about storytelling, please listen to our non traditional storytellers miniseries in episodes 170 and 171.
00:08:56.624 --> 00:09:00.724
This episode was produced by Ryan Campos and me, Matt Abrahams.
00:09:01.015 --> 00:09:02.844
Our music is from Floyd Wonder.
00:09:03.250 --> 00:09:05.880
With special thanks to the Podium Podcast Company.
00:09:06.440 --> 00:09:09.810
Please find us on YouTube and wherever you get your podcasts.
00:09:10.090 --> 00:09:12.190
Be sure to subscribe and rate us.
00:09:12.470 --> 00:09:15.090
Also, follow us on LinkedIn and Instagram.
00:09:15.289 --> 00:09:21.630
And check out FasterSmarter.io for deep dive videos, English language learning content, and our newsletter.
00:09:22.050 --> 00:09:31.660
Please consider our premium offering for extended Deep Thinks episodes, Ask Matt Anythings, and much more at FasterSmarter.io/premium.