Thursday, May 29, 2025

On sabotage

It's been a while since I posted anything funny here. Let me know if this counts as funny.

Some years ago, the CIA declassified a document published by the Office of Strategic Services (OSS) back during World War Two. The document was called Simple Sabotage Field Manual (Strategic Services Field Manual No.3), and it was written to support our allies trapped behind enemy lines as they tried to disrupt Axis war-fighting capability and Axis society generally. It discusses motivation, timing, and tools, and then gives a lot of specific recommendations. You can download a copy of the document from here (or here).

What could be funny about this, you ask? Well, the book got the attention of management consultants and other business excellence experts, because there is a section on how to sabotage "organizations and production." And the advice in that section just sounds so ... normal! 

Here are just a few highlights:

  • Organizations and Conferences
    • Insist on doing everything through "channels." Never permit short-cuts to be taken in order to expedite decisions.
    • When possible, refer all matters to committees, for "further study and consideration." Attempt to make the committees as large as possible- never less than five.
    • Haggle over precise wordings of communications, minutes, resolutions.
  • Managers and Supervisors
    • Don't order new working materials until your current stocks have been virtually exhausted, so that .the slightest delay in filling your order will mean a shutdown.
    • Hold conferences when there is more critical work to be done.  
    • Multiply paper work in plausible ways. Start duplicate files.
    • Apply all regulations to the last letter.
  • Office Workers
    • Misfile essential documents.
    • Tell important callers the boss is busy or talking on another telephone.
    • Spread disturbing rumors that sound like inside dope.
    • Never pass on your skill and experience to a new or less skillful worker.

The list goes on and on. And, as I say, the actions mostly sound like normal human clumsiness, short-sightedness, officiousness, and inefficiency. I've seen some of these measures with my own eyes, and I bet everyone I know can say the same thing—not always and not everywhere, but at some jobs, from some people, at some times.

The thing to remember is that while you or I might call this inefficiency, the OSS called it sabotage! When our organizations stumble through the day allowing these things to go on, we are in fact sabotaging ourselves. Now, in spite of all that, most of us get through the day intact anyway. Most of our organizations live to do business again tomorrow. We don't shut ourselves down. 

But think how amazing our performance would look if we didn't sabotage ourselves!  


If you have time for a longer-form discussion, Kyle Chambers and Caleb Adcock from Texas Quality Assurance chatted about this very topic in two back-to-back podcasts back in early March. The first is half an hour, and the second is just about 45 minutes. As always, they discuss the issues with their trademark humor and pragmatism. 

  
      

Thursday, May 22, 2025

Auditing the climate amendment

In February of last year, the ISO formally adopted an Amendment to ISO 9001, relating to climate change. (In a stroke of ironic timing, I published an article with Quality Digest just days before the decision, on the subject, "What would it mean if this amendment were adopted?") And right away, voices began calling out, "How do we audit the new requirement?"

Strictly speaking the Amendment added one new requirement to ISO 9001:2015, and one note. The requirement is added to clause 4.1, which discusses Context of the Organization (including the internal and external issues facing the organization), and it provides:

The organization shall determine whether climate change is a relevant issue.

The note is added to clause 4.2, which discusses the needs and expectations of the organization's interested parties, and it reminds the reader:

Relevant interested parties can have requirements related to climate change.

That's it.

Now, the note is literally just a reminder. It is not auditable, which means that there is no need for the organization to show an auditor any objective evidence related to it. But whenever the ISO standard uses the word "shall," that word creates a requirement. The organization has to do it, and has to be able to prove it to an auditor.

Only, ... what questions can the auditor ask to check whether the organization made the determination they are required to make? Auditors started asking for guidance.

And the ISO 9001 Auditing Practices Group rode to the rescue! I don't remember if I've mentioned this group before, but they write papers on how to audit to ISO 9001. They have a website here, which hosts a large library of these papers available for free download. If you ever want official advice on how to audit some part of the ISO 9001 standard, check their library first.

Sure enough, just a month after the Amendment went into effect, the APG published ISO 9001 Auditing Practices Group Guidance on: Auditing Climate Change issues in ISO 9001. You can find it online for free, located here.

As a side note ... I remember when this document first came out, somebody on LinkedIn remarked that the paper is ten pages long. He argued that for it to be so long "proves" that the new requirement "must be" heavy and onerous. I no longer remember if he went so far as to accuse the Lizard People of using this requirement to crush small businesses, and I have lost the link so I can no longer re-read his post to check. But I almost expected him to.

