Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Way of the Quality Warrior
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • Quality Engineering Statistics
    • An Introduction to Reliability Engineering
    • Reliability Engineering for Heavy Industry
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Dianna Deeney Leave a Comment

QDD 128 Leveraging Proven Frameworks or Concept Development

Leveraging Proven Frameworks or Concept Development

Ready to sharpen your toolset with the wisdom of ancient warriors?

Today’s episode includes knowledge to guide your journey into the world of quality tools and reliability frameworks. Drawing inspiration from the seven weapons of warrior monk Benkei, we introduce the first seven quality tools collected by industry quality professional, Ishikawa. Discover how these types of tools, more typically used for monitoring and continuous improvement, can also be leveraged for early concept development, thus leading to successful product designs.

For those seeking to put theory into practice, we delve into a strategic system model that centers on customer inputs, intended and unintended outputs, and the use process, demonstrating how these tools can be applied to concept development. By the end of this episode, you’ll have a deeper understanding of how quality thinking can revolutionize your product design and development process.

 

View the Episode Transcript

ADEPT Quality Tools Focus on the User for Early Work

 

ADEPT teams work early, using quality methods to align their knowledge, discover through prompted activities to enhance ideas and prioritize them.

Even though we’re exploring this outside customer space at concept development, we’re still focused on what we need to be able to make design decisions. This is how quality tools can help with design and creation. Quality tools can be graphical, they can be prompted and they can be iterative. You can also scale them to what is needed for the project. We use what makes sense for what we need and then we can iterate on the things that are most impactful or for the questions that we still have to do more.

ADEPT for concept development:

  • Align the team against the users and the user needs, or comparing ideal versus actual, or which need for which user.
  • Discover hidden needs and interfaces.
  • Examine use experiences for design inputs.
  • Prioritize parts of the use process.
  • Teamwork to bring-in cross-functional experiences and collaboration opportunities.

What’s today’s insight to action? In early concept development, we don’t have a lot to talk about. One of the solutions that we try is to jump ahead and start designing solutions so that we can have something to talk about, something to edit and something to move forward with and to discuss. That’s where we get into the trouble of not really exploring the problem space enough to start designing. Instead of designing something to talk about, we can use quality tools as a substitute. Quality tools are, by nature, graphical, they’re very adaptable and they’re very approachable for teams to be able to use to explore ideas. They’re the perfect kind of tool to start developing design inputs from concepts, from high level ideas.


Other Quality during Design podcast episodes leading up to this episode:

Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

Understanding Cross-Functional Collaboration


Episode Transcript

In the quality world we have a lot of quality tools and frameworks and reliability methods that we use for monitoring and for continuous improvement. Did you know that design teams and cross-functional teams can use many of these same tools for design and creation?

Welcome back to Quality During Design. In the last two episodes we’ve been talking about the product designer’s role in early concept development, how we want to stay in the problem space a little bit longer, and the benefits and challenges and how to overcome the challenges of working with our cross-functional team and cross-functional collaboration in that early concept development.

Today, we’re talking about leveraging proven quality and reliability frameworks for concept development. We’re going to be talking about how we can adapt these frameworks to drive effective conversations about an idea. Listen in to learn more after this brief introduction.

Hello and welcome to Quality During Design, the place to use quality thinking to create products others love for and less. Each week, we talk about ways to use quality during design and product development. I’m your host, Dianna Deeney. I’m a senior-level quality professional and engineer with over 20 years of experience in manufacturing and design. I consult with businesses and coach individuals on how to apply quality during design to their processes. Listen in and then join us. Visit qualityduringdesigncom.

Just a few weeks ago, I was a guest on a webinar series with Scott Abel, The Content Wrangler, and Herreto. I was talking to technical communication experts about using flowcharts for their product designs, for instructions, user manuals and other user interfaces that technical writers get involved with. Today’s episode is an excerpt from that webinar. I talk about the history of quality tools, why we call them that, how they’re used, how we can use them for design and creation. If you’d like to see the webinar episode itself, or you can see the slides that I was using to talk against sometimes, visit qualityduringdesign.com. You’ll see a link to that workshop that I gave. You can sign up for a free account and view the recorded webinar. Now let’s get into how we can leverage proven quality frameworks for concept development.

Now about quality tools. I usually get a question about what is a quality tool. I don’t understand why you call it that, and I also get an understanding from people that well, why are you doing quality early? Isn’t that checking parts at the end of the assembly line? Aren’t you measuring parts and deciding if they’re good or bad?

