When the Six Sigma project is launched, you need to know what processes are being performed and what people are being implemented, what their efforts are, what customer feedback is about them, both inside and outside.
This helps to optimize actions that can be useful for reducing cycle time and reducing the number of failures and process inconveniences to achieve the best quality that the customer expects.
BOLO list (be on the lookout) in process map analysis
When analyzing the actions displayed on the process map, the goal is to identify bottlenecks and latency areas and convert them into process.
Sometimes errors or failures can occur if process operators are unaware of a particular problem or do not know what role is being performed. Bolo’s list can alert you to assumptions made when making decisions based on instincts rather than facts.
There are often duplicates of input data, as well as several stages of the process in different areas. The BOLO list will be able to trigger this fact to verify this duplication. This eliminates some unnecessary steps in the process that add too much time to complete.
The total cycle time can be analyzed from these process charts – and since duplication and unnecessary steps are indicated, it becomes possible to eliminate these steps, shorten the cycle time and make the process more efficient.
The process map analysis also examines decisions about uncertainty about people’s authority and the need to make decisions at that time. It is also necessary to analyze the ongoing recovery and find steps that do not add value to the process.
The BOLO list usually includes assumptions, duplications, scalability problems, etc.
The Bolo list can also help find processes that use the software but have a lengthy process and too many documents that can be investigated and deleted.
Quality control measures
Even quality control measures are listed, as some controls could have been avoided and others are not needed at the operator level.
It contains quality control steps that should be performed not by the operator, but by someone outside the process. It also includes a scalability scenario (i.e. whether the system can function well as the business continues to grow).
Last but not least, it also lists areas where specifications are set each time a process is started, rather than setting common standards for everyone.
This checklist of things to look out for will help you understand and improve the new process in these areas. The BOLO list is very useful for displaying processes and making improvements.