So as a public service, let me reassure you: There is no sign that any Lizard People wrote this paper, and the requirements are not heavy or onerous.

Fine, what does it say?

The basic advice is simple:

  • Stay objective.
  • Ask if the organization has decided climate change is relevant to them?
  • If yes, what steps are they taking?

Let's look at each of these briefly.

Stay objective

When this amendment was first debated, I heard one person say:

"It is impossible for anyone to pretend they aren't affected by climate change. Therefore the answer to the question 'Is it relevant?' has to be Yes, and if someone says No you can write him up!"

The APG rejects this line of thinking. They point out that each organization has a right to make this decision for themselves. The APG paper goes on to say:

In some parts of the world climate change and its causes are controversial topics. Consistent with ISO 19011:2018 Guide­lines for auditing management systems, auditors are to maintain objectivity and neutrality when auditing climate change issues. They should not express personal beliefs relating to climate change. The role of the auditors is to assess whether the organization determined if climate change issues are relevant or not in relation to their QMS and its intended results and, if that is the case, then how it is addressed within the QMS.

This amendment does not require an organization to have climate change initiatives unless it has been identified as a relevant issue to achieve the intended results of the QMS.

Is it relevant?

So the first thing to ask is whether the organization thinks climate change is relevant to them? This means: Do they think that there is a credible risk that climate change can affect their ability to supply their goods or services to customers?

While you are asking that, the paper suggests that you might also check whether the organization has any statutory or regulatory requirements that could affect the answer? And likewise, do they have any contractual requirements that could affect the answer? Obviously you (as an auditor) want to see that the organization's decision on this point is aligned with their legal or contractual requirements.

And then the paper suggests other directions you might explore:

  • Is the organization starting to use renewable materials?
  • Have they been asked to move to carbon neutral products and services?
  • Have energy issues pushed them to reorganize their operations or infrastructure?
  • Are they seeing a greater frequency of storms, floods, fires, or drought? And if so, do those developments affect their employees, their supply chain, or their distribution?

And so on. The paper lists many more questions that you might consider.

What steps are they taking?

If the organization determines that climate change is out of scope for their Quality Management System, the discussion ends there. But if they decide that it is a relevant issue, then the basic logic of ISO 9001 requires that they address it one way or another. Naturally the details will be different for every organization. But you can follow the climate theme as a thread throughout the rest of the audit:

  • When you audit the scope of the QMS in clause 4.3, you can check whether they still use the same industry codes as before. Are they still making the same products, or in the same line of work?
  • When you audit risks and opportunities in clause 6.1, what risks and opportunities have they explicitly identified that relate to the climate? How have they evaluated them? Have they assigned actions to address the risks or capitalize on the opportunities?
  • When you audit changes in clause 6.3, consider all the other changes listed here. Has the organization handled them in a planned and controlled way?
  • When you audit the work environment in clause 7.1.4, has it been affected by the climate in any way? Has the organization taken any steps?
  • When you audit operations in clause 8, how have their operations been affected? (The APG paper offers a full page of suggested questions for clause 8 alone, but of course the details will always depend on the individual organization.)
  • When you audit performance evaluation in clause 9, what aspects of climate impact or climate mitigation are the organization monitoring and measuring? Are they monitoring and measuring data that are related to the impact or the risks they have identified? Are the tools and methods that they use for this monitoring and measuring actually fit for purpose? And how is the organization checking to ensure that the changes they have implemented really work?

Again, the paper gives many more suggestions besides these. And of course you would never use every single question. It all depends on what fits, based on the details of the organization.

None of it is heavy or onerous. And it all flows logically from the actual requirements. But I am glad to know that the suggestions are available, as a support.

If you're not familiar with the Auditing Practices Group, be sure to check out their library.     


    

Thursday, May 15, 2025

"The paradox of Quality"

A couple months ago, Anthony Lenarz of GE Vernova posted an article in LinkedIn called "The Paradox of Quality." His point was much like that of an Innovation Manager I once worked with who joked, "You and I are mortal enemies, because we pull the company in opposite ways. You work in Quality, so you want to eliminate variation; I work in Innovation, so I want to inject change everywhere." 

This is exactly what Lenarz says:

