Category Archives: Quality Tools

8 Mistakes Your QMS Makes

not one of the 8 Mistakes, but not a good one to make
Too Highbrow?

8 Mistakes
A Quality Management System – any management system, is only as good as the sum of its parts. Lots of things go right, and we all try our best. Yet, out in the world I see the same mistakes over and over again. I want to share those things with you now.

Here they are, in a particular order.

1st of 8 Mistakes: Focusing on Manufacturing

A business is a complicated thing. No kidding, it really is. But it is too easy to think that the sections of it that appear to actually produce tangible objects are the most important. Quite simply – it’s all important.

The more you want to get the most out of everything you’ve got, the more important everything you’ve got becomes.  If you own a racehorse (and who doesn’t?) it’s easy to think the galloping equine beast is the main… workhorse. But what about the shoes, and the guy who puts them on? (it’s a farrier, but that sounds highfalutin, so I didn’t say it).

And there’s the jockey- and the jockey’s Jockeys, the nutritionist, stable boy – and a whole slew of influential entities. If any of those are non-optimal, do you think the whole system can be optimal?

Many companies I go to have continual improvement projects related to assembly areas but neglect sales departments, or purchasing groups or human resource departments. There are always better ways of doing things, mostly because “better” is an evolving concept. Options need to be considered and tried out in all areas – not just manufacturing.

I’ll take a second to cover the frequent exception. Design functions, along with production, are often targeted for streamlining. Or rather, they become streamlined over time. It may be a stereotype, but engineers tend to find optimum paths somewhat organically. Or they are at least interesting paths.

This may be influenced by two factors. One is that 9001 and the related standards that share design and development pieces with it, provide a good skeleton that hasn’t really changed in lots of years. It’s just might be a  common-sense starting point or the successful modifications to it have traveled from company to company along with the migrations of engineers.

The other factor is, I believe, the cerebral nature of the activity itself. When you get a bunch of brains focused on development, the tendency for self-development; the development of the organism that’s developing – is a genetic inclination. It’s a bit like cleaning your office instead of working – but in a good way.

There’s more to businesses than design or manufacturing; opportunities for improvement abound. One of my favorite quotes encapsulates and summarizes this idea well, “How you do anything, is how you do everything.”

2: Fixing Problems Without Understanding Cause

Up here in the Great White North, we like to think we have “Yankee Ingenuity”. We’re really good at fixing things using creative approaches. Duct tape and elbow grease.

But sometimes we spend lots of effort on the solution, and not enough resource figuring out why the problem happened in the first place. Fortunately, when the problem happens again – we can fix it right quick. Third time’s the charm! Sound familiar?

Some of this is because each of us carries a sort of personal toolbox. We tend to do the things we’re good at. One apt phrase is, “When you know how to use a hammer, everything looks like a nail.”

Fortunately, not only are there different types of hammers, there are other tools that can be brought to good use (what did you call me?!). These help an organization get to the root of the problem, or to a main cause. Since each of them could span a blog entry of their own I won’t do much more than list them here.

  • 5 Whys Analysis – Asking “why” multiple times until the culprit is found. Make it so the culprit can’t come back
  • Change Analysis – Won’t always generate root cause, but will arrive at a cause. Six step process worthy of further investigation.
  • Barrier Analysis – Identifies barriers used to protect a target from harm. The terms are flexible; think shoe/foot/glass. Glass is the threat, shoe is the barrier, foot is the thing to protect. Foot is cut – how, specifically, did the shoe fail?
  • Ishikawa (fishbone) diagrams – or any kind of tree diagram. In general, each branch of the tree, or each branching bone of the fish, adds to the understanding of the factors involved. By understanding the factors, countermeasures can be considered.

And on and on – There are so many tools available it just doesn’t make sense to start with a solution that may have nothing to do with the problem.

3: Too Many Corrective Actions

While it may seem counter-intuitive to a continual improvement mindset – it really isn’t. A mature management system is very good at collecting data, then by analyzing that data, it can target areas for improvement.

Writing a NCMR (Non-Conforming Material Report) as if it was a CAR (Corrective Action Request) is a terrible resource-waster. Do this instead when you find nonconforming material:

  • Capture the data and look for common failure modes
  • Create a set list of failure modes (you may need to adjust this over time)
  • Make a Pareto chart of the failure modes
  • Create a CAR for the big hitter.
  • Do it again for the next biggest hitter.

