Bridging the Gap Between Design, Development, and Regulatory Certification

The Challenge

The client's platform was built by an external agency and handed off to an internal engineering team for ongoing maintenance. There was no dedicated UX function. Development teams and business stakeholders were aligned on goals, but not on the language, behaviors, or design standards needed to get there.  

What was missing? The connective tissue between business intent and technical execution. Teams knew how to build and they knew what outcomes they wanted, but without someone translating between those two worlds, decisions were made on assumptions rather than evidence, and the product showed it.  

A broader organizational goal, achieving FDA and IVDR regulatory certification, made this gap impossible to ignore. Existing quality processes weren't rigorous enough to meet certification requirements, and usability engineering was the missing piece.  

The Solution

Concord placed a small, embedded UX team to serve as the bridge between development and business stakeholders. Rather than adding process overhead, the team removed ambiguity, giving developers clear, validated specifications and giving business stakeholders real confidence that what was being built matched what users actually needed.  

• Creating a shared product language. The team built a design system from the ground up and mapped the full application, establishing a consistent visual and interaction language across the platform. Clean developer handoffs replaced the guesswork that had been slowing releases.  

• Grounding decisions in real user behavior. Designs were tested with real users in clinical environments. Observed behavior replaced assumptions, and insights fed directly back into feature design and workflow decisions.  

• Building the usability engineering infrastructure for certification. Concord constructed the structured usability engineering processes required to meet FDA and IVDR standards and maintained that infrastructure across every subsequent release to keep the product in compliance.  

• Integrating, not duplicating. The team embedded alongside existing product and engineering leadership rather than creating a parallel structure. Knowledge transfer was built in from the start, ensuring continuity survived transitions on both sides.