4.2 Project Selection & Stakeholder Analysis

Project Selection & Stakeholder Analysis

Quick Answer: Six Sigma project selection filters potential initiatives based on strategic organizational relevance, high Cost of Poor Quality (COPQ) leverage, measurable data availability, and a manageable 3-to-6 month execution scope. Financial benefits are divided into hard savings (direct P&L reductions such as scrap and overtime) and soft savings (cost avoidance and customer loyalty). Competing projects are ranked using a weighted Project Prioritization Matrix. To sustain improvements, teams conduct stakeholder analysis using the Power/Interest Grid to tailor engagement strategies and manage organizational resistance. Independent CSSYB study guide by OpenExamPrep.

Six Sigma Project Selection Criteria

Organizations possess finite capital, engineering hours, and Belt resources. Selecting an inappropriate project leads to squandered resources, team frustration, and diminished organizational confidence in Six Sigma. Quality leaders deploy rigorous selection criteria to evaluate candidate initiatives:

1. Strategic Connection: The project must directly support organizational strategic priorities, such as entering key markets, improving product delivery speed, elevating customer retention, or satisfying stringent regulatory mandates.
2. High Financial Leverage (COPQ Reduction): High-priority projects target substantial Cost of Poor Quality—eliminating chronic scrap, expensive rework loops, heavy warranty reserves, or lost operational capacity.
3. Measurable Customer Impact: The problem must directly influence Critical-to-Quality (CTQ) parameters valued by internal or external customers, resolving chronic complaints and operational pain points.
4. Manageable Scope: A successful Six Sigma project is bounded sufficiently to be completed within a targeted timeframe of 3 to 6 months. Projects that attempt to solve enterprise-wide dysfunction all at once ("boiling the ocean") almost inevitably suffer from scope creep, analytical paralysis, and team fatigue.
5. Baseline Data Availability: Meaningful, reliable data must be accessible or readily collectable. If establishing a measurement system requires a multi-year enterprise software overhaul, the project is ill-suited for immediate Six Sigma execution.
6. Root Cause Unknown: Six Sigma DMAIC is designed for complex, chronic problems where the root causes are not evident. If the cause is obvious and an established low-risk solution is available, the team should execute an immediate Kaizen "Just-Do-It" action rather than launching an extensive 6-month DMAIC cycle.

---

Financial Justification: Hard Savings vs. Soft Savings

Rigorous Six Sigma organizations require financial validation from the corporate Finance department before a project is chartered and upon project completion. Financial benefits fall into two distinct classifications:

Hard Savings (Direct Bottom-Line Reductions)

Hard savings represent direct, measurable financial reductions that clearly reflect on the organization's Profit and Loss (P&L) statements.

• Examples: Tangible reductions in raw material scrap expenses, elimination of scheduled overtime payroll hours, termination of contracted third-party sorting or inspection services, lower physical warranty payouts, and reduced material procurement costs through improved process yields.
• Significance: Hard savings directly boost net operating profit, lower unit manufacturing costs, and generate verifiable cash flow improvements. Finance controllers routinely track these line items directly against operating budgets.

Soft Savings (Indirect, Intangible, and Cost Avoidance)

Soft savings represent financial and operational benefits that do not produce an immediate, direct line-item reduction on current financial accounting statements.

• Examples: Cost avoidance (such as expanding existing machine throughput to avoid purchasing a second $500,000 packaging unit in the next fiscal year), improved employee safety and morale, accelerated customer inquiry response times leading to improved retention, and reduced exposure to potential regulatory penalties.
• Significance: While soft savings provide immense strategic value, executive sponsors typically require projects to deliver verifiable hard savings to justify dedicated resource investments and capital allocation.

---

The Project Prioritization Matrix

To select objectively among dozens of competing project proposals, organizations utilize a Project Prioritization Matrix. This tool establishes a structured, multi-criteria decision model that scores candidate projects against weighted criteria. Each organization sets its own criteria and weights; a typical example is:

