Assess Lean Manufacturing Readiness Before You Launch

Start a Lean pilot when the team can name a real customer or process problem, observe the work, protect required safety and quality controls, and review evidence after the change. A general goal such as “reduce waste” is not a project brief. Use this readiness assessment to decide whether to start a bounded pilot, clear a specific blocker first, or choose a different process. It is a decision aid, not a Lean certification or a promise of savings.

The previous company-story framing did not identify a traceable organization or source for its implied outcomes. This article does not claim that an unnamed company completed a transformation. Instead, it gives you a practical readiness check and shows how to evaluate published case claims without extending them beyond their evidence.

Define the pilot before scoring readiness

State the problem in one sentence that names the process, the affected customer or next operation, and the condition that needs attention. For example: “The enclosure cell misses the agreed daily completion sequence when inspection-ready jobs wait for a final drawing check.” This is a problem statement to investigate, not a finding. It points the team toward a process boundary, a measure, and the people who can verify the facts.

Define the pilot’s start and end events. An order-release-to-shipment measure is different from time spent inside one work cell. Identify the product family or transaction, the shift or operating calendar, the responsible process owner, and the required approvals. Keep the first pilot small enough to observe directly and broad enough to include the handoffs that create the problem.

Before work starts, identify which decisions the pilot team can make. A team may adjust a visual handoff or test a schedule within its authority. It may not change a controlled process parameter, inspection, safety control, customer requirement, or released design without the required approval. The readiness review should expose those decision boundaries before a trial begins.

Use evidence gates, not an average score

Rate each area green, yellow, or red and attach evidence. Do not convert the colors into a single average. A red safety or authority blocker cannot be offset by green marks in training, staffing, and baseline collection. A yellow item needs an owner and due date; a red item needs a decision about whether the pilot must wait or change scope.

Lean pilot readiness check: record the evidence and the next decision for each gate

Readiness gate	Evidence to inspect	Green condition	If yellow or red	Owner
Customer or downstream need	Order, delivery, quality, service, or internal handoff records	A specific unmet need and affected recipient are identified	Clarify who receives the work and what requirement is not being met	Process owner with customer-facing role
Process boundary	Observed route, start and finish events, product family, handoffs	The team can follow one representative work unit end to end	Narrow the family or include the missing upstream/downstream handoff	Improvement lead and operator
Baseline	Consistent records for lead time, WIP, defects, rework, delivery, or another defined measure	Definition, unit, sample, dates, and data owner are recorded	Collect a short baseline before setting a numeric target	Measure owner
Stable and safe work	Current instructions, equipment condition, risk controls, material availability	Required safeguards are in place and the work can be observed safely	Resolve safety or basic-stability issues through their responsible owners	Supervisor with safety and maintenance as needed
People and skills	Operators, supervisor, quality, maintenance, engineering, planning, and relevant supplier roles	Affected people can participate and required skills are available	Secure release time, training, or qualified coverage before the test	Department manager
Authority and change control	Approval matrix, customer requirements, document revisions, escalation route	The team knows who may approve each proposed change	Ask the authorized owner to approve, narrow, or reject the test	Process owner and required approver
Follow-through	Named action owner, review time, stop rule, and standard-update process	The team can study the result and close or revise the change	Assign follow-up and escalation before launching the trial	Sponsor or supervisor

Use the colors to plan work, not to judge employees. A yellow baseline gate may need five days of consistent measurement. A red equipment condition may require maintenance before a flow experiment is safe. A customer-requirement gate may require a decision from sales or engineering. Each color should explain a condition and a next action.

Check published cases claim by claim

A named case can provide useful evidence, but the source supports only the details it reports. NIST’s Manufacturing Extension Partnership (MEP) profile for Sagewood Gear identifies the company, describes its small Duluth operation, and reports that its adviser used value-stream mapping to examine processes and value streams. The page describes layout and product decisions, and it lists business outcomes. It does not provide a full before-and-after data table, a consistent measurement period for every listed outcome, or enough detail to predict the same result elsewhere.

A second NIST MEP profile for Fiberglass Unlimited describes a custom-build manufacturer that sought support after an acquisition. The source reports employee training, visual controls, 5S, load balancing, and changes to manufacturing and logistics processes. It also lists financial and employment results, but does not define every denominator or the measurement window beside each figure. Those facts can be attributed to the NIST page; they should not be rewritten as universal expected returns.

Evidence ledger: what named NIST MEP cases support and what they do not establish

Case and assertion	What the source reports	What is missing or limited	Safe use in your assessment
Sagewood Gear: value-stream work	NIST MEP names the manufacturer and adviser, describes mapping key processes, and lists layout and product decisions	The page does not publish the full map, observation sample, or comparable baseline and follow-up measures for every result	Use it as an attributed example that a small manufacturer used outside expertise and value-stream thinking; do not claim the same design or result fits your plant
Sagewood Gear: listed business results	The page lists retained sales, increased sales, jobs, investment, and cost savings	Several figures have no visible calculation, measurement window, or denominator on the page	Attribute each figure to the NIST MEP case page and disclose the missing method; do not calculate an unsupported percentage
Fiberglass Unlimited: process work	NIST MEP describes training, visual controls, 5S, load balancing, and manufacturing/logistics reorganization after an acquisition	The page does not isolate the contribution of each intervention or show a controlled comparison	Use the sequence as a reported case description, not as proof that each tool caused each result
Fiberglass Unlimited: financial results	The page lists retained sales, new jobs, plant/equipment investment, cost savings, and avoided investment	The page does not define all calculation methods or periods next to those listed results	Quote or summarize only with direct attribution and stated limitations; keep them separate from a local pilot forecast

