3 ms·
Well, keep in mind that "improvement" here implies non-transformative change (we usually call this "optimization" on informatics). If you are not sure you have
by marcosdumay 5y ago
Well, keep in mind that "improvement" here implies non-transformative change (we usually call this "optimization" on informatics). If you are not sure you have the correct system running, stabilizing it is the last thing you want.
- avs733 5y agoI think that may be a too narrow vision of “transformative” improvement. I worked in a factory where one of the biggest, and hardest, improvements we made was coaching the managers and engineers to leave the technicians alone when they were doing maintenance. We collected data on how often they were interrupted, how much time it cost, and how interruptions could lead to RIT changes in procedures that affected quality. Previously the engineers and managers saw the checking as helping because they could se ethe status of things and observe and answer questions, many would even lend a hand. Oversight and engagement was seem as a path to improved quality. To let go of that was a huge transformation. It started with data - a lot of data - that allowed us to identify that weekend and night maintenance generally went faster and better.
- marcosdumay 5y agoWell, I claim that is a way too broad definition of "transformative". The people kept creating the same products, by almost the same procedure.
- zepto 5y ago> If you are not sure you have the correct system running, stabilizing it is the last thing you want. Stable in this case just means you are clear what the system is and can keep operating it if you want to. That is a prerequisite to evaluating the system in order to determine whether it is what you want.