--- content_id: WACK-CONTENT-0064 library_id: WACK-CASEFILES-0001 channel: web-long-read related_concept_ids: [WACK-CONCEPT-0011, WACK-CONCEPT-0014, WACK-CONCEPT-0012] field_manual_content_id: WACK-CONTENT-0055 publication_status: ready claim_class: editorial_composite technical_review: not_required verified: 2026-09-03 --- # The Diagram Nobody Wanted to Update > The architecture changed every month. The picture stayed beautiful for three years. _Fictional composite synthesized from common practitioner patterns; it does not describe a client, assessment, or incident. Practitioner education, not PCI SSC terminology or a compliance determination._ The diagram was wrong, the spreadsheet was current, and the truth was distributed across six people who had never been in the same meeting. ## The scene The diagram had survived a cloud migration, two acquisitions, a network redesign, and three branding updates. It remained visually excellent. Boxes aligned. Arrows avoided one another. The legend was tasteful. It appeared in onboarding decks and assessment packets because it was the only artifact that made the environment look explainable at a glance. The team also maintained a scope spreadsheet. Unlike the diagram, it changed constantly. Rows arrived through tickets, discoveries, and annual review. Colors marked inclusion, exclusion, ownership, and uncertainty. People trusted the spreadsheet because it felt current, but the rows did not consistently link to flows, trust boundaries, or administrative paths. One artifact had shape without freshness. The other had freshness without architecture. ## Six versions of current When the team compared the two sources, disagreements appeared immediately. A payment support service existed in the spreadsheet but not the diagram. A retired gateway remained on the diagram but not the inventory. A newly acquired environment used the same name for a different component. Two arrows represented connections nobody could validate. Each artifact was current according to a different clock. The search for answers became Evidence Archaeology. Network engineering had a troubleshooting sketch. The cloud team had a deployment view. An application owner had a data-flow slide. Security had firewall objects. Compliance had last year’s annotated PDF. None was the authoritative architecture, yet each contained facts the official diagram had omitted. ## Why nobody fixed it Updating the official picture felt risky because every change invited a bigger question. Add the acquired environment and someone would ask about its boundary. Remove the gateway and someone would ask when it retired. Draw the management path and someone would revisit the scope rationale. The diagram stayed polished because polish protected the team from reopening unresolved decisions. Meanwhile, the spreadsheet absorbed uncertainty without resolving it. A yellow row could remain yellow indefinitely. A comment could say pending architecture confirmation for several quarters. The table became a waiting room for decisions the diagram refused to host. Together they formed a stable Cluster of Wack: one artifact simplified the story and the other postponed it. ## The reconciliation drill The team stopped trying to redraw everything. They selected one transaction path and one administrative path, then walked both across the diagram, spreadsheet, configurations, and owners. Each mismatch entered a log with the competing claims, available evidence, decision owner, and due date. Unknown became an explicit state instead of an embarrassing blank. The drill produced an imperfect but dated baseline. Components carried stable identifiers. Spreadsheet rows linked to diagram nodes. Diagram edges linked to evidence or open questions. A retirement event removed the component from both views. A new trust relationship triggered review of both. The artifacts did not become identical; they became reconcilable. ## What the team finally saw Diagram Drift is not primarily a drawing problem. It is a synchronization and decision problem. Scope by Spreadsheet emerges when the table is asked to replace the relationships it can only summarize. Evidence Archaeology fills the gap when teams must excavate current facts from local artifacts and memory. The way out is not a perfect master diagram. It is a repeatable reconciliation motion with identifiers, dates, owners, triggers, and a place for uncertainty to become work. ## The way out ### Find Choose one business transaction and one administrative workflow that cross important boundaries. Gather the official diagram, scope table, relevant configurations, local sketches, and people who operate the path. ### Map Walk each step across every source. Record matching facts, contradictions, missing nodes, missing edges, stale components, naming collisions, and unanswered ownership questions in one reconciliation log. ### Explain Assign a decision owner to each contradiction and state which evidence would resolve it. Keep unknown visible and time-bounded; do not hide it in an unlabeled arrow or permanent yellow cell. ### Reduce Retire obsolete views, normalize identifiers, remove unsupported edges, and limit each artifact to a clear purpose. Fewer maintained representations create fewer places for silent drift. ### Prove Publish a dated baseline, link table rows to diagram nodes, record review triggers, and retain the reconciliation log. Demonstrate that one recent change propagated through every affected view. ## Field notes - A beautiful diagram can be the most persuasive stale artifact in the room. - Current is meaningless unless the artifact declares its clock and trigger. - Unknown should become an owned work item, not a permanent color. - Architecture views do not need to be identical; they need to be reconcilable. ## What changed The official diagram became less beautiful and more useful. It displayed dates, identifiers, unresolved edges, and review ownership. The spreadsheet lost several decorative status columns and gained links to architecture facts. Teams could now disagree in one visible place instead of maintaining separate versions of certainty. At the next review, an engineer corrected an arrow without triggering panic. The mismatch entered the log, the owner validated the configuration, and both views changed together. The organization had not frozen the architecture. It had finally given change a route into the documentation. **The next useful question:** Run a one-path reconciliation drill: compare the diagram, scope table, live configuration, and operating owner before attempting a complete redraw.