Starting to Write in Public

There’s a design review I still think about. A junior designer proposed cutting a form field. Good instinct. Wrong reason: he’d never tested it, never read the research, just felt it was clutter. He was right by accident. That bothered me more than if he’d been wrong.

Most of what I know about systems, I’ve never said out loud. Two decades of it: first in the Army, now in enterprise design. It sits in private notebooks, internal design docs, a Scripture journal nobody but me reads. That was fine for a long time. It isn’t anymore.

An idea that only survives inside your own head isn’t tested. It just feels true. The junior designer was right, but he got there by accident, and accidents don’t scale. Neither does private thinking. I’ve watched good design systems fail this way: not because the thinking was wrong, but because it never met a disagreement sharp enough to correct it.

So I’m writing here on purpose. Design systems and accessibility, because that’s the work. Faith and discipline, because that’s underneath the work. Accessibility is infrastructure, not overhead. Clarity is a leadership responsibility, not a personality trait. The uncomfortable truth is usually the important one.

I’d rather be wrong in public and corrected than right in private and never tested.