Reflection · · 4 min read

A reflection on quality

A reflection on quality
Photo by Nicolas Hoizey / Unsplash
"What cannot be named cannot be known. What cannot be known cannot be found. What cannot be found can't be understood."

If you prefer the audio version, try it on Spotify:


A mundane conversation presents a sublime noun.

Quality is a word that I've started thinking of more and more, not in how I can create or destroy it, but in how others are using it and what they mean. Somebody in the manufacturing industry would constantly play "hide and seek" with the word, always trying to ensure its work is on the same level. Others might think they want it but need to know what it means. After some weeks, I consider myself better prepared to answer this - of course, I'm comparing with myself only.

Whenever I ask others what it means, they tend to converge to the "conformance to specifications" definition. If a product meets the design specifications, offering a satisfaction factor that fulfills all the customer's expectations, then the product has quality. Here, products can be interchanged with services or experiences. This offers a way to objectively measure and remove any esoteric attributes from the subject. But from there, a few questions come up, asking for answers.

What happens if customers need to learn the requirements? Does a quality product mean an average and not something extraordinary? Is there a spectrum of quality, or is it binary with a specific threshold after which we attribute quality? And there are more, but we need some answers before we move forward.

Read next