"Quality is a profession that thrives on confusion. It's like being told to walk in a straight line while doing the tango. On the one hand, we're told to standardize everything, make it all uniform, reduce variation to a whisper. It's a bit like telling a jazz band to play the same note over and over again—consistently—until they all fall asleep.

"But on the other hand, in the same breath we say, 'Take the initiative, drive change, and continually improve.' It's as if we want our jazz band to suddenly break into a solo, each musician playing a different tune but somehow making it all sound like a symphony."

It's funny, of course. And I love the image. But in the end I disagree with the basic point. And I think it misrepresents (no doubt unintentionally) what Quality is all about. 

Part of the error is that Quality isn't really about standardization, or reducing variation, or any of those things—any more than profitability is "really about" eliminating waste. Those are just means to an end. The real heart of Quality is a lot more basic: Quality means getting what you want. And all the rules and procedures in the whole Quality toolchest are just gimmicks to get you there.

Maybe it looks like I'm playing games by drawing this distinction, because we all know that in practice implementing a Quality system means doing work in a consistent way and guaranteeing a consistent output. You can say that's just a technique, but it's still what we do every single day.

Yes that's true, but there's an issue of scale. To the extent that Quality does involve reducing variation, it means making each widget like the next in the same production run, which in turn simply means executing the design correctly. If you make one-foot rulers, Quality means (among other things) that Customer A doesn't get an 11-inch ruler on the same day that Customer B gets a 13-inch ruler. It means that when you sell a one-foot ruler, that's what you deliver.

This doesn't impede innovation, because innovation isn't about shipping rulers that might randomly be 11 inches long, or 13 inches long, or somewhere in between. Innovation is about developing new kinds of rulers, to meet new needs: yardsticks, meter sticks, other kinds of measuring tools. 

It's true that there is no foolproof procedure for designing brand-new ideas, any more than there are any other foolproof processes. But when you succeed in designing these new measuring tools, Quality ensures that your design gets to the customer correctly, as you planned it—and not mucked up by a bunch of random accidents.

Of all Lenarz's tantalizing images, I think the one that best captures the true interrelation between Quality and Innovation is the symphony. A symphony is only possible if there is a score, if each musician is using the same score, and if each musician is well-enough trained to produce a consistent melody from that score, without fail, during every single performance. Also, each instrument has to be tuned (calibrated), and good enough for orchestral work (fit for purpose). Standardization, the reduction of variation. and the other traditional Quality tools go so far.

At the same time, there is a level of craftsmanship and mastery that comes in below the level of the score, where each musician has to make subtle accommodations to get the best sound out of each instrument. This craftsmanship depends on individual skill and cannot possibly be standardized. Therefore Quality systems impose requirements for training and expertise. 

The conductor interprets the piece in ways that are always consistent with the score but that nonetheless express a personal spirit or vision. This vision and interpretation are part of the job of Leadership, which is one of the principles undergirding Quality management.

And Innovation? Well after all, who writes the score? This is the role of the composer, be it Mozart, Beethoven, Wagner, Copland, or Salonen. Without innovation—without a score—the members of the orchestra sit idle and have nothing to do. But it takes all of the orchestra's Quality processes to deliver that score to the audience.


   

__________

          

Thursday, May 8, 2025

What's in the new ISO 9000?

Two years ago* I wrote about some changes that had been proposed in the ISO 9000:2015 standard, Quality management systems — Fundamentals and vocabulary. Since that time, the responsible committee TC176 decided to move forward with an update, and they have recently posted a Draft International Standard (ISO/DIS 9000) for review and voting. This draft contains numerous changes and updates. And to be clear, the DIS has not been formally approved yet. Something might still change. On the other hand, since the document is now public, the confidentiality rules on committee work no longer apply and we can discuss it publicly.

For those who want to follow along at home:

⇒ YOU CAN BUY A COPY OF ISO/DIS 9000 FROM THIS WEBPAGE HERE. ⇐⇐   

What's changing?

Remember that ISO 9000 is like a dictionary: it contains definitions of technical terms, and it contains explanations of fundamental concepts. So the changes include new technical terms, and new fundamental concepts. In addition, the committee rewrote many existing passages even while keeping their substance. 

Rewriting passages

