Use this year’s budget. Deliver next year’s win. The Green Belt Accelerator starts January 19.

What to Expect from Lean Process Optimization Consulting

Published November 6, 2026. Updated November 9, 2026.

If you are shopping for process optimization consulting, the proposals can look alike: assess, improve, sustain. The useful differences sit inside those words. What exactly gets mapped? What data is collected before anything changes? How is a fix tested? Who owns the result when the consultants leave?

Request a scoping call

What this guide covers

This guide walks through what a lean process optimization consulting engagement usually involves, using general good practice. Most firms that offer “lean” consulting today use Lean Six Sigma, so this guide covers that combined approach: lean tools for flow and waste, plus DMAIC for data discipline. It will help you read a proposal, compare consultants, and prepare your own team.

Engagements have ranged from 2 weeks to 10 years, depending on the client’s needs. Timing is set once the scope is clear, so treat the steps below as a framework rather than a fixed schedule. For unfamiliar terms, see the Lean Six Sigma glossary.

What lean process optimization consulting is

Lean process optimization consulting, as most providers practice it now, combines lean and Six Sigma. Lean looks at how work flows: where it waits, where it is redone, and which steps do not help the customer. Six Sigma methods, including the DMAIC cycle (define, measure, analyze, improve, control), add data discipline: measure the problem, prove the cause, and verify the fix. A good engagement uses both, so changes are practical for the people doing the work and backed by evidence.

Process improvement consulting is a broader term that can include lean, Six Sigma, workflow redesign, and software or staffing changes. In this guide, process optimization is the main term, and it means a Lean Six Sigma engagement that moves from a defined problem to a measured result, with your people involved throughout. Whatever the label on a proposal, ask which tools will actually be used.

The engagement, step by step

Each step below is labeled with its DMAIC phase. Lean tools such as gemba walks, value stream mapping, kaizen events, standard work and visual management show up where they usually fit. The duration of each step is agreed during scoping. Overall engagements have ranged from 2 weeks to 10 years, depending on the client’s needs.

Eight engagement steps grouped under assessment, improvement, and sustainment Assessment covers scoping and charter, current-state mapping, baseline data, and root cause analysis. Improvement covers solution design and pilot, and implementation and standard work. Sustainment covers the control plan and the handoff. Assessment 1. Scoping and charter 2. Current-state mapping 3. Baseline data 4. Root cause analysis Improvement 5. Solution design and pilot 6. Implementation and standard work Sustainment 7. Control plan 8. Handoff

Work Stream groups these eight steps into three stages: assessment, improvement and sustainment.

Work Stream stageSteps in this guideDMAIC phases
Assessment1. Scoping and charter, 2. Current-state mapping, 3. Baseline data, 4. Root cause analysisDefine, Measure, Analyze
Improvement5. Solution design and pilot, 6. Implementation and standard workImprove
Sustainment7. Control plan, 8. HandoffControl

1. Scoping and charter

DMAIC: Define. Lean tools often used: initial gemba walks to see the process before the charter is locked.

What happens: Good engagements start with a short, specific agreement on what is being fixed. That usually includes a problem statement in factual terms, where the process starts and ends, what is out of scope, two or three measures of success, the sponsor, the process owner, and known constraints. Scope that is too wide leads to shallow analysis, and scope that is too vague lets the work drift.

Who is involved: The sponsor, the process owner and the consultants, with input from the people who run the process when it is time to estimate their involvement.

Typical duration: Agreed during scoping.

What you get: A signed charter with scope, measures and a clear picture of who from your side will be involved, and how much of their time is needed.

2. Current-state mapping

DMAIC: Measure. Lean tools often used: gemba, value stream mapping, SIPOC and detailed process maps.

What happens: The team maps how the process actually works, not how the procedure says it works. That means going to the gemba, following real work from start to finish, and talking with the people who do it. Common tools include SIPOC (suppliers, inputs, process, outputs, customers) for the big picture and value stream mapping or detailed process maps for the steps, handoffs and waits.

Who is involved: The people who do the work, the process owner and the consultants.

Typical duration: Agreed during scoping.

What you get: A visual current-state map that the people in the process recognize as true. If they do not, the map is not finished.