If you find the same issues continue to arise then see Mistake number 2, above.

Corrective actions are indeed that avenue to improvement but they need to rise above the level of the noise. The noise is the inherent variability in the system; few things are perfect.

Find the trends, then with a healthy use of the corrective action tools like those listed above – focus the limited resources toward determining root cause.

4: Not Auditing Internal Audits

Internal audits should be deep, and thorough and, dare I say – brutal.  With internal audits, you won’t make any friends by making friends. Tough love.

The whole system should be checked against existing procedures (documented, or not) and against the requirements of your standard of choice.

The audits should be planned, that plan should be based on some analysis of the status and importance of the areas to be audited.

They should be carried out by qualified individuals who are independent of the function being audited. When problems arise, those corrective actions must be taken without undue delay and the cause of the findings corrected and verified as effective.

Sounds lovely, doesn’t it? Not only do you need to do those things in order to have an effective internal audit program – but the standard requires that you do those things.

A frequent “gotcha” here is if you have a contractor perform your audits. One of the rules is that the auditor must be independent of the thing being audited. Sometimes the contracting company can provide another auditor specifically to audit that function – that could work. Or, you could, given the proper training and procedure, audit the internal audit process as part of Management Review.

Or you could have someone internal to the company and from a department typically outside of the QMS – like accounting, do the audit of audits.

If the audit process itself isn’t checked to make sure it continues to do all of the above, then all of your credibility goes straight out the window. And in through the front door comes a written nonconformance from your friendly ISO auditor.

5: No Dashboard, No Goals

For this, I refer you to last week’s post on Quality Metrics.

A Dashboard is simply a frequently updated collection of the upper level metrics presented in a way that is quickly and easily digested. Goals for these metrics should be evident. Where the trend of the data is moving significantly away from the goal then there should be an action plan to adjust the trend.

Action plans have owners, they have something that needs doing – and they have accountability.

Sometimes the dashboard includes a collection of charts along a frequently traveled hallway. Who needs to see these things? Anyone that can influence the data – that often means everyone in the organization.

If you do have one of these metrics boards/dashboards do make sure the date is current please.

Nothing says “We really don’t care what’s going on, nor do we care if no one else knows what’s going on” like charts that are four months out of date.

Am I preaching to the choir? Sing with me, my friend.

6: Rework Without Collecting Data

This is fairly common, meaning I see it once or twice a month (I do somewhere around a hundred audits a year; three to five audit days per week).

Example? Take a manufacturing floor, someone builds something – let’s use a contract manufacturer. The assembler does his job and sends it off to an in-process or final inspection step.

The inspector does a nice inspection, using documented and established inspection criteria. They find a missing screw – and record it on their inspection sheet or enter it into a database. They have a box of the correct screws and they correct the problem. Fine – no issues there (ideally yes, someone else checks the fix).

Then they find another screw that’s a bit loose – not that loose, really. They tighten it down. They begin to look at the cosmetic criteria – looks good.

Oops. That loose screw should have been recorded, right? Maybe that missing screw started out as loose (I blame the parents).

This happens more often when everyone is really friendly and there are penalties for failure. So, when Maria in inspection finds something Mary in assembly missed – Maria fixes it and nobody gets hurt. Except the reliability of the product and cost of assembly.

Either make sure nobody likes each other, or don’t attach a stigma to making mistakes (or mistake proof the process!). I’ll leave it up to you to choose.

7: Big Meetings Without Action Items

I’ll keep this one real short.

Don’t have a meeting without action items. A meeting without action items is called e-mail.

I said “Big” meetings; if two or three people need to exchange data verbally, fine. You define “big”.

Let me assert that Management Review meetings are big meetings. Please have action items.

If you have a meeting, and it turns into a status meeting – and everything looks good, then take the opportunity to change the definition of “good” to “great”.

Change the specification, or bring in the date – at least look at the feasibility of doing it better. If you feel like you’re already at “great” then re-allocate a resource, record some “lessons learned”.

Continual Improvement, my friend, generates Actions.

