Latest / No Way Out / Theory of Constraints: Flow, TPS and Boyd's OODA Loop with Steve Holt | Ep 53
Transcript
- 0:21Brian "Ponch" Rivera: All right.
- 0:21Brian "Ponch" Rivera: There are just times when you have to stop what you're doing, having a conversation with somebody, ask them to come on a Riverside FM and record with you.
- 0:28Brian "Ponch" Rivera: This is one of those moments where our friend, steve Holt, who happens to be a technical fellow at Boeing and, by the way, all of the views that he shares today are his own, potentially, and he'll make that clarification if we need to.
- 0:41Brian "Ponch" Rivera: But I've known Steve for several years now.
- 0:45Brian "Ponch" Rivera: We've engaged up in Canada, up at Whistler through Dave Snowden, and, of course, at the Kinevin Oodleoo exploratory that we had in Quantico, virginia, in 2019.
- 0:55Brian "Ponch" Rivera: So I got to spend a lot of time with Steve, and Steve happens to know a lot about John Boyd and the theory of constraints and quite a bit of other things that I just don't have the depth of knowledge about.
- 1:06Brian "Ponch" Rivera: So let me start with how this conversation began.
- 1:09Brian "Ponch" Rivera: Got an email and said hey, brian, are you familiar with Dan Peterson's book Top Gun?
- 1:14Brian "Ponch" Rivera: Did you know that back in early 1970s, john Boyd had an engagement with the Navy Fighter Weapon School where there was a disagreement?
- 1:25Brian "Ponch" Rivera: And I made the comment yes, I'm very familiar with that and that's where the conversation started today, but we don't know where it's going to go.
- 1:33Brian "Ponch" Rivera: But anyway, welcome, steve.
- 1:34Brian "Ponch" Rivera: Great to have you here on.
- 1:36Brian "Ponch" Rivera: No Way Out Been looking forward to having you on as a guest and here you are, and I know it's the last minute thing, isn't it?
- 1:43Brian "Ponch" Rivera: So this is going to be fun.
- 1:44Brian "Ponch" Rivera: So, steve, we were talking, prior to coming on the recording, about a few things that happened in the 70s and some watershed moments that we believe happened to John Boyd.
- 1:54Brian "Ponch" Rivera: Do you want to share some of your insights with the audience?
- 2:00Steve Holt: Well, I was reading the book, the story of Boyd running into the top ground instructors, and in some ways it didn't quite feel right in a way.
- 2:11Steve Holt: So it seemed like Boyd gave up the argument a little bit too early, but at the same time, at the time he was making the point, at least in the story, that it was all about the technology, it was all about the airplane, which just seemed totally at odds with the same Boyd that said people fight wars and they use their minds and people process and tools in that order.
- 2:39Steve Holt: So it seems like either he was compiling this and put it together and it helped him realize yeah, there's got to be something more to it, or something similar.
- 2:55Steve Holt: But it did seem to be what seems like a pivotal moment.
- 3:03Brian "Ponch" Rivera: And just for some more context there, the Dan Peterson's book, and we've written about this a few times.
- 3:09Brian "Ponch" Rivera: We talked about this a few times on the podcast.
- 3:11Brian "Ponch" Rivera: It's really John Boyd coming in with his EM theory.
- 3:14Brian "Ponch" Rivera: In my view it's a closed system view of how things work and it's very powerful.
- 3:24Brian "Ponch" Rivera: Many folks think that EM theory has a nice connection to even the free energy principle, a nice connection to agility.
- 3:30Brian "Ponch" Rivera: There's a lot of possible connections there that we may delve into in this podcast down the road.
- 3:38Brian "Ponch" Rivera: But the EM theory was so powerful that we ended up with the F-16, f-15, yf-17, which is now the F-18 out of that program and it really influenced quite a bit about how we designed aircraft.
- 3:49Brian "Ponch" Rivera: But the top gun, the Navy Weft Fighter, weft School Bros did is.
- 3:53Brian "Ponch" Rivera: They came in and said hey, you're forgetting about one thing, probably the most important thing, and that's the crew or the person in the cockpit.
- 4:00Brian "Ponch" Rivera: There's an open system, a complex adaptive system that's actually going to fight with this machine as one fighting another potential combatant in an air and some type of dog fight.
- 4:14Brian "Ponch" Rivera: So that's the conversation.
- 4:17Brian "Ponch" Rivera: It's kind of a thumbnail sketch of what was actually said down in, I think, if it's, eglin Air Force Base in the early 70s, but this is where we're pulling from right now.
- 4:26Brian "Ponch" Rivera: Is that engagement with John Boyd?
- 4:29Brian "Ponch" Rivera: So Steve and I were having that conversation.
- 4:32Brian "Ponch" Rivera: I agree with Steve that there is a we all go through a learning process and I think at that point Steve John Boyd was fixated on entropy, the second law of thermodynamics applied to closed systems and we know today that living systems, we fend off the second law of thermodynamics entropy, that's how we persist through time.
- 4:59Brian "Ponch" Rivera: Right, that's how we live is we're always fighting the second law of thermodynamics and when we lose, we're part of the system.
- 5:06Brian "Ponch" Rivera: Right, and that's called death.
- 5:08Brian "Ponch" Rivera: Right.
- 5:09Steve Holt: So just back to the if everything's stable, you're dead.
- 5:13Brian "Ponch" Rivera: Yeah, and this is why it's so important to it's okay to have that closed system view of things and an open system view of things Because, as you know and we all know that we don't we're always going back and forth between different types of systems, and that's what we get from the dynamics of the Kinevan framework.
- 5:32Brian "Ponch" Rivera: So, steve, I appreciate those insights today and anything else you want to add on that topic before we jump over to theory of constraints.
- 5:42Steve Holt: Maybe not, but I'll come back to it if I think of some more of what we're going on.
- 5:45Steve Holt: All right, I did think I would.
- 5:48Steve Holt: I might tell you, though, how I first came across Boyd yeah, please do Because it was.
- 5:53Steve Holt: It was a direct result of a theory of constraints.
- 5:56Steve Holt: So I was in a workshop from a person that was helping us.
- 6:02Steve Holt: His name is Tony Rizzo and he he actually was talking about critical chain project management and how to do it and he brought up Boyd and he expressed Boyd from a standpoint of the, the kind of prototypical OODA loop, and talking about the fact that he saw the point of saying Boyd's approach to, to going faster than your opponent, applies to product development.
- 6:37Steve Holt: So if you can get your products to market faster, then you're going to, you're going to win right, and it's.
- 6:46Steve Holt: There's a.
- 6:46Steve Holt: There's some great examples from the past with the I think it was Yamaha and Honda's motorcycle wars, hewlett Packard did that with digital cameras for a long time where you would say, why would I, why would I buy from these guys, when, when these guys are turning out a brand new model every six months, right, so you, you capture the market by going faster.
- 7:12Steve Holt: Well, this really got me interested in in knowing more about Boyd.
- 7:17Steve Holt: So that just started off this whole reading campaign, right I I followed up with, like Bill Lynn's maneuver warfare handbook, frans Ozinga's book, chat Richards, certain to win right, corum's book, obviously, and just on and on and on and it, it just really it really looked to me like.
- 7:40Steve Holt: And then I realized that there was a, there was maneuver conflict theory and not just maneuver warfare theory.
- 7:49Steve Holt: And then the fact that Boyd, according to chat Richards right, had actually looked at Toyota and said at the time, very early on, that the only example he had ever run into in in business was the Toyota product development system.
- 8:10Steve Holt: And this was before any book had been written, as far as I know, on the Toyota product development system.
- 8:19Brian "Ponch" Rivera: It came out later in a really, really major work by Leica and Morgan, and I have actually, you and I, we've been in the archives and we got the chance to look at that.
- 8:31Brian "Ponch" Rivera: We've had Charlie Protsman on the show, a single prize winning author, charlie Protsman.
- 8:36Brian "Ponch" Rivera: And right, I happen to have in front of me some of the notes from the machine that changed the world and I was going to read some of these.
- 8:42Brian "Ponch" Rivera: These are John Boyd's notes in the book.
- 8:44Brian "Ponch" Rivera: These comments are misleading.
- 8:46Brian "Ponch" Rivera: Authors did not read Ono carefully enough, right?
- 8:48Brian "Ponch" Rivera: That's from page 56.
- 8:50Brian "Ponch" Rivera: These comments, together with those on the next page, reveal once again authors have failed to come to grips with Ono's concepts and associated action as to what's being done, why it's done and how it works.
- 9:01Brian "Ponch" Rivera: And he goes on and on.
- 9:02Brian "Ponch" Rivera: I've got one last one here.
- 9:03Brian "Ponch" Rivera: It's clear from reading chapter three that the authors did not come to grips with Taiichi Ono and the Toyota production system.
- 9:10Brian "Ponch" Rivera: Furthermore, there are no mentions of Shingo and his contributions.
- 9:16Brian "Ponch" Rivera: Why is this so?
- 9:17Brian "Ponch" Rivera: Because, in reality, they do not understand how to make snowmobiles, which in turn permits one to leapfrog the competition.
- 9:23Brian "Ponch" Rivera: And leapfrogging is the name of the game if you want to survive and grow in an evolving competitive reality.
- 9:29Brian "Ponch" Rivera: These are John Boyd's notes inside the book the machine that changed the world.
- 9:35Brian "Ponch" Rivera: Right, it's pretty amazing.
- 9:38Steve Holt: And because you're right, I've got a chance to go to the archives as well and read this material and it's really fantastic to read what he wrote.
- 9:47Steve Holt: And this is an example where he's criticizing some people that are viewed today as some of the real seminal thinkers right, and making the point that they didn't really understand the real concept.
- 10:00Steve Holt: And you can look at that with a certain degree of arrogance, of course, but that doesn't necessarily mean he's wrong, right?
- 10:09Brian "Ponch" Rivera: Correct, yeah, and he's an equal opportunity critic, a player, yeah, critic, yeah.
- 10:18Brian "Ponch" Rivera: So I mean, there's so many things that we're talking about today that I imagine he would critique you and I were talking about the free energy principle, active inference, bayesian inference, things like that, but theory of constraints, I don't know.
- 10:30Brian "Ponch" Rivera: Did Boyd have access to theory of constraints, or can you walk us through the history of that a little bit more?
- 10:36Steve Holt: It's sort of hard to say.
- 10:37Steve Holt: The real primary work from theory of constraints that comes out the most.
- 10:44Steve Holt: The most people learn about is Ellie Goldrath's book the Goal.
- 10:48Steve Holt: And he I mean he was a PhD nuclear physics that converted over then into helping to create success in businesses and from almost from day one he focused on flow and the importance of improving flow.
- 11:12Steve Holt: So when he wrote the Goal it was interesting.
- 11:18Steve Holt: We're used to the concept of a business novel today, but it appears that the Goal was the first ever business novel and he wrote it intentionally as a story because he thought it would be more effective at getting people to pay attention.
- 11:36Steve Holt: And so he wrote the book and then he shopped it around to dozens of publishers and they all rejected it, except one, north River Press and he was very pleased with that and has gone back to North River Press on all his subsequent books.
- 12:00Steve Holt: That book is really effective because it's a story of a plant manager who's given 90 days to increase profitability of his plant or it'll be shut down and all the people laid off.
- 12:11Steve Holt: And he realizes through some meeting an old college professor of his, that just about everything he learned in MBA school is going to take him in exactly the wrong direction.
- 12:24Steve Holt: So he he implements some things that are extremely effective and he saves the day, right?
- 12:33Steve Holt: Well, you learn how to do production scheduling along the way reading this book.
- 12:39Steve Holt: But it isn't a book to explain this to you, right?
- 12:44Steve Holt: You just get it because you come away from reading that book and saying, wow, I wish we could do that.
- 12:54Steve Holt: And there's a bit of an irony here because the the the story is that Goldwright wrote that book as marketing and when you you would get to the end of the book and you'd see the if you want more information, call us up and we'll sell you our software.
- 13:08Steve Holt: What was happening is he would run into people and they'd say, hey, I read the book, I did exactly what you said, and they had our profits are up 20%.
- 13:18Steve Holt: So people weren't buying the software, they were just using the basic principles in the park.
- 13:26Steve Holt: And he had to retrench and he had to step back and say, okay, what am I missing here?
- 13:32Steve Holt: And then that's when he kind of converted his whole I don't wanna say business model, because his original partners were not that happy with him, because he basically said we have to stop selling software and actually help teach people how to think, and that became his goal in life.
- 13:53Steve Holt: Is teaching people how to think Sounds familiar?
- 13:57Steve Holt: Yeah, it does, doesn't?
- 13:59Brian "Ponch" Rivera: it, yeah.
- 14:00Brian "Ponch" Rivera: So when I first came across Gold Rat's work, theory of Constraints was through Gene Kim's the Phoenix project.
- 14:08Brian "Ponch" Rivera: Right, so I didn't get a chance.
- 14:11Brian "Ponch" Rivera: Yeah, so Gene Kim followed the same approach.
- 14:13Brian "Ponch" Rivera: We get DevOps, or the kind of DevOps, out of that world same type of thinking.
- 14:18Brian "Ponch" Rivera: One of the things I'm seeing with Theory of Constraints, though, is and I think you and I talked about this several years ago as well that is, some people take it as a one size fits all approach, right, and then they don't look into what constraints actually mean, and I'll tell you right now like, the feedback pathway inside John Boyd's ooloop is a constraint, all right.
- 14:39Brian "Ponch" Rivera: This is pretty cool, and so is the new information that's coming in from the outside world, because that gives you context, which is a constraint, right.
- 14:46Brian "Ponch" Rivera: So we get into governing constraints, we get into enabling constraints.
- 14:49Brian "Ponch" Rivera: We get all these different things and kind of like biases.
- 14:52Brian "Ponch" Rivera: When people say there's a cognitive bias out there and it has a negative annotation or connotation with it, it's not a bad thing.
- 15:00Brian "Ponch" Rivera: Biases are okay-ish, and I think constraints can be viewed as okay-ish.
- 15:06Steve Holt: There's sometimes we need a little yeah, definitely there's a.
- 15:08Steve Holt: Once I started looking at the Knevin framework and we talked initially it said it talked about enabling constraints right, and that led me then to try to find more about enabling constraints.
- 15:21Steve Holt: So that led to Alicia Guerrero and other people and I realized that and I ended up doing a presentation at a TOC conference in 2019, where I made the point that TOC is filled full of enabling constraints, but we don't call them constraints.
- 15:45Steve Holt: We actually call them solutions.
- 15:47Steve Holt: And if you go back to the goal, there's a great example in there.
- 15:52Steve Holt: There is a machine in the factory that is their constraint, and so the main character, alex, says what can we do to increase the flow of parts for this machine?
- 16:06Brian "Ponch" Rivera: Yeah.
- 16:08Steve Holt: One of the things he realizes is when lunchtime comes, everybody takes the lunch break.
- 16:13Brian "Ponch" Rivera: Yep.
- 16:14Steve Holt: So what he said was stop doing that.
- 16:16Steve Holt: From now on, I want you guys to shift your lunch schedule so one of you is always at the machine producing all day long, and if this, of course, an improvement at the system constraint, is an improvement for the entire system, if you improve anywhere else, the odds are you are not gonna improve your overall throughput, your flow rate, because, by definition, nobody else is the system constraint.
- 16:52Steve Holt: So when Goldrat went in in the book and he described the character saying you guys gotta shift your lunch hour, well, if I'm a worker on that machine, I'm having a constraint.
- 17:05Steve Holt: My boss is telling me I don't get to have friends lunch with my friends anymore, right?
- 17:11Steve Holt: Yep, yes, I gotta be working, we all gotta do this.
- 17:14Steve Holt: Well, I've had a constraint labeled on me, right, it's like.
- 17:19Steve Holt: But what it is is it enables the system to perform at a much higher level.
- 17:25Steve Holt: Yes, toc calls it injection, but if you looked at it another way, it's actually an enabling constraint.
- 17:35Steve Holt: So we hypothesized that it could very well be that when we talk about TOC, rather than the perception that we wanna remove constraints, the real benefit comes in what constraints we wanna add.
- 17:56Brian "Ponch" Rivera: Yeah, there's so much on Pac here and we'll have Alicia Gerardo on the podcast, but I have this right in front of me right now her definition from her book.
- 18:06Brian "Ponch" Rivera: Her book, which is context, changes everything.
- 18:09Brian "Ponch" Rivera: Constraints are entities, processes, events, relationships, conditions that raise or lower barriers to energy flow, and energy flow could be information, value, whatever.
- 18:20Brian "Ponch" Rivera: So, and I think that aligns to your little accounting there, your little story that you just shared with us as to what it means.
- 18:29Brian "Ponch" Rivera: And then you have unintended consequences too, when you, as social creatures, you say, hey, you can't go socialize with your coworkers, that creates something else, but as a leader, you have to have, you're responsible for the consequences of that right.
- 18:45Steve Holt: Yeah, no, you're absolutely right.
- 18:47Steve Holt: And it's why.
- 18:48Steve Holt: So, when the goal first came out, it really was about physical constraints.
- 18:56Steve Holt: This machine doesn't have the capability of every other machine in the factory, and so it gave the perception early on that that's all it cared about.
- 19:06Steve Holt: Well, goldratt began to see what you're talking about and he said no, wait a minute, there are other things that limit us.
- 19:13Steve Holt: Sometimes it's policies, sometimes it's mindset, and so we have to actually look at all of those, because if you wanna come up with a solution, you have to deal with each one of those.
- 19:28Steve Holt: It's not just enough to deal with one.
- 19:32Steve Holt: Yeah, and so he created this thing called the thinking process, which logical thinking process, which is another way to say how to solve any problem, but it absolutely.
- 19:45Steve Holt: You are not done solving a problem until you have figured out how to implement, what the negative ramifications of implementation are, how to avoid those and how to get people to do it.
- 19:58Steve Holt: All of that.
- 19:59Steve Holt: It's not enough to say, hey, we just need this new scheduling system, go do that Right.
- 20:06Steve Holt: That won't do it.
- 20:10Brian "Ponch" Rivera: So there's more in here the idea of using when I was working at Amazon, you know, at Fortes for a time I was there.
- 20:19Brian "Ponch" Rivera: It's basically a flow system there, right, and you're just trying to optimize the flow of packages throughout the day and the bottlenecks are and shift handovers and things like that how do you maximize the output or throughput through that system?
- 20:31Brian "Ponch" Rivera: And if you look at a fulfillment center, it is a perfect example of a I'm gonna use a complicated flow system.
- 20:39Brian "Ponch" Rivera: But once you put people in it, you inject some complexity and then you add in some outputs from vendors that change the size of their boxes, that jam the system up because the computer says that can't be true, that box size is not.
- 20:53Brian "Ponch" Rivera: That is pretty amazing.
- 20:54Brian "Ponch" Rivera: So it is a great example to go see a flow system live and how you deal with different constraints throughout the day because it does change, right.
- 21:03Brian "Ponch" Rivera: And now you add in robots and you add in some artificial intelligence.
- 21:07Brian "Ponch" Rivera: It's, and someday, when those fulfillment centers start making money, I would highly recommend by a lot of Amazon you know that day's coming here real soon.
- 21:16Steve Holt: You know, you bring up a really interesting point too, which is there's gonna be this difference in opinion, which is really important.
- 21:24Steve Holt: So as a supplier, as a customer, I may wanna get my stuff right away, right, I want it fast.
- 21:31Steve Holt: But then I'm gonna complain.
- 21:34Steve Holt: If I order something and it's something really small, right, and it comes in a giant box, I'm gonna say, well, that's just wasteful, why isn't it a smaller box?
- 21:48Steve Holt: Well, the more you optimize the box size to fit the product size, in a sense, the more variation you're putting into the system, because now you gotta have the capability.
- 21:59Steve Holt: It'd be great if you know from a, if you were just going after efficiency, you'd do something like every single box, exactly the same, same size, every single product.
- 22:11Steve Holt: It'd be super easy to automate it, but you wouldn't necessarily make your customers happy.
- 22:19Brian "Ponch" Rivera: Right, right.
- 22:20Brian "Ponch" Rivera: Which is bizarre, yeah.
- 22:22Brian "Ponch" Rivera: And what's fascinating about the short period I was at at Amazon is the system would tell you, hey, these are the dimensions of each of your products and would tell you which box you need to be using, but it would leave it up to the human to figure out how everything fits in there, and it's a puzzle, right.
- 22:39Brian "Ponch" Rivera: So sometimes you're like, oh okay, the computer's smarter than I am, and eventually you'd get it right, or one of the product dimensions was out of size or out of scope, and that would throw everything off right.
- 22:47Brian "Ponch" Rivera: So it is a great socio-technical system to go and examine how humans operate with technology.
- 22:58Steve Holt: So you said a keyword.
- 22:59Steve Holt: I gotta point it out.
- 23:00Steve Holt: If people ask me what I do right, what I tell them is I am a socio-technical systems engineer, and again it's back to a lot of things we all know from the School of Hard Knocks.
- 23:13Steve Holt: I can have an absolutely perfect product that meets all the requirements, but people aren't gonna use it.
- 23:21Steve Holt: It's too difficult, and there's some really good or bad examples from product development Within systems engineering.
- 23:38Steve Holt: I believe it's the Stinger missile, the man-powered one.
- 23:41Steve Holt: It did a superb job at passing all those tests until they went out and actually tried it in the field with real people, and the success rate just plummeted.
- 23:56Steve Holt: And what they came to realize pretty obviously is it had this long, extensive list of steps you had to take in order to fire the missile.
- 24:06Steve Holt: It was just too difficult, and so what they did is they redesigned it and made it much, much simpler to use, and that's what then made it successful.
- 24:17Steve Holt: But again, the original product met 100% of its requirements that had been set for it.
- 24:26Brian "Ponch" Rivera: Except you give it to a knucklehead like me and then I'm going to figure out something to screw up on it.
- 24:30Brian "Ponch" Rivera: Right, that's awesome.
- 24:30Brian "Ponch" Rivera: We hear those stories all the time.
- 24:33Brian "Ponch" Rivera: I want to come back to theory constraints and I want to talk about weakest link, and the reason I bring that up is when we talk about complex adaptive systems, you hear people say, hey, you don't want to be the weakest link.
- 24:44Brian "Ponch" Rivera: Well, it doesn't really work like that in complex adaptive systems.
- 24:47Brian "Ponch" Rivera: So I want to get your thoughts on this thinking of a weakest link with theory of constraints and how it fits into.
- 24:54Steve Holt: Oh, part of the issue is it's an interesting thing and that kind of gets into some aspects of Kinevin as well At any one point in time, there's really only one true constraint to a system.
- 25:12Steve Holt: Now there may be a couple of them that are really similar, which is not good, but what it means also is the constraint can change and in fact you can end up with this concept called wandering bottlenecks, and that's what happens if capacity is.
- 25:35Steve Holt: We try to balance capacity on a system.
- 25:38Steve Holt: I mean, there's always this efficiency goal that says we should have exactly the right number of people and machines and resources so that everything is working in complete lockstep and so there's just absolutely smooth flow.
- 25:55Steve Holt: But the reality is there's always going to be inherent variation in everything you do.
- 26:03Steve Holt: So the more capacity is balanced in a system, the greater the odds that the actual system constraint is going to change from resource to resource, possibly multiple times a day, and so what it looks like is it looks like you can't possibly choose a constraint.
- 26:26Steve Holt: Everything's a constraint.
- 26:27Steve Holt: We just have to do massive amount of firefighter, so it's a really easy thing to track down, and what you really do is just you choose something that you think might be the constraint and say nothing, moves through this step until it's finished.
- 26:48Steve Holt: And it's amazing, right?
- 26:54Steve Holt: There was a story early on actually it's a book called the Rudolph Factor and it's about C-17, early days in production, and they were having a lot of trouble getting planes delivered.
- 27:08Steve Holt: And there was a senior manager who walked out in the factory one day and he put his hand up on a plane and he said this airplane does not move until it's 100% up to date in this particular assembly station.
- 27:24Steve Holt: No travel work, nothing go on past it.
- 27:28Steve Holt: It's got to be done at this point and it's not moving.
- 27:31Steve Holt: Until then.
- 27:31Steve Holt: And there was consternation because everybody was convinced that it was going to.
- 27:38Steve Holt: The rails were going to come off, it's going to come off, the rails, they were all going to be fired, et cetera, et cetera.
- 27:44Steve Holt: And what happened is in about two weeks things really smoothed out and suddenly they were getting things done and had a schedule and all the chaos that they'd seen before essentially disappeared.
- 28:00Steve Holt: Now this gets into a place where there's an apparent disconnect between Kenevan and TOC, and I say apparent because it doesn't really exist.
- 28:14Steve Holt: One of the points Goldrat made is you have to find a point of inherent simplicity, and inherent simplicity allows you to manage.
- 28:26Steve Holt: Now, if you've read about Kenevan, then you get the impression that what he's saying is, if I use TOC, I will actually convert a complex system into a simple or a clear system.
- 28:44Steve Holt: And that is not at all what he's saying.
- 28:51Steve Holt: Not as slightest Can you see a?
- 28:54Brian "Ponch" Rivera: lot of folks that profess talk actually say that, and I struggle with this because they'll also talk about complexity.
- 29:00Brian "Ponch" Rivera: I'm like you know that what you're saying over here doesn't match what you're saying over here, but I love this point, steve.
- 29:07Brian "Ponch" Rivera: This is critical because I know of a few folks up in Pacific Northwest maybe that talk about TOC as the way to go.
- 29:16Brian "Ponch" Rivera: Right.
- 29:18Steve Holt: And it helps you get there if you really use it.
- 29:21Steve Holt: So if you really go back and look at what Goldrat wrote and what he talked about in some of his works, what he follows is very, very much a Kenevan type approach of when you're, when you find yourself in a complex domain, you have to think about what might be happening, come up with some coherent theories, try some things out and then figure out what seems to be working, then zero in on OK, what do I think is happening here and what can we do to capitalize on this?
- 30:00Steve Holt: So and then what they would do often is they would document what they came up with through this logical thinking process, analysis approach, which gives people the mistaken impression that Goldrat invented processes by using the analytical thinking process.
- 30:20Steve Holt: He didn't.
- 30:21Steve Holt: He used that to document why the approach worked.
- 30:26Steve Holt: Ok, that's not how it was invented.
- 30:29Steve Holt: He was.
- 30:29Steve Holt: He was actually doing much more frequently abductive logic and thinking things through and saying what, what could be going on here and what could I test?
- 30:42Steve Holt: He?
- 30:45Steve Holt: One of his books he wrote with his daughter, who's a PhD psychologist.
- 30:49Steve Holt: She asked him like what, how do you stand to be wrong so much?
- 30:55Steve Holt: And he said well, it's wonderful, because when I'm wrong, it means I've discovered one more thing.
- 31:01Steve Holt: That's not the answer and it just means I have to keep going.
- 31:07Brian "Ponch" Rivera: And it was pretty intriguing.
- 31:08Brian "Ponch" Rivera: So, as you were sharing the story about the Goldrat's theory of constraints, I wrote this down.
- 31:16Brian "Ponch" Rivera: Hopefully I get this right.
- 31:18Brian "Ponch" Rivera: So, just as many people oversimplified Boyd's Doodle Loop, it is very possible that people are oversimplifying what Goldrat actually meant Definitely, absolutely.
- 31:30Steve Holt: So that's human nature, though right it is and in fact there's a, there's a nuance in that, with, in in the book, the goal.
- 31:37Steve Holt: There's one part of that book that everybody remembers, and it's because the main character, alex, takes his, his son and a Boy Scout troop out on a hike and they're not making a good time.
- 31:54Steve Holt: And there's one of the Scouts who's the slowest scout in the whole group and his name is Herbie.
- 31:59Steve Holt: And so what they have to do is they have to identify Herbie and then say, ok, now what can we do to enable him to go faster.
- 32:10Steve Holt: So they did things like put him at the head of the line, they went through his backpack and took out all the heavy stuff and gave it to other other Scouts.
- 32:20Steve Holt: So pretty soon, right, herbie's ability to go faster is successful, and then the whole troop is faster.
- 32:28Steve Holt: So there's, it left a mistaken impression that all of TLC is about going on a high Herbie hunt.
- 32:37Steve Holt: And you find today's Herbie and you break that constraint and then you find the next Herbie Gotcha, and there's an element of truth in that.
- 32:47Steve Holt: But the real value is goes back to what is it?
- 32:53Steve Holt: I want to be the constraint of my system, because once you do that, you now have put your finger on what that controlling mechanism is that gives you that sense of inherent simplicity.
- 33:08Steve Holt: I need to manage this one thing, and the rest of them will take care of themselves.
- 33:15Steve Holt: To a great extent.
- 33:17Steve Holt: It goes within critical chain project management, the TLC approach to project management.
- 33:25Steve Holt: The most heavily loaded resource is what sets the stage for the whole thing, and it's called a drum resource because it's like beating the drum right For the cadence.
- 33:36Steve Holt: Yes, well, that means, from a project management standpoint, I really only have to level load that one resource and, by definition, everybody else has greater capacity, and so they may get overwhelmed periodically, but they can catch up.
- 34:01Steve Holt: There's a great example, actually, if we go back to the Toyota production system.
- 34:04Steve Holt: Many people go on a tour of a Toyota factory like Georgetown, kentucky, and they see what they think they're seeing and not what they're actually seeing, and one of the things I used to work there.
- 34:22Steve Holt: I used to go there.
- 34:22Steve Holt: So one thing that people think they see when they go there is and again, this number may be a little out of whack, but it was true at the time I think they see an entire assembly line that's operating at a 57-second attack time.
- 34:37Steve Holt: That's actually not true.
- 34:41Steve Holt: It's only the last stage in final assembly.
- 34:45Steve Holt: That's 57 seconds.
- 34:46Steve Holt: Upstream steps are less than 57 seconds and what that means is if there's a breakdown in final assembly, everybody else can catch up and they can keep going until they, so they never run out of work, and at the same time, if there's a breakdown further upstream, they can get caught back up again so they don't disrupt that final step.
- 35:15Steve Holt: Interesting.
- 35:18Brian "Ponch" Rivera: So I've been there and I've also been up in Seattle at the 737 line, and I've been 787777 line, and let me tell you this the 737 line looks like Kentucky, right, more so than the 777777 line and you go up I forget the city that the 777777 is built in, but it looks like two different companies.
- 35:44Brian "Ponch" Rivera: Just from visiting, I'm like, wait a minute, you don't know that they're doing this down there down in southern Seattle?
- 35:51Brian "Ponch" Rivera: Right, you should go down and visit your other place.
- 35:52Brian "Ponch" Rivera: So it's amazing that, even in a company and this is my view and it's not Steve Holds for you that it says, though two different companies are operating two different types of assembly lines called Boeing.
- 36:07Brian "Ponch" Rivera: So I don't know.
- 36:09Brian "Ponch" Rivera: It's always good to go and see for yourself.
- 36:11Brian "Ponch" Rivera: What do things actually look like?
- 36:13Brian "Ponch" Rivera: Right, and I think at the time is 2018, 2019, when I went into the 737 line and where they were going to go with the max production and how I forgot it was like every three days they're going to pop out one.
- 36:26Brian "Ponch" Rivera: I forgot to take one.
- 36:26Brian "Ponch" Rivera: Three days, it's really fast.
- 36:28Steve Holt: Yeah, it's really fast, yeah, yeah.
- 36:31Brian "Ponch" Rivera: And so there's a lot to be learned from, not just theory of constraints and drum buffer rope drum buffer rope, you know toy production system, things like that, but there's also a lot to be learned within an organization that's already executing on something like this.
- 36:46Brian "Ponch" Rivera: Right, absolutely.
- 36:47Brian "Ponch" Rivera: And I see this quite often in organizations where they just don't learn or they don't take the time to learn from somebody else with, you know, 20 miles away, or in this case, seattle, I think it's about 70 miles away, it's like 45, but close enough.
- 37:01Steve Holt: Okay, I'm not good with, but you know, at the same time there's a really wonderful thing that Goldwright came up with and he put it in one of his first books, and it's called the PQ game and it's a really simple thought experiment.
- 37:22Steve Holt: It's like look, you're a company and you make two products, p and Q.
- 37:25Steve Holt: Here's the assembly process.
- 37:28Steve Holt: Here's the amount of time it takes.
- 37:29Steve Holt: Here's what resources it takes to do it.
- 37:31Steve Holt: Here are the parts we buy and what we pay for them.
- 37:35Steve Holt: Here's what we pay our employees.
- 37:38Steve Holt: Our employees are perfect attendants.
- 37:41Steve Holt: Nobody ever gets sick.
- 37:42Steve Holt: They're all there every single time.
- 37:45Steve Holt: And the simple question he asks is what's the maximum profit you can get out of this line?
- 37:50Steve Holt: It is an unbelievably devious question because the system looks really simple.
- 38:01Steve Holt: But if you are the person who does supply chain acquisition, you're going to probably come up with one answer.
- 38:12Steve Holt: And if you're the person who's trying to cut down on labor cost, you're going to come up with a different answer.
- 38:19Steve Holt: And if you're the person who gets a commission from sales, you're going to come up with a different answer.
- 38:24Steve Holt: And none of them are even close to the optimum.
- 38:29Brian "Ponch" Rivera: Sounds like they all have different constraints.
- 38:32Steve Holt: They're levying their own constraints on the system, right?
- 38:35Steve Holt: I mean, this is one of the reasons why Goldratt made a point.
- 38:39Steve Holt: In fact, it's what he did before he even wrote his first book.
- 38:42Steve Holt: He used to do on these very John Boyd-like lecture series to talk about how cost accounting was enemy number one for production and how full absorption cost accounting just almost always led you to the wrong answer, things that were actively harmful.
- 39:06Steve Holt: There's a this sounds funny, but there's a really wonderful book, and it's another business novel by Gerald Solomon called who's Counting, and that's like who Apostrophe S.
- 39:20Steve Holt: And it is literally a book about the application of lean accounting in a manufacturing company, and Goldratt came up with a thing he called throughput accounting, which is practically identical to what later on then became known as lean accounting.
- 39:39Steve Holt: And who's Counting is a great book because it really actively shows you how the finance organization and what they can just traditionally measure can actually be actively harmful at your company maximizing its profit.
- 40:02Steve Holt: And frankly, it's not.
- 40:04Steve Holt: It won't allow you to take advantage of flow is one thing.
- 40:09Brian "Ponch" Rivera: Can you go on to add some more?
- 40:10Brian "Ponch" Rivera: This is interesting because I think a lot of organizations suffer from this.
- 40:15Steve Holt: Oh, yeah, so in a way it goes back to Goldratt is If there's one thing he complained about almost beyond anything else, it was the negative impact of local efficiencies and the idea that every machine, every person, had to be maximized 100% of the time because that would allow us to produce the most Well again, when you do that, it means you're a victim of any amount of variation in the system.
- 40:48Steve Holt: Can we, Can we stop here for a second?
- 40:52Brian "Ponch" Rivera: I want to make sure I have something right.
- 40:53Brian "Ponch" Rivera: I understand local optimization.
- 40:57Brian "Ponch" Rivera: Used another term there.
- 40:58Brian "Ponch" Rivera: Are they the same?
- 40:58Brian "Ponch" Rivera: Yes, can we maximize efficiencies?
- 41:01Steve Holt: Yeah, local efficiencies and local optima are the same thing.
- 41:04Steve Holt: Efficiencies here is like your run rate, right?
- 41:08Steve Holt: Yep?
- 41:09Steve Holt: Well, this machine is only being utilized 80% of the time, as opposed to this machine is being utilized 100% of the time, so that's got to be better.
- 41:20Steve Holt: What that does is anybody who's not the system constrained is going to overproduce.
- 41:29Steve Holt: And that gets back to Taiji Ono saying that the number one form of risk was overproduction.
- 41:37Steve Holt: So Goldback came up with a set of four rules of flow on back, and I'll tell you what these are because it fits in.
- 41:47Steve Holt: The first one is if improving flow is a primary objective of operations and management.
- 41:56Steve Holt: First step improving flow.
- 41:58Steve Holt: Second, the primary objective should translate into a practical mechanism that guides the operation when not to produce.
- 42:11Steve Holt: And again, the reason is because overproduction is so incredibly wasteful.
- 42:15Steve Holt: The third one, then, is to abolish local efficiencies.
- 42:19Steve Holt: Stop measuring people on the local efficiencies in the organization.
- 42:25Steve Holt: And then the final one is where the things get tricky about.
- 42:31Steve Holt: Misinterpretation is there has to be a focusing process to balance flow, not balance capacity, balance flow, because you don't want peaks and valleys in what's being produced.
- 42:50Steve Holt: He wrote a.
- 42:51Steve Holt: There was a paper he wrote called Standing on the Shoulders of Giants, and he talked about what Henry Ford did to balance flow, and he used literally the space between machines and his factories.
- 43:08Steve Holt: So he would tell everybody to produce, but they would reach a point where, if they were overproducing, there'd be so much work in process inventory there wouldn't be room for anymore, so they'd have to stop working.
- 43:20Steve Holt: All right, that's an effective way to do it.
- 43:23Steve Holt: Well, taiichiyono came along and he said we don't have a lot of money, we can't afford to do that, we have to find another way to do it.
- 43:34Steve Holt: So he invented the Kanban system then to be able to say let's limit it to just what's needed and set up a pole system.
- 43:47Steve Holt: But then what was happening is Taiichiyono could get away with that at Toyota, because they really didn't have very many products at the time.
- 43:55Steve Holt: They could only afford to have like one or two different types of cars.
- 44:01Steve Holt: They couldn't afford a bunch of spare parts, they couldn't afford a bunch of inventory.
- 44:05Steve Holt: So once businesses that had hundreds or even thousands of products, they tried to set up a Kanban system.
- 44:16Steve Holt: What they end up with is the whole factory is awash in Kanban cars.
- 44:21Steve Holt: There needed to be something else.
- 44:25Steve Holt: So then what Goldred came up with with drum buffer rope is a way to say you don't have to have a pole system on every single part of the line, it really just needs to be at the constraint.
- 44:41Steve Holt: So you want, upstream of the constraint, you want them to work at a pace that the constraint can accept.
- 45:47Steve Holt: Downstream of the constraint, you want them to go as fast as they can and get the product out and sent to market.
- 45:53Steve Holt: But again, it becomes much simpler to operate, much simpler to get the point across, to be successful.
- 46:07Brian "Ponch" Rivera: Steve, let me ask you this.
- 46:07Brian "Ponch" Rivera: You talked about drum earlier and in the story you just shared there it triggered something that goes back to tempo versus speed, right?
- 46:16Brian "Ponch" Rivera: Potentially so tempo Boyd talks about tempo quite a bit.
- 46:23Brian "Ponch" Rivera: He talks about speed too, right?
- 46:24Brian "Ponch" Rivera: It's not about going through the oodaloop faster than your opponent, which everybody says.
- 46:27Brian "Ponch" Rivera: It's really about controlling the tempo.
- 46:30Brian "Ponch" Rivera: What I'm hearing from you right now is that tempo that is upstream from the constraint really drives a lot, right?
- 46:36Brian "Ponch" Rivera: Is that true?
- 46:37Brian "Ponch" Rivera: Yes, okay.
- 46:40Steve Holt: And that tempo is the the real tempo, and it gets back to why it's called the drum right At one spot.
- 46:47Steve Holt: That's what sets the rate for the entire factory, and this gets back to why is it you want to choose where your constraint is.
- 46:56Steve Holt: Let's suppose you've got something like a giant milling machine or maybe an autoclave or something that's incredibly expensive.
- 47:09Steve Holt: Well, almost by definition, that's going to end up being your constraint, and so what you have to do is you have to use that as the pacing process for everything else, and the reason you're choosing that to be the constraint is there's usually a step function change in cost or implementation risk.
- 47:32Steve Holt: If I want to go out and buy another one of these giant milling machines, I have to.
- 47:40Steve Holt: Actually, that's going to be a huge amount of money and I have to know what makes sense.
- 47:47Steve Holt: So let's get the maximum out of the system I can with what I have now before I got to spend any more money.
- 47:56Steve Holt: One of Goldrat's things that are really common are called the five focusing steps, and this really lays it out.
- 48:03Steve Holt: He says you identify what the constraint is and then figure out how you can get the most out of the system given that constraint.
- 48:12Steve Holt: How do I make that constraint be as effective as it can be?
- 48:16Steve Holt: And then the third one is every other step in the entire process subordinates themselves to what you're doing for the constraint.
- 48:27Steve Holt: So if I have a machine, write this my constraint.
- 48:32Steve Holt: Every single step upstream of that, make sure that no defective product ever gets to that machine.
- 48:39Steve Holt: Because if a defective part gets to that machine it's wasted for the entire system.
- 48:44Steve Holt: And so upstream people are going to say well, that means it's going to take us longer, we're not going to be as effective, our efficiencies are going to go down.
- 48:53Steve Holt: We don't care.
- 48:55Steve Holt: That's not what we're being rewarded for.
- 48:59Steve Holt: We're being rewarded when we actually sell a product and get the cash.
- 49:03Steve Holt: It goes back to Tate Jones' book the Toyota Protection System.
- 49:10Steve Holt: One of the most astonishingly insightful statements is right up front.
- 49:17Steve Holt: It's the first page of the preface and it says, quote from Ono.
- 49:23Steve Holt: He said all we're trying to do is take the time between the customer order to part something and when we deliver it and make that as short as possible.
- 49:34Brian "Ponch" Rivera: Yeah, that's simple.
- 49:35Steve Holt: Maximizing flow Right.
- 49:37Steve Holt: And again, what that comes down to also is tempo, because you have to look at your market and say what does the market want?
- 49:48Steve Holt: How fast do they want things, and does it make sense for me to actually go after that?
- 49:58Brian "Ponch" Rivera: All right, Steve, I'm about to make a snowmobile and I think I need your help with this, and I don't know what it really looks like, but I want to kind of kick around this idea.
- 50:05Brian "Ponch" Rivera: So earlier, before we came on to recording this podcast, we were talking about EM Theory, Energy Maneuble Theory.
- 50:11Brian "Ponch" Rivera: We're talking about some stuff that's going on in the early 70s, with John Boyd In my mind.
- 50:15Brian "Ponch" Rivera: Em Theory and we're going to use the Kinevan framework for this EM Theory fits well in the complicated domain.
- 50:21Brian "Ponch" Rivera: It's a closed system thing.
- 50:23Brian "Ponch" Rivera: I believe Theory of Constraints fits there quite well and it's not to categorize it right.
- 50:28Brian "Ponch" Rivera: It's to say, okay, we just want to think about this as a, as a system.
- 50:32Brian "Ponch" Rivera: Yes, Now we also talked about EM Theory as having potential possible connections to things like organizational agility, maybe the free energy principle, things like that.
- 50:45Brian "Ponch" Rivera: Well, the same is true with Theory of Constraints.
- 50:47Brian "Ponch" Rivera: It's just that we're going to take some of these things and apply them to a human system.
- 50:53Brian "Ponch" Rivera: Right, but those constraints are not going to be those things that you can see.
- 50:55Brian "Ponch" Rivera: They're going to be the things that you really can't see.
- 50:57Brian "Ponch" Rivera: They're the dark constraints, if you will.
- 50:59Brian "Ponch" Rivera: Yes, yes.
- 50:59Brian "Ponch" Rivera: So entropy in a closed system is.
- 51:03Brian "Ponch" Rivera: We know what that looks like, and we also know what entropy looks like.
- 51:07Brian "Ponch" Rivera: By the way, the definite entropy changes from book to book and whoever you read, so we got to be careful there.
- 51:15Brian "Ponch" Rivera: But to me there's nothing wrong with EM Theory.
- 51:19Brian "Ponch" Rivera: There's something wrong with EM Theory applied to complex systems.
- 51:23Brian "Ponch" Rivera: That's what Boyd discovered.
- 51:25Brian "Ponch" Rivera: And I think what's happening with the Theory of Constraints community is they're trying to take and then I'm generalizing here they're trying to take something that has bounded applicability and trying to use it somewhere else.
- 51:35Brian "Ponch" Rivera: Now that doesn't mean it's not useful.
- 51:37Brian "Ponch" Rivera: There are elements of it that you can still use.
- 51:40Brian "Ponch" Rivera: But we have to stop going in and looking at a system and saying that visible thing right, there is my number one constraint when it could be something that's a reward system.
- 51:49Brian "Ponch" Rivera: Okay, so that's what I'm trying to.
- 51:51Brian "Ponch" Rivera: I'm trying to make some connections here.
- 51:53Brian "Ponch" Rivera: How far off am I in this thinking, or can you build on that?
- 51:58Steve Holt: I think you're very much on track because, and again, it kind of goes back to this inherent simplicity thing again.
- 52:05Steve Holt: So you could look at what Boyd is doing with EM Theory and saying this is a thing you can use to provide you with some inherent simplicity when it comes to design or use.
- 52:21Steve Holt: Given these two plots for these two aircraft, what does it tell me I should do from a tactical standpoint?
- 52:30Steve Holt: Right, and again, what it's doing is it's providing you a focusing mechanism.
- 52:35Steve Holt: Now, will it cover every single situation?
- 52:40Steve Holt: No, it won't, because there's always going to be new things we discover.
- 52:47Steve Holt: And part of the question is how far into the complex does theory of constraints work?
- 52:53Steve Holt: And the project management solution to TOC, in my mind, works farther into complex than some of the other ones.
- 53:09Steve Holt: There's a really, really similar question is well, which one is better at this point, agile or critical chain?
- 53:18Steve Holt: And the reality is they're almost like I'm not going to.
- 53:24Steve Holt: It's not exactly twins, separated birth, but both of them know that there's inherent variation.
- 53:30Steve Holt: They use two different ways to do it.
- 53:33Steve Holt: So if you're doing sprints, you're actually using a fixed time and a variable amount of work that you accomplish.
- 53:43Brian "Ponch" Rivera: That's called a constraint.
- 53:45Steve Holt: It is.
- 53:45Steve Holt: You're applying constraint right, exactly it.
- 53:49Steve Holt: What critical chain does is it says it's the work that's fixed.
- 53:54Steve Holt: So I'm going to vary the amount of time.
- 53:56Steve Holt: So what you tell in critical chain is you say don't multitask.
- 54:02Steve Holt: Start this when everything's ready.
- 54:05Steve Holt: Go as fast as possible at a sustainable rate, with no other task.
- 54:11Steve Holt: This is your top priority.
- 54:12Steve Holt: And pass it on as soon as you're finished, not when the due date says, but when it's finished.
- 54:21Steve Holt: And then the way you take status in critical chain is you go to the people and say get, given that you're working, a full level of effort, how much longer until you're finished?
- 54:33Steve Holt: And this, this is so radically different than a waterfall approach which is going to want to ask you things like well, what percent complete are you or are you going to be done by this state?
- 54:47Steve Holt: And what you want in when you're doing buffer management like that, is you want to know the reality, you want to know what people think right now, today and it kind of gets back to your point about Bayesian logic again, right, what you're doing as you go forward in a critical chain plan is you're always kind of like going through little oodle loops in a way, saying where are we today?
- 55:14Steve Holt: What's the most critical task today?
- 55:17Steve Holt: Now, this sounds like firefighting, but it's not, because it's a focusing mechanism.
- 55:23Brian "Ponch" Rivera: But you're asking this to people that are actually doing the work, and that's critical.
- 55:26Brian "Ponch" Rivera: The people doing the work.
- 55:28Brian "Ponch" Rivera: Yeah, they're involved in this and this is that Absolutely Okay, and they're actually closest to the customer.
- 55:34Steve Holt: And so I could go to them today, right, and say when are you going to be finished with this task?
- 55:39Steve Holt: And they'll say three days.
- 55:42Steve Holt: I might go to them in a couple of days from now and say when are you going to be finished with this job?
- 55:49Steve Holt: And they might say four weeks, because we discovered something.
- 55:55Steve Holt: The thing we were going to do didn't work, or something didn't come in.
- 55:59Steve Holt: It was late.
- 56:00Steve Holt: So that then becomes a focusing mechanism for them to get all the help they need.
- 56:07Steve Holt: Now you realize the other thing that's important on this is it is hugely beneficial if you have a system of psychological safety.
- 56:17Steve Holt: You want people to tell you the truth and you want it to be safe for them to tell you the truth, because that facilitates flow of information.
- 56:28Brian "Ponch" Rivera: It is, that's exactly it.
- 56:29Brian "Ponch" Rivera: Yeah, it's a life-flow of an organization?
- 56:32Steve Holt: Yeah, and in a system in which we have multiple metrics that people are being judged by, what it almost certainly always does, is it reinforces the absence of psychological safety?
- 56:46Steve Holt: You're correct?
- 56:49Steve Holt: Yes, absolutely.
- 56:49Steve Holt: If I go in and say, hey, I'm going to be late, people get the perception that what you're saying is I'm incompetent and should be replaced, so no one's going to want to do that.
- 57:02Steve Holt: The rare individual will want to do that.
- 57:07Brian "Ponch" Rivera: Yeah, because there's a constraint that allows people to think that that's what that means.
- 57:10Brian "Ponch" Rivera: Right Again, it might be a dark constraint, it may be something in the history of the organization, it could be just your previous experience as an adult, right?
- 57:18Brian "Ponch" Rivera: Right, you don't know.
- 57:20Steve Holt: It's like what do due dates do for you?
- 57:23Steve Holt: You could make an argument that well, I can use a due date to be able to back things off from a capacity standpoint and I can get a better understanding of when I should commit.
- 57:34Steve Holt: The other part of it is like oh, no, no, no, we have to put due dates on every single task to force people to actually work on that.
- 57:47Brian "Ponch" Rivera: Well, that actually constraints people to work on them at the last minute, right.
- 57:52Steve Holt: And this gets back to what Goldrat called the student syndrome.
- 57:55Steve Holt: And it's really simple.
- 57:57Steve Holt: When you say you got the teacher in class and the teacher says, okay, I want you to report your reports due a week from today, and the students all say, oh no, we can't possibly get done a week from today.
- 58:09Steve Holt: We've got all this other stuff we got to do, it's like, okay, okay, you get two extra weeks.
- 58:14Steve Holt: And the question is, when do the students start working on the report?
- 58:20Brian "Ponch" Rivera: About two weeks out.
- 58:21Steve Holt: Yeah Right, what they do is they just delay it, so they end up getting massive amount of work effort they have to do at the last minute.
- 58:30Steve Holt: And then you run into this risk of, if I reach the due date, if I got an assignment, I got to turn in a report.
- 58:38Steve Holt: It's due at nine o'clock tomorrow, right?
- 58:41Steve Holt: I get nothing if I turn it in at 9.05.
- 58:44Steve Holt: So if I'm not done, I'm going to turn it in the way it is, even though I really I actually had plenty of time to be able to do it.
- 58:54Steve Holt: I just frittered it all away.
- 59:00Brian "Ponch" Rivera: We used to joke around a lot If you plan early, you plan twice, right, yeah, yeah, that's been awesome.
- 59:08Brian "Ponch" Rivera: Hey, steve, I really appreciate your time today.
- 59:09Brian "Ponch" Rivera: This was just one of those the universe calling where you just say, hey, pons, I got an idea.
- 59:15Brian "Ponch" Rivera: I want to talk to you and I'm like, hey, let's record this, because we wanted to have some insights on theory of constraints on the show and, plus your background and understanding of John Boyd's Oololoop and, clearly, the Kinect and Framework, I do have a few more questions for you.
- 59:29Brian "Ponch" Rivera: So, boeing, you talked about the C-17, go back to the B-17, go back to World War II.
- 59:36Brian "Ponch" Rivera: We talked about human-centered design, human factors and things like that.
- 59:40Brian "Ponch" Rivera: We have this knowledge from aviation Our crew coming back from missions and they're tired, they're stressed out, high anxiety, landing in aircraft and combat conditions and then collapsing the aircraft as they land because they reach over and they grab us a lever that isn't marked and it collapses the aircraft because it brings it flaps or whatever Easy solution.
- 1:00:03Brian "Ponch" Rivera: make that, put it something that looks like a wheel on the landing gear and something that looks like a flap on the flap.
- 1:00:08Brian "Ponch" Rivera: So we get a lot of the.
- 1:00:09Brian "Ponch" Rivera: This is amazing.
- 1:00:10Brian "Ponch" Rivera: A lot of people don't understand where human factors, human-centered design really comes from right, and I believe it's really that experience in World War II, b-17s, boeing aircraft, things like that.
- 1:00:21Brian "Ponch" Rivera: So basically I'm saying, hey, boeing made bad designs, right?
- 1:00:25Brian "Ponch" Rivera: No, I'm kidding, I'm not saying that, but we learned a lot from Boeing over the years and it's just amazing what we can continue to learn from Boeing.
- 1:00:33Steve Holt: Well, and not to mention the whole crew resource management with respect to, I mean, this is the thing we.
- 1:00:37Steve Holt: I never heard of that man.
- 1:00:38Steve Holt: What is that?
- 1:00:39Steve Holt: Crew resource management?
- 1:00:40Brian "Ponch" Rivera: Yeah right, I know what it is.
- 1:00:41Brian "Ponch" Rivera: Yeah, yeah.
- 1:00:43Brian "Ponch" Rivera: So it's funny.
- 1:00:44Brian "Ponch" Rivera: I don't know if you know this.
- 1:00:46Brian "Ponch" Rivera: When I was living up in Seattle, dr Dan Lowe, who's been on the show he went up to Boeing and sat in a simulator and learned CRM in his time in a helicopter in Europe what he called a HEMS H-E-M-S helicopter for medical services.
- 1:01:02Brian "Ponch" Rivera: He flew next to a SAS special operator pilot from the British military.
- 1:01:09Brian "Ponch" Rivera: Then he came over to Seattle, went into a simulator up at Boeing where they taught him CRM again and he's like we can apply this right now, right?
- 1:01:18Brian "Ponch" Rivera: Yes, so to me it's funny is that the team science is crew resource management.
- 1:01:27Brian "Ponch" Rivera: A crew is a ritualized form of a team.
- 1:01:30Brian "Ponch" Rivera: Teaming is a crew, right.
- 1:01:33Brian "Ponch" Rivera: So I find this very difficult to believe that people in the industry aviation will ignore teaming lessons from their very industry, like how do we work better as a team while you go do scrum?
- 1:01:49Brian "Ponch" Rivera: I don't think you're right.
- 1:01:51Steve Holt: I think you need to do something else, why don't we?
- 1:01:53Steve Holt: look at what we already know, right?
- 1:01:54Steve Holt: Yes, just look inside.
- 1:01:56Steve Holt: I mean, there's a very similar story, and it's partly in Dr Atul Gawande's book the Checklist Manifesto right, where he talks about flying out to Seattle and visiting the people in Boeing that write aviation checklists.
- 1:02:12Steve Holt: They give him some advice, which is just incredibly important.
- 1:02:18Steve Holt: If you think about it, it fits in with what we're talking about, is it provides you a focusing mechanism.
- 1:02:23Steve Holt: So if you go to a Cessna 150 or 172, or, for that matter, probably an F-14 checklist for how to do an engine restart in flight, it is not a gigantic list.
- 1:02:40Steve Holt: There you go.
- 1:02:40Steve Holt: It is not a gigantic list of steps.
- 1:02:43Steve Holt: It's the most important things that people are going to be more staffed to follow.
- 1:02:47Steve Holt: They're optimists.
- 1:02:51Brian "Ponch" Rivera: And one of the important things about a checklist is challenge and respond right.
- 1:02:54Brian "Ponch" Rivera: It's not something you just look at and check, check, check, check.
- 1:02:57Brian "Ponch" Rivera: Are you actually doing this?
- 1:02:59Brian "Ponch" Rivera: I'm going through the motions and I'm having somebody not QA me, but back me up.
- 1:03:04Brian "Ponch" Rivera: We call it mutual support, right?
- 1:03:05Brian "Ponch" Rivera: So this is the power of it.
- 1:03:09Steve Holt: There's a famous story actually Famous isn't quite the right word, but you can find it online.
- 1:03:14Steve Holt: Because so many things about accidents or public domain because of the FAA.
- 1:03:19Steve Holt: There was a Air Florida plane that crashed in the summer, in the wintertime in Washington DC into a 14th Street bridge across the Potomac.
- 1:03:31Steve Holt: And when you listen to the cockpit voice recorder of the pilot and co-pilot they're going down through the checklist and they get to the item on the checklist that says anti-ice and the copilot or the pilot says off.
- 1:03:48Steve Holt: Because these guys were used to flying planes in Florida, they were flying out into the Caribbean.
- 1:03:56Steve Holt: They didn't turn on anti-ice in most of their flights, so they were habituated to always have the anti-ice off.
- 1:04:06Steve Holt: So here we have it's part of their orientation.
- 1:04:09Steve Holt: It's snowing right and that they just fell into a pattern.
- 1:04:13Steve Holt: So, even though they had the checklist and even though they went through it and even though it was challenging response, neither one of them caught that that was actually wrong.
- 1:04:25Brian "Ponch" Rivera: I can see that, yeah.
- 1:04:26Brian "Ponch" Rivera: Yeah, I mean, we've had aircraft land on each other, on carriers, right, even though we have redundant systems.
- 1:04:31Brian "Ponch" Rivera: But it still happens and it's there's a, there's a human in the system, right.
- 1:04:35Brian "Ponch" Rivera: We're gonna make mistakes and we're trying.
- 1:04:37Brian "Ponch" Rivera: You know, something else we've learned from CRM is threat and their management.
- 1:04:41Brian "Ponch" Rivera: How you trap Errors.
- 1:04:43Brian "Ponch" Rivera: You know you trap it because there's leave you.
- 1:04:45Brian "Ponch" Rivera: They come from you and then threats come from the external environment.
- 1:04:48Brian "Ponch" Rivera: So think about it as a noodle loop inside your.
- 1:04:51Brian "Ponch" Rivera: I Don't want to jump too far into the little loop, but it's within the internal system of the little loop.
- 1:04:59Brian "Ponch" Rivera: That's where we create errors and then, from the outside, is where we get threats, and your job is to Minimize the threats and minimize errors, right?
- 1:05:10Steve Holt: There's a Amy Edmondson who's famous for psychological safety research, just came out it with a new book called right way to be wrong, mm-hmm, and she really talks a lot about this and and and why it's so important and and how there are basic errors and those are the ones that are avoidable and those are the ones we really can't find ways to avoid.
- 1:05:33Steve Holt: There's other ones that we're doing for learning.
- 1:05:36Steve Holt: If you're gonna be doing a flight test of some new piece of equipment, you don't know what you're gonna find.
- 1:05:43Steve Holt: That's why you're doing the flight test.
- 1:05:45Brian "Ponch" Rivera: Right Sounds like the sounds, like the Kinev and framework very much like that, right, yeah.
- 1:05:50Steve Holt: But then there's also these ones where she says look, no matter what we do, something's gonna happen.
- 1:05:56Steve Holt: It's unpredictable, it's complex.
- 1:05:58Steve Holt: So in that environment People have to be able to speak up as soon as they spot something.
- 1:06:05Steve Holt: We need resilience, we need to be able to psychological safety for people to say something's not right here and we can actually go in and look at it and not just what we typically do, which is what was all too frequent with human systems is people say what does seem right, but you know this is the standard approach, so maybe it's me that's wrong, mm-hmm.
- 1:06:34Brian "Ponch" Rivera: You know we had the opportunity to I've had the opportunity a couple times to sit down with Amy Edmondson Dr Edmondson from Harvard to talk about psych safety, once the Navy and then once working with John and Nigel on the flow system.
- 1:06:46Brian "Ponch" Rivera: One of the questions I was able to ask her this you're gonna love this, because this goes back to crew resource management is the surgical teams that she was observing happen.
- 1:06:55Brian "Ponch" Rivera: Some of them happen to be trained in, not necessarily crew resource management, but by aviators.
- 1:07:00Brian "Ponch" Rivera: They can't, you know, came from the cockpit and train them.
- 1:07:02Brian "Ponch" Rivera: So when you go, when you learn about this, you, you, you learn teaming skills and psych safety happens to be part of it.
- 1:07:09Brian "Ponch" Rivera: It's, you can get, it's.
- 1:07:10Brian "Ponch" Rivera: I guess it's an emergent property of how you act.
- 1:07:12Brian "Ponch" Rivera: Right.
- 1:07:12Brian "Ponch" Rivera: If, instead of something you just do you, you have to create it, it's a condition that's created.
- 1:07:17Steve Holt: Why you're really reinforcing, frankly, why team science is such a critically important part of what you put into the flow system too.
- 1:07:25Brian "Ponch" Rivera: Yeah, yeah, and there's a reason we cite, you know, dr Solace.
- 1:07:30Brian "Ponch" Rivera: There's a reason.
- 1:07:31Brian "Ponch" Rivera: He's been on the show, yep, when I learned about his work not only in Tad miss tackle decision making under stress but also crew, crew, crew, resource management and some work that he did with Gary Klein and I think you and I yeah, you and I met very client up in Canada.
- 1:07:48Brian "Ponch" Rivera: It's amazing how this network starts to form.
- 1:07:50Brian "Ponch" Rivera: Or you get start to see it, and then you start adding dr David Woods in there, then you get a connection to John Schmidt, and then you get a connection to John Boyd and maneuver warfare.
- 1:07:57Brian "Ponch" Rivera: You're like, oh my gosh, this is insane.
- 1:08:00Steve Holt: So we're lucky?
- 1:08:01Steve Holt: No, I agree.
- 1:08:05Steve Holt: And what is telling us is is you know, everything is connected, it's all network and there's gonna be some universal principles out there.
- 1:08:14Brian "Ponch" Rivera: Yeah, yeah.
- 1:08:15Brian "Ponch" Rivera: And we go back to dr David Woods resilience engineering.
- 1:08:18Brian "Ponch" Rivera: You get into Gene Kim's work with dev off.
- 1:08:20Brian "Ponch" Rivera: So we just talked about gold rats work.
- 1:08:21Brian "Ponch" Rivera: You know, I don't know how to make this any easier for folks.
- 1:08:25Brian "Ponch" Rivera: I'm like it's all the same.
- 1:08:27Brian "Ponch" Rivera: Yeah, that's why we created the flow system.
- 1:08:30Brian "Ponch" Rivera: They're like this isn't hard to figure out.
- 1:08:32Brian "Ponch" Rivera: You know, it's not saying we're right, it's just saying what we understand right now.
- 1:08:36Brian "Ponch" Rivera: This is how you know we're seeing, though, how things actually work, but it's not gonna be like that five years from now, because you know what's doctrine on day one is dogma, you know, it's whatever.
- 1:08:48Steve Holt: Yeah, so good stuff.
- 1:08:49Brian "Ponch" Rivera: Hey, anything you any any way our listeners can get in contact with you?
- 1:08:53Brian "Ponch" Rivera: Is it just linked in or you have any way they can.
- 1:08:56Steve Holt: I'm definitely a link, then.
- 1:08:57Steve Holt: I'm still on Twitter and you can actually Probably find a number of the presentations I've done for the theory of constraints international certification organization.
- 1:09:11Steve Holt: Some of them are behind paywalls, um, okay, but not all of them are, so it's just to see.
- 1:09:19Steve Holt: I coorg, I believe, yeah, and, and so you can find a one of the.
- 1:09:28Steve Holt: The videos that's on there every once in a while is the first time I introduced the theory of constraints community to the Kinevon framework, and I went into that presentation with a great deal of Concern and anxiety, because it was gonna come across to some of the people in the audience that I was saying that gold rat either didn't know what he was talking about or that he was wrong, because this is what he was talking about inherent simplicity, and what I had to make the point was is that it wasn't that he was wrong, it's that many people misunderstood what he was actually saying, right, and so they asked me if I wanted to do this as a this is my 15 seconds of fame, by the way yeah, that's me.
- 1:10:19Steve Holt: If I wanted to do this as the, as a Presentation to the whole conference, I said sure.
- 1:10:29Steve Holt: What I hadn't realized is that gold rat would be in the room.
- 1:10:31Steve Holt: Oh and he, he is very much like boy Early on where he.
- 1:10:37Steve Holt: He did not suffer fools gladly.
- 1:10:39Steve Holt: He mellowed a bit in later years, but he was more than willing to challenge you in the middle of a presentation, and so he sat there and said nothing, and I had a few minutes left at the end, as I said, are there any questions?
- 1:10:56Steve Holt: And he stood up and I'm thinking, oh Boy, this is gonna be interesting.
- 1:11:04Steve Holt: He walked up to the front of the stage.
- 1:11:10Steve Holt: He's walked up to the front, came up on stage, gave me a hug, kiss me on both cheeks, turned around and sat down.
- 1:11:20Steve Holt: Great, he made.
- 1:11:22Steve Holt: He made a comment later on in the that he was not in the habit of Kissing men with with beards, so but he it essentially actually paved the way then For for conneven framework to be accepted within the TOC community.
- 1:11:43Brian "Ponch" Rivera: Yeah, this is critically important, that we continue the network that we have to learn from each other.
- 1:11:49Brian "Ponch" Rivera: There's no, there's no one-size-fits-all approach, right, exactly, and this is, I think, why you know a lot of reasons we have the no way out podcast is, you know, boy Gave us a pathway.
- 1:12:01Brian "Ponch" Rivera: He didn't really write anything down, he gave us things that changed and he modified over time.
- 1:12:08Brian "Ponch" Rivera: That allows us to go back and look and go hey, go look at Heisenberg uncertainty principle.
- 1:12:12Brian "Ponch" Rivera: Go look at Cognitive science, neuroscience, go look at these things that biology, dna, which leads us to genetics and epigenetics today.
- 1:12:19Brian "Ponch" Rivera: So it just allows us to go look and find out what we don't know.
- 1:12:24Brian "Ponch" Rivera: Right, because we and the more we learn, the more we Identify that there's more things we don't know.
- 1:12:30Brian "Ponch" Rivera: Yeah, absolutely so, steve.
- 1:12:32Brian "Ponch" Rivera: Hey, I appreciate your time today.
- 1:12:33Brian "Ponch" Rivera: This has been awesome, just a ad hoc opportunity to have a conversation with you, and we'll definitely do this again in the future, definitely fun.
- 1:12:41Brian "Ponch" Rivera: All right.