Certified Is Not Capable
A certificate records that a process was followed on the day it was examined. It is silent on whether the thing works — and it cannot speak to tomorrow.
A certificate attests to something narrow and precise: that on a defined day, a defined process was followed, and that evidence of its having been followed was produced. This is a real statement. It is also a smaller statement than the one most readers hear. The mark is routinely received as proof that the system works. It says no such thing — and it is structurally incapable of saying anything at all about whether the system will work tomorrow.
A snapshot, not a stream
Certification is a point measurement. Capability is a continuous property. An audit samples a moment; the system it samples goes on living in time, accumulating change the certificate never sees — staff turnover, configuration drift, a dependency quietly deprecated, a control followed in the week of the audit and abandoned the week after. The certificate is true at the instant of issue and begins ageing immediately. It does not lie. It describes one frame of a film that keeps running after the photographer has packed up.
There is a further distortion in which frame gets photographed. The audited week is rarely a representative week. It is the most prepared the system will be all year — rehearsed, tidied, fully staffed, every artefact retrieved in advance. The measurement is taken at the system's best, then read as its baseline. The gap between the photographed moment and the lived average is not noise; it is the part the certificate was never designed to capture.
What the mark actually attests
Read precisely, a certificate attests to conformance: a documented process exists, and there is evidence it was executed. It is silent on three questions that matter more. Whether the documented process is the right one. Whether executing it produces the intended outcome. Whether the people who executed it understood why they were doing so. A process can be conformant and wrong; evidenced and ineffective; followed and not understood. Certified and fragile are not in tension — they describe different axes, and a system can sit high on one and low on the other with no contradiction at all.
Why the mark is sought regardless
If the certificate proves so little about capability, its pursuit requires another explanation — and the explanation is not capability. A certificate is sought because its absence is conspicuous and its presence is legible. It answers a question that procurement, regulators, and boards can ask cheaply and file easily — are they certified? — in place of the question that is expensive to ask and harder to file: are they capable? The field certifies because the field certifies; the mark becomes the objective, and the capability it was meant to evidence recedes quietly behind it. This is not fraud. It is substitution — and the substitution is comfortable precisely because the cheaper question wears the costume of the expensive one.
A certificate is not worthless. It is precise — more precise than the use commonly made of it. The error is not in holding one; it is in reading a snapshot of process-conformance as a guarantee of continuous capability, and in letting the legible question stand in for the one that matters. The useful move is not to ask whether the certificate exists. It is to ask what the certificate is silent about — and whether anyone has looked at that silence since the day the photograph was taken.