This plastics manufacturer had already seen what a Management Operating System could do. An earlier POWERS engagement at a sister plant had replaced opinion and tribal knowledge with credible standards and real-time visibility, and the results followed. Site leadership wanted that system working here too: a structured way to drive daily performance and lift site profitability.
A plastics manufacturer duplicated its sister plant's proven Management Operating System in 11 weeks instead of 28, cutting scrap 64% and quality findings 60%.
A proven blueprint one plant away, a site still run on tribal knowledge, and leadership that knew exactly what was missing.
This plastics manufacturer had already seen what a Management Operating System could do. An earlier POWERS engagement at a sister plant had replaced opinion and tribal knowledge with credible standards and real-time visibility, and the results followed. Site leadership wanted that system working here too: a structured way to drive daily performance and lift site profitability.
The starting point, though, looked a lot like the sister plant before its transformation. Fundamental management tools either did not exist or were not used, and the leadership team knew it: elements were missing, and the gaps needed to be filled. Front-line leadership and the workforce were deeply tenured, built on a long history of promotion from within, and carried the deep roots of “this is how we’ve always done it.” Day to day, the operation ran largely on tribal knowledge.
A proven system one plant away does not install itself. The blueprint still had to take hold in a different building, on different lines, with leaders who had run things their own way for decades, and it had to do so quickly. What the site needed was the original engagement, compressed: the same operating system, stood up in a fraction of the time, and owned by the people already on the floor.
Six structural gaps: a compact Discovery found the same system missing everywhere it looked.
An MOS critique found essential Management Operating System elements neither in place nor in use across three different production areas and within quality.
One line lost 70% of its capacity to a mechanical issue, another 12%, three more ran between 67% and 85% of hourly capacity, and only a single line hit 100%.
Machine cycle times went unmanaged, with some lines running faster than the stated cycle yet still missing hourly capacity and others running slower than the standard allowed.
Actual machine tooling was not managed against plan, so what the schedule assumed was running and what was in production routinely disagreed.
Supervisors did not demonstrate active management skills and did not manage actual performance against job standards, leaving output to experience and habit.
The site had a single Production Report, and Supervisors did not actively use it, so the one window into performance drove no daily decisions.
Duplicated a proven operating system in 11 weeks instead of 28.
POWERS scoped the engagement around a single objective: duplicate the Management Operating System proven at the sister plant, in 11 weeks rather than the original 28. DPS (Digital Production System) software went in as the foundation for behavior change, not a reporting layer bolted on afterward, giving Leads and Supervisors a live, shared view of performance to manage against.
Around that foundation the team installed the full set of MOS elements. Plant goals were established and communicated, and roles and responsibilities were defined with production Leads and Supervisors so ownership was explicit. Daily schedule control with short-interval follow-up put a rhythm under every shift, while KPI dashboards, Sunday night startup scorecards, and downtime and lost-production Pareto charts made performance and its losses visible. A defined communication structure, an action item log, and a skills flexibility matrix gave the site the routines to act on performance barriers.
The engagement also invested directly in the site’s next leader. POWERS worked with the new Plant Manager in Training on a systematic way to manage and drive performance through essential KPIs, so the operating system would belong to the person running the building rather than the consultants who installed it. Eleven weeks in, the routines were running on their own and the numbers were already moving.
Six measurable gains, delivered in less than half the time of the original engagement.
Scrap fell 64% as credible standards, short-interval follow-up, and live DPS visibility caught losses at the machine instead of at month end.
Quality findings dropped 60% as MOS discipline took hold inside quality, one of the areas the critique flagged alongside production.
Sunday night startup scorecards turned the week's first hours from an unmanaged loss into a measured routine, lifting startup scores 36%.
Production run rates rose 6% across a site where five of six lines had been running below stated capacity.
Setups fell 18% as schedule control and tooling discipline cut unnecessary changes on the floor.
Changeover time dropped 9% as daily schedule control and short-interval follow-up kept transitions planned, staffed, and on the clock.
Ready to build disciplined execution in your operation?
Every POWERS engagement starts with our intensive Discovery Process. We work with everyone on your team, identify the gaps in the five disciplines that hold execution back, and build the partnership that closes them. The results stay built long after we’re gone.
A plastics manufacturer duplicated its sister plant's proven Management Operating System in 11 weeks instead of 28, cutting scrap 64% and quality findings 60%.
A proven blueprint one plant away, a site still run on tribal knowledge, and leadership that knew exactly what was missing.
The starting point, though, looked a lot like the sister plant before its transformation. Fundamental management tools either did not exist or were not used, and the leadership team knew it: elements were missing, and the gaps needed to be filled. Front-line leadership and the workforce were deeply tenured, built on a long history of promotion from within, and carried the deep roots of “this is how we’ve always done it.” Day to day, the operation ran largely on tribal knowledge.
A proven system one plant away does not install itself. The blueprint still had to take hold in a different building, on different lines, with leaders who had run things their own way for decades, and it had to do so quickly. What the site needed was the original engagement, compressed: the same operating system, stood up in a fraction of the time, and owned by the people already on the floor.
Six structural gaps: a compact Discovery found the same system missing everywhere it looked.
An MOS critique found essential Management Operating System elements neither in place nor in use across three different production areas and within quality.
One line lost 70% of its capacity to a mechanical issue, another 12%, three more ran between 67% and 85% of hourly capacity, and only a single line hit 100%.
Machine cycle times went unmanaged, with some lines running faster than the stated cycle yet still missing hourly capacity and others running slower than the standard allowed.
Actual machine tooling was not managed against plan, so what the schedule assumed was running and what was in production routinely disagreed.
Supervisors did not demonstrate active management skills and did not manage actual performance against job standards, leaving output to experience and habit.
The site had a single Production Report, and Supervisors did not actively use it, so the one window into performance drove no daily decisions.
Duplicated a proven operating system in 11 weeks instead of 28.
POWERS scoped the engagement around a single objective: duplicate the Management Operating System proven at the sister plant, in 11 weeks rather than the original 28. DPS (Digital Production System) software went in as the foundation for behavior change, not a reporting layer bolted on afterward, giving Leads and Supervisors a live, shared view of performance to manage against.
Around that foundation the team installed the full set of MOS elements. Plant goals were established and communicated, and roles and responsibilities were defined with production Leads and Supervisors so ownership was explicit. Daily schedule control with short-interval follow-up put a rhythm under every shift, while KPI dashboards, Sunday night startup scorecards, and downtime and lost-production Pareto charts made performance and its losses visible. A defined communication structure, an action item log, and a skills flexibility matrix gave the site the routines to act on performance barriers.
The engagement also invested directly in the site’s next leader. POWERS worked with the new Plant Manager in Training on a systematic way to manage and drive performance through essential KPIs, so the operating system would belong to the person running the building rather than the consultants who installed it. Eleven weeks in, the routines were running on their own and the numbers were already moving.
Scrap fell 64% as credible standards, short-interval follow-up, and live DPS visibility caught losses at the machine instead of at month end.
Quality findings dropped 60% as MOS discipline took hold inside quality, one of the areas the critique flagged alongside production.
Sunday night startup scorecards turned the week's first hours from an unmanaged loss into a measured routine, lifting startup scores 36%.
Production run rates rose 6% across a site where five of six lines had been running below stated capacity.
Setups fell 18% as schedule control and tooling discipline cut unnecessary changes on the floor.
Changeover time dropped 9% as daily schedule control and short-interval follow-up kept transitions planned, staffed, and on the clock.
