We welcomed a total of 8 members at tonight’s user group meeting. We broke into 2 groups and these are the results from our discussion about establishing measurement system analysis for problems and/or process difficult to measure.
Some examples of difficult to measure process:
· Subjective items (such as price, perception of value, pain, taste, spice, etc.) – for example, mild salsa in Texas is different than mild Salsa in the mid-west
Some examples of difficult to measure problems:
· Why do people leave a web site
· Moral, team work
· Behavior based
· People based – perception
o (talk about perception mapping may be important here)
Answers…..
Group 1:
1. If it’s a problem: you need to define the problem first
2. If it’s a process: you need to ask, why are you measuring something first
3. Then figure out the method you’re using to measure
4. Ability to quantify circumstances –(attributes) (Define what you can and can’t control)
5. Sampling method – make sure you have a good sample
6. Gauge R&R
7. Observe the process…. And how the measuring process is performed.
8. Clear operational definitions – what makes it a pass or fail.
Group 2:
1. Define why measuring
2. Indentify key points of interest
3. What is the most effective level to measure to
4. (sometime you want work out the high level and let the lower level work itself out)
5. Who does the measuring? Who sets the goals and who is tracking?
a. Question asked: why does it matter who does the measuring? People are more motivated to achieve that goal if they are self-measuring the goals. – trust but verify
6. Identify the most effective level and measure/analyze
7. How many times should one measure?
Let’s move from ambiguity to data!
Thanks to everyone who attending tonight. Next month's discussion may be a case study -- that's Dan for great suggestion. We're going to try to make it happen.
Join us next month - we meet the 2nd thursday of the month in Blue Ash. www.isssc3.com
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment