UXcalibur: A Design Studio for Regulated Industries
Design that holds up
under scrutiny.
I help regulated industries design products that are as trustworthy as they are usable, leading engagements end to end, from first scope call to shipped product.
Where this goes wrong
Five ways compliance and design fall out of sync
These are the same gaps I find on almost every regulated product I get pulled into, usually right before they turn into an audit finding.
Compliance shows up after design ships, not during it.
Legal or compliance catches the gaps in review, days before launch, and the fix becomes a scramble instead of a decision.
The fix — I bring the compliance read into the design process itself, not the punch list at the end.
The audit trail lives in a log file, not on screen.
Engineering can prove who did what after the fact. Users, reviewers, and auditors can't see it without asking someone to pull records.
The fix — I design the audit trail as a first-class part of the interface, so accountability is visible, not just recoverable.
Your design system doesn't know it's regulated.
Generic components don't encode disclosure timing, permission scoping, or privilege boundaries, so every new flow re-litigates the same compliance questions from scratch.
The fix — I build systems that carry the regulated logic in the components themselves, not in tribal knowledge.
Speed and defensibility get treated as a trade-off.
Teams either move fast and hope compliance holds up, or slow down and lose momentum chasing sign-off.
The fix — I use the same AI-fluent, ships-in-code workflow that keeps consumer teams fast, aimed at flows that have to hold up under review.
The judgment leaves when the consultant does.
A shipped deliverable doesn't teach a team what to do differently next time.
The fix — Some engagements are hands-on design, but the ones that stick are the ones where that instinct gets trained into whoever's still there after I'm gone.
Who I work with
Regulated industries don't have room for guesswork. Compliance requirements, complex permissioning, and high-stakes users mean the margin for a confusing interface is basically zero. That's the kind of complexity I've spent my career in, and it's the only kind of client UXcalibur takes on. Some engagements are hands-on design work. Others are about training an in-house team to build that same instinct for compliant, trustworthy design into how they already work.
Contractor and defense-adjacent platforms don't get to fail quietly. A confusing permission structure isn't a support ticket, it's a security incident. I've designed inside systems with strict, audited access controls, where the UI has to enforce those controls as reliably as the backend does, for users who range from field operators to compliance officers, often in the same interface.
See the ISI Defense case study→How engagements work
Discovery call
A 30-minute scope conversation, no cost, to figure out if this is a fit before either of us commits to more.
Scoped proposal
A fixed-scope project or a monthly retainer, depending on whether you need a defined deliverable or ongoing design capacity. Most engagements run anywhere from a few weeks to several months, depending on scope.
Working with your process
I work inside your existing security and review requirements, and sign NDAs as a normal part of getting started. If your team needs sign-off from legal, compliance, or security before a vendor gets access to real data or systems, that's normal here and I plan for it up front.
Solo or embedded
Some engagements are me doing the design work directly. Others are me training your in-house team so the instinct stays after I leave.
Common questions
Do you sign NDAs?
Yes, signing an NDA is a normal part of getting started.
What's a typical project size or timeline?
It varies with scope, but most engagements run anywhere from a few weeks to several months.
Do you work with our security review process?
Yes. I've worked inside procurement and security review processes before and expect it as part of working with regulated clients.
Do you do hands-on design work, or just training?
Both. Some engagements are me shipping the design directly, others are about building that judgment into your existing team. We'll figure out which one you need on the discovery call.
Can you work with an existing design system, or only build new ones?
Both. I can work within a design system you already have, or help build one from scratch if you don't.
Do you use AI in your process?
Yes. AI is part of how I work, for early structure, rapid prototyping, and drafting. It speeds up how fast I get to a decision; it doesn't make the decision. Everything that ships still goes through the same regulated-design judgment you're bringing me in for.
Free self-audit
The Regulated UX Checklist
Not ready to talk yet? Run your product through 24 yes-or-no questions on the UX failure points that turn into audit findings and compliance problems after launch.
Have a project that needs to hold up under real scrutiny?
Let's talk about what you're building and whether UXcalibur is the right fit.