John R. Loftis

Category: Continuous Improvement

  • Moving from Lean Training to Measurable Operational Results

    Moving from Lean Training to Measurable Operational Results

    Many organizations have trained dozens—or even hundreds—of employees in Lean methods and still struggle to show a meaningful operational return.

    People know the language. They can identify the eight wastes, build a process map, participate in a Kaizen event, and explain the basics of root-cause analysis. Certificates appear on office walls. Training completion looks impressive on a dashboard.

    Yet lead times remain long, recurring problems return, improvement ideas wait for decisions, and business leaders continue asking a reasonable question: What results did the training produce?

    The problem is rarely that Lean concepts have no value. The problem is that training was treated as the outcome rather than as preparation for better work. Knowledge becomes operational value only when people apply it to important problems, leaders remove barriers, and the organization measures whether performance actually improves.

    Training Is an Input, Not a Business Result

    Training can build vocabulary, confidence, and basic capability. It cannot, by itself, reduce defects, release capacity, improve delivery, or lower working capital. Those outcomes require changes to processes and management behavior.

    This distinction sounds obvious, but many improvement programs blur it. Their scorecards track:

    • Employees trained
    • Green Belts or facilitators certified
    • Kaizen events completed
    • Ideas submitted
    • Hours spent in workshops

    These are activity measures. They can help leaders understand whether capability-building work is occurring, but they do not prove that operations are better. A stronger system connects learning to measures such as yield, schedule adherence, changeover time, customer complaints, inventory, cost, safety risk, or decision speed.

    The purpose of Lean training is not to create people who can describe tools. It is to help people recognize problems, improve processes, and sustain better results.

    Why Lean Training Often Fails to Transfer

    Several predictable gaps prevent classroom learning from becoming measurable performance.

    The training is disconnected from business priorities

    Generic examples make concepts easier to teach, but learners often return to work without a clear connection between the method and the problems leadership needs solved. If the site is struggling with yield, service, or capacity, training should help participants work on those priorities—not on hypothetical processes with no operational consequence.

    Employees lack an immediate application

    Skills decay when they are not used. Someone who learns value-stream mapping but waits six months to facilitate a mapping session will need to relearn much of the method. Application should begin during or immediately after training, with a real problem and a named sponsor.

    Managers do not change their routines

    Employees may learn to expose waste and surface root causes, but their managers may continue rewarding firefighting, issuing solutions without investigation, or postponing decisions. If daily leadership behavior conflicts with the training, the management system wins.

    Projects are selected for convenience

    Certification programs sometimes encourage participants to choose projects that are easy to complete rather than important to the business. This produces completed templates and modest local wins, but little executive confidence in the improvement system.

    Benefits are declared but not verified

    A team may estimate savings from reduced labor time, scrap, or downtime without establishing a baseline or checking whether the gain appears in operating performance. When every project claims benefits but the financial and operational results remain unchanged, credibility erodes.

    A Five-Part System for Turning Learning into Results

    Organizations can close these gaps by managing Lean development as a performance system rather than a series of classes.

    1. Begin with the performance gap

    Before scheduling training, identify the operational gaps the organization must address. Examples include unstable output, excessive changeover time, recurring deviations, poor schedule attainment, long approval cycles, or high material loss.

    Then determine which skills are needed to address those gaps. A visible flow problem may call for observation, standard work, and Kaizen capability. A chronic variation problem may require measurement-system review and statistical analysis. Training should follow the problem portfolio.

    2. Pair every learner with a real application

    Each participant should have an opportunity to apply the new skill to a defined problem. The application does not need to be a large project. It does need a clear owner, baseline, target, scope, and review date.

    For example, a supervisor learning standard work might improve a daily line-start process. An engineer learning problem-solving might lead analysis of a recurring minor stoppage. A manager learning visual management might redesign a tier meeting around exceptions and decisions.

    This changes the question from “Did the employee complete the course?” to “Can the employee use the method effectively on real work?”

    3. Provide coaching at the point of use

    Classroom understanding is not the same as independent competence. People need coaching while defining problems, collecting data, testing causes, facilitating discussions, and building controls.

    Coaches should challenge the quality of the thinking, not complete the work for the learner. Useful questions include:

    • What evidence shows that this is the real problem?
    • How was the baseline established?
    • Which assumptions have not been tested?
    • Who must help design and sustain the change?
    • What measure will confirm that the result lasts?

    4. Integrate improvement into leadership routines

    Lean capability grows when leaders repeatedly ask about problems, evidence, ownership, barriers, and follow-through. Project reviews should be part of normal operating reviews, not separate events attended only by improvement specialists.

    Leaders also need to act. If a team has waited three weeks for a maintenance window, a data extract, or a cross-functional decision, more training will not help. Leadership must create the conditions in which trained employees can succeed.

    5. Measure transfer, results, and sustainment

    A useful measurement system has three levels:

    1. Capability: Can the learner demonstrate the method on real work?
    2. Operational result: Did the target measure improve against a credible baseline?
    3. Sustainment: Is the result still present after 30, 60, or 90 days, with ownership and controls in place?

    Financial benefits should be classified carefully. Cost avoidance, released capacity, productivity improvement, and budget reduction are not interchangeable. Operations and finance should agree on benefit definitions before projects begin.

    An Anonymized Manufacturing Example

    Consider a manufacturing operation that trained supervisors and technical staff in Lean fundamentals. Initial enthusiasm was high, but six months later the program could point only to workshop attendance and several small workplace-organization improvements.

    Leadership changed the approach. Instead of offering another broad training wave, the site identified three operational priorities: lengthy product changeovers, repeated line-start delays, and avoidable material loss. Participants were assigned to small teams aligned with those priorities, and each team received coaching during weekly project reviews.

    The changeover team separated work that required stopped equipment from preparation that could happen in advance. The line-start team clarified readiness criteria and ownership across production, quality, and materials. The material-loss team improved measurement and discovered that one assumed cause did not explain the variation.

    Not every idea worked, and not every benefit became a direct cost reduction. But the site could now connect training to verified changes in time, reliability, and loss. More importantly, supervisors began using the same problem-solving habits in daily work.

    The breakthrough was not a new Lean tool. It was a stronger connection among business priorities, real applications, coaching, management attention, and results.

    Common Implementation Risks

    • Overloading learners: Assigning a project without protecting time makes improvement an after-hours responsibility.
    • Forcing every problem into one method: Simple issues need less structure than chronic, high-risk problems.
    • Counting unverified savings: Inflated claims damage trust faster than modest, credible results build it.
    • Ignoring frontline ownership: Changes designed around operators rather than with them are difficult to sustain.
    • Ending support at certification: Capability develops through repeated application, reflection, and coaching.

    A Practical Scorecard

    Executives do not need dozens of improvement-program metrics. A concise scorecard can answer five questions:

    • What percentage of trained employees applied the skill within 30 days?
    • How many active applications address a stated business priority?
    • What operational measures improved against an agreed baseline?
    • Which benefits were verified by the appropriate functional owner?
    • What percentage of completed improvements sustained their result at the follow-up review?

    Training completion still matters, but it belongs at the beginning of the chain—not at the end.

    Lean training creates potential. A management system converts that potential into operating performance.

  • Just-Do-It vs DMAIC: When to Use Each Method

    Just-Do-It vs DMAIC: When to Use Each Method

    Improvement teams often make one of two mistakes. They use a complex method for a simple problem, or they rush into action when the problem requires deeper analysis.

    A loose guard needs repair, but someone proposes a full DMAIC project. A recurring yield loss affects several products, but the team schedules a one-day Kaizen event. A leader asks for an A3 because it is the standard template, even though the solution is already known and low risk.

    The method becomes the focus instead of the problem.

    Kaizen, DMAIC, A3, and Just-Do-It are not competing brands. They are different levels of structure for different types of problems. Choosing well improves speed, preserves rigor where it matters, and prevents teams from wasting energy on unnecessary process.

    Start with the Problem, Not the Preferred Tool

    Organizations often default to the method their internal experts know best. Lean teams may favor Kaizen. Six Sigma practitioners may prefer DMAIC. Some companies require A3s for almost every improvement. Frontline teams may simply implement the first practical idea.

    Each approach can work, but no single method fits every situation. The choice should reflect six characteristics:

    • How clearly the problem is defined
    • Whether the cause is known
    • Whether the solution is known
    • The level of risk and reversibility
    • The number of functions involved
    • The amount of data and analysis required

    A good rule is to use the lightest method that provides enough discipline to manage the problem safely and sustainably.

    Just-Do-It: When the Solution Is Clear and Low Risk

    A Just-Do-It improvement is a small, straightforward change with a known cause, an obvious solution, limited scope, and low implementation risk. It should not require a project team or extensive analysis.

    Examples might include replacing a damaged label holder, relocating a commonly used tool, clarifying a visual signal, correcting an outdated contact list, or changing the location of a non-controlled supply.

    Use Just-Do-It when:

    • The problem and cause are directly observable.
    • The solution is known and affordable.
    • The change is easy to reverse if it does not work.
    • Quality, safety, regulatory, technical, and customer risks are low.
    • One person or local team can implement and confirm the result.

    Simple does not mean uncontrolled. The owner should still check whether procedures, training, drawings, or approvals are affected. The change should also be documented enough that the organization does not repeatedly rediscover the same issue.

    Kaizen: When a Focused Team Can Improve a Process Quickly

    Kaizen means improvement. In practice, a Kaizen event is a focused, time-bound effort in which people who understand the work analyze a process, test changes, and establish a better method.

    It is useful when the problem is visible, the process can be observed, and rapid cross-functional collaboration can produce meaningful change. Common applications include reducing changeover time, improving workplace organization, simplifying material flow, improving line readiness, or removing delays in an administrative process.

    Use Kaizen when:

    • The process and boundaries are clear.
    • Waste, delay, motion, handoffs, or flow problems are visible.
    • The people doing the work can participate directly.
    • Changes can be tested within days.
    • Leadership can make timely decisions and provide resources.

    Kaizen is less suitable when root causes are uncertain, data must be collected over long periods, or the solution requires major capital, validation, or system redesign. An event can identify next steps, but it should not create false confidence that a complex problem has been solved in three days.

    A3: When the Team Needs Structured Thinking and Alignment

    A3 problem-solving uses a concise document—traditionally one large sheet—to tell the story of a problem, analysis, proposed response, implementation, and follow-up. Its real value is not the paper size. It is the thinking and dialogue required to build a logical case.

    A3 is especially useful for management and cross-functional problems where alignment matters as much as technical analysis. It can support issues such as schedule adherence, recurring escalation failures, unclear ownership, inconsistent training, or a process that crosses several departments.

    Use A3 when:

    • The problem needs clearer definition and shared understanding.
    • Several stakeholders must agree on causes and countermeasures.
    • The analysis is meaningful but not statistically complex.
    • The team needs a concise record of decisions and learning.
    • Coaching the problem-solving process is an important objective.

    An A3 should not become a form completed after decisions have already been made. Leaders should use it to ask questions, test logic, and make assumptions visible.

    DMAIC: When Causes Are Uncertain and Data Must Lead

    DMAIC stands for Define, Measure, Analyze, Improve, and Control. It is a structured Six Sigma method for problems where performance is measurable, causes are uncertain, and disciplined analysis is required.

    DMAIC is appropriate for chronic variation, recurring defects, yield losses, reliability problems, or process relationships that cannot be understood through observation alone. The method helps teams separate symptoms from causes, test evidence, and build controls that sustain the result.

    Use DMAIC when:

    • The problem is significant and recurring.
    • The output and process can be measured.
    • The root causes are not known or are disputed.
    • Several possible variables may influence the result.
    • The cost of a wrong solution is high.
    • The organization can support data collection and analysis.

    DMAIC should not be selected simply because a certified practitioner is available. It requires time, reliable data, process access, and committed sponsorship. If the cause and safe solution are already known, DMAIC may delay action without adding value.

    A Simple Selection Guide

    Leaders can use the following sequence before assigning a method:

    1. Is the solution already known, low risk, and locally controlled? Use Just-Do-It.
    2. Is the process visible, the scope focused, and rapid team experimentation practical? Use Kaizen.
    3. Does the issue require structured thinking, cross-functional alignment, and a concise management story? Use A3.
    4. Are causes uncertain, variation important, and data analysis essential? Use DMAIC.

    These boundaries are not absolute. A Kaizen event may use an A3 to document its reasoning. DMAIC may include focused Kaizen activity during the Improve phase. A Just-Do-It action may become part of an A3 countermeasure plan.

    The objective is not methodological purity. It is enough structure to reach a credible, safe, and sustainable result.

    An Example: Four Problems, Four Different Responses

    Consider a manufacturing site reviewing four improvement opportunities.

    First, operators repeatedly walk across the area to retrieve a non-controlled cleaning tool. The cause and solution are obvious, risk is low, and the local supervisor can confirm the new location. This is a Just-Do-It improvement.

    Second, changeovers include excessive searching, waiting, and internal setup work. The steps are observable, operators and support functions can participate, and changes can be tested during scheduled runs. This is a strong Kaizen candidate.

    Third, production schedules change frequently because sales, planning, operations, and quality use different assumptions. The problem requires shared facts, clearer decision rules, and stakeholder alignment. An A3 provides an effective structure.

    Fourth, a product family shows inconsistent yield, but the team cannot agree whether material properties, equipment settings, environmental conditions, or operator practices are responsible. The issue is measurable, significant, and analytically complex. DMAIC is appropriate.

    Treating all four problems with the same method would either create unnecessary work or insufficient rigor.

    Common Selection Mistakes

    • Choosing a method before defining the problem
    • Using DMAIC to add prestige to a simple fix
    • Using a Kaizen event when necessary data cannot be collected during the event
    • Using an A3 as a reporting template rather than a thinking process
    • Calling a risky or cross-functional change “Just-Do-It” to avoid governance
    • Failing to define ownership, measures, and sustainment regardless of method

    Three Actions to Begin

    1. Define the problem first. State the gap, scope, baseline, and business impact without proposing a solution.
    2. Assess uncertainty and risk. Ask whether the cause and solution are known, what evidence is needed, and what happens if the change is wrong.
    3. Match support to the method. Give simple problems fast decisions and complex problems the data, expertise, sponsorship, and time they require.

    The best improvement method is not the most sophisticated one. It is the simplest method that can solve the problem responsibly and sustain the result.

  • How to Build an Improvement Portfolio Instead of Chasing Isolated Projects

    How to Build an Improvement Portfolio Instead of Chasing Isolated Projects

    Many organizations do not suffer from a shortage of improvement ideas. They suffer from too many ideas competing for the same people, time, and attention.

    A quality team wants to reduce recurring deviations. Operations wants more capacity. Supply chain wants better schedule stability. Engineering proposes equipment upgrades. Finance wants cost savings. Each project may be reasonable on its own, yet the combined workload can exceed what the organization can execute.

    The result is a familiar pattern: projects start enthusiastically, progress slows, resources shift, and expected benefits remain difficult to verify. Leaders continue approving new work because every request appears important.

    The solution is not a better list. It is an improvement portfolio—a governed set of projects selected and balanced to advance strategy, control risk, and match available capacity.

    The Cost of Managing Projects in Isolation

    When projects are evaluated one at a time, leaders rarely see their combined demands. Two projects may need the same process engineer. Several may require validation support during the same month. A capital installation may compete with a major product launch for maintenance and operations resources.

    Isolated decisions create four problems:

    • Strategic dilution: Resources spread across work with weak connections to the most important business outcomes.
    • Hidden overload: The same specialists and leaders appear on more projects than they can realistically support.
    • Slow completion: Too much work in process increases waiting, handoffs, and schedule changes.
    • Unclear value: Activity is reported, but leaders cannot compare expected and realized benefits across the full set of projects.

    A portfolio view changes the question from “Is this a good project?” to “Is this one of the best uses of our limited improvement capacity right now?”

    What Belongs in an Improvement Portfolio

    An improvement portfolio should include meaningful work that requires shared resources, leadership attention, or coordinated governance. It does not need to capture every local action.

    A useful portfolio often contains four types of work:

    1. Strategic growth and capacity projects that enable revenue, service, or expansion.
    2. Risk and compliance projects that protect patients, customers, employees, products, or regulatory commitments.
    3. Performance improvement projects that strengthen quality, delivery, cost, yield, reliability, or productivity.
    4. Capability projects that improve systems, skills, data, standard work, or management practices.

    Local teams should still solve routine problems. The portfolio is for work significant enough that leadership must make tradeoffs.

    A Practical Process for Building the Portfolio

    1. Start with business priorities and operating risks

    Begin with the outcomes the organization must achieve over the next 6 to 18 months. These may include creating dependable capacity, improving customer service, reducing quality risk, supporting a product transfer, or improving cash flow.

    Translate each outcome into operational gaps. If the business needs growth, the relevant gaps might include constraint capacity, staffing readiness, supplier reliability, or launch capability. If the priority is quality, the gaps might include recurring deviations, right-first-time performance, or weak corrective-action effectiveness.

    This translation makes project selection more disciplined. Ideas are judged by their contribution to a defined need rather than by who presents them most persuasively.

    2. Create a common project intake

    Every proposed project should enter through a simple, consistent process. A short intake should capture:

    • The problem or opportunity
    • The measurable baseline and desired outcome
    • The strategic objective or risk it supports
    • The likely value and who benefits
    • The functions, resources, and decisions required
    • The estimated effort, timing, and major dependencies
    • The proposed owner and sponsor

    The intake is not a full project charter. It provides enough information to compare opportunities before the organization invests heavily in planning.

    3. Evaluate value, risk, and effort separately

    A single return-on-investment number can hide important considerations. Leaders should score proposals across several dimensions.

    • Strategic value: How directly does the project support a priority?
    • Risk reduction: What safety, quality, compliance, supply, or customer exposure will it reduce?
    • Operational impact: How much will it affect capacity, delivery, yield, reliability, cost, or service?
    • Urgency: Is there a customer, regulatory, seasonal, or commercial deadline?
    • Effort and complexity: How many functions, decisions, resources, and dependencies are involved?
    • Confidence: How credible are the baseline, assumptions, and expected benefits?

    Scoring does not replace judgment. It makes assumptions visible and gives leadership a consistent basis for discussion.

    4. Check capacity before approving work

    A portfolio is only credible when it reflects resource constraints. Identify the people and functions that commonly become bottlenecks: engineering, quality, validation, maintenance, finance, data analysis, or experienced frontline employees.

    Estimate how much improvement capacity these groups can support after essential operating responsibilities. Then limit active work accordingly.

    This requires leaders to distinguish among four decisions:

    • Start now because the project is important and resourced.
    • Sequence next because it is valuable but depends on capacity becoming available.
    • Develop further because the problem or benefits are not yet clear.
    • Stop or decline because it does not justify the required effort.

    A visible queue is not a failure. It is evidence that the organization is making deliberate choices.

    5. Balance the portfolio

    The highest-scoring projects should not automatically consume the entire portfolio. A healthy mix protects the organization from becoming overly concentrated in one kind of work.

    For example, a portfolio dominated by cost reduction may neglect growth capacity or quality risk. A portfolio filled only with large cross-functional projects may produce few near-term results. A portfolio of quick wins may fail to address structural constraints.

    Leaders should review balance across strategic themes, risk, time horizon, project size, and resource demand. The objective is not equal distribution. It is a mix that reflects the business strategy and operating reality.

    6. Govern progress and benefits

    Once projects enter the active portfolio, governance should focus on decisions rather than presentations. A monthly portfolio review should ask:

    • Are active projects still aligned with current priorities?
    • Are milestones and benefits on track?
    • Which barriers require leadership action?
    • Have resource needs or dependencies changed?
    • Should any project be paused, combined, accelerated, or stopped?
    • When will capacity be available for the next project?

    Benefits should be tracked after implementation, not only at approval. Operational results must be sustained long enough to support the claimed business impact.

    An Example: Reducing Overload at a Manufacturing Site

    Consider a site with 24 active improvement projects. The list includes downtime reduction, yield improvement, line clearance, scheduling, workplace organization, supplier changes, training updates, and several capital requests.

    Each project has an owner, but many rely on the same small group of engineers and quality specialists. Deadlines slip, meetings multiply, and leaders receive status reports without a clear view of priority.

    The site maps every project against three business priorities and identifies resource demand. Six projects have weak alignment or unclear baselines and are returned for further definition. Five local improvements move to department ownership without portfolio-level governance. Four projects are paused until a major product transfer is complete.

    The remaining active portfolio contains nine projects with clear sponsorship and realistic staffing. The organization appears to be doing less, but completion improves because resources are no longer fragmented. Leaders can also explain why each project matters and what will start next.

    Common Portfolio Mistakes

    • Using a complex scoring model that creates false precision
    • Approving projects without checking shared-resource capacity
    • Treating mandatory risk work as if it competes only on financial return
    • Allowing influential sponsors to bypass the intake process
    • Keeping stalled projects active to avoid a difficult stopping decision
    • Reporting forecast benefits without confirming realized results

    Three Actions to Begin

    1. Build one complete list. Gather every active and proposed cross-functional improvement effort in one place.
    2. Test alignment and capacity. Link each project to a business priority or material risk, then identify the shared resources it requires.
    3. Make explicit decisions. Start, sequence, develop, or stop each item—and communicate the reasoning.

    An improvement portfolio does not reduce ambition. It converts ambition into choices the organization can execute.

    Review your current project list this week. If everything is a priority, the most valuable first improvement may be the way you select improvement work.