Improvement tools - Best practices - Including Mind Maps vs. Fishbone

[Claes Gefvenberg]

Considering the emphasis ISO 9001:2000 puts on improvement, this forum appears strangely quiet. Let's get it going. I want to discuss tools and techniques, so let's do a little web based brainstorming here.

To start things off:

I briefly mentioned using mindmaps instead of fishbone (Cause and effect) diagrams in another thread. I consider mindmaps to be great tools. Now I'm out fishing for new ideas.

1. Can you provide me with more examples on creative use of mindmaps?

2. How about other good tools and techniques? Come on now, I know there is bags of good stuff to find among the cove dwellers. What are you using, and how?

/Claes

 

[M Greenaway]

Claes

We use FMEA, as described in the QS9000 Manuals, a very useful tool to quantify the risks once you have brainstormed and come up with your fishbone's.

 

[Claes Gefvenberg]

M Greenaway said:

Claes

We use FMEA, as described in the QS9000 Manuals, a very useful tool to quantify the risks once you have brainstormed and come up with your fishbone's.

Hi Martin,

Yes, I agree. FMEA is an absolutley brilliant tool. And while we're on about FMEA: Lets say we're looking at 8.5.3 in ISO 9001:2000: Preventive action:

When the key processes have been identified, I'd say that they form a great input for process FMEA's, and the resulting actions would indeed be true preventive actions. Has any of you used them as such?

/Claes

 

[Claes Gefvenberg]

Jim Wade said:

----X----
Technique: if you have problem, figure out what it is before you start solving it; get the opinions of others involved in the problem and its eventual solution. Get the problem written down and agreed by those 'stakeholders'.
----X----

Absolutley right. All too often we start taking action without knowing or agreeing on what the true problem is...

More? Come on now, the rest of you...

/Claes

 

[Mike S.]

How about throwing a pinch of DOE into the improvement tool soup?

 

[M Greenaway]

What no FMEA ?

 

[M Greenaway]

WLMEC ??

 

[Claes Gefvenberg]

Aaargh... I fell for that WLMEC trick too. We've been had, martin...

Ok... Assume we're considering a new product.
What techniques / tools would you use?

/Claes

 

[M Greenaway]

Thats why I had never heard of it

 

[johnnybegood]

In resolving quality issue, we use Pareto chart. Our team have mix opinion as to which issue should be address first. ....the highest in the Pareto (normally take longer time to resolve) or the vital few (which can be resolve much shorter time). Let say the highest in the Pareto cause 20 dpku and this takes time to resolve versus 5 vital few which add-up 15 dpku and take much shorter time to resolve. Question is which issue should be the priority? In generall people will for for the highest Pareto but if we go for the vital few will ISO auditor question why we choose the vital few and not the highest in the Pareto?