Change Management and Project Leadership Basics

Learning Objectives

By the end of this lesson, the learner will be able to:

Explain why change management is important in Six Sigma projects.
Describe the relationship between process improvement and organizational change.
Identify common sources of resistance to change.
Understand the human and organizational factors that influence project success.
Explain the basic responsibilities of a Green Belt project leader.
Identify key stakeholders and understand their interests and influence.
Communicate project objectives, progress, risks, and results effectively.
Apply basic stakeholder-management techniques.
Explain the importance of team roles, engagement, and accountability.
Recognize common causes of project-team conflict.
Apply practical approaches to managing resistance and conflict.
Establish effective project governance and escalation.
Support adoption of improved processes through training, communication, and standardization.
Understand the Green Belt’s role in transferring ownership to the Process Owner.

1. Introduction

Six Sigma projects are often described in terms of:

Data
Statistical analysis
Root causes
Process improvements
Control charts
Capability

However, even an analytically excellent solution can fail if people do not adopt and sustain the new way of working.

For example, a team may develop an improved process that reduces defects by 40%.

The technical solution is validated.

The control plan is prepared.

The process owner agrees with the results.

Yet, several months later, the original performance returns.

Why?

Possible reasons include:

Employees did not understand the reason for the change.
Training was inadequate.
Supervisors did not reinforce the new standard.
The improvement added work without addressing practical concerns.
Roles and responsibilities were unclear.
Performance measures were not aligned.
Stakeholders were not adequately involved.
Resistance was not addressed.
The improved process was not integrated into normal operations.

This is why change management and project leadership are important Green Belt competencies.

A Green Belt is not only an analyst.

The Green Belt also helps people understand, implement, adopt, and sustain process improvement.

2. Concept / Theory

2.1 What Is Change Management?

Change management is a structured approach for helping individuals, teams, and organizations transition from a current way of working to a desired future state.

In a Six Sigma project, change may involve:

New procedures
New technology
New responsibilities
New measurements
New workflows
New quality requirements
New approval processes
New performance expectations
New roles
New behaviors

Change management focuses on the people and organizational aspects of implementing the improvement.

It complements technical project management.

2.2 Why People Resist Change

Resistance to change is not always irrational.

People may resist because they:

Do not understand the reason for change.
Fear loss of authority or status.
Are concerned about increased workload.
Do not trust the proposed solution.
Have experienced unsuccessful changes in the past.
Lack required skills.
Fear job consequences.
Were not consulted.
Believe the current process works adequately.
Do not see personal or customer benefit.
Are uncertain about expectations.

The Green Belt should therefore investigate resistance rather than simply labeling people as “difficult.”

2.3 Change and the Current State

Every improvement project involves movement from:

Current State → Future State

The gap between the two may include:

Process differences
Skill differences
Technology differences
Responsibility differences
Behavioral differences
Measurement differences

A successful change plan identifies these gaps and determines how they will be addressed.

2.4 Stakeholders

A stakeholder is a person, group, or organization that can affect, be affected by, or have an interest in the project or its outcome.

Examples include:

Sponsor
Process Owner
Customers
Employees
Supervisors
Quality
Finance
IT
Engineering
Suppliers
Regulatory functions
Senior management

Not every stakeholder requires the same type or frequency of communication.

2.5 Stakeholder Influence and Interest

A useful stakeholder analysis considers two dimensions:

Influence

How much ability does the stakeholder have to affect the project?

Interest

How strongly is the stakeholder affected by or interested in the project?

This helps the Green Belt determine appropriate engagement.

For example:

A senior sponsor may have high influence and high interest.
A frontline employee may have lower formal authority but high practical influence over implementation.
A remote support function may have moderate influence and lower day-to-day interest.

The analysis should be based on the actual project context.

2.6 Communication

Effective communication is essential throughout DMAIC.

Communication should answer:

Why is the project necessary?
What problem are we solving?
What does the data show?
What is changing?
Who will be affected?
What is expected?
When will the change occur?
What support is available?
How will success be measured?

Communication should be:

Clear
Timely
Relevant
Audience-appropriate
Evidence-based
Two-way where appropriate

2.7 Project Leadership

