Processes are ever evolving. They keep changing to suit
business and their goals. As an analyst weneed to keep finding ways to improve
it, make it more relevant and optimal. Business process management only talks
about lifecycle of a process, it doesn’t gives us tools to optimize. There are
very few tools that help an analyst to think in a structural fashion. One such
tool is “Lean”.
Lean essentially talks about reducing waste and in turn make
a process more efficient and optimal. Lean is specifically very relevant for
process optimization as it talks about flow of process. Although it was first
applied in manufacturing, but we as an analyst can take a lot of clues from it,
to optimize process in any sector. Toyota, which was pioneer in Lean
manufacturing, talks about three kinds of wastes.
- Muri – Related to design of process, it talks about what we can proactively avoid while designing the process.
- Mura – Related to implementation of process and elimination of fluctuations
- Muda – Specifically talks about seven kinds of wastes
Application of Lean in Process Automation and Optimization
In terms of software lifecycle, Muri and Mura come into play
during requirement gathering, System design and Testing Phases. Whereas Muda is
something that we can observer while alpha or beta launch or when software is
in production.
But from a process optimizer or BPR point of view Muda
principles are most important. As an analyst if we are doing process
optimization or reengineering, process is mostly know. We need to find what’s
going wrong. Muda seven wastes can give us indications where to look for. Lets
try to translate these seven wastes into BPR or Process Optimization context.
- Transportation – It says if we are moving products for processing it, it is a waste. This can be directly translated to one of BPR principle, “Organize around outcomes, not tasks”. So if tasks (Activities) not organized around the outcomes, we have to look into why it is happening so.
- Inventory – Any kind of inventory is waste according to Muda principle. In software world inventory can be storing temporary data be in excel or CSV. So if we have activity, which says to store data only for reference purpose, we are creating a kind of waste.
- Motion – Originally it refers to movement of manpower or machine where as for process we can refer it usage of too many screen for completing a single task.
- Overproduction – If we producing results that are not being used currently we are producing waste.
- Over Processing – Generally in reporting or documenting steps we produce results for future and hence we need to do more calculation and representation like creating charts. This can also be termed as waste.
- Waiting – This can also be translated to one of BPR principle “Have those who use the output of the process perform the process” and hence there should not be any waiting.
- Defects – I guess defect definition remains same, be it manufacturing or software or process
Comments