Why do architecture diagrams always go stale? I think it's the tools, not the teams.
Genuine question I've been chewing on. Every diagramming tool I've used (draw.io, Lucid, Miro, Excalidraw) treats shapes as pictures, not as instances of types. A "database" is just a labeled rectangle. With the growing complexities of applications, it seems most of the details are not being captured.
I think this is why diagrams drift, not laziness or bad process. The diagram has no relationship to the running system from the moment it's drawn — so of course it's wrong six months later. There's no shared schema to compare against, nothing to validate, nothing to flag when reality has moved.
The pushback I take seriously: maybe it's a discipline problem. Teams that care keep diagrams alive in even bad tools. Teams that don't care won't be saved by better tools.
I'm not fully convinced though. Tools shape behavior more than discipline shapes tools, in my experience.
Curious whether anyone here has worked at a company where architecture docs were genuinely healthy — does your choice of tools make the difference, or was it pure culture?