Operational Excellence Roadmap: A 12-Month Plan for One Plant

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

An operational excellence roadmap turns improvement into a plan. See a 12-month plan for one plant, from assessment and pilot to rollout, with an example.

A plant can turn operational excellence into a plan with five phases in twelve months: assess, pilot, standardize, extend and review. This article is for operational excellence leads and plant managers who must plan the first year in one plant. It explains what to set up before month one, what to do in each phase, how to handle the people side, a worked example with numbers and the mistakes that stall the plan.

Key points

• A plant needs a system, not a set of tools. Barry-Wehmiller found that tools used ad hoc gave uneven results and faded when strong practitioners left.
• Set up governance first: an executive sponsor, a steering group and one dedicated lead who owns the plan.
• Follow five phases in 12 months: assess, pilot, standardize, extend and review. Test in one area before you scale.
• Write the method into a playbook, and use the pilot team to coach the next area. Bench strength keeps gains alive.
• Real change takes longer than a year. The Shingo Challenge asks for at least three years of sustained improvement.

What is an operational excellence roadmap?

An operational excellence roadmap is a sequence of steps, with owners and dates, that turns the idea of continuous improvement into daily work. It names the phases, the pilot area, the measures and the people who lead.

Why do plants need one? An IndustryWeek interview with Barry-Wehmiller gives a clear case. The company had many lean tools, but teams used them ad hoc, and gains were uneven. It lacked a systematic improvement roadmap. When a strong lean practitioner left a plant, the improvements faded, because there was no bench strength to keep them up.

The company then set up formal governance and a dedicated leader, tested the approach at model sites and built a playbook to scale it. This is a single company interview of a programme that was still early, and it reports no outcome numbers. But the pattern is useful: a system, an owner, a pilot and a playbook.

The plan below follows that pattern. It is my own planning aid, built on the sources named in the text. It is not a standard, so adapt it to your plant.

What should you set up before month one?

Three things come first.

1. Governance. Barry-Wehmiller used a steering committee with an executive sponsor to set the direction. In one plant, that can be the plant manager as sponsor and a small group of area leaders.
2. One lead. Name one person who owns the plan and has time for it. The company hired a central leader, and that leader's first priority was to build credibility with leaders and the workforce, and to show people how the changes would benefit them.
3. A scope. Choose one plant, and within it a few value streams. A value stream is all the steps that take a product from order to delivery. Do not start with everything.

Also agree on three to five goals tied to the business strategy, for example delivery, quality and cost. Write them on one page, and align every later choice with them. Good management of the plan starts here.

Months 1 and 2: how do you assess where the plant stands?

Start with a diagnostic, not with tools. The Kaizen Institute describes a case in which an initial diagnostic identified where operational excellence could be strengthened and where lean behaviours would add the most value. The source is a consultancy and its case is self-reported, so use it as an example of the approach, not as proof.

Look at four things:

• Flow. Use process mapping to draw one value stream from order to delivery, with the waiting times between steps. Mark the bottleneck.
• Quality. Collect scrap, rework and returns for the last months.
• Delivery. Measure on-time delivery and schedule attainment.
• Culture. Walk the floor at the gemba, the real place of work. Talk to operators and team leaders. Ask what stops them from doing the job well.

End the phase with a short list: the three biggest problems, the first pilot area and the baseline numbers. Keep a baseline, because without one you cannot show progress later.

Months 3 to 5: how do you run a pilot?

Pick one area as a pilot, such as one value stream or one line. Barry-Wehmiller launched six model sites, one in each business division, to test its framework. The Kaizen Institute case describes a pilot at one reference site. The idea is the same: learn in a small place before you scale.

In the pilot, introduce a small set of practices:

1. A daily routine. A short meeting at the line to review the measures and the open problems.
2. A few measures. Delivery, quality, safety and cost, shown with targets.
3. Standard work for the key tasks, written with the operators.
4. A problem-solving method. Use root cause analysis, for example the five whys, and track actions to closure.
5. Leader presence. Leaders go to the area every day and ask questions. The Kaizen Institute case lists daily process confirmation and gemba walks as part of the model.

Keep the implementation simple. A pilot succeeds when people use the routine without being reminded, not when the board looks perfect.

Months 6 to 8: how do you standardize what works?

