Designing for Trust: UX Lessons from Public-Sector Software

Most UX writing is aimed at products competing for attention: e-commerce, consumer apps, anything where a bad experience means the user simply leaves. Public-sector and internal enterprise software plays by different rules. Often, the user has no alternative. They have to renew a licence, submit a claim, or log a complaint through your interface whether they enjoy it or not.

That changes what "good design" means. Delight is a nice-to-have. Clarity is the job. In practice, that means writing form labels in plain language instead of internal department terminology, showing people exactly where they are in a multi-step process and how much is left, and never letting an error message tell someone something went wrong without also telling them what to do next.

It also means taking accessibility seriously as a baseline, not an add-on: sufficient colour contrast, full keyboard navigation, and screen-reader-friendly markup, because "our users are diverse" is simply true by default when the users didn't choose to be there. We've found that designing for the person having the worst day, someone stressed, on a slow connection, using an old phone, tends to produce an interface that's better for everyone else too.