TRANSCRIPTION 🔗
WEBVTT
00:00:00.000 --> 00:00:04.572
It’s not in many cases understanding the situation.
00:00:04.641 --> 00:00:05.921
that allows you to solve it.
00:00:05.966 --> 00:00:15.381
It’s understanding that there is a systemic situation, and that it is going to demand a thoughtful intervention.
00:00:21.411 --> 00:00:27.792
You’re listening to Traction Heroes, digging in to get results with Harry Max and Jorge Arango.
00:00:30.175 --> 00:00:31.754
Hey Harry, good to see you again.
00:00:32.154 --> 00:00:33.823
Excellent to see you, Jorge.
00:00:34.137 --> 00:00:36.204
I’m so glad we’re keeping it going, man.
00:00:37.628 --> 00:00:39.784
Keeping it going is what we do.
00:00:40.670 --> 00:00:48.341
I’ve brought a reading that hopefully spurs some more interesting conversation.
00:00:48.521 --> 00:00:49.421
I can’t wait.
00:00:49.993 --> 00:00:50.555
All right, let’s do it.
00:00:51.085 --> 00:01:04.917
“In the late nineteenth and early twentieth century, the lumberjacks of the Pacific Northwest felled trees and floated them down the rivers to the sawmill on the high water from melting mountain snow.
00:01:06.132 --> 00:01:11.007
From time to time, the logs would stick and cause logjams.
00:01:12.194 --> 00:01:18.844
Some logjams became famous, involving thousands of logs and flooding many square kilometers.
00:01:20.138 --> 00:01:34.796
The photograph shows one such logjam.” And then there is a photograph in the text, and here’s the caption of the photograph. “A 1907 logjam on the Coquille River, Prosper, Oregon, from a contemporary postcard.
00:01:35.581 --> 00:01:43.962
The river was prone to logjams because incoming tides had the effect of blocking the river at the estuary where the mill was located.
00:01:44.194 --> 00:01:53.727
This small logjam was two hundred and ten meters long and contained over five thousand logs.” On with the text.
00:01:53.972 --> 00:02:07.203
“Dealing with intractable situations is rather like my mental picture of the log drivers as they jump from log to log across the jam, freeing it up to get both lumber and river moving again.
00:02:08.074 --> 00:02:16.271
A skilled driver, I imagine, can spot which log to move and how to move it, surrounding logs and creating movement.
00:02:17.407 --> 00:02:32.998
Skillfully moving a small number of logs, perhaps rocking them rather than removing them, would be enough to get the water flowing, dislodging neighboring logs and breaking up the jam until eventually the flowing water once again carried the logs downstream.
00:02:34.228 --> 00:02:41.400
Systems thinking allows me to spot the ‘logs’ that, if moved, will improve the situation.
00:02:42.417 --> 00:02:46.544
I don’t have to solve every bit of the puzzle created by the messy situation.
00:02:47.282 --> 00:02:51.308
I just have to set it on a path to continuing improvement.”
00:02:52.610 --> 00:02:54.830
Well, I have to say two things jumped out at me.
00:02:54.830 --> 00:02:57.402
Number one is that sounds like a dangerous job.
Load full transcript
00:02:58.551 --> 00:03:08.710
And number two, it’s interesting that you’re talking about Oregon and then you’re using kilometers and meters, which seems like probably some kind of giveaway.
00:03:09.294 --> 00:03:10.957
I’m just not sure what kind.
00:03:11.530 --> 00:03:14.429
What is this book?
00:03:15.123 --> 00:03:23.139
So this is a book called Growing Wings on the Way, and the subtitle is Systems Thinking for Messy Situations.
00:03:23.938 --> 00:03:34.485
The author is Rosalind Armson, and I believe that Rosalind Armson is from the UK, which might explain the measurements there.
00:03:36.216 --> 00:04:01.864
I have to say, I love that idea of jumping log to log as a way of making visceral the and understandable the challenge when we’re faced with something that’s stuck at a systems level.
00:04:02.503 --> 00:04:09.894
Because looking at it as a system is often the least helpful thing to do.
00:04:10.670 --> 00:04:31.790
But zooming in can often cause us to lose sight of all of the complex interdependencies that create the situation that puts something into, into some kind of interlocking state.
00:04:32.600 --> 00:04:38.651
What were you-- Like, when did you stumble into this reading or how did you find this book?
00:04:39.315 --> 00:04:43.523
taught systems thinking at, uh, level, right?
00:04:43.523 --> 00:04:57.834
So lot of books about systems, and this one in particular stood out to me because systems thinking books tend to be fairly abstract and
00:04:58.185 --> 00:04:58.430
Mm-hmm.
00:04:59.235 --> 00:04:59.774
Yes.
00:04:59.807 --> 00:05:03.283
this book is very practical and
00:05:03.353 --> 00:05:03.362
Mm-hmm.
00:05:04.704 --> 00:05:22.858
And I chose this image of the log jam as the best way to get into the conversation because to your point, for some categories of problems, you do have to understand the system, right?
00:05:22.858 --> 00:05:26.439
You have to understand that this is not an isolated thing that is happening.
00:05:27.379 --> 00:05:47.132
It is part of a more complex situation, something that, perhaps, you’re seeing the effects of a much deeper underlying cause, you might be treating the symptoms rather than the actual cause.
00:05:47.975 --> 00:05:48.168
Mhm.
00:05:48.651 --> 00:06:05.487
So understanding the systemic situation is important, but can also lead to a sense of paralysis because on the one hand there are these questions like where do you stop, right?
00:06:05.487 --> 00:06:13.403
Like, you’re looking to understand the system. One of the trickiest things about understanding systems is where do you draw the boundaries?
00:06:14.168 --> 00:06:14.394
Mm-hmm.
00:06:14.511 --> 00:06:31.238
If you’re, um, the example I always use with my students is If you’re trying to design an electric vehicle for a world where electric charging stations do not exist, you have a problem, right?
00:06:31.283 --> 00:06:40.704
Because there’s a large network of gas, you know, petrol pumping stations for internal combustion
engines.
00:06:40.723 --> 00:06:52.305
But before they came on the market, there wasn’t really a choice, you know, for there wasn’t really like a network of electric charging stations.
00:06:55.406 --> 00:06:58.899
that created the question of like, well, where are you going to charge this vehicle?
00:06:59.874 --> 00:07:04.735
the design of the car and the design of the charging network kind of go hand in hand.
00:07:04.805 --> 00:07:05.757
And that’s, uh,
00:07:05.812 --> 00:07:05.918
Mm-hmm.
00:07:05.987 --> 00:07:14.091
designing and deploying a charging network is a different order of challenge than designing and, and producing a vehicle, right?
00:07:14.547 --> 00:07:20.076
So understanding the system is important, but it can also lead to paralysis.
00:07:20.891 --> 00:07:36.122
And this passage of the logjam, the image that stayed with me and what led me to bring it to our conversation, and I must also say I read this book many, many years ago and I haven’t revisited it in a long time.
00:07:36.740 --> 00:07:38.307
But this image stuck with me.
00:07:39.033 --> 00:07:48.939
And the reason it stuck with me is the way that these people cleared the logjams was not by going in and removing a bunch of logs.
00:07:48.983 --> 00:07:50.081
That’s not what it’s saying.
00:07:50.081 --> 00:08:00.826
What it’s saying is, you know, sometimes all it took was knowing which ones to jog, and that creates the conditions that lead the system to free itself up, right?
00:08:01.625 --> 00:08:19.807
So it’s this combination both of understanding that the situation that you’re dealing with might be almost intractably complex and like, you know, to a degree that you might actually be paralyzed if you try to intervene at a whole systems level.
00:08:20.307 --> 00:08:26.564
But also if you have the know-how to know where to intervene
00:08:26.927 --> 00:08:27.112
Mm-hmm.
00:08:27.279 --> 00:08:38.534
to intervene in a very, focused way, you can create the conditions that allow things to start flowing again.
00:08:38.922 --> 00:08:41.413
And that seems really interesting and powerful.
00:08:42.232 --> 00:08:46.703
I’m so glad you brought this reading for so many reasons.
00:08:46.714 --> 00:09:06.330
One of them is it’s tightly related to that TEDx talk I did, The Problem Is Not The Problem, you know, where it’s really about intervention strategies based on the scope of impact and the perceived solvability of, of, of a given challenge, if you will.
00:09:06.988 --> 00:09:15.250
But the thing that just jumps out at me here is it’s kind of picking up on something you said here.
00:09:15.578 --> 00:09:22.782
It’s not in many cases understanding the situation that allows you to solve it.
00:09:22.826 --> 00:09:33.168
It’s understanding that there is a systemic situation, and that it is going to demand a thoughtful intervention, right?
00:09:33.417 --> 00:09:46.333
And the distinction I’m trying to make, just to underscore it once more, is the difference between understanding the systemic situation and understanding there is a systemic situation, right?
00:09:46.583 --> 00:09:58.020
Because sometimes nothing-- sometimes just understanding there is a systemic situation allows you to figure out that there are logs you need to then start attending to.
00:09:58.296 --> 00:10:07.921
And this is incredibly similar to the work that I do in both my coaching and consulting, where I am going in and interviewing people.
00:10:07.932 --> 00:10:24.109
Like, we know there’s a systemic situation because they’ve got a problem they, that the client perceives is intractable or very, very difficult, and perhaps that they’ve even tried to solve it and maybe things have gotten worse, right?
00:10:24.436 --> 00:10:34.659
And so they pick up the phone and they call me, and I go in and typically, and you’re probably very similar in much of your work, you go in and you interview people, right?
00:10:34.951 --> 00:10:38.902
It’s about gathering information to figure out what the entry points in.
00:10:38.908 --> 00:10:41.294
What are the dynamics of the system, right?
00:10:41.388 --> 00:10:43.080
How are the pieces held together?
00:10:43.392 --> 00:10:50.366
What is changing in that system over time which can make it vexing from a solution point of view?
00:10:54.965 --> 00:11:02.798
Because, you know, you think the situation is one way, but by the time you actually start to intervene, it’s already shifted.
00:11:03.168 --> 00:11:08.346
And these things are challenging because people are involved, and people are complicated.
00:11:08.836 --> 00:11:19.326
So this notion of, in my case, I’m thinking about, you know, each conversation I’m having with somebody in a client site is a log, right?
00:11:19.671 --> 00:11:23.188
And then, of course, where do you draw the boundaries?
00:11:23.254 --> 00:11:25.292
How many conversations is enough?
00:11:25.405 --> 00:11:32.350
Every single client engagement I encounter, that’s always a question going in.
00:11:32.350 --> 00:11:38.797
It’s always a question that evolves and continues revealing itself as the work is unfolding.
00:11:38.947 --> 00:12:10.277
And at some point, I have to start-- I have to say to myself, and I often have to explain to other people, “Okay, we’re starting to see a lot of similarity in either the description of the current state, the description of the desired state, or the description of the dynamics that’s holding it in place, and even potentially the description of what’s good or what’s bad that might need to change.” And your comment about the electric car reminded me of Shai Agassi and A Better Place.
00:12:10.277 --> 00:12:12.307
I don’t know if you’re familiar with that.
00:12:12.356 --> 00:12:20.011
Shai Agassi started a company, I think he started it in Israel and then moved it to Silicon Valley.
00:12:20.013 --> 00:12:24.317
He then sold that company to SAP, and he ended up on the board of SAP.
00:12:24.836 --> 00:12:27.947
I worked at A Better Place--
Not A Better Place, excuse me.
00:12:27.947 --> 00:12:43.316
I worked at TopTier, which was the name of the company that he sold to SAP, and then I ended up-- O’Reilly brought me in to provide the information architecture expertise for the SAP developer network design.
00:12:43.827 --> 00:12:47.096
And so I ended up working with Shai and his team again there.
00:12:47.320 --> 00:13:03.298
Well, when he left SAP, he went back to Israel to create an electric car company, pre-Tesla, and encountered this problem and did not succeed.
00:13:03.702 --> 00:13:13.142
And there is a book about this, and I’ll have to go dig up the name of the book, but it is on the conundrum of what do you do when faced with these kinds of dynamics.
00:13:13.549 --> 00:13:31.697
And this is part of the magic of what Musk, love him or hate him, has managed to accomplish, is in figuring out how to move the, the vision of the electric car and the infrastructure necessary to make it possible into the mainstream.
00:13:32.234 --> 00:13:42.249
Well, it feels like that’s really fertile grounds for a different conversation, and maybe when you resurface that book, maybe bring it to one of our,
00:13:42.431 --> 00:13:42.441
Mhm.
00:13:43.028 --> 00:13:44.326
one of our podcasts.
00:13:44.510 --> 00:13:57.400
Because what I really wanted to focus on here is the more kind of tactical interventions that get the logjam flowing.
00:13:57.539 --> 00:13:57.845
Mhm.
00:13:58.557 --> 00:13:58.777
Ja
00:13:59.764 --> 00:14:05.960
I mean, another image that comes to mind is the Buckminster Fuller, trim tab thing.
00:14:06.254 --> 00:14:07.355
Oh, yes.
00:14:07.755 --> 00:14:17.606
You know, this idea that it’s really hard get the rudder of a big ship to turn because there’s the inertia of the weight of that stuff and the weight of the water.
00:14:18.263 --> 00:14:29.389
Nautical designers create this, like, mini rudder that moves the rudder, right?
00:14:29.455 --> 00:14:29.741
Mm-hmm.
00:14:29.892 --> 00:14:29.979
It’s
00:14:30.011 --> 00:14:30.346
Yeah.
00:14:30.551 --> 00:14:48.196
start small and with a small intervention, like if you know exactly where to intervene You can exert a minimal amount of force that starts the system moving in the right direction almost on its own.
00:14:48.201 --> 00:14:58.331
Like that, that’s the image that feels really important and something that I hadn’t run across before this book.
00:14:58.363 --> 00:15:07.000
I mean, I had read a lot of books about systems thinking, but many of them took the big picture approach, right?
00:15:07.000 --> 00:15:10.734
Like the whole, we need to build a charger network as we are designing the cars.
00:15:10.756 --> 00:15:12.205
Like, yeah, okay, fine, but that’s an expensive and risky proposition.
00:15:19.596 --> 00:15:33.086
The really interesting question is, you know, in this intractable situation, what is the minimum viable intervention that will get the system’s dynamics to start changing things in the direction you
want them to change in?
00:15:33.514 --> 00:15:36.394
Yeah, ’cause it’s not just the minimally viable, it’s like the minimally leverageable.
00:15:40.144 --> 00:15:42.916
It’s like, what can you do that starts building on itself?
00:15:42.932 --> 00:16:03.984
I mean, you said both things, but there’s something in the minimal, the MVP description, the minimally viable description, that often falls short for me because I think in the, in the description that you had there, you went beyond that because it really talks about the minimally leverageable or minimally accruable.
00:16:03.995 --> 00:16:08.048
Like, I’m not sure how to talk about it as a phrase, but that’s right.
00:16:08.206 --> 00:16:18.438
And weirdly, in almost all of my, like, consulting proposals, I always talk about the trim tab, you know, because I talk about the trim tab change, right?
00:16:18.452 --> 00:16:19.706
That is the thing you want.
00:16:19.716 --> 00:16:29.528
You want the thing that is going to be the smallest possible intervention that allows you to start moving the thing in the right direction.
00:16:29.955 --> 00:16:42.720
And partly that’s a risk function, you know, it’s a way to manage risk, and partly it’s because the forces are typically far too strong for any kind of significant change to happen quickly.
00:16:43.451 --> 00:17:14.294
You know, I’m gonna, I’m gonna shift directions here, um, because it might help for the sake of the conversation to illustrate a corollary to this, and one which I am, uh, risk, um, prone to, uh, and I suspect that other people who are kind of systems-minded might also suffer from this.
00:17:15.016 --> 00:17:26.192
There was an article, a blog post, and it’s one of the oldest blog posts that I am still referencing twenty-five years on.
00:17:26.556 --> 00:17:46.251
This was a blog post by Joel Spolsky called, “Don’t Let the Architecture Astronauts Scare You.” Spolsky is a developer, so he was coming, you know, he was coming at this from kind of a software engineering perspective.
00:17:46.952 --> 00:17:56.946
And the point he was making in this article is that there is a kind of mindset, and I will speak to this freely because I’m, like, guilty as charged.
00:17:56.948 --> 00:18:01.794
I’m one of these people I look at a problem, right?
00:18:02.059 --> 00:18:14.603
I look at some issue that needs solving, and I immediately start thinking about abstracting out the solution
00:18:14.980 --> 00:18:14.990
Mm-hmm.
00:18:14.990 --> 00:18:15.000
Mm-hmm.
00:18:15.163 --> 00:18:18.201
some kind of architectural construct, right?
00:18:18.878 --> 00:18:27.863
Because I start seeing it’s like, okay, this problem manifests like this in this way, and I’ve seen other parts of the system that also suffer from similar things.
00:18:28.152 --> 00:18:36.021
So if I create a layer here that solves for both of them, I will have created a systemic intervention, right?
00:18:36.559 --> 00:18:52.853
One of the examples that Spolsky uses in this post is a fairly common pattern in software development, which is part A of the application is generating some kind of message, and part B is also having to do that.
00:18:52.854 --> 00:18:55.304
So now you’re thinking, it’s like, well, I need a messaging framework
00:18:55.684 --> 00:18:55.694
Mm-hmm.
00:18:56.164 --> 00:18:57.407
to solve for all of these things.
00:18:57.410 --> 00:19:04.104
And all of a sudden, you’ve developed this new layer in the system that only deals with messages, right?
00:19:04.105 --> 00:19:09.086
And it’s like you’re designing this messaging system within this other system that you’re working on.
00:19:09.753 --> 00:19:11.666
And there’s certainly space for that.
00:19:11.666 --> 00:19:24.596
And it’s important to think about the parts of a system in ways that make them reusable and efficient, right?
00:19:25.384 --> 00:19:34.670
But it is possible to get yourself lost in abstractions and to start, um, overfitting the system in ways that are counterproductive.
00:19:35.917 --> 00:19:43.578
And sometimes what you need to do is build these little one-off interventions just to get things moving.
00:19:45.222 --> 00:19:52.698
And thinking about intervening at the broader system level will actually get in the way.
00:19:53.040 --> 00:19:53.298
Yeah.
00:19:53.298 --> 00:19:57.013
I mean, back to Shai Agassi for a minute.
00:19:57.055 --> 00:20:02.961
I mean, one of the reasons I always think of him is because he said the most memorable thing to me.
00:20:02.971 --> 00:20:15.634
He said, “The best path between two points isn’t the shortest path, it’s the most meaningful path.” And you know, I mean, you can’t really challenge that on some level.
00:20:16.124 --> 00:20:37.930
And in the kind of work that we do, I think it’s so easy to try to actually solve the big long-term thing at the expense of actually getting the near-term change to start moving in a direction that’s visible sooner and marketable internally, potentially.
00:20:44.964 --> 00:20:54.738
You know, because I think it’s one of the challenges that we face as consultants and coaches and people inside of businesses, right?
00:20:54.741 --> 00:21:13.315
People inside the business is attempting to address the root causes, which is more complicated, it takes longer, it’s a higher level abstraction, requires greater communication about what you’re doing and why, and it’s going to require a much higher level of coordination.
00:21:13.797 --> 00:21:24.821
And I think your point about just addressing these smaller things to get the movement to happen, that’s also better marketing on some level.
00:21:24.913 --> 00:21:51.981
It’s easier to communicate, and I think that’s part of the challenge isn’t just the time it takes and isn’t just the effort it takes to get these more systemic fixes in place, but it’s also trying to communicate the setup, the time, and what it will actually yield, since only two of the data points or problems have even materialized at this point.
00:21:52.426 --> 00:22:02.409
There is a role for solving the problem of logs getting jammed in the river permanently,
00:22:02.982 --> 00:22:02.992
Mm-hmm.
00:22:03.173 --> 00:22:03.455
right?
00:22:03.502 --> 00:22:19.115
You want to be able to circle back and think about how you might float these five thousand logs out without them getting stuck, and that will probably require some kind of large-scale systemic intervention.
00:22:20.001 --> 00:22:34.065
But if you are in the midst of an actual log jam, that’s not the moment to think about how you’re going to do this big architectural project.
00:22:34.519 --> 00:22:46.602
What you have to do is look for the specific logs that are, that, uh, might cause the biggest positive effect if you just kinda jog them a little bit.
00:22:47.082 --> 00:22:47.510
Yeah.
00:22:47.655 --> 00:23:11.973
And this-- You know, Ed Catmull in Creativity, Inc., the latest edition, not the first edition, hits this head-on as a strategic problem and really paints a very compelling picture for how to know when and then how to apply the longer-term, more systemic, more strategic fix.
00:23:12.499 --> 00:24:00.189
And I mean, if there’s-- if I were gonna slap snow chains on this, because it’s such a difficult say take a look at the few new chapters in Catmull’s book, Creativity, Inc., to took a course at MIT with him on this new version of the book and walked away with a real profound sense actually go beyond the point solutions and then how to actually implement the broader, more systemic solution.
00:24:03.375 --> 00:24:16.873
If you’re in a situation where the logs are backing up and the system is getting, is breaking down, that can be really scary for people, and it can throw the whole team into a state of crisis, and that’s not conducive to making progress, right?
00:24:17.349 --> 00:24:27.265
So people don’t think at their most effective.
00:24:27.266 --> 00:24:34.633
So I’m just reflecting this back because you used the word marketing, and I just wanted to sure that I heard it correctly.
00:24:34.634 --> 00:24:47.977
The way that I understood what you were saying was knowing where to do the tactical systemic intervention, and that almost seems like a contradictory statement, right?
00:24:47.977 --> 00:24:49.778
Like tactical systemic intervention.
00:24:52.371 --> 00:25:13.040
But I do think of it as, like, you know, knowing which part of the system you need to jog the thing moving again can be a very powerful tool in getting the team aligned in a more productive direction than just kind of flailing about and going, “Oh no, we are, you know, we’re in trouble here.”
00:25:13.919 --> 00:25:14.240
Yeah.
00:25:14.634 --> 00:25:18.141
Yeah, and I think it’s there’s a real gift to it as well, and part of that gift is
00:25:22.377 --> 00:25:24.201
Go, going back to the UK thing, right?
00:25:24.222 --> 00:25:25.840
Stay calm and,
00:25:26.101 --> 00:25:26.734
Carry on.
00:25:27.161 --> 00:25:28.248
and carry on, right.
00:25:28.625 --> 00:25:33.912
Well, but I think that here I would invert that statement
00:25:36.891 --> 00:25:37.295
Ah.
00:25:37.356 --> 00:25:37.761
meaning, like, you know, don’t panic.
00:25:41.003 --> 00:25:43.512
Instead, think about the system.
00:25:43.516 --> 00:26:05.394
You know, understand that what is happening is a systemic problem, but then look for the point in the system where you can intervene to get you back to a more normal situation where maybe you can actually start opening up the space to make the more permanent systemic fix, right?
00:26:06.343 --> 00:26:06.659
Yeah.
00:26:06.796 --> 00:26:09.463
And this is where leadership becomes a question.
00:26:09.582 --> 00:26:16.319
Like, at what point do you say we really need to start attending to this in a more systemic way?
00:26:16.976 --> 00:26:17.885
We need to look at it.
00:26:17.888 --> 00:26:18.974
We need to understand it.
00:26:18.989 --> 00:26:20.884
We need to figure out how to make a transition.
00:26:21.358 --> 00:26:21.892
That’s right.
00:26:22.073 --> 00:26:28.055
And I think that systems thinking is a critical leadership skill, right?
00:26:28.055 --> 00:26:32.480
Which is why I keep bringing up books about systems thinking.
00:26:32.986 --> 00:26:33.472
I love it.
00:26:33.534 --> 00:26:35.280
I wanted to share it with you.
00:26:35.281 --> 00:26:39.673
I thought it was a meaty subject, and glad that we had the opportunity to talk about it.
00:26:39.957 --> 00:26:40.836
What a great book.
00:26:40.900 --> 00:26:42.160
Yeah, I’m looking forward to reading it.
00:26:43.053 --> 00:26:44.176
Yeah, it’s very practical.
00:26:44.194 --> 00:26:45.516
I recommend it.
00:26:46.201 --> 00:26:46.500
Cool.
00:26:46.557 --> 00:26:47.181
Thanks, Jorge.
00:26:47.726 --> 00:26:49.506
All right, Harry, good to talk to you.