The Real Reason Your Lean Six Sigma Projects Fail: You’re Measuring Everything Except What Matters

The Data Collection Trap That’s Killing Your Projects

I watched a Black Belt spend three months collecting cycle times, defect rates, and process variations for a customer onboarding project at a mid-sized financial services firm. Beautiful histograms. Perfect control charts. Statistical significance on everything.

The project failed spectacularly.

Why? Because nobody asked the customers what “fast onboarding” actually meant to them. Turns out they didn’t care if the process took 3 days or 5 days. They cared about getting clear communication on day one about what documents they needed and when to expect their account to be active.

We reduced cycle time by 40% but customer satisfaction dropped because we automated away the human touchpoints that made people feel confident about their decision.

The Backward Logic of Most DMAIC Projects

Here’s what I see in 8 out of 10 Lean Six Sigma projects: teams start with existing process metrics because they’re easy to collect. Time stamps in the system. Error logs. Volume counts. Then they try to optimize those numbers.

This is backward.

During a finance transformation at a utility company, my team inherited a project focused on reducing invoice processing time. The previous team had mapped every step, timed every handoff, and identified 23 sources of variation.

I spent two days talking to department managers who actually received those invoices. Their biggest frustration wasn’t speed. It was getting invoices rejected for missing information after they’d already been in the system for a week.

We shifted focus from cycle time to first-pass accuracy. Same tools. Same DMAIC methodology. Completely different outcome.

What “Good” Actually Looks Like to Your Customer

Most project charters I review have objectives like “reduce processing time by 25%” or “decrease defect rate to less than 0.1%”. These aren’t customer outcomes. They’re internal efficiency metrics dressed up as customer value.

Real customer outcomes sound different:

“Employees can submit expense reports without wondering if they filled out the form correctly.”

“Suppliers know exactly when they’ll get paid and don’t need to call us for status updates.”

“Department heads can access budget variance reports without waiting for month-end.”

Notice the difference? These statements describe experiences, not measurements.

The 5-Question Reality Check

Before any Define phase ends, I make teams answer these five questions. Not with data. With conversations.

What does the customer actually do with our output? I’ve seen teams optimize report generation time when customers only looked at the reports once a quarter. The optimization didn’t matter because the frequency was wrong.

When does the customer feel frustrated with us? During a procurement process improvement project, we discovered vendors weren’t upset about the 6-week approval time. They were upset about the silence between week 2 and week 5.

What would make the customer choose us again? This question reveals the difference between “acceptable” and “preferred”. Most process improvements aim for acceptable.

How does the customer define quality? At an insurance company, claims processors thought quality meant accuracy. Customers thought quality meant empathy. Both were right, but only one was being measured.

What’s the customer’s backup plan when we fail? Understanding workarounds reveals what customers really value. If they have 17 workarounds for your process, you’re solving the wrong problem.

Why Process Mining Isn’t Enough

I love Signavio. I use it constantly for process discovery and analysis. But process mining tools show you what happened, not why it mattered to the customer.

During an accounts payable project, Signavio showed us that 30% of invoices followed a “happy path” with no rework. The other 70% had at least one rejection loop.

Standard Lean Six Sigma thinking: eliminate the rejection loops.

But when we talked to suppliers, many preferred the rejection loop because it gave them a chance to fix pricing errors before committing. They saw it as a safety net, not a defect.

We optimized the rejection process instead of eliminating it. Supplier satisfaction went up 35%.

The Conversation Before the Charter

I now start every project with what I call “customer reality sessions”. Not surveys. Not interviews. Working sessions where team members actually observe or participate in the customer experience.

For an employee onboarding project, HR team members went through the new hire process themselves using dummy profiles. They discovered that the “streamlined” digital forms were impossible to complete on mobile devices. New hires were printing PDFs and scanning them back because that was easier than zooming in and out on their phones.

The data would never have shown this. The call center logs showed “successful form submissions”. What they didn’t show was the 45 minutes of frustration before each submission.

Fixing the Foundation

Most Lean Six Sigma training teaches you to start with process maps and current state data. I’ve learned to start with customer outcome definitions instead.

Write down what success looks like from the customer’s perspective before you collect a single data point. Make it specific enough that someone could observe it happening.

Then work backward to figure out what you need to measure.

This isn’t just philosophical. It changes which tools you use in each DMAIC phase. It changes which stakeholders you interview. It changes how you define control limits in the Control phase.

Your project might still fail, but at least it will fail for the right reasons.

Getting Your Next Project Right

If you’re leading Lean Six Sigma projects that deliver impressive process metrics but questionable business results, the problem isn’t your technical skills. It’s your starting point.

I work with teams who want to fix this foundation before they waste months optimizing the wrong things. We can help you design customer-first project charters that actually drive business outcomes, not just pretty charts.

Ready to stop measuring everything except what matters? Let’s talk about what customer-centered process improvement looks like for your specific projects. Book a call and bring your current project charter. I’ll show you exactly where the gaps are.