Now write down what worked. A playbook is a short description of each practice: why it exists, how it runs, who does what and how you check it. The Kaizen Institute case built playbooks for each standard, with methods, metrics and maturity assessments, and used them for training and governance. Barry-Wehmiller planned a playbook to be well vetted before more sites launched, and it expected this to take several months.

This phase also deals with the people side of change management:

• Explain why. Tell people what is changing and how it helps them. Change management is mostly good communication.
• Be careful with new labels. In the interview, Barry-Wehmiller's leader warned that new terminology can make staff resist change. Use the words your teams already know.
• Involve every stakeholder. Operators, maintenance, planners and quality all take part.
• Train in the work. Short sessions at the line beat long classroom days.
• Share best practices. Let the pilot team show what works in the plant.
• Build bench strength. Train deputies, so that the routine does not depend on one strong person.

Months 9 to 11: how do you extend to other areas?

Use the pilot team to help the next area. The Kaizen Institute case describes peer transfer: representatives of the reference site joined deployments at other locations, which helped prepare internal coaches. In a single plant, the pilot area's team leader and an operator can join the start-up of the next area for a few weeks.

For each new area, follow the same short sequence: assess, set up the routine, agree on measures, write the standard work and coach. Do not start more areas than your coaches can support, and keep the method repeatable. Two areas at the same time are often enough for a first year.

Keep an eye on the workflow between areas too. A gain in one area can push a bottleneck to the next, and productivity gains vanish at the new constraint. A short review of the whole value stream shows where it moved.

Month 12: how do you review and plan year two?

Review the year with the sponsor and the steering group.

1. Compare the baseline with the results. Show the measures, not stories.
2. Ask the people. What helped, what did not, and what was too much?
3. Check the playbook. Update it with what you learned.
4. Choose the next areas and the next level of ambition. Add a deeper method, such as Six Sigma tools for variation problems, if the data call for it.
5. Set the plan for year two.

The Shingo Institute says on its model page that its Challenge asks for evidence of at least three years of sustained transformational improvement. Treat year one as the start, not the finish.

Example: a 12-month plan for one plant

This is an illustration with made-up numbers.

A plant has four value streams, 120 employees, and ships 500 orders per week. Baseline: 85% on-time delivery, and a 3.5% scrap rate on 8,000 units per week.

The plan:

• Months 1 to 2: assess all four value streams. Select value stream A as the pilot.
• Months 3 to 5: pilot in A.
• Months 6 to 8: write the playbook, train the other areas.
• Months 9 to 11: extend to B and C.
• Month 12: review. Value stream D is planned for year two.

Targets after 12 months: on-time delivery of 92% and scrap of 2.8%.

• Orders on time now: 500 × 85% = 425.
• Orders on time at target: 500 × 92% = 460. That is 35 more orders per week.
• Scrap now: 8,000 × 3.5% = 280 units.
• Scrap at target: 8,000 × 2.8% = 224 units. That is 56 fewer units per week.

Training effort: each of the 120 people gets 6 hours of training in the first year.

• Total: 120 × 6 = 720 hours.
• In 40-hour weeks: 720 ÷ 40 = 18 person-weeks.

The numbers are assumptions. The point is the shape of the plan: one pilot, a playbook, a staged extension and a review. Use your own baseline.

Common mistakes

• Sampling tools. Using tools one by one gives uneven results that fade. Build one system.
• No owner. A plan that belongs to everyone belongs to nobody. Name one lead and one sponsor.
• Starting everywhere. Too many areas at once overload the coaches. Start with a pilot.
• Skipping the baseline. Without starting numbers you cannot show progress.
• Ignoring the people side. New labels and sudden changes create resistance. Explain and involve.
• No bench strength. If one person carries the routine, it fades when that person leaves.
• A plan with an end date. Sustained change takes years. Plan year one in detail, and keep going.

How software can help

A plan needs data on the plant: plans, flow, stops and results. iFAKT is a Stuttgart-based consulting company and software specialist for Industry 4.0, founded in 2001, that helps manufacturers plan and optimize production and logistics processes. It develops the Polaris software. Whatever you choose, start with the routine, and add software where the data hurts most. Check that the numbers match what people see at the line.

Next step

Name a sponsor and one lead, and pick the pilot area for your operational excellence roadmap. Then book two weeks for the assessment and write down the baseline for three to five measures.