Why we still draw data-flow by hand

There is always a nicer diagram in a wiki, generated last spring, with boxes that no longer exist and arrows that skip the mailer. Architecture pictures age like milk. A hand drawing done this morning ages like bread: still food tomorrow, stale next week, honest about it.

In clinic we ask learners to trace one personal-data hop with a pen. Browser to API to worker to object store to the email that goes out at 02:10. The first version is wrong. Someone forgot the antivirus appliance. Someone else forgot that the worker re-opens the file from a second bucket “for thumbnails.” That is the moment the application security audit becomes specific.

We do not ban digital whiteboards. We ban starting from the official picture. Official pictures are political documents. They omit the shameful batch. Hand drawings include the shameful batch because the person who runs it is sitting next to you and will correct the line.

A proxy log can confirm a hop. It will not tell you the hop you did not think to request. The drawing is a list of questions. The tool is how you answer two of them. Mixing those jobs up is how people generate forty-page appendices and still miss the callback.

If your handwriting is terrible, type the labels. Keep the arrows messy. Mess is a feature: it marks uncertainty. A perfectly aligned diagram usually means nobody argued with it yet.