Why the best quality leaders don’t think in black and white, and why “it depends” is only half an answer.
My graduate students have a love-hate relationship with my favorite answer. They ask a reasonable question: Would this deviation need a CAPA? Is this a complaint? Do we really have to validate this process? And I smile and say, “It depends.”
Cue the collective groan.
I get it. Most of us came into quality from science, where there’s comfort in a right answer. I started in a clinical laboratory, where a result was either in range or it wasn’t. I have a rule-following streak a mile wide. Black and white feels safe.
But November 12th is World Quality Day, and after nearly four decades in this field, here’s the truth I want to celebrate: the most important work in quality doesn’t happen in the black or the white. It happens in the grey.
The Regulations Were Written in Grey on Purpose
Read the requirements closely and notice how often they refuse to give you a number. ISO 13485, now incorporated by reference into FDA’s QMSR, asks us to apply a risk-based approach to controlling the appropriate processes. The MDR regulation asks whether information reasonably suggests a device may have caused or contributed to a death or serious injury. For our pharma friends, 21 CFR 211 asks for laboratory controls that are scientifically sound and appropriate, and ICH Q9(R1) tells us the formality of risk management should be commensurate with the level of risk. The 2023 revision even calls out subjectivity as something to manage, not something we can wish away.
That isn’t sloppy drafting. Regulators can’t anticipate every product, process, and patient. So they hand us a principle and trust (then verify) that we’ll apply it with judgment. When a regulation says “appropriate,” it isn’t letting you off the hook. It’s handing you the pen, and it expects to read what you wrote.
Two Ways Black-and-White Thinking Fails
The Fortress. Everything is critical. Every change needs full revalidation. Every call from a customer becomes a formal investigation. It looks rigorous, but it’s actually risk-blind: when everything is high priority, nothing is. The team exhausts itself on the trivial, and the one real signal gets the same fifteen minutes as everything else.
The Loophole. The opposite problem. “The regulation doesn’t specifically say we have to, so we won’t.” This team reads the regulations like a contract, looking for the exit. It’s grey used as camouflage, and investigators see through it quickly.
Notice that both are escapes from the same hard thing: making a decision and owning it.
How to Live in the Grey Without Getting Lost
“It depends” is only half an answer. The other half is “…on what.” Here’s how I coach teams, and my students, to finish that sentence.
- Know where the lines really are black and white. Some things are not grey. Data you didn’t generate doesn’t go in a record. A patient safety signal doesn’t wait for a convenient quarter. An investigator’s question gets a truthful answer. The grey zone is wide, but it has hard edges, and good quality leaders know exactly where they are.
- Ask the risk question first. Before “What does the SOP say?” ask “What could happen to the patient, the product, or the data if we get this wrong?” Severity and likelihood tell you how much rigor the decision deserves.
- Write down your reasoning, not just your answer. A grey decision without a rationale looks like a bad decision. A documented, risk-based rationale (here’s what we considered, here’s what we concluded, here’s why) is often the difference between an investigator nodding and an investigator writing. Future-you will be grateful, too.
- Invite the dissenting view. The grey is where bias loves to hide. Bring in someone who will push back: operations, clinical, the skeptical engineer. Some of my best decisions came from someone making me defend them!
- Be willing to revisit. A grey decision is made with the data you have today. New complaints, trends, or information can move the line. Changing your mind in the face of new evidence isn’t weakness.
What the Grey Looks Like in Real Life
Picture this: a customer reports that a device alarm “seemed quieter than usual.” No injury. The unit comes back, and testing shows the alarm is within specification.
The black-and-white answer says: within spec, close it. The Fortress answer says: open a CAPA and escalate everything. The grey answer asks better questions. Is this the first report, or the fourth this quarter? What happens clinically if a user misses this alarm? Does our risk file rely on alarm audibility as a control for a serious hazard? Is the specification itself right for the environments where the device is actually used?
Depending on those answers, the right path might be trending, a look at the use environment, a design question, or yes, a CAPA. Whether it rises to MDR reportability depends on the facts, which is precisely the point. The grey answer isn’t the easy one. It’s the thoughtful one.
A Word to the Women Leading in Quality
Living in the grey takes confidence, because there’s no rulebook answer to hide behind. I’ve watched many talented women in quality reach for the black-and-white answer because it feels unassailable. “The regulation says…” is hard to argue with. I did it myself early on, especially in rooms where I felt I had to be twice as sure to be taken half as seriously.
Here’s what I wish someone had told me sooner: judgment is a leadership skill, not a liability. “It depends, and here is what it depends on” is one of the most authoritative sentences a quality leader can say. Say it clearly. Back it with evidence. Then own the call.
Celebrating the Grey This World Quality Day
So this World Quality Month, let’s celebrate the people who live in the grey with rigor. The complaint analyst who asked one more question. The engineer who argued a process didn’t need full revalidation and then proved it. The QA manager who said “not yet” when everyone in the room wanted “yes.”
They didn’t find the answer in the black or the white. They built it.
What was the greyest decision you made this year, and how did you document it? I’d love to hear your stories in the comments.
