When I tell people I design for regulated industries, the response is usually some version of "that sounds hard." It is hard, but not for the reason most people assume.
The difficulty isn't the regulations themselves. Regulations, for all their formality, are usually written down in one place, read by lawyers and compliance partners, and interpreted with care. The difficulty is the translation layer.
Between the regulatory text and the final product, there are usually three people who need to hold the same mental model: a legal or compliance partner, a product designer, and the customer who will eventually use the thing. Legal knows what the regulation says. Product knows what the feature needs to do. The customer knows what they actually came for. These three views rarely line up without someone sitting in the middle doing the translation work.
The translation layer is where the design actually lives.
Most of the visible design (the type, the layout, the choices of color and rhythm) is downstream of translation. If the translation is right, the design has a chance of being clear. If the translation is wrong, no amount of visual polish can save it.
If the translation is right, the design has a chance of being clear. If the translation is wrong, no amount of visual polish can save it.
A concrete example.
On a recent engagement in consumer payments, a network regulation required three specific disclosures at enrollment. The existing design packed all three into a single legal wall at the end of the flow, where customers skipped past them on autopilot and, worse, often mis-attributed which disclosures belonged to the bank and which belonged to the payment network. The compliance intent was met on paper. The design intent had not been translated.
The fix wasn't new typography. It was figuring out, step by step, where each disclosure belonged in the customer's mental sequence, and then redesigning the flow so that each disclosure showed up at the moment the customer was actually making the decision it pertained to.
Enrollment completion rose. Customer satisfaction rose. Compliance held through audit. The work wasn't prettier. It was more legible, because the translation had been done.
What this means for how I work.
Practically, this shapes the first week of most engagements. Before I map a flow or sketch a screen, I sit with the regulatory text and the legal partner and rewrite it as constraints a product team can hold in its head. Then I map the customer journey as it actually happens, not as the brief describes it. Only then do the design artifacts start to appear.
If you're designing inside a regulated industry and the work feels stuck on polish, the translation layer is probably where to look first. Clarity lives there.
This is a working draft. If you have a thought, a disagreement, or a similar story from your own practice, I would genuinely like to hear it. Send a note.