Design that survives review
In a regulated build, the question is never only whether something works. It is whether you can show how it works, why it was built that way, what you tested and what happens when it fails. That record is easier to produce when the product was designed with it in mind.
We work the constraints in early: risk, traceability, failure states, the human factors that reviewers ask about. It makes for slower first drafts and considerably faster approvals.
Real time, real stakes
Some of this work is live. An operating room, a trading floor, an incident response. The software has to be legible under pressure by someone who has no attention to spare for it, and it has to behave predictably when the network does not.
That changes the design brief. Fewer choices on screen, clearer system states, latency you can see rather than guess at, and recovery that does not punish the user for a dropped connection.
Where this comes from
Product strategy and design leadership for real-time surgical collaboration and operating-room software, built to clinical and regulatory standards, FDA and CE compliant, through an $80M Series C. Related experience in financial data products where regulators, auditors and risk functions all have a say.