Skip to main content

Lean - A Primer

A Brief Primer on LEAN

© 2014, Adam S. Keck

Based on:

Four Capabilities of Accelerating organizations

  • Specify precise approach to every task with built-in tests to detect failure and stop on error.
  • Swarm to solve problems – immediate RCA.
  • Share new knowledge throughout organization.
  • Leaders lead by developing above capabilities in every single employee.

Work Flow and System Design

  • LEAN is a framework for successfully designing complex systems and work flows. A system is a collection of related work flows. A company can be viewed as a single complex system that  provides value to customers in return for money.
  • LEAN is a way of working: Every employee uses LEAN work flow every day to both follow and improve the processes for which they are responsible.
  • LEAN is a specific implementation of Deming’s “Plan, Do, Check, Act” (PDCA)
  • Work flows should stop on error or self-regulate (“autonomation”): Each step has built in tests for verification.

On failure, stop the process and trigger an immediate RCA (Autonomation)

  • Start from the delivery of the correct work flow output to its consumer. Each downstream need paces and specifies work upstream in the process (Kanban is a specific method of achieving this goal).
  • Develop the work flow by working backward from the output that exactly fulfills the needs and requirements of final customer (i.e., what Raving Fans calls the Ideal).
  • Mistakes: Human error generally considered only when a person does not follow the current written process or does not verify that the output of each step is correct. All other errors are considered defects in the process that allow errors to occur. This philosophy drives the “Swarm to RCA each failure” capability.

Work Flow Creation Framework (In order)

  • Specify outputs – What does the work flow have to deliver, to whom, when, and what does it mean for the work flow to be successful?
  • Design pathways – Flow of materials, information, and services. Who is specifically responsible for each step in a pathway?
  • Design step connections – Linkages between adjacent process steps
  • Specify task methods – How exactly is each step in each process accomplished successfully?

Work Flow Creation Tools

  • Checklist
  • Automation code
  • Flow chart
  • Input/Output/Handoff chart

Problem Solving (Iterate)


  • Defect-free work flow
  • On-demand work flow
  • Work flow provides only exact output needed by client process or customer.
  • Immediate fulfillment of needed output.
  • Work flow runs without waste
  • Work flow is safe and secure (personnel not harmed, and information and assets secure) 


  • The commonly cited “A3 process” is a specific work flow and presentation format that implements the elements below in a way that ensures customer buy-in at each step.
  • Use graphical elements to efficiently present and confirm information with customers.


  • Background: Why is this problem important?
  • Current condition: Measurements and metrics. Get and confirm information directly.
  • Gap analysis: How do the process and its outputs differ from the ideal (see previous section)
  • Root Cause Analysis: Swarm on failure; analyze gaps from ideal
  • Develop Countermeasures (rapid prototyping = experiments to find right solutions.)
  • Specify target condition: Desired new process with countermeasures in place
  • Measure actual outcome of new process: repeat measurements and metrics
  • Gap analysis and further RCA

Sharing Knowledge

  • Organization-wide sharing accelerates productivity. Everyone follows documented work flows. 
  • See one, Show one, Do one (from hospital LEAN efforts).
  • Codify discoveries for wide dissemination (e.g. Toyota “Lesson learned books” specify what’s feasible/cost-effective for a certain type of output or process)
  • Knowledge-base that stores documented work flows = “company memory”


  • Regularly practice system design and problem solving
  • Develop LEAN skills in all employees, at every level.
  • Practice following work flows with verification of each step to prevent defects.


  • Everyone works using LEAN principles every day. Bottom up – sometimes guided - work flow improvement.
  • Everyone who knows the skills above leads those who are new by teaching them the above skills.
  • Learn to see and solve problems with rapid prototype iterations. Practice this skill.
  • Work flow improvers get and confirm information directly. Nothing is assumed.


Popular posts from this blog

How to fix this ssh error from a Cisco switch: ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits

Problem ssh user@cisco_switch returns: ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits key_verify failed for server_host_key Solution The modulus of the ssh RSA key pair on the switch is too small. If you have access, generate a new key pair on the switch with a larger modulus. Procedure Login with ssh protocol version 1 ( ssh space dash one ): ssh -1 user@cisco_switch (On the switch): enable (On the switch): Authenticate to "Privileged Exec Mode" mode on the switch. (On the switch): conf t (On the switch): crypto key generate rsa general-keys modulus 1024 (On the switch): Press enter to accept that the current key pair for the switch will be replaced. You now should be able to log into the switch with ssh protocol version 2.

How do I dual-boot Ubuntu 18.04 on a 2011 Mac Mini?

Machine Specs: Mac Mini (Mid 2011), Macmini5,2 Core i7 16 GB RAM (2x8 GB) AMD Radeon HD 6630M 256MB 27-inch Apple Thunderbolt Display 512 GB SSD Running macOS 10.13 High Sierra Caution: This process can result in data loss. If you have personal data on the Mac Mini before starting, back it up first. Twice! (One is none. Two is one. ~ U.S. Navy Seal saying).  Also, mistyping in the parts of this process may brick your Mac Mini. You have been warned. If in doubt, stop working and do research on Google until you understand what's going on in the step. If you find an error, please leave a comment. I will update. Note: This is process I figured out in lieu of booting the Ubuntu install with EFI via refind. Via the refind boot method, I would constantly get: 10:39:07 kernel: Couldn't get size: 0x800000000000000e 10:39:07 kernel: MODSIGN: Couldn't get UEFI db list 10:39:07 kernel: Couldn't get size: 0x800000000000000e The error seems to be relate

Fixing SSH connection problems in EGit in Eclipse

Note: I posted a version of this on Stack Overflow. Errors can occur when there is an underlying SSH authentication issue, like having the wrong public key on the git remote server or if the git remote server changed its SSH host key. Often the an SSH error will appear as: " Invalid remote: origin: Invalid remote: origin" Eclipse will use the .ssh directory you specify in Preferences -> General -> Network Connections -> SSH2 for its ssh configuration. Set it "{your default user directory}.ssh\" . To fix things, first you need to determine which ssh client you are using for Git. This is stored in the GIT_SSH environmental variable. Right-click on "Computer" (Windows 7), then choose Properties -> Advanced System Settings -> Environment Variables. If GIT_SSH contains a path to plink.exe, you are using the PuTTY stack. To get your public key, open PuTTYgen.exe and then load your private key file (*.ppk). The listed public key sho