UX in regulated products: constraints as creative brief
When legal says no to half your ideas, you learn to make the other half work twice as hard.
The constraint problem
The first time I worked on an insurance product, legal blocked five of my seven proposed UI patterns. I was annoyed. Then I realized: these constraints were doing me a favor.
When you can't rely on dark patterns, you have to make the honest experience good enough that people choose it anyway.
What "regulated" actually means for UX
Regulated products can't obscure pricing. Can't hide cancellation flows. Can't use urgency scarcity tricks. In fintech especially, every disclosure must be legible and accessible. This sounds limiting until you reframe it: you're being asked to build the most honest version of the product.
The creative brief reframe
Every constraint is a creative brief. "You can't hide the fee" becomes "design a fee disclosure that users actually read and don't resent." That's a harder problem and a better product.
Three patterns that survive compliance
1. Progressive disclosure: Show the minimum required; let users pull more. Compliant because it's opt-in, clear because it's not overwhelming. 2. Plain language first, legal second: Write the human version. Lawyers add the footnote. Most users only read the human version — make it right. 3. State-based consistency: Every status (pending, approved, failed, expired) needs a consistent visual treatment. In regulated products, ambiguous state is a legal risk.
What I learned
Five years in regulated products taught me that constraints make designers better. The brief isn't "what can I get away with." It's "what's the clearest, most honest path through this flow." That's a better question.