8th of 8 Mistakes: Taking Classes But Not Learning

Most courses and seminars are PowerPoint snooze-fests in over-air-conditioned rooms where you’re lucky to have a quiz at the end of four days. Just because the data is presented to you – doesn’t mean it has been taught to you, or that you have learned  it.

But yes, the lemon Danish was awesome and hey, you got a Certificate.

Certificates are nice, but skills and knowledge brought back to the work environment are like bars of gold-pressed latinum. Time and money are being spent- why not learn something?

Even if you’re a conscientious student executing the study habits that got you through high school or college – you could be retaining a whole lot more.

To most people, underlining and highlighting, rereading, cramming, and single-minded repetition are the extent of their learning repertoire. Recent studies have shown clearly that these skills create the illusion of mastery, and that any gains fade quickly.

Durable learning comes from things like:

  • self-testing,
  • introducing difficulties in practice,
  • waiting to re-study new material until a little forgetting has set in,
  • interleaving the practice of one skill or topic with another.

That’s basically the introductory paragraph of the book, Make It Stick: The Science of Successful Learning. I’ve read that book – it is an enlightening and inspiring read.

While there is a wealth of vital material on the internet, and within the corporate training rooms (and those freezing hotel conference rooms), most of it is simply that – material.

Learning is really your responsibility, you can’t rely on an instructor to do it for you.  Read. That. Book.

 

Thank you for listening, I hope you got something useful from the 8 common QMS Mistakes I see regularly. I’d love to hear back from you with something from your own list of painful things.

Sal

 

 

Metrics 2 – How To’sday

Mouse MetricsLast How To’sday we introduced the topic of metrics and half of the Why of it – namely, “because it makes sense”.

This week, the other Why, “because it’s required” is covered – it means putting a little more focus on Objectives, but metrics are at the core of that.

Lastly, we’ll make a good start at examples of metrics by looking at a typical suite of HR measureables.

Where are the Requirements?

Within 9001:2008

Let’s start with ISO 9001:2008 as it is representative of the requirement within several other standards. Mainly, there’s this:

4.2 Documentation requirements
4.2.1 General
The quality management system documentation shall include

a) documented statements of a quality policy and quality objectives,
b) a quality manual…

This section requires that objectives be documented, and by documented this means according to the methods described in 4.2.3 Control of documents.

So, objectives are in the same documentation category as your Quality Manual, the Quality Policy and all of the required procedures as stated in the standard.

I thought we were talking about metrics? As covered in the last installment, metrics are the method by which performance to an objective is measured. Can’t discuss objectives, without touching metrics.

5.4.1 Quality objectives
Top management shall ensure that quality objectives, including those needed to meet requirements for product…, are established at relevant functions and levels within the organization. The quality objectives shall be measurable and consistent with the quality policy.

One key point here is, “established at relevant functions and levels within the organization“. So, if a function doesn’t have at least one objective, an organization would have to make the claim that the function isn’t relevant. If it isn’t relevant – why is it there?

And to underscore the point of what a metric is, the section also contains, “The quality objectives shall be measurable“.

I do realize that may present a slight contradiction to what is stated in ISO 9000:2005 (Definitions) as it says, under the term (3.5.1) distinguishing feature (a component of an objective), “A characteristic can be qualitative or quantitative.

We’ll have to assume that a qualitative characteristic is measurable. I guess that’s what adjectives are for. Don’t worry, that potential disconnect is the least of your worries.

These Metrics are Out of Control

Objectives are built into PDCA

Also, within 9001:2008 is a discussion of the Plan-Do-Check-Act (PDCA) process. In the description of “Plan” it states:

“establish the objectives and processes necessary to deliver results in accordance with customer requirements and the organization’s policies.”

And for “Check”, it adds:

“monitor and measure processes and product against policies, objectives and requirements for the product and report the results.”

Clearly, for an organization to be compliant with ISO 9001:2008, it must conform to the model presented by PDCA – a major component of the current version. Establishing objectives and monitoring performance against them via metrics is then a key management system component.

Annex SL

For the future, it’s wise to look toward Annex SL as a guide as this will cover many sectors – and it is built into the next version of ISO 9001.

