I am implementing a small DMAIC project at work, but my team is pushing back. They think it is just extra work. How do I demonstrate the value of these changes without sounding like a corporate drone? Any tips on 'selling' Lean Six Sigma to skeptics? I need some practical ways to show them that this is about making their jobs easier, not harder.
Resistance to process improvement is mitigated by focusing exclusively on the removal of specific operational pain points and demonstrating direct, tangible benefits to the workflow through evidence-based results rather than methodology-centric communication.
7 answers
I have spent twenty years in manufacturing, and I can tell you that if your team thinks your project is just 'extra work,' they are usually right. Most Lean Six Sigma projects are poorly scoped, high-effort, low-impact administrative nightmares. You need to stop being a process consultant and start being an operator.
Execute this:
- Get on the floor. Work their shift. Understand the actual, physical labor involved.
- Delete any documentation or reporting requirement that doesn't produce an immediate, tangible improvement in their daily operations.
- Show them the data once, then get out of the way.
Stop talking about 'Lean' and start talking about fixing broken machines or simplifying reporting. If you cannot explain why your project makes their job easier in one sentence, you have no business implementing it. Respect their time, cut the fluff, and produce a result that puts more money in their pocket or less stress on their shoulders.
Stop selling the methodology. Nobody cares about DMAIC except the people who paid for your certification. Your team sees extra work because, right now, it is extra work.
You need to pivot to the pain point. If they are complaining about manual data entry, fix that specific friction point first. Do not frame it as a project. Frame it as removing a repetitive task. If you cannot identify one thing that makes their daily grind objectively shorter or less annoying, the project is likely worthless. Stop using Lean Six Sigma jargon in meetings immediately. If I hear 'value stream' or 'waste' in a team huddle, I check out. Talk about time saved, fewer email errors, or not staying late on Fridays. If you solve one small, irritating problem for them, they will stop fighting you on the rest.
Resistance is usually a signal that your project charter is disconnected from the current workflow reality. You are viewing this as a process improvement; they are viewing it as a disruption to their quota.
To bridge this gap:
- Quantify the waste in their terms. If they spend two hours a day on rework, show them that data.
- Include them in the solution design. If they help design the process change, they own the outcome rather than resisting it.
- Verify that your measurement system is not burdensome. If data collection takes longer than the process improvement itself, your methodology is flawed.
Shift your approach from prescribing solutions to asking, 'What is the biggest roadblock preventing you from hitting your targets by 2:00 PM?' Address that roadblock using your DMAIC tools as the engine, not the topic of conversation. Keep the methodology under the hood.
I feel like I'm constantly fighting this disconnect, Kristin. Trying to keep the methodology under the hood while hitting quotas is exhausting, but I see the logic in your approach.
DMAIC is a framework for process stability, not an administrative burden. The friction you are experiencing is a failure to establish the Business Case effectively at the operator level. You are failing to demonstrate that the output of your DMAIC cycle directly correlates to a reduction in process variance that currently makes their tasks difficult.
Consider these three steps:
- Audit your current data collection requirements. If operators are manually logging data for your project, replace that with automated captures.
- Visualize the defect rate. When they see the volume of failures, the improvement becomes a shared goal rather than a management directive.
- Review the process stability. If they see you are reducing the number of 'bad parts' or 'escalated tickets' they have to handle, the 'extra work' argument evaporates.
Data should be used to advocate for their workload reduction, not to scrutinize their performance. If your project does not yield a measurable reduction in operator task-load, you have defined the problem incorrectly.
The key to overcoming resistance is transparency in the Voice of the Customer—in this case, your team. Use a simple SIPOC diagram to show them exactly where their process currently breaks down and forces them to work harder.
You must move away from the 'corporate drone' language by focusing exclusively on outcomes. If your DMAIC project is aimed at reducing cycle time, translate that into 'not being stuck on the floor for an extra hour.' When you frame the change as a mechanism to reclaim their time, you transition from an intruder to an advocate. Use quick wins to build credibility. If you can eliminate one high-frequency pain point in the Define and Measure phase, the buy-in for the Analyze and Improve phases happens organically because they see the immediate utility of the project framework. Keep the tools behind the curtain; share the results at the desk level.
Joann, your suggestion to focus on quick wins is very insightful. I am often caught up in the methodology, but I see now that results matter more than the tools used.
Joann, I love the idea of using a SIPOC to show them the real issues. It sounds much less intimidating than how I’ve been presenting things to my team lately.
Resistance is a natural reaction to uncertainty. When you introduce a DMAIC framework, you are introducing a system they do not understand, which they perceive as a threat to their established routines. The error here is presenting the framework as the objective.
The methodology is merely a tool for gathering evidence. You should be conducting a Gap Analysis on the current state of their workload, not the process efficiency itself. If you shift your focus to the friction they face, the DMAIC tools become the instruments of your support. Engage them in the Measurement phase by asking for their input on what metrics actually reflect their frustration. When you allow them to define what 'better' looks like, the resistance turns into collaboration. Ensure your final process map reflects their operational input, not just your theoretical model. Documentation serves the user; if it does not, it is waste.
If the team sees extra work, you have failed to identify the Value-Add for the end user. Stop trying to 'sell' Lean. It is a tool, not a lifestyle. If your project doesn't solve a problem that bothers them, they are right to resist it.
Checklist for your next team meeting:
- Identify a specific bottleneck causing them overtime.
- Use your data to prove the bottleneck is external to their effort.
- Map the solution that eliminates the bottleneck.
If you aren't saving them time, stop the project. Lean Six Sigma exists to reduce waste, and if your project is creating administrative overhead for your staff, you are committing the very waste you claim to be solving. Drop the terminology, show them the improved throughput, and make the change invisible to their daily habits. If the job gets easier, they will support you. If you keep pushing for process compliance, expect the pushback to continue.
Spot on, Chad. Most projects fail because we prioritize our internal checklists over actual throughput. If it’s not making the job easier, we’re just another layer of corporate bureaucracy.
I struggle with the balance, Chad, but your point about administrative waste really hits home. I need to re-evaluate whether my documentation is actually helping or just adding to the bottleneck.
Thanks for this perspective, Chad. I've been so focused on the Lean terminology that I missed how much I was stressing the team out. I’ll start focusing on their daily bottlenecks instead.
Kristin, your point about the measurement system being burdensome is exactly my current struggle. I need to simplify my data collection so the team doesn't see it as another chore.