3. Baseline data

DMAIC: Measure. Lean tools often used: time observation at the gemba and simple counts of wait, rework and inventory.

What happens: Before changing anything, the team measures. Typical measures include lead time, cycle time, volume, error or rework rates, first-pass yield (the share of work done right the first time), and backlog. If the data is not already tracked, the team may collect it manually for long enough to establish a reliable baseline. Without a baseline, there is no credible way to show later that anything improved. Ask how the consultant will define each measure and whether the same definitions will be used for the final comparison.

Who is involved: The process owner, the people who run the process, the consultants and, when savings are part of the goal, a finance contact.

Typical duration: Agreed during scoping.

What you get: Agreed measure definitions and a documented baseline that will be used for the final comparison.

4. Root cause analysis

DMAIC: Analyze. Lean tools often used: 5 Whys, fishbone diagrams and waste walks tied back to the value stream map.

What happens: With the map and baseline, the team looks for what really drives the problem. Tools range from the 5 Whys and fishbone diagrams to Pareto charts and, for variation-heavy problems, statistical analysis. The aim is to separate the few causes that matter from the many that do not. The loudest theory in the room is often a symptom, not the root cause. Evidence keeps the team from solving the wrong problem.

Who is involved: A cross-functional team that includes the process owner, people who do the work and the consultants.

Typical duration: Agreed during scoping.

What you get: Documented root causes, with the evidence behind them.

5. Solution design and pilot

DMAIC: Improve. Lean tools often used: kaizen events (also called a kaizen blitz or rapid improvement event), future-state value stream mapping and rapid experiments on real work.

What happens: Once root causes are clear, the team generates countermeasures, ranks them by impact and effort, and designs the future state. Then the important part: test before rolling out. A pilot runs the change on a small scale, in a single area or shift, while measuring the same baseline metrics. If results do not move, the team adjusts or goes back to root cause. A kaizen event is a common way to run this step, because a cross-functional team can test changes quickly on real work. Our guide on how to plan a Kaizen event shows what that looks like.

Who is involved: The process owner, a cross-functional pilot team and the consultants, with the sponsor reviewing whether to proceed after the pilot.

Typical duration: Agreed during scoping.

What you get: Ranked countermeasures, a future-state design and pilot results measured on the same baseline metrics.

6. Implementation and standard work

DMAIC: Improve. Lean tools often used: standard work, visual management and training for everyone who uses the process.

What happens: Changes that work in the pilot are scaled. This step includes writing standard work (the agreed, documented best method), updating forms, systems and layouts, and training everyone who uses the process, including people who were not in the pilot. Visual management, such as boards or signals that show whether work is on track, helps people see problems early.

Who is involved: The process owner, everyone who uses the process and the consultants.

Typical duration: Agreed during scoping.

What you get: Standard work, updated forms, systems or layouts as needed, visual management and training materials for the new process.

7. Control plan

DMAIC: Control. Lean tools often used: visual management, leader standard routines and scheduled reviews against the control plan.

What happens: A control plan describes how the gain will be held: which few measures to watch, how often, what level triggers action, and who responds. Many improvements fade because nobody checks. A simple control plan, reviewed on a regular schedule, is one of the most valuable things a consultant leaves behind. Sponsors and managers who will own those reviews often need leadership habits as well as process tools; programs such as Lean Leader are built for that role.

Who is involved: The sponsor, the process owner, the managers who will run the reviews and the consultants.

Typical duration: Agreed during scoping.

What you get: A control plan with named owners, review frequency and action triggers.

8. Handoff

DMAIC: Control. Lean tools often used: updated standard work, visual boards handed to the process owner, and a clear owner for each open action.

What happens: The engagement ends when your people can run the process and the controls without outside help. A proper handoff includes documentation, training for process owners, a final comparison with the baseline stated plainly, finance sign-off on any claimed savings and a list of next opportunities. It should also include any open actions, each with an owner and a due date.

Who is involved: The sponsor, the process owner, finance when savings were part of the goal and the consultants.

Typical duration: Agreed during scoping.

What you get: A complete handoff package: documentation, trained process owners, a before-and-after comparison on the same definitions, finance validation of claimed savings where savings were part of the goal and a short list of what to tackle next, with owners and due dates.

