Most teams proudly show off architecture diagrams that look like a bowl of spaghetti in a thunderstorm. They live in Lucidchart, draw.io, or some internal wiki, get paraded around in reviews, and then quietly ignored when real work starts. My latest Simplicity-First essay flips the usual narrative: it argues that the real test of your architecture is not how pretty the diagram is, but whether anyone on your team can sketch the core flows from memory in two minutes on a whiteboard.
In the piece, I unpack why complex diagrams survive inside organizations, how they quietly increase cognitive load and risk, and what it looks like to design systems that pass the “two-minute whiteboard test.” If you care about architectures that real humans can reason about during incidents, onboarding, and planning, this essay is meant for you.