I tried to keep track of the changes in wording, to see if I could discover a common thread, and finally gave up. In many cases the changes seemed no more than another way to say the same thing; other times they introduced qualifiers which might be helpful but were probably not really essential. In some places the new text backs away from promising that Quality management will bring you success,** but in other places it adds those suggestions where they weren't before.*** 

The only absolutely consistent change that I detected was that ISO DIS 9000 no longer refers to itself as an International Standard. Time and again the phrase "this International Standard" has been replaced with "this document." Where the Introduction to the current edition promises that "This International Standard … provides the foundation for other QMS standards" [Emphasis mine.] the Draft says more modestly that "This document … provides the foundation for quality management and quality management systems (QMS) standards." In fact there is only one point in the whole document where the Draft retains the words "this International Standard," and I am certain it represents a copy-paste error.****

Does anyone know why? Is there a technical reason that ISO 9000 will no longer count as an "Inter­national Standard" after this edition is published? I don't know, but I'd love to understand it better.

New technical terms

The new Draft standard defines a lot of new words. Oddly enough, it also deletes a few old ones.

There are five technical terms deleted from the vocabulary definitions in the new Draft, and they all relate to configuration management. In this version, you can no longer find definitions for: change control, configuration authority, configuration control board, configuration management, or dispositioning authority. Again, does anyone know why? It's not like these concepts aren't important. Nor has the committee taken a principled stand to move configuration management topics into a different document, because the new Draft still contains definitions for configuration baseline and configuration status accounting.***** So I'm puzzled. Do you understand it?

At the same time, the committee added far more terms than it deleted. I count eighty-six new terms. A few of these relate to traditional Quality topics, which makes their earlier exclusion look like an oversight: complainant, form, good practice, result, work instruction. There are even two new terms related to configuration management (configuration information and configuration item), which makes the loss of the others still more of a puzzle. Then there are terms related to ancillary disciplines like project management (project life cycle, project phase), or to tools that have become popular enough to be considered more or less standard (change matrix, dashboard).

But over half the new terms—forty-five in all—relate to government and voting. These terms aren't used anywhere else in the new Draft, so it's not like they are part of the regular conceptual infrastructure. They seem to come from ISO/TS 54001:2019, Quality management systems: Particular requirements for the application of ISO 9001:2015 for electoral organizations at all levels of government: terms like electoral body, outsourced electoral process, ballot proposal, electoral service development plan, and so on. I assume that the committee wants to pull all the technical vocabulary for all specialized applications of quality management into one large pool where they can be kept consistent with each other, rather than letting them hide in specialized documents where they can be scattered and hard to find. But I wasn't part of the subcommittee which decided this point, so I am only guessing. 

New concepts

Then there are the principles and the concepts. Here there has been both rearrangement and addition.

In the first place, whole sections have been rearranged. The 2015 edition broke up clause 2 as follows:

2.1 General

2.2 Fundamental concepts

2.3 Quality management principles

2.4 Developing the QMS using fundamental concepts and principles

The new DIS 9000 swaps the position of concepts and principles, and then splits concepts into "fundamental" and "additional" as follows:

2.1 General

2.2 Quality management principles

2.3 Fundamental quality management concepts

2.4 Additional concepts relevant to quality management

2.5 Developing the QMS using fundamental concepts and principles 

Here in this blog, we just finished a two-month series on the Quality management principles (starting here and ending last week), so I'm happy to report that there were no important changes to that section. I won't have to rewrite two months' worth of posts. 😀 Of course all the paragraph numbers changed when the principles moved from clause 2.3 to clause 2.2. And there were minor wording changes like I described above. But that's it.

Among the concepts, … well, the existing concepts that were carried forward didn't change much, though some were put in clause 2.3 and others in clause 2.4.****** But there were a lot of new concepts added. Some of these "new concepts" are familiar terms that Quality professionals have been using for decades, but which were never before now brought into this standard. Others are  a lot newer. Here's the list of new concepts that have been added:

Quality management

Quality assurance

Quality control

Quality planning

Process management

Risk-based thinking

Organizational quality culture

Continual improvement

Integrated management system

Circular economy

Emerging technologies

Innovation

Change management

Customer experience

Knowledge management

Information management

People aspects

Business continuity

It's quite a list. Each one gets a short essay of a couple paragraphs (the longest is a page), explaining what it is and why it is listed.

Where does this leave us?  