So let me tell you a little bit about the history of quality tools. Kaoru Ishikawa was really active in the quality world in the 1950s and 60s, but he was still publishing up until the 1980s. He was in Japanese industry and a lot of quality professionals know who he is. He’s like one of the grandfathers of quality and he had published and he promoted these seven basic quality tools and said that as much as 95% of all quality related problems in the factory can be solved with these seven tools. Now the story has it is that he picked seven as the seven tools because he had in mind the story of the seven weapons of Benkei. Benkei was a warrior monk that lived in the 1100s. He’s depicted as very strong and loyal and he’s still depicted in some current productions today, like in anime and in video games, and I also saw a reference about him being in an American detective show, but I couldn’t find any more about that. I don’t know any more about him being part of a detective show, but he did have seven weapons, which is why we think that Ishikawa referenced the seven quality tools.

So here are the first seven, or the old seven that Ishikawa really promoted is on the left hand side, and you’ll hear quality practitioners talk about them as the first seven when things have been around for a long time after about 80 or so years, there’s going to be development and new people are going to get involved. So now we have the seven plus basic quality tools. Scott and I were talking a little bit earlier. These tools don’t really give you a solution. They are a way for you to investigate problems, have discussions so that you can get the information together to be able to make a decision. So think of them as tools in a toolbox. You wouldn’t want to use a hammer on everything you get to choose the tool that’s going to make the most sense to help you solve a problem.

Knowing the story of Benkei and the origin of these seven quality tools, you do get the impression that it’s more of a warrior type of thing, that we are attacking problems and we are, you know, getting rid of things that cause bad quality, and a lot of people do think of quality as monitoring and continuous improvement. But I’ve learned through my working journey that quality tools can also be used for design and creation. Let me tell you what I mean. When we’re thinking about designing a product, you know, when we go from, “Hey, we have a problem!” and we start thinking about the solution. We kind of think about this simple model: our design, or whatever it is that we’re working on, is in the middle in the square, and then we have inputs and then it’s outputting something. But we focus in on that system model when really what we need to do is develop less solutions around that system and do more discovery about what’s going on around the system. If we take a big step back, we can use little bees to represent our customers and they’re really on the outside of our design, which is the way it should be.

  • We have at the beginning of their inputs. We’re meeting our customers somewhere. They have certain conditions and they have assumptions where there’s some place, where they are and we want them to be able to use our products so they can be somewhere else. And that is where the intended outputs come into play.
  • When our design works the way it should, our customers are going to see benefits,
  • and when our design doesn’t work like it should, they’re going to have experiencing symptoms to the problem.
  • And, of course, at the top is what I call the the use process. We want our users to go from A to B, to have some sort of a journey, and they’re going to be interacting with our product to be able to take that journey.

Ultimately, we don’t want to stay in the outside. We do need to get to work and actually get a design done. So we’re. Even though we’re exploring this outside customer space, we’re still focused on what we need to be able to make design decisions, and this is how quality tools can help with design and creation. Quality tools can be graphical, they can be prompted and they can be iterative. You can also scale them to be what it is.

  • You need Alignment exercises, for the team could be getting alignment on the users and the user needs, or comparing ideal versus actual, or which need for which user.
  • We can discover hidden needs and interfaces.
  • We can examine use experiences for design inputs
  • and we can prioritize parts of the use process.

So ADEPT teams work early, using quality methods to align their knowledge, discover through prompted activities to enhance ideas and prioritize them. What are your early concept working team meetings like? So somebody has come up with idea and then everybody decides let’s get together and talk about what to do with this idea. There isn’t a whole lot to talk about, right? You haven’t designed anything yet, which I think is one of the itches for a lot of people, skipping that middle, second half of the problem space. We don’t know what to talk about, there’s nothing to talk to or examine, whereas we can use quality tools as a substitute for that.

We’re using quality tools to explore the use space and we can talk to it and talk against it, and today we’re specifically going to be talking about using flow charts as the quality tool to be able to work with our team to do early problem space discovery. I have my initial seven to get started and then I have the second seven to iterate, and there are a lot of tools on this list but again, we don’t use them all. We use what makes sense for what we need and then we can iterate on the things that are most impactful or for the questions that we still have to do more. If some of you work in regulated industries, you might recognize some of these tools as being required use anyway.

So what’s today’s insight to action? In early concept development, we don’t have a lot to talk about. One of the solutions that we try is to jump ahead and start designing solutions so that we can have something to talk about, something to edit and something to move forward with and to discuss. That’s where we get into the trouble of not really exploring the problem space enough to start designing. Instead of designing something to talk about, we can use quality tools as a substitute. Quality tools are, by nature, graphical, they’re very adaptable and they’re very approachable for teams to be able to use to explore ideas. They’re the perfect kind of tool to start developing design inputs from concepts, from high level ideas.

