If you did not design the exception, you did not design the product

We still see product specs that end at “user submits.” Everything after that — failure, retry, partial success, a human having to decide — is left to engineering improvisation, or to a spreadsheet running next to the “real” system.

In payments, logistics, clinics, and public services, the exception is the job. If your interface does not make the messy case obvious, people will invent a side channel. That side channel becomes the business.

Design the queue as a first-class surface

Give operations a place to see what is stuck, why, and what they can do. Write the reasons in language they use. Log the action so audit is not a forensic exercise.

When we rebuilt Northline’s payouts console, the customer dashboard was the second screen we designed. The first was the exception list. That is the screen that pays for the project.