I think the committee is trying to do too much. Most of the new Draft is fine, of course. But that list of new concepts is too long. Or rather, it's not the length that troubles me. It's that a few of the concepts—circular economy, for example, or emerging technologies—have only the thinnest connection to Quality.

To be clear, I don't think these concepts are unimportant. And I recognize that the committee is trying to encourage businesses to look past tomorrow, to take account of the issues that lurk in the shadows, waiting for them in the wider world. Emerging technologies affect all of us, like it or not. Innovation has become a fact of life in the marketplace. And the more we can adopt the perspective of a circular economy, the less strain we will put on our resource base, our supply chains, and our natural environment. These topics are all important ones to think about, and the actions stemming from them are valuable things to do.

But they're not about Quality. Quality is about satisfying the needs and expectations of customers and other interested parties. And while it is important to understand the impact that our actions will have on the natural environment or on future generations, it's a stretch to identify either the environment or our successor generations as "interested parties." What's more, I worry that trying to do too much will distract us from focusing on the topic at hand. For this reason, I'm inclined to think that ISO 9000 should stay in its lane.  

This is exactly the same argument I made when we discussed whether the Quality standards should address climate change. You may remember that the majority disagreed with me last time, so I won't be surprised if they disagree with me this time too. It happens.

To put the best face on it, I do understand that the committee is trying to nudge businesses and other organizations into considering these important issues. And in a sense, this document is a good place to put these topics, precisely because it is explanatory and not directive. ISO 9000 never tells you what to do; that's ISO 9001's job. ISO 9000 just tells you what things mean, words and concepts. So if you really don't care what circular economy means, you can skip that part and no harm done. No auditor is going to quiz you about it later.

It almost looks as if the committee has decided to make ISO 9000 into an overall Generic Framework for Organizational Management. Maybe that's even a useful thing to do. But it's not what I was expecting from the document title.

__________

Has it really been that long? Time flies when you're having fun! 

** In the 2015 edition, clause 2.3.1.2 begins, "Sustained success is achieved when an organization attracts and retains the confidence of customers and other relevant interested parties." The new Draft deletes this sentence in its entirety. It does retain a later sentence which offers no more than that "Understanding current and future needs of customers and other interested parties contributes to the sustained success of the organization." [My emphasis.] Also, for some reason the new Draft shuffles around the order of the sentences—not just here, but in most of the clauses that were otherwise retained more or less intact.

*** In the 2015 edition, clause 2.1 para. 1 ends, "The impact of quality extends beyond customer satisfaction: it can also have a direct impact on the organization’s reputation." The new Draft adds the words "and sustained success" before the period. 

**** Note 2 to definition 3.2.10 ("quality management system consultant") says, "This International Standard provides guidance on how to distinguish a competent quality management system consultant from one who is not." [Emphasis mine.] Now in fact ISO DIS 9000 says nothing at all about the competence of quality management system consultants. But another standard does discuss this subject: ISO 10019:2005, Guidelines for the selection of quality management system consultants and use of their services. What is more, the definition of "quality management system consultant" that we find in the new DIS 9000 appears word-for-word in ISO 10019:2005, along with two notes. The two notes are also repeated word-for-word in the new Draft, and the second of those notes promises to distinguish competent consultants from incompetent ones. 

***** The Alphabetical index of terms at the end of the new Draft standard also lists configuration object, but the item reference pointer is wrong and the term never appears in the text of clause 3. It has been replaced by configuration item, which has the exact same definition here in the Draft that configuration object has in the 2015 edition.

****** The concept "Support" from the 2015 edition is covered by the concept "People aspects" in the new DIS.    

      

Thursday, May 1, 2025

Why are we only defining this NOW?

Over the last two months, we've reviewed the seven fundamental Quality Management Principles defined in ISO 9000:2015: Customer focus, Leadership, Engagement of people, the Process approach, Improvement, Evidence-based decision making, and Relationship management. We started by investigating why Quality Management should be based on these seven principles in particular, and not some others instead. And then we looked at each principle, one by one, to understand what it means, why we should care, and what we can do about it. I've found it interesting, and I hope you have.

But there is one fact we haven't addressed yet. These principles are the conceptual foundation on which the concepts of Quality and Quality management are built. And they are spelled out in ISO 9000:2015, clause 2.3. But the ISO 9000 standard is still undergoing regular revision, which means that these concepts are still being refined and improved. In a future edition, the committee responsible for the document (ISO TC176) might even decide to add another basic principle, or change the foundations in other ways. All of this is still being defined—actively, here and now, in the present day.