Tune in next week while I will share some practical tips of how you can apply some quality frameworks to get those design inputs and also to prioritize them based on the user. As always, qualityduringdesign.com has a blog associated with this podcast. Visit it for transcripts and extra links. And just a reminder if you wanted to view the recorded workshop, go to qualityduringdesign.com slash workshops for the link. This has been a production of Deeney Enterprises. Thanks for listening.

Filed Under: Quality during Design

About Dianna Deeney

Dianna is a senior-level Quality Professional and an experienced engineer. She has worked over 20 years in product manufacturing and design and is active in learning about the latest techniques in business.

Dianna promotes strategic use of quality tools and techniques throughout the design process.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Quality during Design podcast logo

Tips for using quality tools and methods to help you design products others love, for less.


by Dianna Deeney
Quality during Design,
Hosted on Buzzsprout.com
Subscribe and enjoy every episode
Google
Apple
Spotify

Recent Episodes

QDD 128 Leveraging Proven Frameworks or Concept Development

QDD 127 Understanding Cross-Functional Collaboration

QDD 126 Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

QDD 125 Exploring Product Development and AI Through Literature

QDD 124 Design for User Tasks using an Urgent/Important Matrix

QDD 123 Information Development in Design, with Scott Abel – Part 2 (A Chat with Cross-Functional Experts)

QDD 122 Information Development in Design, with Scott Abel – Part 1 (A Chat with Cross-Functional Experts)

QDD 121 Crafting Effective Technical Documents for the Engineering Field

QDD 120 How to use FMEA for Complaint Investigation

QDD 119 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 118 Journey from Production to Consumption: Enhancing Product Reliability

QDD 117 QDD Redux: Choose Reliability Goals for Modules

QDD 116 Reliability Engineering during Design, with Adam Bahret (A Chat with Cross-Functional Experts)

QDD 115 QDD Redux: 5 Options to Manage Risks during Product Engineering

QDD 114 The Instant Glory of Projects

QDD 113 What to do about Virtual Meetings

QDD 112 QDD Redux: How to self-advocate for more customer face time (and why it’s important)

QDD 111 Engineering with Receptivity, with Sol Rosenbaum (A Chat with Cross-Functional Experts)

QDD 110 Don’t Wish for Cross-Functional Buy-in on Product Designs – Plan to Get It!

QDD 109 Before You Start Engineering Solutions, Do This

QDD 108 QDD Redux Ep. 4: Statistical vs. Practical Significance

QDD 107 QDD Redux Ep. 3: When it’s Not Normal: How to Choose from a Library of Distributions

QDD 106 QDD Redux Ep. 2: How to Handle Competing Failure Modes

QDD 105 QDD Redux Ep. 1: How Many Do We Need to Test?

QDD 104 The Fundamental Thing to Know from Statistics for Design Engineering

QDD 103 What to do for Effective and Efficient Working Meetings

QDD 102 Get Design Inputs with Flowcharts

QDD 101 Quality Tools are Legos of Development (and Their 7 Uses)

QDD 100 Lessons Learned from Coffee Pod Stories

QDD 099 Crucial Conversations in Engineering, with Shere Tuckey (A Chat with Cross-Functional Experts)

QDD 098 Challenges Getting Team Input in Concept Development

QDD 097 Brainstorming within Design Sprints

QDD 096 After the ‘Storm: Compare and Prioritize Ideas

QDD 095 After the ‘Storm: Pareto Voting and Screening Methods

QDD 094 After the ‘Storm: Group and Explore Ideas

QDD 093 Product Design with Brainstorming, with Emily Haidemenos (A Chat with Cross Functional Experts)

QDD 092 Ways to Gather Ideas with a Team

QDD 091 The Spirits of Technical Writing Past, Present, and Future

QDD 090 The Gifts Others Bring

QDD 089 Next Steps after Surprising Test Results

QDD 088 Choose Reliability Goals for Modules

QDD 087 Start a System Architecture Diagram Early

QDD 086 Why Yield Quality in the Front-End of Product Development

QDD 085 Book Cast

QDD 084 Engineering in the Color Economy

QDD 083 Getting to Great Designs

QDD 082 Get Clarity on Goals with a Continuum

QDD 081 Variable Relationships: Correlation and Causation

QDD 080 Use Meetings to Add Productivity

QDD 079 Ways to Partner with Test Engineers

QDD 078 What do We do with FMEA Early in Design Concept?

QDD 077 A Severity Scale based on Quality Dimensions

QDD 076 Use Force Field Analysis to Understand Nuances

QDD 075 Getting Use Information without a Prototype

QDD 074 Finite Element Analysis (FEA) Supplements Test

