Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Elevate Construction

Elevate Construction artwork

Ep.1700 - The System Asking for Help

Oct 5, 202610 minAudio

What if your system could tell you when it needed help? In this episode, Jason explores the Jidoka principle and reframes it as something much bigger than a machine simply stopping when something goes wrong. A truly lean process should make problems visible, flag them in real time, and ask a human to intervene when help is needed. Jason connects Jidoka, Just-in-Time, Kaizen, visual systems, and respect for people to explain why lean systems should never hide problems. What you'll learn in this episode: Why Jidoka can be understood as a system or process asking a human for help. How flow makes interruptions, bottlenecks, and roadblocks visible. Why visual systems should expose problems instead of hiding them. How respect for people connects Jidoka, Kaizen, and continuous improvement. Why a system isn't truly lean until it can flag problems at the right time. Does everything you've set up ask a human for help when a problem appears? If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two 馃槉). Also, here are links to our YouTube Channels: 路 Jason Schroeder YouTube Channel: https://www.youtube.com/channel/UC4xpRYvrW5Op5Ckxs4vDGDg 路 LeanTakt YouTube Channel: https://www.youtube.com/c/leanTakt 路 LeanSuper YouTube Channel: https://www.youtube.com/channel/UCzQDevqQP19L4LePuqma3Fg/featured 路 LeanSurvey YouTube Channel: https://www.youtube.com/channel/UC-Ztn3okFhyB_3p5nmMKnsw

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Hey there, welcome everybody out to podcast number 1700. Can you believe we're at podcast 1700? I hope they're value add and I hope you're enjoying them. In this podcast, I'm going to talk about the system asking for help. If you're interested in that, please stay with us. Welcome everybody. I hope you're doing well and staying safe out there. I'm super excited to be with you on this podcast. This one right here is super interesting to me. Let me tell you the history behind this. And I want to make a point, a

couple of points actually. First of all, I learned in the book, This is Lean by Nicholas Modig, that the Jidoka principle isn't a principle that's commonly taught in lean circles. And in his framework, he basically, I'm going to say it like this, but it makes sense to me. He basically frames or braces lean as just in time, which is to do things in

a flow. So his definition of just in time, isn't just bring materials just in time when you need them, but just in time in a flow. So just in time for him really means like flow in my opinion. And the concept here is that you first have to be on a flow. Okay. And once you're on a flow, you can see if there's problems with that flow. So when you're, if you know the flow

and can see the flow, or if there's an actual established flow, are there problems with that? Are there what he calls stops and restarts? Are there interruptions? Are there what Elihu Goldratt talked about bottlenecks? Are there roadblocks in construction for the train of trades? Are there system problems that are hindering your progress? These are all things that you must notice. And what Nicholas Modig is saying is the

Jidoka principle, not Jidoka itself, but the Jidoka principle is that if you have a flow, then you see problems with that flow. Then the concept of Kaizen comes in, which is where you fix it, the situation, the problem that you saw with the Jidoka principle. And it's all based on respect for people. So essentially with his system, he is like, you know, you really need to make sure

that you understand what your flow is. And then you need to make sure that you understand where there are problems. And then you need to improve those. And it's all based on respect for people. You have to have a fundamental respect for people. So his is one of the simplest frameworks in lean that I know of. So very, very simple framework, very, very effective framework. And so he got me into thinking about the concept of the Jidoka principle. And I'm like, wow, this is a pretty cool concept. Then I go to Japan, fast forward, I

go to Japan with Paul Lakers and on his lean trip, not one-on-one, but with a group. And I find out that the two principles of the Toyota production system are actually Jidoka and just in time. And that the Japanese culture is based around Kaizen to make better. They always have this like never ending search for improvement to make things better. They had it with in the Meiji restoration.

They had it amongst the Shogun. I mean, it's just a part of Japanese culture. So, I mean, this is not something that they learned from Western society, even if Western society had things to teach. And in their Shinto and Buddhist backgrounds, they do not believe in throwing away human beings. They honor the inherent value of a human being. So again, we see this pattern of respect for people at the base, then just in time and Jidoka and this always elevating magnetizing