Project leadership is the ability to guide a team toward the project objective while coordinating people, information, decisions, and actions.

A Green Belt project leader typically helps:

Define the project.
Coordinate the team.
Facilitate meetings.
Maintain project focus.
Analyze data.
Remove or escalate barriers.
Track actions.
Communicate status.
Engage stakeholders.
Support implementation.
Verify results.
Transfer ownership.

The Green Belt may not have formal authority over all project participants.

Leadership therefore often depends on influence, facilitation, credibility, communication, and evidence rather than hierarchy alone.

3. Key Topics

3.1 Project Sponsor

The Sponsor provides organizational support and helps ensure that the project is aligned with business priorities.

Typical responsibilities include:

Approving the project.
Providing organizational support.
Helping resolve major barriers.
Providing resources where appropriate.
Reviewing progress.
Supporting escalation.
Helping ensure benefits are realized.

The Sponsor should not normally perform the Green Belt’s analytical work.

3.2 Process Owner

The Process Owner is responsible for the ongoing operation and performance of the process.

Responsibilities may include:

Maintaining process standards.
Monitoring performance.
Ensuring controls remain effective.
Supporting corrective action.
Managing process changes.
Maintaining process documentation.

The Process Owner is particularly important during project handover and sustainment.

3.3 Green Belt

The Green Belt commonly serves as the project leader or improvement practitioner.

Responsibilities include:

Define the problem.
Establish the project charter.
Coordinate the team.
Collect and analyze data.
Identify root causes.
Facilitate improvement.
Validate results.
Establish control mechanisms.
Communicate project status.
Support implementation.
Transfer ownership.

The exact role depends on the organization’s Six Sigma deployment model.

3.4 Team Members

Team members provide:

Process knowledge
Functional expertise
Data
Ideas
Testing support
Implementation support

A strong project team should include people who understand the process from different perspectives.

3.5 Subject Matter Experts

Subject Matter Experts (SMEs) provide specialized knowledge.

Examples:

Engineering
IT
Finance
Regulatory
Quality
Maintenance
Operations

SMEs can be particularly useful when the Green Belt does not possess detailed technical knowledge of a process.

3.6 RACI and Role Clarity

A RACI matrix can help clarify responsibility.

RACI commonly represents:

R — Responsible
A — Accountable
C — Consulted
I — Informed

For example:

Activity	Sponsor	Green Belt	Process Owner	Team
Approve project	A	R/C	C	I
Analyze process	I	R	C	R
Implement improvement	C	R	A	R
Sustain controls	I	C	A/R	R/C

The exact assignment should reflect the organization’s governance structure.

3.7 Project Meetings

Effective meetings should have:

Clear purpose
Agenda
Appropriate participants
Defined decisions
Action owners
Due dates
Follow-up

A project meeting should not become a general discussion without decisions or actions.

A practical meeting structure is:

Review objective.
Review previous actions.
Review data and milestones.
Discuss barriers.
Make required decisions.
Assign actions.
Confirm deadlines.
Escalate unresolved issues.

3.8 Managing Resistance

Resistance should first be understood.

The Green Belt can ask:

What specifically is the concern?
Is the concern supported by evidence?
Is the proposed change practical?
Does the employee understand the reason?
Is additional training needed?
Does the new process create unintended consequences?
Were frontline users involved in design?
Is management reinforcement adequate?

Possible responses include:

Communication
Training
Demonstration
Pilot testing
Employee involvement
Process redesign
Coaching
Additional support

Not every resistance issue can be solved through communication alone.

Sometimes the proposed solution itself needs modification.

3.9 Training and Competence

Training should address the actual requirements of the changed process.

Training may include:

New standard work
New system functions
New inspection methods
New data collection
New escalation rules
New responsibilities

Training effectiveness should be evaluated where appropriate.

Attendance alone does not prove competence.

3.10 Conflict Management

Conflict can occur because team members have different:

Objectives
Priorities
Data interpretations
Functional responsibilities
Incentives
Risk perceptions

The Green Belt should focus discussion on:

Problem → Evidence → Options → Decision

rather than:

Person → Blame → Argument

A useful approach is to distinguish:

Facts
Assumptions
Opinions
Unresolved questions

This helps make disagreements more productive.