QDD 073 2 Lessons about Remote Work for Design Engineers

QDD 072 Always Plot the Data

QDD 071 Supplier Control Plans and Design Specs

QDD 070 Use FMEA to Design for In-Process Testing

QDD 069 Use FMEA to Choose Critical Design Features

QDD 068 Get Unstuck: Expand and Contract Our Problem

QDD 067 Get Unstuck: Reframe our Problem

QDD 066 5 Options to Manage Risks during Product Engineering

QDD 065 Prioritizing Technical Requirements with a House of Quality

QDD 064 Gemba for Product Design Engineering

QDD 063 Product Design from a Data Professional Viewpoint, with Gabor Szabo (A Chat with Cross Functional Experts)

QDD 062 How Does Reliability Engineering Affect (Not Just Assess) Design?

QDD 061 How to use FMEA for Complaint Investigation

QDD 060 3 Tips for Planning Design Reviews

QDD 059 Product Design from a Marketing Viewpoint, with Laura Krick (A Chat with Cross Functional Experts)

QDD 058 UFMEA vs. DFMEA

QDD 057 Design Input & Specs vs. Test & Measure Capability

QDD 056 ALT vs. HALT

QDD 055 Quality as a Strategic Asset vs. Quality as a Control

QDD 054 Design Specs vs. Process Control, Capability, and SPC

QDD 053 Internal Customers vs. External Customers

QDD 052 Discrete Data vs. Continuous Data

QDD 051 Prevention Controls vs. Detection Controls

QDD 050 Try this Method to Help with Complex Decisions (DMRCS)

QDD 049 Overlapping Ideas: Quality, Reliability, and Safety

QDD 048 Using SIPOC to Get Started

QDD 047 Risk Barriers as Swiss Cheese?

QDD 046 Environmental Stress Testing for Robust Designs

QDD 045 Choosing a Confidence Level for Test using FMEA

QDD 044 Getting Started with FMEA – It All Begins with a Plan

QDD 043 How can 8D help Solve my Recurring Problem?

QDD 042 Mistake-Proofing – The Poka-Yoke of Usability

QDD 041 Getting Comfortable with using Reliability Results

QDD 040 How to Self-Advocate for More Customer Face Time (and why it’s important)

QDD 039 Choosing Quality Tools (Mind Map vs. Flowchart vs. Spaghetti Diagram)

QDD 038 The DFE Part of DFX (Design For Environment and eXcellence)

QDD 037 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 036 When to use DOE (Design of Experiments)?

QDD 035 Design for User Tasks using an Urgent/Important Matrix

QDD 034 Statistical vs. Practical Significance

QDD 033 How Many Do We Need To Test?

QDD 032 Life Cycle Costing for Product Design Choices

QDD 031 5 Aspects of Good Reliability Goals and Requirements

QDD 030 Using Failure Rate Functions to Drive Early Design Decisions

QDD 029 Types of Design Analyses possible with User Process Flowcharts

QDD 028 Design Tolerances Based on Economics (Using the Taguchi Loss Function)

QDD 027 How Many Controls do we Need to Reduce Risk?

QDD 026 Solving Symptoms Instead of Causes?

QDD 025 Do you have SMART ACORN objectives?

QDD 024 Why Look to Standards

QDD 023 Getting the Voice of the Customer

QDD 022 The Way We Test Matters

QDD 021 Designing Specs for QA

QDD 020 Every Failure is a Gift

QDD 019 Understanding the Purposes behind Kaizen

QDD 018 Fishbone Diagram: A Supertool to Understand Problems, Potential Solutions, and Goals

QDD 017 What is ‘Production Equivalent’ and Why Does it Matter?

QDD 016 About Visual Quality Standards

QDD 015 Using the Pareto Principle and Avoiding Common Pitfalls

QDD 014 The Who’s Who of your Quality Team

QDD 013 When it’s Not Normal: How to Choose from a Library of Distributions

QDD 012 What are TQM, QFD, Six Sigma, and Lean?

QDD 011 The Designer’s Important Influence on Monitoring After Launch

QDD 010 How to Handle Competing Failure Modes

QDD 009 About Using Slide Decks for Technical Design Reviews

QDD 008 Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.

QDD 007 Need to innovate? Stop brainstorming and try a systematic approach.

QDD 006 HALT! Watch out for that weakest link

QDD 005 The Designer’s Risk Analysis affects Business, Projects, and Suppliers

QDD 004 A big failure and too many causes? Try this analysis.

QDD 003 Why Your Design Inputs Need to Include Quality & Reliability

QDD 002 My product works. Why don’t they want it?

QDD 001 How to Choose the Right Improvement Model

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy