1.3 Selecting Lean Six Sigma Projects

Selecting Lean Six Sigma Projects Understanding What Makes a Good Lean Six Sigma Project Selecting the right projects is the foundation of effective Lean Six Sigma deployment. A good project is not just about fixing a problem; it must be aligned, feasible, data-driven, and oriented toward measurable improvement. Characteristics of a Strong Project A strong Lean Six Sigma project typically has: - Clear problem: A specific, observable gap in performance. - Business impact: Meaningful effect on cost, quality, delivery, safety, or customer satisfaction. - Process focus: Involves an existing, repeatable process that can be measured and improved. - Data availability: Current or attainable data to define baseline and measure results. - Feasible scope: Achievable within a reasonable timeframe and resource level. - Improvement potential: A realistic opportunity to reduce variation, defects, waste, or lead time. Projects that do not meet these conditions risk becoming unmanageable, low-impact, or impossible to complete. Problems Well-Suited for Lean Six Sigma Lean Six Sigma projects are most appropriate when: - A process has chronic performance issues (ongoing, not one-time). - The problem recurs and is not solved by simple fixes. - The root cause is unknown and needs structured investigation. - There is measurable variation in performance across time, shifts, units, or locations. - Defects, delays, or rework are significant and costly. - The process spans multiple steps or departments and suffers from handoff issues. Situations that are usually not suitable include: - One-time events (e.g., system outage caused by a known incident). - Purely strategic or policy decisions with no clear process to improve. - Projects driven only by technology installation without a process problem. --- Aligning Projects With Organizational Strategy Projects must support organizational goals. Selection decisions are not made in isolation; they are made to advance strategic priorities. Linking Projects to Critical Objectives Effective project selection asks how a project contributes to: - Strategic goals: Growth, market share, competitiveness. - Key performance indicators: On-time delivery, defect rate, cycle time, service level. - Financial targets: Revenue, cost reduction, margin improvement, asset utilization. - Customer priorities: Quality, reliability, speed, ease of use. A strong candidate project typically has: - A clear connection to at least one critical objective. - Stakeholders who can articulate why the project matters now. - Measurable benefits in terms that leadership cares about. Defining Project Boundaries and Scope Oversized or vague projects rarely succeed. Scope must be constrained so it is actionable. Useful scoping dimensions include: - Process boundaries: Define start point and end point of the process under study. - Organizational boundaries: Identify which units, sites, or teams are in scope. - Product / service focus: Specify which product lines, customers, or service types are included. - Timeframe: Define the period of historical data and the anticipated project duration. Well-scoped projects: - Are neither too broad (e.g., “eliminate all defects in the company”) nor too narrow (e.g., “fix this one specific incident”). - Can show meaningful results in a practical timeframe. - Have a manageable number of stakeholders and interfaces. --- Screening and Prioritizing Candidate Projects Organizations typically have more potential problems than they can tackle. A structured screening and prioritization approach is essential. Initial Screening Criteria First, remove projects that clearly do not fit Lean Six Sigma. Key screening questions: - Is there a real process? If not, it may be a design or policy issue instead. - Is the goal improvement, not just compliance? If it is only to meet a checklist or regulatory requirement, Lean Six Sigma may not add value. - Is there a measurable performance gap? If not, the project may lack a clear problem. - Is data feasible to collect? If data is impossible or extremely costly to obtain, the project is risky. - Is leadership support available? If no sponsor is willing to own the project, it is unlikely to succeed. Projects failing these checks should be deferred, reframed, or rejected. Prioritization Factors Among screened projects, prioritization ensures resources go to the most valuable opportunities. Common factors include: - Impact magnitude - Size of the financial benefit (savings, cost avoidance, revenue). - Degree of improvement in customer satisfaction or risk reduction. - Urgency - Regulatory deadlines. - Major customer complaints or contract risks. - Safety or critical quality issues. - Feasibility - Availability of data and subject-matter experts. - Complexity and cross-functional involvement. - Dependence on major system or infrastructure changes. - Strategic alignment - Fit with current strategic initiatives. - Support from leadership and key stakeholders. A simple scoring approach can be used, rating each project on impact, urgency, feasibility, and alignment, then comparing overall scores to decide which to launch. --- Clarifying Project Problem and Goal Clear problem and goal statements guide selection decisions and prevent wasted effort. Problem Statement Essentials A strong problem statement is: - Specific and factual: Describes what is wrong, where, and when. - Neutral in tone: Avoids blame or proposed solutions. - Quantitative where possible: Includes data on current performance. Helpful components: - Current condition: What is happening now? - Gap: How far is performance from the target or requirement? - Location and scope: Where is the problem occurring? - Timeframe: Over what period has this been observed? Example structure: - “In [process], over the period [timeframe], [metric] averages [current level] versus the target of [target level], leading to [consequence].” Ambiguous statements like “The process is bad” or “We need automation” are inadequate and should be refined before selecting the project. Goal and Project Objective Clear goals help evaluate whether the project is worth doing and whether it is feasible. A well-formed project objective is: - Specific: States the exact metric to improve. - Measurable: Quantifies the desired change. - Time-bound: Defines by when the improvement should occur. - Realistic: Challenging but achievable with process changes. Example structure: - “Reduce [metric] from [current level] to [target level] by [date], for [defined scope].” When considering whether to select a project, validate: - The gap between current and target is significant enough to matter. - The target is not already being consistently achieved in parts of the process (which may indicate a different type of problem). - The time horizon fits other commitments and resource availability. --- Understanding Project Types: DMAIC, DMADV/DFSS, and Lean-Focused Different improvement methods are better suited to different kinds of problems. Project selection must match the method to the need. When to Use DMAIC DMAIC is typically used when: - There is an existing process in need of performance improvement. - The output is known but inconsistent or below requirements. - The main issue is excessive variation, defects, rework, or delay. - The process is stable enough to measure and analyze. Project selection for DMAIC focuses on: - Clearly defined defect or performance metrics. - Historical data or the ability to collect it. - Opportunities to reduce variation or shift mean performance. When to Use DMADV or Design for Six Sigma DMADV or Design for Six Sigma methods are best when: - A new product or process must be created to meet customer needs. - The existing process is so inadequate that incremental improvement is insufficient. - There is no established process baseline. For project selection, consider DMADV/DFSS if: - Requirements are changing significantly (new market, new technology, new regulations). - The organization is launching a new service or product where first-time quality is critical. - The risk of failure in a design decision is high. When to Use Primarily Lean-Focused Projects Lean-focused projects are well-suited when: - Main pain points are visible waste: long queues, motion, waiting, excess inventory, or overprocessing. - The process is cluttered or overly complex. - Flow, lead time, or productivity are the immediate priorities. During selection, consider a Lean-focused approach if: - The problem is readily observable through process walks and basic time measurements. - The primary issue is inefficiency, not necessarily variation in quality. - Improvements can be realized quickly by eliminating obvious waste. --- Evaluating Project Feasibility and Risk Not every high-impact idea is feasible right now. Feasibility and risk assessments help avoid stalled projects. Resource and Stakeholder Considerations Key questions when evaluating feasibility: - Sponsor commitment: Is there an engaged sponsor who will remove barriers? - Team availability: Are knowledgeable participants and support functions available? - Competing initiatives: Are there major changes already underway in the same area? - Change readiness: Are the affected groups capable and willing to adopt changes? If vital resources are missing, the project should be delayed, re-scoped, or replaced. Data and Measurement Feasibility The ability to define and measure the problem is central to selection decisions. Check: - Existing data: Are historical data available from systems, logs, or reports? - Data quality: Are current measures consistent and reliable enough to trust? - Measurable outputs: Is there a clear output parameter that captures the problem? - Practical collection: Can needed new data be collected without excessive burden? If data are extremely difficult to obtain, consider either: - Adjusting scope to an area where data are accessible, or - Rejecting the project in favor of one with more measurable outcomes. Risk Assessment for Project Selection A project may be feasible but present high organizational risk. Key risk aspects include: - Operational disruption: Could the work interfere with critical operations? - Regulatory and compliance: Are there constraints that restrict experimentation? - Technical uncertainty: Is there an unknown or untested technology dependency? - Stakeholder resistance: Are key groups likely to strongly oppose changes? Projects with excessive risk relative to their potential benefits or with unresolved ethical or compliance concerns are poor candidates. --- Estimating Benefits and Building a Business Case Before selecting a project, estimate its potential value. This does not require exact precision but must be reasonable and transparent. Cost of Poor Quality and Other Impacts Lean Six Sigma project benefits often relate to the cost of poor quality and wasted resources. Common impact categories: - Direct costs: Scrap, rework, returns, warranty costs, reprocessing. - Indirect costs: Expediting, overtime, extra handling, additional inspections. - Capacity and throughput: Ability to do more work with the same resources. - Customer effects: Complaints, lost sales, churn, penalties, or reputation damage. - Risk reduction: Lower probability of critical failures or non-compliance events. For selection purposes, approximate the financial or operational impact by: - Estimating current defect or waste levels. - Applying cost per defect, per hour of delay, or per unit of waste. - Projecting benefits from reasonable percentage reductions in these metrics. Balancing Benefit with Effort Project selection must balance the potential benefit against the expected effort and complexity. Consider: - Effort drivers: Number of stakeholders, data complexity, number of process steps, required changes in systems. - Implementation cost: Investments in tools, systems, or training needed. - Time to benefit: How quickly meaningful results can be realized. Prefer projects that offer: - Significant impact relative to the required time and resources. - Early wins or quick measurable improvements without compromising robustness. - The potential to create reusable methods or templates for future work. --- Defining Project Scope and Boundaries in Detail Once a project is selected in principle, its detailed scope must be confirmed to avoid misalignment later. Process, Product, and Customer Scope Clarify exactly where the project will concentrate: - Process scope - Define the precise start and end of the process flow to be analyzed. - Identify which steps are inside the scope and which are explicitly excluded. - Product or service scope - Specify which product families, service types, or customer groups are included. - Exclude areas that would stretch the project excessively. - Customer scope - Determine whether the project will focus on internal customers, external customers, or both. - Clarify which specific customer segments the project will impact. Well-defined scope avoids scope creep and keeps analysis manageable. Time, Location, and Data Scope Scope also includes temporal and geographic dimensions: - Time period - Decide the historical period to use for baseline data. - Ensure that this period represents typical operations. - Locations and units - Specify which sites, departments, or branches are in scope. - Note any differences in processes among these locations that could affect analysis. - Data scope - Define which metrics will be measured and how often. - Clarify the granularity of data (per unit, per batch, per day, per shift). Clear scope allows better planning of data collection and analysis tasks. --- Selecting Projects Within a Portfolio In many organizations, project selection occurs within a portfolio of improvement initiatives. Decisions must account for interactions and dependencies. Avoiding Overlap and Redundancy Project proposals can often overlap in process area or objective. Check: - Overlap in scope: Do two projects target the same process step or metric? - Conflicting changes: Could different projects propose incompatible solutions? - Shared data: Will multiple projects rely on the same limited data or resources? When overlap exists: - Merge projects if they share objectives and stakeholders and remain manageable in scope. - Sequence projects if one is a prerequisite for another. - Clarify boundaries to avoid confusion and duplicated effort. Sequencing and Dependencies Some projects depend on others to be completed first. For project selection and scheduling: - Identify technical or process dependencies. - For example, measurement system improvements may be needed before variation-reduction work. - Evaluate whether enabling projects (such as data collection system upgrades) are mandatory before others. - Decide the order in which projects should start and end to maximize value and minimize interference. Portfolio-level selection ensures that resources are not overcommitted and that higher-priority dependencies are addressed first. --- Formalizing Project Selection Decisions After evaluation, decisions must be made explicit so that everyone understands what has been chosen and why. Approval Criteria and Documentation Before launching, confirm: - Problem and objective clarity: The problem statement and objective are approved. - Scope agreement: All affected parties understand what is in and out of scope. - Expected benefits: The projected impact is documented and considered credible. - Resource commitment: The sponsor confirms availability of key team members and support. Keep concise documentation covering: - Problem, goal, and scope. - Key metrics and baseline estimates. - Expected benefits and approximate financial impact. - Key risks and initial mitigation ideas. This documentation should be sufficient to justify why the project was selected and how it will be evaluated. Reassessing the Project Pipeline Project selection is not a one-time decision. Over time: - New information may change estimated benefits, costs, or risks. - Business conditions or priorities may shift. - Some projects may need to be paused or replaced. Regularly review the project pipeline and actively: - Confirm that ongoing projects still align with current priorities. - Replace or re-scope projects that no longer provide sufficient value. - Introduce new, better-aligned projects as needed. Continuous reassessment ensures that selected Lean Six Sigma projects remain relevant and effective. --- Summary Effective selection of Lean Six Sigma projects focuses improvement resources on the right problems. Strong projects: - Address a clearly defined process issue with measurable performance gaps. - Align with strategic and operational goals that matter to the organization. - Have feasible scope, sufficient data, and realistic timeframes. - Show a favorable balance of expected benefits versus required effort and risk. - Match the appropriate methodology (DMAIC, DMADV/DFSS, or Lean-focused) to the nature of the problem. By rigorously screening, prioritizing, scoping, and formalizing project choices, organizations create a focused portfolio of Lean Six Sigma initiatives that deliver meaningful, sustained improvement.