3.11 Escalation

Some project barriers cannot be resolved by the Green Belt alone.

Examples:

Resource conflicts
Major technology issues
Policy conflicts
Cross-functional disagreements
Budget constraints
Regulatory restrictions

The Green Belt should escalate appropriately rather than allowing critical issues to remain unresolved.

Escalation should include:

Problem
Evidence
Impact
Options considered
Decision required
Timing

4. Tools / Methodology

4.1 Change Management Methodology

A practical approach is:

Step 1 — Define the Change

Clearly describe:

Current State → Desired Future State

Step 2 — Identify Who Is Affected

List:

Employees
Customers
Managers
Support functions
Suppliers
Other stakeholders

Step 3 — Assess Impact

Determine how the change affects:

Roles
Workload
Skills
Technology
Measures
Responsibilities

Step 4 — Identify Risks and Resistance

Ask what could prevent adoption.

Step 5 — Develop Communication

Define:

Message
Audience
Channel
Timing
Owner

Step 6 — Provide Training and Support

Ensure affected personnel understand:

What changed.
Why it changed.
How to perform the new process.
What to do when problems occur.

Step 7 — Pilot Where Appropriate

A pilot can identify:

Unintended consequences
Usability problems
Training gaps
Process constraints

Step 8 — Implement

Deploy the validated change.

Step 9 — Monitor Adoption

Monitor:

Compliance
Process performance
Employee feedback
Customer outcomes
Exceptions

Step 10 — Sustain

Integrate the change into:

Standard work
Control Plans
Training
Performance management
Audits
Process ownership

4.2 Stakeholder Analysis

Create a stakeholder table:

Stakeholder	Interest	Influence	Impact	Engagement Approach
Sponsor	High	High	High	Regular executive updates
Process Owner	High	High	High	Active involvement
Frontline staff	High	Moderate	High	Training and feedback
IT	Moderate	High	Moderate	Technical coordination
Finance	Moderate	Moderate	Moderate	Benefit validation

The table should be updated as the project evolves.

4.3 Communication Plan

A simple communication plan may contain:

Audience	Message	Channel	Frequency	Owner
Sponsor	Project status	Review meeting	Monthly	Green Belt
Project team	Actions and barriers	Team meeting	Weekly	Green Belt
Employees	Process changes	Training/briefing	Before implementation	Process Owner
Management	Results and risks	Dashboard	Monthly	Green Belt

The level of communication should match the audience and project needs.

4.4 Change Readiness Assessment

Before implementation, ask:

Is the reason for change understood?
Is leadership support visible?
Are roles clear?
Is training complete?
Are resources available?
Is the technology ready?
Are procedures updated?
Are measures defined?
Are controls ready?
Is the Process Owner prepared to assume ownership?

If important gaps remain, implementation risk increases.

5. Worked Example / Case Study

Case Study: Reducing Invoice Processing Errors

A Six Sigma project reduces invoice errors by introducing:

Automated validation against approved pricing data.

The technical solution is validated.

However, the improvement changes how employees perform invoice processing.

5.1 Stakeholder Identification

Affected stakeholders include:

Invoice-processing employees
Finance manager
IT
Sales
Process Owner
Customers

Each group has different concerns.

Employees

Concern:

“Will the new system make processing slower?”

Finance

Concern:

“Will the change reduce billing errors?”

IT

Concern:

“Can the system be implemented reliably?”

Sales

Concern:

“Will legitimate exceptions be blocked?”

Customers

Expected benefit:

More accurate invoices.

5.2 Change Impact

The new process changes:

Data-entry method
Exception handling
Training requirements
Approval process
Performance monitoring

The Green Belt documents these changes.

5.3 Communication

The project team explains:

Why invoice errors are a problem.
What the data show.
What is changing.
What will remain unchanged.
How exceptions will be handled.
What training will be provided.
How performance will be measured.

This communication should be two-way so that practical concerns can be identified.

5.4 Pilot

The solution is piloted with a limited group.

The team measures:

Error rate
Processing time
Exception rate
User issues
Customer impact

The pilot identifies an issue:

Some legitimate special-price transactions are being flagged.

The project team works with Sales and IT to define an appropriate exception process.

