Documents lie through omission, through drift, through the gap between what was decided and what was recorded. The tangled web of cross-references is not a documentation problem. It is a governance problem.
A document can pass every review, carry every signature, and still misrepresent the system it purports to describe. Here are the five most common failure modes.
The document is accurate as far as it goes. But it does not go far enough. Critical design decisions, risk trade-offs, and configuration choices that shaped the device are missing from the record. The document is complete on its face. The system it describes is not.
The document was accurate when it was written. Time passed. The device changed. The process changed. The requirements changed. The document did not. It still describes a reality that no longer exists. The approval date on the cover page is now a fiction.
Drawing 100519-Rev-C shows a polymer specification. The BOM shows a different grade. The SOP shows a third. All three are approved. All three are current. They cannot all be correct. The system is incoherent — and no individual document reveals it.
The document references URS 401042. URS 401042 was superseded by revision. The reference was never updated. The traceability chain appears intact. Follow it and you arrive at an orphaned requirement that no longer governs anything. The chain is broken at a link no one can see.
SOP-14 references DMR 100518. DMR 100518 references Drawing 100519. Drawing 100519 references Material Spec 100519-MS. Material Spec references Test Method, Supplier Qualification, and incoming inspection SOP-14. The web is complete. The change impact is unknowable.
During inspection, the auditor asks: show me how this user requirement traces to your verification evidence. The documents exist. The connections do not. The quality engineer knows what the system does. The records do not demonstrate it. The system cannot explain itself.
Every failure mode described above is a relationship failure. Omission is a failure to connect design decisions to records. Drift is a failure to maintain synchronization between the device and its documentation. Unsynchronized records are a failure of configuration governance. False traceability is a failure of governed reference management. The cross-reference web is a failure of architectural discipline.
Lean Documents and Lean Configuration does not add more documentation. It does not add more review cycles or more signatures. It addresses the root cause: the absence of governed relationships between records.
When relationships are governed, documents cannot drift without detection. Changes cannot propagate without traceability. Inspection cannot surprise you. The system explains itself.
Consider an organization that has just completed a design change. The change was reviewed. It was approved. An ECN was issued. The DHF was updated. The DMR was revised. All the boxes were checked.
Six months later, an auditor asks: show me how this change affected your risk management file. The quality engineer pauses. The change was documented. The review minutes reference the change. But the risk management file — 100312 — was not explicitly part of the change scope. It was assumed to be unaffected.
The auditor asks: how do you know it was unaffected? The quality engineer cannot answer. Not because the risk management file was affected. Not because it was not. But because the question was never formally asked. The relationship between the change and the risk file was not governed. It was assumed.
Assumptions are the mechanism by which documents lie. The document is complete. The signature is present. The assumption is invisible. The record describes a decision that was never made.
"The tangled web of cross-references is not a documentation problem. It is a governance problem."
Lean Documents and Lean Configuration begins with a simple premise: every relationship between records must be governed, or the records cannot be trusted. Not referenced — governed. There is a difference. A reference says "this document is related to that document." A governed relationship says "this record is derived from that record, and a change to that record requires a formal assessment of this record."
A systematic examination of how documents fail — not through error or negligence, but through the absence of governed relationships between them. Required reading for quality leaders, regulatory affairs professionals, and anyone responsible for inspection readiness in a regulated industry.
Available in print and digital editions. Contact for bulk licensing and organizational use.
"A document can be complete, current, approved — and still lie."WHEN DOCUMENTS LIE — Introduction
Part I: How Documents Lie
Part II: The Cross-Reference Problem
Part III: The Governance Architecture
Part IV: Lean Documents in Practice
Part V: Lean Configuration in Practice
Part VI: Inspection Readiness
When Documents Lie diagnoses the problem. The LDLC framework provides the architecture for the solution. The book is not a manual — it is a case for why a governance architecture is necessary. The framework is that architecture.
Readers who recognize their own organization in the book's examples will find the LDLC Map, the Change Propagation Explorer, and the consulting services a natural next step.
Begin with a conversation about where your documentation system is creating risk.