Lean Consulting

Lean operations consulting, defined

Lean operations consulting is the discipline of redesigning how work flows through an organization so that waste, queue time, and handoffs collapse, capacity frees up, and the gains hold past the consultant’s exit. It is built on the Toyota Production System lineage and adapted to modern operations: claims, healthcare service lines, financial close, software delivery, plant floors. Rockmere’s Lean operations consulting practice installs the management system that holds the gains, not just the kaizen events that produce them. By the time we exit, your operators and your managers run the system, the value stream map gets updated every quarter, and the OEE or cycle-time numbers stay where we left them.

The pattern that brings clients to us is improvement fatigue. You have run kaizen events. You have trained Belts. You have watched gains drift back inside a year. The diagnosis is almost always the same. The management system did not change.

Value stream first, kaizen second

A Lean engagement that opens with kaizen events fixes symptoms. We open with current-state and future-state value stream mapping. Mapped against measured cycle time, queue time, first-pass yield, and the handoff count. Then we sequence the improvements by impact on flow, not by who shouted loudest in the planning room.

A typical engagement opens with a two-week diagnostic on the target value stream. Our practitioners walk the gemba. We time the cycles. We count the handoffs. We observe a full shift, or its equivalent in a service operation. Picture a Tuesday at 6am in a claims center: one of our practitioners is standing behind a tenured adjuster, stopwatch in hand, counting screens. That is the start. The output is a current-state value stream map with measured cycle times, queue times, and quality losses, plus a future-state map showing what the operation can become and the sequence to get there.

The first 30 days target the largest queue or rework loop the value stream map identifies. We install daily standard work. We stand up the first tier huddle. We install visual management for the target process. We run one or two focused kaizen events on items the value stream map identifies as the constraints with the largest return. Months two through four build the rest of the management system. By month five we are coaching managers on their own improvement cycles, not running them. By month six we have certified internal practitioners and we begin our exit.

The management system is the deliverable

Improvements drift back when the management system stays the same. We install tier 1 through tier 4 huddles with KPI boards, escalation protocols, and standard work for leaders at every layer. Tier 1 is the team huddle on the floor or in the open-plan. Tier 2 is the value stream lead. Tier 3 is the operations leader. Tier 4 is the executive operating review. Each tier has a defined cadence, a defined board, and a defined set of standard problems that escalate up the chain.

Standard work for leaders is the artifact that holds the system together. A manager’s day is structured around gemba walks, board reviews, and coaching cycles, not around firefighting. Daily management gets paired with Hoshin Kanri for the annual strategy deployment, so the value stream improvements ladder up to the executive priorities your board is reading about. The management system is the deliverable. The events are just one input.

Lean for knowledge work

Lean for knowledge work applies the same principles (flow, pull, waste elimination, respect for people) to office and service processes rather than factory lines. We apply them to claims processing, software delivery, the financial close, payroll, the call center, and the underwriting desk. The principles transfer. The artifacts adapt. A claims operation does not run andon cords; it runs an escalation board with a defined threshold for raising a problem. The financial close does not run takt time; it runs a daily standard work schedule against the close calendar, with the same surface-the-problem discipline as a plant tier huddle.

Knowledge-work Lean engagements pair well with Agile coaching where the work is software delivery, and with AI Transformation where the waste is information-handling and the flow can be cut by a well-scoped AI assistant. We have run all three combinations.

How we differ from Lean Six Sigma engagements

Lean and Six Sigma solve different problems: Lean targets flow and waste, while Six Sigma targets variation and defects. We use Six Sigma where statistical rigor matters, like defect reduction in a regulated process where you need DPMO inside a contractual ceiling. For flow problems, Six Sigma is the wrong tool. A DMAIC project takes months to deliver a fix that a properly mapped value stream and a sequenced kaizen would have produced in weeks. We pick the tool to fit the constraint, not the certificate. Our practitioners hold Lean Black Belt and Master Black Belt credentials where they earned them, but the engagement starts with the value stream map, not with the project charter.

The same logic applies to the consultants. We do not staff Lean engagements with classroom-only Black Belts. Our team has run plants, claims operations, distribution centers, and financial close operations themselves. They have stood at the andon. They can walk the floor and show you the waste. The senior practitioners are named in the SOW and they stay until the management system holds.