This demonstrates an important principle:

Pilot feedback should be used to improve the solution before full deployment.

5.5 Implementation

After validation:

Standard work is updated.
Training is completed.
The Control Plan is updated.
Performance measures are established.
Process ownership is transferred.
Escalation rules are documented.

The project team continues monitoring long enough to verify that the change has been adopted and performance is sustained.

6. Practical Application

Exercise 1 — Stakeholder Analysis

Select a Six Sigma project and identify:

Sponsor
Process Owner
Green Belt
Team members
Frontline employees
Customers
Support functions
Other affected stakeholders

For each, document:

Interest
Influence
Impact
Communication needs

Exercise 2 — Change Impact Assessment

For a proposed process improvement, identify changes in:

Roles
Responsibilities
Skills
Technology
Work instructions
Measures
Reporting
Customer interaction

Then identify the support required.

Exercise 3 — Resistance Analysis

Suppose employees say:

“The old process worked well enough. We don’t see why we need to change it.”

Develop an appropriate response.

Consider:

What data demonstrate the problem?
What customer impact exists?
What benefits does the proposed change provide?
What concerns do employees have?
What evidence can be shared?
What training is required?
Could the solution itself be improved?

Exercise 4 — Communication Plan

Develop a communication plan for a Six Sigma project.

Include:

Audience
Message
Communication channel
Timing
Owner
Feedback mechanism

Exercise 5 — Project Leadership Scenario

A project team has missed two milestones because the IT department has not completed a required system change.

As Green Belt, determine:

What facts should be gathered?
What is the impact on the project?
What can the team resolve directly?
What should be escalated?
What decision is required?
Who should make the decision?
What revised action and date should be documented?

The objective is to demonstrate structured leadership rather than simply escalating a complaint.

6.1 Change Management Checklist

Before implementing a significant improvement, verify:

Current state is understood.
Future state is clearly defined.
Stakeholders are identified.
Change impacts are assessed.
Risks are identified.
Resistance concerns are understood.
Communication plan is established.
Training requirements are defined.
Standard work is updated.
Control Plan is updated.
Process Owner is engaged.
Pilot is conducted where appropriate.
Implementation responsibilities are clear.
Performance measures are defined.
Adoption is monitored.
Escalation routes are defined.
Ownership is transferred.

7. Lesson Summary

Successful Six Sigma improvement requires both technical and human effectiveness.

The major principles are:

Change management supports adoption of improved processes.
People may resist change for understandable reasons.
Resistance should be investigated rather than dismissed.
Stakeholders differ in interest, influence, and impact.
Communication should be clear, timely, relevant, and two-way where appropriate.
The Green Belt often leads through influence rather than formal authority.
The Sponsor provides organizational support.
The Process Owner owns ongoing process performance.
Team members and SMEs provide process and technical knowledge.
RACI can clarify responsibilities.
Training should build actual competence.
Pilot testing can reveal unintended consequences.
Conflict should be managed through facts, evidence, and structured decision-making.
Escalation should be timely and supported by evidence.
Change should be integrated into standard work, controls, training, and process ownership.
Sustaining improvement requires adoption as well as technical effectiveness.

A useful sequence is:

Understand → Engage → Communicate → Train → Pilot → Implement → Monitor → Sustain

8. Lesson Learnt / Conclusion

A Six Sigma improvement is ultimately implemented by people.

Data may identify the problem.

Statistical analysis may identify important relationships.

Root Cause Analysis may identify the underlying cause.

An improvement solution may address the cause.

But people must still:

Understand the change.
Accept the new process.
Learn the new method.
Apply it consistently.
Monitor the results.
Respond to problems.
Sustain the improvement.

The Green Belt therefore has an important leadership responsibility.

Effective project leadership does not mean having all the answers.

It means creating a structured environment in which:

The problem is clear.
Data are respected.
People are heard.
Responsibilities are clear.
Decisions are made.
Actions are followed.
Problems are escalated appropriately.
Improvements become part of normal operations.

The Green Belt should remember:

Technical solutions improve processes; effective leadership helps organizations adopt and sustain those solutions.

Key takeaway:

Lead the change, engage the people, validate the solution, and make the improved process the new standard.