{domain:"www.qualitydigest.com",server:"169.47.211.87"} Skip to main content

        
User account menu
Main navigation
  • Topics
    • Customer Care
    • Regulated Industries
    • Research & Tech
    • Quality Improvement Tools
    • People Management
    • Metrology
    • Manufacturing
    • Roadshow
    • QMS & Standards
    • Statistical Methods
    • Resource Management
  • Videos/Webinars
    • All videos
    • Product Demos
    • Webinars
  • Advertise
    • Advertise
    • Submit B2B Press Release
    • Write for us
  • Metrology Hub
  • Training
  • Subscribe
  • Log in
Mobile Menu
  • Home
  • Topics
    • Customer Care
    • Regulated Industries
    • Research & Tech
    • Quality Improvement Tools
    • People Management
    • Metrology
    • Manufacturing
    • Roadshow
    • QMS & Standards
    • Statistical Methods
    • Supply Chain
    • Resource Management
  • Login / Subscribe
  • More...
    • All Features
    • All News
    • All Videos
    • Contact
    • Training

Avoiding a Lean Six Sigma Project Failure, Part 2

Using the critical-to-quality (CTQ) tree

Carly Barry
Thu, 09/26/2013 - 10:58
  • Comment
  • RSS

Social Sharing block

  • Print
Body

In part one, I discussed how to avoid a lean Six Sigma project failure, specifically if the reason behind the failure is that the project solution never gets implemented. Now let’s discuss a few other project roadblocks that prevent teams from completing projects and some suggestions for overcoming them from Minitab trainers.

ADVERTISEMENT

Is the project scope too large?

One common reason quality improvement projects get started on the wrong foot is that their scope is too large. One of our customers provided us with a great example.

In this particular case, the customer’s project goal was to “improve the profitability of the company’s South American Division.” In theory, this sounds like a pretty good project goal, but when they actually began work on the project, the project team needed to hone in on that broad goal to work on something less vague and more specific—not to mention measurable.

To help the team drill down to a more concrete project goal, they created a critical-to-quality (CTQ) tree:

 …

Want to continue?
Log in or create a FREE account.
Enter your username or email address
Enter the password that accompanies your username.
By logging in you agree to receive communication from Quality Digest. Privacy Policy.
Create a FREE account
Forgot My Password
Top Stories
Your First 12 Months of ISO 9001:2026 Transition: An Auditor’s Perspective
Why Remote Work Isn’t Working
A Blueprint for Keeping Humans in Control of AI
A Passing Gauge R&R Doesn’t Mean the Measurement System Is Capable
Don’t Buy the Fix Before You Find the Problem

Add new comment

Please login to comment.

© 2026 Quality Digest. Copyright on content held by Quality Digest or by individual authors. Contact Quality Digest for reprint information.
“Quality Digest" is a trademark owned by Quality Circle Institute Inc.

footer
  • Home
  • Print QD: 1995-2008
  • Print QD: 2008-2009
  • Videos
  • Privacy Policy
  • Write for us
footer second menu
  • Subscribe to Quality Digest
  • About Us
  • Contact Us