A note on tools. We use the Toyota Production System lineage as the spine: 5S, standard work, just-in-time, jidoka, kaizen. We add A3 problem solving for the structured root-cause cycles, Theory of Constraints where the value stream has a hard bottleneck, and Hoshin Kanri for the annual strategy deployment that ties value-stream improvements to executive priorities. Where a regulated process needs statistical rigor, Lean Six Sigma’s DMAIC tooling enters the engagement, but only on items the value stream map identified as warranting it. The toolset adapts to the constraint. The discipline does not.

Where Lean pays off

Lean fits when the work is operational, repeatable, and has measurable flow. The use cases we deliver most often:

• Insurance operations. Claims processing, underwriting throughput, policyholder service. We have cut claims cycle time 30 to 50 percent inside Insurance carriers without headcount reduction.
• Healthcare service lines. Lab, imaging, ED throughput, OR turnover, revenue cycle. Cycle time and patient flow improvements that survive Joint Commission review. See our Healthcare practice.
• Manufacturing. OEE improvement, line balancing, changeover reduction, supply chain flow. The Automotive Supplier OEE engagement moved OEE eleven points in 90 days inside an existing Lean program that had stalled.
• Financial services back office. Financial close, payroll, AP and AR, reconciliations. Knowledge-work value stream mapping with measurable cycle-time impact.
• Software delivery release operations. Where flow metrics (lead time, deployment frequency, change-failure rate) are the target and Agile alone has not moved them.

Case studies

Two engagements anchor the practice. The Automotive Supplier OEE engagement moved a stalled OEE program eleven points in 90 days by installing tier huddles and standard work the plant manager owned by exit. The plant had run two prior CI programs that drifted; the difference this time was the management system. Tier 1 huddles at shift change. Tier 2 every morning on the value stream board. Tier 3 weekly with the plant manager. Leader standard work that put the operations team on the floor for two hours daily. The OEE numbers held twelve months past our exit because the system that produced them held.

A CPG demand-planning engagement paired Lean with a forecasting model and freed $40 million of working capital while cutting MAPE by eleven points across the planning cycle. The Lean work mapped the planning value stream, removed twelve queue points, and put a tier huddle around the weekly S&OP. The forecasting model carried the demand signal; the management system carried the response. Both started with a value stream map. Neither finished without a management system the client operates today.

What we will not do

We will not run kaizen theater. If you want a week of events with no tier huddle install, no leader standard work, and no plan for who runs the system on Monday morning, we will pass. The gains evaporate by quarter two and we would rather not be the firm whose name was on the slide. We will not promise a headcount reduction. Lean targets capacity, not headcount. If headcount reduction is the goal we will say Lean is not what you are hiring for.

What success looks like at exit

By the end of a Lean operations consulting engagement the target value stream runs with measurably faster cycle time and freed capacity. A management system surfaces problems daily, not quarterly. Standard work is installed for both operators and managers. An internal practitioner team holds Lean credentials and runs the next improvement cycles without us. An operating playbook documents how the management system works so it survives leadership turnover. The OEE, cycle-time, and capacity numbers stay where we left them, and the gains compound rather than drift.

A 12-month re-engagement check is standard practice. We come back, walk the value stream, audit the tier huddles, and produce a one-page report on whether the management system has held. The re-engagement check is free; the report is the client’s. The reason we do it is not nostalgia. It is that the only honest measure of a Lean engagement is whether the gains held after the consultants left.

Frequently asked

Who it's for

Our approach

Outcomes you can measure

• 30–50% cycle-time reduction in the target value stream
• 15–25% capacity freed up without new headcount
• < 5% of improvements drift back within 12 months (industry baseline is roughly 70%)

What you leave with

• Current-state and future-state value stream maps
• Prioritized improvement backlog with quantified business cases
• Standard work for operators and for managers
• Tier huddle cadence (1 through 4) with KPI boards and escalation protocols
• Visual management installation (boards, andon, run-the-business dashboards)
• Operational excellence playbook for sustaining the management system