What you should have when it ends

  • A signed charter with scope and measures
  • A current-state map and a future-state design
  • Baseline data and a final before-and-after comparison on the same definitions
  • Documented root causes with the evidence behind them
  • Standard work and training materials for the new process
  • A control plan with named owners
  • Finance validation of claimed savings, where savings were part of the goal
  • A short list of what to tackle next

See how Work Stream structures a lean process optimization engagement on the process optimization and Lean Six Sigma consulting page.

Ready to talk through a process?

If you have a process in mind, request a scoping call and we will help you judge whether a full engagement is the right fit.

Request a scoping call

Signs of a good engagement, and warning signs

Good signs: your frontline staff are involved from the start; the consultant spends time at the gemba; targets are measurable; pilots happen before rollout; and the handoff is planned from day one.

Warning signs: a solution is announced before the data is collected; the consultant works mostly away from the process; results are described but never measured against a baseline; or nobody on your side owns the outcome.

Questions to ask before you sign

  1. How will you decide what is in and out of scope?
  2. What data will you collect, and how will you verify it?
  3. How will my team be involved, and how much of their time will it take?
  4. How will changes be tested before full rollout?
  5. What exactly will we receive at each step?
  6. How will you train our people so we can sustain the results?
  7. What happens if the pilot does not hit the target?
  8. Who validates the financial results?

Bring these questions to a scoping call

Use the list above when you compare proposals, or request a scoping call and we can walk through them with you.

Request a scoping call

Consulting, on-demand support or training?

The right model depends on what you need. A full engagement suits a defined problem that needs structure and outside expertise. On-demand support suits a gap, such as a backlog, a stalled initiative or an open improvement role. Training suits organizations that want to build their own capability, and many engagements include some of it. For people who will plan and lead events, see the Kaizen Facilitator training program. For a flexible model, see on-demand process improvement consulting. For team capability, see our group and on-site training options.

How Work Stream approaches it

Work Stream’s process optimization and Lean Six Sigma consulting follows the three stages in the diagram above: assessment, improvement and sustainment.

Master Black Belts lead the work on site, remotely or as a mix, depending on the engagement. Some engagements are hands-on improvement work, some are training and some are an outside review. When training is part of the work, your people learn the tools by using them on a real process. Timing depends on scope and is agreed at the start. Engagements have ranged from 2 weeks to 10 years, depending on the client’s needs.

To talk through your situation, request a scoping call or review the industries we have worked with.

Frequently asked questions

How long does a process optimization engagement take?

It depends on the scope and complexity of the process, how many processes are involved and how available your people are. Work Stream engagements have ranged from 2 weeks to 10 years, depending on the client’s needs. A good consultant sets the scope first and agrees the timeline with you before improvement work begins.

What if our data is poor?

That is common, and it should not stop the work. If measures are missing, incomplete or defined inconsistently, the team agrees on clear definitions and collects data manually, often at the gemba, for long enough to establish a reliable baseline. The same definitions are then used to judge the result. Be wary of a consultant who promises savings before the measures are agreed.

Can this be done remotely?

Yes. Work can be on site, remote or a mix, depending on the process and the client’s needs. Mapping and observation are stronger when someone can see the real work, so even a largely remote engagement usually includes some time at the gemba, in person or through structured observation with your team.

What does my sponsor actually have to do?

The sponsor helps set scope, removes barriers, makes time for the people who run the process and reviews progress at agreed points, including after the pilot and at handoff. The sponsor does not have to attend every working session. They do need to be available for key decisions and to own the reviews that hold the gain after the consultants leave.

What should I prepare before hiring a process optimization consultant?

Name a sponsor and a process owner, write a short problem statement, gather any existing data on the problem and identify who can be released to work with the consultants. Know what success would look like in measurable terms.

How do I make sure improvements last after the consultants leave?

Ask for standard work, training for everyone who uses the process, a control plan with named owners, finance sign-off on claimed savings where savings were part of the goal and a scheduled review of results against the baseline. Sustainment should be planned from the start, not added at the end.

Inquire Now

Lean Six Sigma