I have shipped design across supply chain, healthcare, and fintech. Three industries where the cost of getting it wrong is not a bad review. It is a failed audit, a missed shipment, or a patient who did not get the right information at the right moment.
Most designers who come into regulated industries for the first time make the same mistake. They treat compliance as a constraint on the design. Something to work around. A list of rules handed down from legal that shrinks the creative space.
That is the wrong mental model, and it will slow you down every time.
At TrueCommerce and previously at Orderful, I was designing for supply chain operators managing EDI transactions at scale. The interface was almost secondary. What those users needed before they would change a single workflow was confidence that the system would not break something downstream. A missed transaction in supply chain does not stay in the software. It ripples into warehouses, carriers, and purchase orders across multiple organizations.
At CirrusMD, the stakes were different, but the lesson was identical. We were designing a platform in which physicians delivered care via a screen. The interface had to disappear completely. Any friction, any moment where the tool called attention to itself, was a moment that did not belong to the patient.
In both cases, the design problem was never really about the interface. It was about trust. Whether the person on the other side of the screen believed the system would do what it promised, protect what it held, and not introduce risk into a process that already carried enough of it.
That reframe changes everything about how you work. You stop asking "how do we make this easier to use" and start asking "how does this design make someone feel safer making a high-stakes decision?" Those are not the same question.
Trust is the product. The interface is just where trust gets built or broken.
If you are leading design in a regulated industry and your team is still arguing about aesthetics before they have answered that question, you are working in the wrong order.