I used to have a major problem with system design. Every time I sat down to map out a new architecture, my first thought wasn’t actually about how the system should function. Instead, I’d ask myself: “What diagram should I draw to make this look impressive?” I’d obsess over the details. Should it be a high-level architecture map? A complex sequence diagram? Does it look “clean” enough? I wanted my work to look like those polished engineering blogs or high-end conference slides. Honestly, that pressure was paralyzing. I would stare at a blank canvas, drag a few boxes, delete them, move them around, and still feel like something was missing — not because the design was bad, but because I was treating the diagram like a piece of art rather than a technical tool. Eventually, I realized I was wrong. A system design diagram doesn’t need to look “cool” first. It needs to make your thinking visible. Example of a clear, functional diagram layout.…