Where is says, “XXX” it means “Insert management system nomenclature of choice here” – such as “Environmental” or “Quality” or “Safety“, etc.

6.2 XXX objectives and planning to achieve them
The organization shall establish XXX objectives at relevant functions and levels. The XXX objectives shall

  • be consistent with the XXX policy
  • be measurable (if practicable)
  • take into account applicable requirements
  • be monitored
  • be communicated, and
  • be updated as appropriate.

Nearly the same as 9001:2008, right? Those bullets are, with the exception of the last, accounted for within the current text in several places.

There’s a few helpful Notes further down the section as well:

NOTE 1 to entry:   An objective can be strategic, tactical, or operational.

NOTE 2 to entry: Objectives can relate to different disciplines (such as financial, health and safety, and environmental goals) and can apply at different levels (such as strategic, organization-wide, project, product and process (3.12)). 

NOTE 3 to entry:   An objective can be expressed in other ways, e.g. as an intended outcome, a purpose, an operational criterion, as an XXX objective or by the use of other words with similar meaning (e.g. aim, goal, or target).

Some Actual Metrics

Here’s a look at the possibilities. Not all of these are suitable for all organizations and the list isn’t exhaustive.

And, just like more rivets won’t make an airplane stronger, the full collection isn’t something to “strive for”. Some of these may even be mutually exclusive.

In no particular order – Here we go!

Human Resources

Timing related

  • Days to orientation training: Assumes must be done within X days,
  • Other required training completed on-time
  • Reviews done: (percentage)
  • Reviews late

Training Related

  • Percentage of required training completed: Forces a clearer definition of training requirements
  • Pass/Fail rate for verification of effectiveness: Are some methods better than others; can they be made better? Should everyone pass every time?
  • Trainer/Training satisfaction indexes: Are some trainings better than others… Ask the students.

Recruitment related

  • Interviews to offers ratio: Provides a measure of how efficient recruitment is. Track by manager to get data across departments, and which managers might need help.
  • Referral rates by department: Part of the new hiring process or even the exit interview (in some cases) – “Would you recommend [your company] to a friend?” Better to make it a scale from 1-5, for example.
  • Percentage of hires by source: For your business, is Monster better than LinkedIn? And so-on.

Retention related

  • Retention rate by type of employee: What are the  mission critical roles, or the day-to-day “getting it done”, or the “can find this role anywhere” types? Are you better at retaining some levels over others?
  • Resignation rates by department:  Not necessarily a reflection of a bad manager, there may be other factors at work.
  • Overall Monthly Turnover Rate: The standard calculation goes:  (number of departures during month divided by the average number of employees during month) x 100 to get the rate).

Performance Related

  • Revenue per Employee: Simply total revenue divided by total number of employees.
  • Human Capital Cost: Pay + Benefits + Contingent Labor Cost / Full Time associates.
  • HR to Staff Ratio: Employees / Human Resources Team Members. Essential if you ever want to justify departmental expansion.
  • Promotion Rate:  Promotions / Headcount.
  • Overtime per Individual Contributor Headcount: Overtime Hours/Individual Contributor Headcount.
  • Employee Absence Rate: Number of days in month / (average number of employees during month x number of days).

Demographic Related

Hires that meet certain demographic characteristics can reflect a broad spectrum of requirements, policies and philosophies. These metrics are not a means toward discrimination, but as a tool to determine progress toward a goal or objective.

  • Percentage [Females, Military Service, Race] by Management Level:  Can be essential when bidding some government contracts and to fortify positions with a given quality policy.
  •  Average Age of Employees: Consider breaking this down by department, management level – or both.

Until Next Week!

I hope you were able to find something useful in the HR list of metrics. And, with some luck, you’ve gained a broader understanding of why we need metrics at all.

Next week we’ll look at the other main departments within a typical organization – along with additional rationale behind their implementation.

Thanks again for reading.

Sal

Metrics – How To’sday

W. Edwards Deming

Collecting Metrics and tracking them is widely considered to be key to improvement – but the specifics are often elusive, particularly for relatively small organizations.

And, naturally, acting appropriately to the results is critical to improvement as well. We’ll touch on that, too. Eventually.

These posts (there will be at least two of them on the topic), while not providing an exhaustive list of departmental metrics, will provide at least a starting point for many.

