Myth of Tech Omnipotence: Boosting Lean with Deming (Part 6)

Many companies strive to automate by using more technology and fewer humans. But does their productivity really improve? Does it keep them agile? In this episode, Jacob Stoller and Andrew Stotz share stories of companies that improve productivity because they focus on processes instead of tech alone.

TRANSCRIPT

0:00:02.3 Andrew Stotz: My name is Andrew Stotz, and I'll be your host as we dive deeper into the teachings of Dr. W. Edwards Deming. Today, I continue my conversation with Jacob Stoller, Shingo Prize-winning author of The Lean CEO and Productivity Reimagined, which explores applying Lean and Deming management principles at the enterprise level. The topic for today is myth number five, the Myth of Tech Omnipotence. Jacob, take it away.

0:00:29.8 Jacob Stoller: Great, Andrew. Thanks. Great to be here again. Yeah. Tech omnipotence. Well, it's quite a myth. We sort of worship technology. We have for a long time, and we tend to think it can solve all our problems, and sometimes we get a little too optimistic about it. What I wanna talk about is in the context of companies adopting technology and go through some of the stories about that and how that relates to productivity. Really, the myth of tech omnipotence is kind of like a corollary to the the myth of segmented success. In other words, people have believed that you can take a chunk of a company. Now we'll take Dr. Deming's pyramid, and we take a chunk out of that and say, oh, well, that fits so and so in the org chart, let's automate that.

0:01:28.1 JS: And they don't consider what happens to the rest of the organization. It's just this idea that you can superimpose automation. So this has a long checkered history. And the way technology gets justified in organizations is generally what it's been, is reducing headcount. And I used to work in a tech firm, and we used to do this. We would do these studies, not really a study, but you do a questionnaire and you figure out if we adopt this, if we automate this workflow, let's just say, I don't know, it's accounts payable. So you automate accounts payable and you say, well, you got so many people involved, we think we could cut this by three people or something like that. So that becomes your business case. Now, they had categories in these little questionnaires where you would try to get other benefits from the technology, but they tended to be what they call soft benefits.

0:02:35.4 JS: And you know what that word means. Soft benefits means, well, okay, nice to have, but it's not going to get budget money or it's not gonna get approved. So anyway that's really been the kind of standard way of getting tech projects justified. And that goes through pretty much any industry. So what would happen is people adopt these technologies without looking at the whole system. And guess what? You put the software in, you start to implement it, and you run into problems. Doesn't quite work. Doesn't work the way it was supposed to. And so the tech people tended and still do tend to blame the company. They say, well, they had user problems. Users weren't really adjusting to it. These people are sort of way behind. We're a tech company. We've automated the same process for 50 different companies, we know what's good for them. We have to educate them, but they don't seem to want to be educated. So that was kind of the way it was. And I'll give you an extreme example. I did some freelance work for research firm, and one of the studies I worked on, I'm not making this up, it was called Aligning the Business with IT. So it was trying to get people to smarten up with their business and align it to what the smart people are doing with IT. So that's how extreme that kind of feeling was.

0:04:17.3 AS: As opposed to maybe aligning with the customer or something like that.

0:04:21.1 JS: Well, yeah, wouldn't that be crazy? Or how about aligning IT with the business? Finding out what the business wants.