>thing we decided is important for us to measure and increase This is a great explanation, and I just wanted to nitpick that for some KPI's (e.g. percentage of

>thing we decided is important for us to measure and increase This is a great explanation, and I just wanted to nitpick that for some KPI's (e.g. percentage of defective components, or latency), you would aim to "decrease" the KPI, and in some rare instances, you'd want to keep the KPI within a range (e.g. resource utilization, or inventory size, when you want a predefined amount of buffer).