• Strategic Contribution & Customer Impact (Weight: 30%)
• Financial Return / COPQ Reduction (Weight: 30%)
• Implementation Feasibility & Technical Risk (Weight: 20%)
• Time to Completion & Resource Availability (Weight: 20%)

Team leaders assign a numerical score (e.g., 1 to 5 or 1 to 10) to each candidate project across each criterion. Scores are multiplied by the respective criteria weights and summed to produce a composite priority index. The highest-ranked projects are advanced for formal chartering and Champion approval.

---

Stakeholder Identification and Analysis

A stakeholder is any individual, functional group, or external entity who has an interest in, exerts influence over, or is impacted by the process and its prospective modifications. Failing to engage stakeholders early is one of the leading causes of project failure.

Common stakeholders include:

• Process Owners: Operational managers with ongoing accountability for process performance.
• Frontline Personnel: Operators, technicians, and clerks executing daily process tasks.
• Project Champion / Executive Sponsor: Leaders who allocate funding, remove roadblocks, and approve tollgates.
• Support Functions: IT, maintenance, human resources, procurement, and regulatory compliance.
• Suppliers and Customers: Upstream resource providers and downstream output recipients.
• End Users: The people who ultimately use the product or service; their experience decides whether the change succeeds.
• Subject Matter Experts (SMEs): Specialists such as engineers, auditors, or IT analysts whose knowledge the team needs and whose work may change.

Stakeholder analysis also looks beyond people to factors the project will affect, such as regulations, contracts, IT systems, and union agreements. For each stakeholder or factor, record how it could help or block the project; that assessment drives the engagement strategy below.

---

The Stakeholder Power / Interest Grid

The Power/Interest Grid is a 2x2 matrix classifying stakeholders according to their organizational power (ability to allocate resources, enforce policies, or block initiatives) and their interest (degree to which they are personally or professionally affected by project outcomes).

The four quadrants dictate specific engagement strategies:

1. High Power, High Interest (Manage Closely / Key Players):
   • Includes the Project Champion, the primary Process Owner, and key functional department heads.
   • Strategy: Active partnership and continuous collaboration. Involve them directly in project scope definition, risk assessments, and tollgate milestone reviews. Ensure their ongoing buy-in, as their support is vital to sustain process improvements.
2. High Power, Low Interest (Keep Satisfied):
   • Includes corporate executive leaders, legal counsel, and finance controllers who oversee broad operations but have limited time for daily project mechanics.
   • Strategy: Provide concise executive updates focusing on high-level milestones, budget tracking, and risk management. Address their potential concerns proactively to prevent unexpected project roadblocks or vetoes.
3. Low Power, High Interest (Keep Informed):
   • Includes frontline technicians, machine operators, customer service staff, and downstream internal recipients who live with the process every day.
   • Strategy: Keep them continuously informed through regular briefings, focus groups, and feedback loops. Frontline personnel possess deep institutional knowledge of root causes; engaging them builds grassroots ownership and turns them into enthusiastic project advocates.
4. Low Power, Low Interest (Monitor):
   • Includes peripheral departments and external observers who are only marginally affected by the process changes.
   • Strategy: Monitor with minimal effort through routine company-wide newsletters or open portal updates without overwhelming them with detailed reports.

---

Managing Organizational Resistance to Change

Process improvements invariably alter workflows, operating procedures, and job responsibilities. People naturally resist change due to fear of the unknown, concern over increased workloads, perceived loss of autonomy, or skepticism bred by past failed management programs. Six Sigma practitioners overcome resistance through proactive change management:

• Early Engagement: Involve frontline workers in process mapping, Ishikawa root cause brainstorming, and data collection rather than imposing top-down solutions.
• Transparent Communication: Clearly articulate the business rationale ("Why change is necessary") and address personal concerns ("What this means for daily work").
• Collaborative Pilot Testing: Test prospective solutions in controlled, small-scale pilot environments to demonstrate efficacy, gather constructive feedback, and build confidence before full-scale deployment.