So I have to ask: Why are we only defining these concepts now? It's not like Quality is a new idea. People have known the difference between doing good work and doing bad work as long as there have been people doing any work at all. The Code of Hammurabi contains provisions for product liability, in case of poor workmanship.* Even Plato discusses product Quality incidentally, while trying to enquire what makes things good or beautiful.** So why didn't someone work out the conceptual foundations of Quality way back in Antiquity? If Quality is important—which it is!—and if it has been known for so long, why didn't Aristotle write about it?

Aristotle (marble portrait bust, Roman copy of a Greek original).
He never discusses Quality Management.

Let's take another look at that list of seven principles, in search of a clue.

Three of them are ancient

There is no question that the last three principles in the list date from Antiquity. The Stoics taught methods for systematic personal Improvement covering all aspects of life. The whole focus of ancient philosophy was in support of Evidence-based decision making, instead of following rules supported by tradition or public opinion. And the idea of Relationship management is at least as old as the Golden Rule. If these had been the only foundations needed for the concept of Quality, it certainly would have been discussed in ancient times.

One is very modern

At the other extreme, the Process approach was created by Walter Shewhart in the first half of the twentieth century. Shewhart distilled the experience of a century of industrialists who had implemented more or less formal procedures in their factories. His work also drew on earlier developments in statistics, such as Charles S. Peirce's application of statistics to the design of experiments, and Francis Galton's development of standard deviation and regression analysis. It is even possible that Shewhart's work might have been influenced by the process metaphysics of Alfred North Whitehead.*** But in any event, from the perspective of intellectual history the Process approach is very new.

And the other three have grown on us

The history of the first three principles, though, is more interesting.

Leadership and the Engagement of people

Frederick W. Taylor, founder of
"scientific management."

Leadership and Engagement of people have both been known since ancient times, but not in the way they appear here.**** In the past, studies of leadership—from Sun Tzu's Art of War and Xenophon's Education of Cyrus through Machiavelli's The Prince—were written about military or political organizations. By contrast, the study of business or factory management is generally supposed to have started with Frederick W. Taylor, who published Shop Management in 1903, and Principles of Scientific Management in 1911. (Some sources identify additional pioneers besides Taylor in the study of management, but nearly all these pioneers lived—like he did—in the nineteenth and twentieth centuries.)

What accounts for the difference? Why is there a gap of more than two millennia between the first studies of princes and the first studies of managers? At the highest level of abstraction, princes and managers are engaged in the same kind of job: getting other people to do things. Of course their methods are different, as are the details of what they want done. But for the current question, I think the most relevant difference is that by the late nineteenth century, managers were becoming far more common than they used to be.

It's true that there were large-scale business concerns in Antiquity: the Roman latifundia covered hundreds or thousands of acres and employed hundreds of slaves. And all through the years since, there were always a few large businesses. But for centuries they represented a small share of the economy. Most people were farmers or sole proprietors. It is only in the last—oh, let's say 150 or 200 years—that things have changed significantly. 

Two hundred years ago, if you met someone new and wanted to know about his work, you might ask, "What do you do?" Today, the question is at least as likely to be "Who do you work for?" In the modern economy, nearly everyone is an employer or an employee—or sometimes, both at once. And therefore, the twin topics of Leadership and Engagement of people have taken on an importance in everyone's daily work life that they never had before. As I say, they have grown on us.

Customer focus

We see exactly the same evolution in the concept of Customer focus.

Of course the basic idea that a customer should get what he pays for is very old. In the past, that principle would have been seen as an instance of the concept Justice

But Customer focus involves so much more than that! As we saw back in March, Customer focus requires you to identify who your customers are, and then to understand what they really need. This requirement is a lot more demanding than just not cheating them (although obviously it includes not cheating them as a consequence!).

Where did this broader requirement come from? I think there are two sources. 

One source is that our market today is defined by competition. Of course competition existed before now, but today it is presupposed as a fundamental rule of economic engagement in a way that seems more pervasive than earlier. 

