Compliance has an image problem. The word conjures grey filing cabinets, regulatory box-ticking, the least creative corner of any business. So when a company says it has a compliance problem, the instinct is to reach for process and policy, not design. That instinct is usually wrong.
Working on document compliance for cruise-ship musicians taught me that what looks like a paperwork problem is very often a user-experience problem wearing a paperwork costume. The rules were not the hard part. The hard part was the gap between what the rules required and how painful the software made it to comply.
What compliance actually is
Strip away the jargon and crew compliance is simple to state. Before someone can sail, certain documents must be valid: a passport, the right visas, a medical certificate, various certifications, each with an expiry date. Someone has to gather them, check them, chase the missing ones, and keep them current as they expire. That is the whole shape of it.
Notice that none of that is conceptually difficult. It is a known set of documents and a known set of dates. The difficulty is entirely in the doing — and the doing is a design problem from start to finish.
Where the pain actually lived
When we looked at how it really worked, the pain was almost never the rules. It was the experience around them.
- Reminders that fired too late to act on, or so often that people tuned them out entirely.
- A document’s status living in one person’s inbox, so everyone else had to ask.
- The same expiry date typed into three different places, drifting out of sync the moment one changed.
- A musician at sea, on bad Wi-Fi, trying to upload a passport scan through an interface clearly designed at a desk on a fast connection.
Every one of those is a design decision, not a regulatory one. And every one of them was quietly making compliance harder, slower, and more error-prone than the actual rules ever demanded.
Designing the pain out
Once you see compliance as a UX problem, the work changes completely. You stop asking “what are the rules?” and start asking “what is the least painful way for a real person to satisfy them?” The reminder fires once, at the right moment, and not again. Each document has a single source of truth, so a status is something you read, not something you chase. The upload flow assumes a tired person on a phone at sea, because that is who is actually using it.
None of that changes the regulations one bit. It changes whether complying with them is a dread-filled scramble or a quiet, manageable routine. Same rules, completely different experience — and the difference was entirely in the design.
The wider lesson
This is not really about cruise ships, or even about compliance. It is about a habit worth carrying everywhere: when something feels like a tedious process problem, look closer, because underneath it is often a design problem nobody framed that way. The tedium is frequently not inherent. It is manufactured by tools that made a hard-but-bounded task feel chaotic.
Call something a “compliance problem” and you will go looking for more rules and more discipline. Call it a UX problem and you will go looking for the friction — and the friction is usually where the real fix is hiding.