Practice notes on service design, AI in the loop, and the systems that serve people.

I spent the last few weeks doing something I don’t recommend. I tried to figure out what was actually happening in the world.

I designed a federal application — every screen, every label, every flow. Then I walked it screen by screen as a user instead of its designer, and I hit a document upload labeled “If Applicable.” Same words. My words. Completely different meaning.

He said: product owns quality. I pushed back. That’s what a QA team is for. He said it doesn’t matter. You can have the best QA team in the world and they’ll tell you the buttons work and the flows complete.

The code is easy. The humans are hard. Last week’s navigation debate: executive couldn’t find the hamburger menu, front-end dev loved his blue banner, engineering lead feared scope creep, ops liaison needed tickets by Friday. Everyone’s right. I had a working solution by end of week.

Document verification sits at the center of most bureaucratic processes. What should be simple becomes a nightmare of inefficiency that wastes thousands of mission hours annually. The problem isn’t outdated technology or stubborn employees. It’s a workflow design failure.