This ledger is a model for source checking. Before repeating any case claim, save the original source, identify the speaker or publisher, record its date, and match the claim to a specific passage or data point. If the source is an interview or program summary, say who reports the result. Do not add a company name, quotation, before-state, date, or cause that the source does not provide.

Build a measurable pilot plan

A readiness review should end with one of three decisions: start the bounded pilot, clear named blockers and return on a set date, or select another process. The pilot plan should include one outcome measure, two or more guardrails, a baseline period, a test owner, and a review date. If the team cannot measure the result consistently, narrow the question or improve the data before changing the work.

For example, a machining team might define the outcome as elapsed hours from a complete job packet to inspection-ready output for one part family. It could monitor first-pass acceptance and safety exceptions as guardrails. Those measure names are only an example: the team must use the site’s approved inspection definition and data rules. A faster completion measure is not useful if the part fails inspection or the operator bypasses a required control.

When a percentage is appropriate, show the formula and denominator. If a fictional process completed 40 of 50 jobs on time before a test and 44 of 50 afterward, the on-time rates would be 80% and 88%. The difference is 8 percentage points; the relative increase is 10% because (88% − 80%) ÷ 80% = 10%. These invented values do not describe a plant result. A real comparison also needs dates, comparable work mix, exclusions, and sample counts.

Use a 90-day path with decision gates

A 90-day plan is a planning framework, not a promised schedule. Extend it when the process requires more baseline observations, approvals, supplier coordination, or safe equipment changes. The sponsor should check progress against evidence and blockers rather than declaring success because a calendar date has arrived.

Example 90-day Lean pilot sequence with review gates

Period	Work	Evidence produced	Decision gate
Days 1–15: define	Choose one problem and process family; confirm recipient, start/end events, owner, and approval path	One-page problem statement, route sketch, risk and authority check	Do the affected people agree that this is the right problem and scope?
Days 16–30: observe	Walk the process, collect a consistent baseline, document variation and interruptions	Current-state map, data definitions, sample size, and evidence gaps	Can the team measure the current condition safely and consistently?
Days 31–45: prepare	Develop a small test, review risks, set guardrails, train affected roles, obtain required approval	Test plan, controlled instructions, responsibility list, and stop rule	Is the test authorized and reversible within the team’s scope?
Days 46–75: test and study	Run the bounded change, record observations, defects, disruptions, and unexpected effects	Time-ordered measurements and issue/action log	Does evidence support keeping, changing, or stopping the test?
Days 76–90: decide and follow up	Review outcomes with affected roles; update or restore the standard through the approved route	Decision record, updated document or rollback, and follow-up owner	Is there enough evidence to standardize, extend, or abandon the change?

Do not proceed through a gate because a sponsor expects a favorable number. A “pause and prepare” decision is useful when the baseline is weak, a required approver is unavailable, or a safety condition is unresolved. Record the blocker and the person who can clear it.

Choose a response for each readiness result

Start when the need, process boundary, baseline, authority, safeguards, and follow-up are clear enough for a limited test. Prepare when one or more gaps have an owner and a realistic due date. Pause when a safety or quality control is missing, the team lacks authority, or the work cannot be measured without changing the definition midstream. Redirect when the problem is not a Lean process question or another team owns the required decision.

Recheck only the evidence that changed. If equipment is repaired, confirm its condition and the authorized release. If the customer changes the schedule, update the baseline context. If a new product or revision changes the route, verify whether the pilot still represents the same process. Readiness is specific to the proposed test, not a permanent label for the factory.

Know when to narrow or stop

Do not launch a flow experiment to compensate for an unstable or unsafe process. Resolve equipment faults, missing required materials, unclear approved instructions, or unqualified work through the responsible owner first. Do not use an average readiness score to hide a critical red condition. Do not call an event successful when the team has not checked quality, safety, customer need, or follow-up.

Small samples can produce noisy results. If only a few orders ran during the pilot, describe the count and work mix and continue observing before claiming a lasting effect. If demand changed, staffing changed, or a new machine entered service, report that context. If the test failed, record what the team learned and whether it restored the previous approved method.

For a staged implementation sequence, see the Lean implementation guide. After the team has defined the problem, use the Lean tool selection guide to compare methods.

Start the readiness review

1. Name the process, product family, customer or downstream need, and process owner.
2. Define the start event, finish event, unit, and baseline period.
3. Walk the actual work with operators and required support roles.
4. Check safety, quality, document control, skills, capacity, and decision authority.
5. Mark each gate green, yellow, or red and attach evidence.
6. Assign owners and due dates to every blocker.
7. Approve a small test only after its measures, guardrails, review date, and stop rule are clear.

Record the first observed condition and the owner responsible for the next decision. That gives the team a traceable reason to start, prepare, pause, or redirect.

Sources

• Lean Enterprise Institute: Kaizen — supports defining the current condition, checking results, and following up on a demonstrated improvement.
• Lean Enterprise Institute: Standardized Work — explains the role of current work sequence and a baseline in process improvement.
• NIST MEP: Huge Value in Value Stream Mapping — Sagewood Gear — named small-manufacturer case used in the evidence ledger.
• NIST MEP: Lean Tools Lead to New Investments and Retained Sales — Fiberglass Unlimited — named case used in the evidence ledger; listed financial results are not presented as local expectations.