The terms themselves are often used interchangeably, even if they clearly aren’t synonymous; metrics, KPIs, measurables, goals and objectives, dashboards…  where to begin?

Define Your Terms

Beyond dictionary and accepted terminology, ISO 9000:2005 “Quality management systems — Fundamentals and vocabulary” has formal definitions for a few of the key terms we’ll be using.

3.2.5 quality objective – something sought, or aimed for, related to quality (3.1.1)

3.1.1 quality – degree to which a set of inherent characteristics (3.5.1 – “distinguishing feature”) fulfils requirements (3.1.2 – “need or expectation that is stated, generally implied or obligatory”)

The next question is, “How does one measure progress against an objective?”

Fortunately, the 2nd note in ISO 9000:2005 under the term (3.5.1) distinguishing feature (a component of an objective) says, “A characteristic can be qualitative or quantitative.

Helpful or not, Note 3 goes on to state:

NOTE 3 There are various classes of characteristic, such as the following:

  • physical (e.g. mechanical, electrical, chemical or biological characteristics);
  • sensory (e.g. related to smell, touch, taste, sight, hearing);
  • behavioral (e.g. courtesy, honesty, veracity);
  • temporal (e.g. punctuality, reliability, availability);
  • ergonomic (e.g. physiological characteristic, or related to human safety);
  • functional (e.g. maximum speed of an aircraft).

Essentially, you can measure performance against an objective any way you wish – that performance measurement is what I am calling a metric.

Why have Metrics?

If an organization is going to spend time doing anything, particularly with metrics, then there should be a reason.

So, as with most Management System realities the two main reasons tend to be “Because it’s required” and “Because it makes sense”.

Let’s look at the latter first.

Because it makes sense.

Does it? You may be surprised to learn that not everyone agrees with managing via metrics, or at least, they would say that not everything of importance can be measured.

W. Edwards Deming (October 14, 1900 – December 20, 1993) was one who said it, in fact. Don’t know who Deming is?  Complicated man – almost legendary, possibly self-contradictory (the lens of history often does that to great men). He is thought to be one of the key figures helping Japan rise from the literal ashes after WWII. He gained popularity by expanding and championing concepts of Statistical Process Control, Plan-Do-STUDY-Act (PDSA) – and much, much more. I’d need a book to do him justice.

Side note – Deming was not a fan of the now common “Plan-Do-Check-Act” (PDCA). Notice the difference; “Study” vs “Check”. He called PDCA a “corruption”. His PDSA takes Study literally as deductive and inductive learning – it is built into a learning and improvement cycle. We’re getting a little far from the main topic, but I could expand on this more if anyone would like me to – leave a comment.

Here is a list of Key Deming Books. If you only have time to read one, many would recommend “Out of the Crisis“.

While Deming understood that not everything is measurable, and was quick to point out the dangers of slogans, thoughtless quotas and targets (such as “zero defects”) he still believed a system must be managed and that “There is no substitute for knowledge.” 

For the mere mortals among us, however, a reasonable place to start is by carefully selecting a set of solid process measurements to determine if something is improving – or not.

Another popular way to put it, “If it can’t be measured, it can’t be improved.” (sounds a bit like a slogan, doesn’t it? My apologies to Mr. Deming). That quote, by the way, isn’t attributed to Deming – it is a quote from Lord Kelvin (actually “William Thomson” of Belfast, 1824-1907). He was a mathematical physician and father of the first and second Laws of Thermodynamics. Next time you hear someone say Deming said it, please do let them know how unlikely that would be.

Anyway, what I’m saying is, “A map doesn’t help you if you don’t know where you are.” Another slogan… That one, by the way is probably based on a similar quote by Lewis Carroll, an English writer, mathematician, logician, Anglican deacon and photographer. His went, “If you don’t know where you are going, any road will get you there.”

Did I make my point? What was the point? Do metrics make sense? I’m leaning toward “Probably”. Let’s circle back after we look at some metrics – see if you think they’d make sense.

We’ll address the first reason, “Because it’s a Requirement” – next Tuesday. I’ve got more Deming to read – I can’t decide if he was a genius or if he was insane… typical.

Thanks.

Sal