(By way of contrast, consider the—fictional!—motto of Ralph's Pretty Good Grocery from Garrison Keillor's A Prairie Home Companion: "If you can't find it at Ralph's, you can probably get along (pretty good) without it." Naturally this was never the explicit motto of any real store. But the joke wouldn't have been funny if there had never been a time or place when a shopkeeper might have thought such a thing. Nor would it have been funny if people still believed it today.)

The other source comes from a major demographic shift in the developed world. In 1790, 90% of Americans lived on farms, and necessarily practised some measure of self-sufficiency. They largely made their own tools and their own clothes. Of course you could buy things, and people did. But for everyday items it was often more economical to make your own. 

By 2019, in contrast, that same fraction was 1.4%. And the majority of people who live on farms today are specialists—as farmers—rather than generalists. Even those who still know how to make their own tools and clothes largely don't do it, because it is cheaper to buy them. Also, most farms produce crops for sale rather than for subsistence. Because of massive improvements in transportation and communication, and because of the corresponding changes in the overall economy which those improvements have driven, self-sufficiency is no longer assumed. The consequence is that today, we are all customers! Everybody is a customer of somebody else, or rather many "somebodies." 

I argue that these two changes—the pervasiveness of competition and the universality of the customer-relationship—have changed the nature of Customer focus. Once upon a time, all you had to do for your customers was to be honest and fair with them. Now you have to do more, both because your competitors are doing more (so you have to keep up) and because you yourself are a customer (and so you want to encourage your suppliers to treat you well in turn).

So is Quality a modern concept after all?

Yes and no. Mostly yes.

Everything I wrote at the beginning of this post—about Plato and Hammurabi and the rest—is still true. It is still true that people have known the difference between good work and bad work as long as people have been doing work.

But Quality as we understand it today is a concept rooted in late-stage capitalism. It relies on five developments that are indisputably modern:

  • an understanding of business processes that was possible only after a century of industrialization;
  • an understanding of statistics that grew out of work done in the late nineteenth and early twentieth centuries;
  • the spread of corporations as the default organizing unit of the labor economy; 
  • the assumption of competition as the pervasive principle of the market;
  • and the integration of everyone into that market, so that the supplier-customer relationship became universal.


That's why we are still today refining the conceptual framework that supports Quality. The modern understanding of Quality truly is modern, because it incorporates and builds upon social and intellectual developments that have made our modern day different from every age that went before.   

__________

* There is no general principle of product liability stated explicitly in the Code of Hammurabi, but there are specific provisions from which a common principle can be inferred. For example:

229. If a builder build a house for a man and do not make its construction firm, and the house which he has built collapse and cause the death of the owner of the house, that builder shall be put to death.

233. If a builder build a house for a man and do not make its construction meet the requirements and a wall fall in, that builder shall strengthen that wall at his own expense.

235. If a boatman build a boat for a man and he do not make its construction seaworthy and that boat meet with a disaster in the same year in which it was put into commission, the boatman shall reconstruct the boat and he shall strengthen it at his own expense and he shall give the boat when strengthened to the owner of the boat.

For the complete text, see The Code of Hammurabi (Harper translation) - Wikisource, the free online library.

** In the Hippias Major, Plato has Socrates ask Hippias about the meaning of τὸ καλόν, often translated "the Beautiful," or "the Fine." Hippias first argues that you make something fine by making it out of gold and ivory. But Socrates points out (290D) that for a kitchen spoon to stir soup, it's better to make it out of wood. In this way he gets Hippias to agree that the Fine is "the appropriate." (293E) By similar arguments, he suggests that the Fine is "whatever is useful" (295C), "the useful and able for making some good" (296D/E), and finally "what is pleasant through hearing and sight" (298A). I think it is remarkable that Plato comes so close to modern definitions of Quality such as Crosby's "conformance to requirements" or Juran's "fitness for use." (Compare this post here.) All the same, he never develops a theory of Quality itself, as we understand the term today. 

*** See, e.g., Gregory H. Watson and John R. Dew, "The Reality of Process: The influence of Alfred North Whitehead on quality thinking," in Quality Progress, Volume 55 Issue 2, February 2022, pp. 28-33. 

**** Note that these two principles are linked together because each entails the other. Leadership is meaningless unless there are people engaged who are being led. Conversely, if people are engaged with each other in a common task, then usually there is already a leader—open or hidden—around whom they have coalesced; in the rare cases where a group coalesces without a clear leader, one emerges right quick.     

         

Five laws of administration

It's the last week of the year, so let's end on a light note. Here are five general principles that I've picked up from working ...