concept of Kaizen. So I'm like, wow, this is really cool. And in Japan, Sekiichi Toyoda invented the loom, his famous loom. And the Jidoka principle was that he had little metal pins. I think you can call them pins. I can call them pieces too, but little metal pieces on each strand. If one of them dropped, it would hit a lever and that lever would stop the machine and eventually stop all of machines.

So a machine was asking a human for help. And Jidoka is translated as autonomation or automation with a human touch. You don't really get much from that translation. I think one of the biggest problems is we're not translating some of these Japanese words and concepts right. So autonomation or automation with a human touch, like what am I supposed to understand from that? Well, I don't really know. What really landed with me, and this is

where this podcast turns remarkable, is that it's when a machine asks a human for help. It's when a machine asks a human for help. When a machine asks a human for help. This is so genius. And you can say when a machine asks a human for help, when a process asks a human for help, when a system asks a human for help, when AI asks a human for help, you can you can basically plug anything into it.

But what does that mean? What does that mean? That does mean that machines should notice, according to Pok茅Yoki, notice and stop if there's a problem and ask a human for help. It does mean a process should immediately flag itself and ask a human for help. A system should never hide problems and should make problems visible so it can ask a human for help. And let me even dig deeper.

Logistics environments should automatically signal humans and ask them for help. A schedule should be visual enough to ask a human for help. And anything we do should bring problems to the surface so it can ask a human for help, which means that that is supportive of bringing all problems to the surface and having everything be visual. So the point is your logistics system is

not lean enough yet until it flags problems automatically through visual systems and asks a human for help. Your process is not good enough until it asks a human for help. Your system is not good enough until it asks a human for help. Your contracting methods are not good enough until they ask a human for help. A safety system and environment is not good enough until it asks a human for help. So everything in lean is about seeing. Everything in lean is about bringing problems to

the surface. And this Jidoka principle is not just some machine stops somewhere. It's can human beings see what needs to be seen, know what needs to be known, and act together to solve a problem. If a principle or a technology or anything ever turns into hiding something from a human being or not allowing a human being to see what needs to be seen, it is not lean. Ask yourself, does everything you've set up... And real quick, let me give you an

example. In the lean community, we've got people talking about poll plans and weekly work plans, and they're like, yeah, put it up there. And let's go ahead and talk about where we are, what zone we are, and how much labor we have. I, Jason, am like, no, let's put visuals on the wall that show where roadblocks are, and let's talk about problems. My conference room layout and lean teaching actually is Jidoka in the sense that I'm focused

on the process or the system or the schedule asking a human for help. And these other ones are hiding problems, so they are not essentially or effectively lean. Ask yourself this, is everything I set up, does it ask a human to help at the right point by flagging problems real time? I hope you've enjoyed this podcast. On we go.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Ep.1730 - Go to the Pain

    Nov 20, 20268 minAudio

    Avoiding the hardest problem rarely makes it disappear; it usually gives it more time to grow. In this episode, Jason explains why one of the best ways to improve projects, leadership, and even your own peace of mind is...

    Credit the people on this episode

  2. Ep.1729 - Sandbaggers and Superhumans

    Nov 20, 20268 minAudio

    When estimating durations, people tend to drift toward one of two dangerous extremes: padding the schedule because they have been burned before, or promising unrealistic performance because they believe they can push...

    Credit the people on this episode

  3. Ep.1728 - How to Lead From Below

    Nov 20, 20267 minAudio

    You do not need authority over the entire project to start leading. In this episode, Jason shares a story from his own career to explain why the most effective way to lead from below is not to wait for permission,...

    Credit the people on this episode

  4. Ep.1727 - Why Three-Week Pulls Don't Work

    Nov 18, 20267 minAudio

    A three-week pull may look like Lean planning, but Jason argues that it can leave teams focused on what is directly in front of them instead of preparing the entire phase properly. In this episode, he explains why...

    Credit the people on this episode

  5. Ep.1726 - Level 10 Meetings: Identify, Discuss, Solve

    Nov 18, 20268 minAudio

    A great meeting should do more than share updates it should expose what is off track and help the team solve it. In this episode, Jason breaks down the purpose and flow of the Level 10 Meeting from the Entrepreneurial...

    Credit the people on this episode