TASK
Develop a self-service logic configuration tool that allowed non-technical study teams to create and manage complex clinical trial logic independently from their development team, accelerating the study setup process and reducing costs.
The tool needed to be versatile to accommodate the unique requirements of a wide variety of clinical trials, yet intuitive for non-technical staff to use effectively without specialized coding knowledge.
PROJECT ROLE
Led the end-to-end UX research and design for the entire Clinical Trial Management System.
Successfully navigated large-scale, complex platform use cases and requirements for diverse internal and external users, highly regulated industry, tight deadlines and a geographically distributed team.
Balanced complex business requirements, technical constraints and an emphasis on usability.
Timeframe
2025 - 2026
Client
JAEB Center for Health Research
Role
Sr. UX/ UI Designer
APPROACH & CONTRIBUTION
Led team through ambiguity & complexity
Translated complex document-based specifications into validated logic scenarios.
Partnered with stakeholders, users, Product Management and Engineering to lead requirements gathering and ideation.
Led the concept development and design for the Logic Builder and accelerated the feedback loop by co-creation and AI-assisted prototyping.
Influenced Product Strategy & Roadmap
Identified patterns and hidden complexities early.
Accelerated stakeholder sign-off by aligning the team on “how it works” (functional logic) before diving into “how it looks” (visual design).
Maximized user experience, design consistency and engineering efficiency
Improved the user experience by iterating and validating the desirability and feasibility of the solution.
Maximized existing component usage and achieved design consistency by exploring ideas and collaborating with engineering.
PROJECT CONTEXT
The Need
The Jaeb Center for Health Research (JCHR) conducts multi-center clinical trials, provides safety monitoring and manages data for research projects. JCHR had an outdated Clinical Trial Management System (CTMS) that relied heavily on developer support and had inherited a lot of development and user experience debt throughout the years.
Desired Future
Create a custom, scalable, user-friendly platform to enable non-technical study teams to create and manage complex clinical trial setup logic independently from their development team, accelerating the study setup process and reducing costs.
Key New Features
Clinical trial self-service set-up
Form Builder
Visit Builder & Scheduler
Dynamic Menu Builder
Logic Builder
Patient Onboarding
Informed Consent Form Creation
Document Management
Challenges
Complex workflows
Versatile logic
Need to balance between flexibility and simplicity
Need to balance between versatility and standardization
Highly regulated industry
Tight project deadlines
Geographically distributed team
CONDITIONAL LOGIC BUILDER
The Vision
Starting Point
Approved study specific, comprehensive logic requirements and specifications.
Conditional Logic Builder
Self-service tool for non-technical team
Conditional logic for visits schedules and form usage without coding
Versatile and flexible to be used for a variety of studies
The Goal
Render study, user and patient specific menu and interfaces to be used by clinical site users or study participants.
CONDITIONAL LOGIC BUILDER - PROCESS & SOLUTION
Led team from ambiguity to actionable design direction
Facilitated regular discovery sessions with stakeholders and users
Synthesized research and coordinated cross-functional team alignment
Explored user needs for defining logic holistically in the context of dynamically managing forms, visits, and orchestrating system behavior subject to study protocol and participant’s data and status
I led discovery workshops with stakeholders to understand the existing process, dependencies and pain points.
I led envisioning workshops with stakeholders to define a vision and constraints.
I led a discovery session to capture existing high-level use cases and logic components for the logic configuration.
I created concept for the Logic Builder in context, which was reviewed and approved by the client for further exploration.
Led Logic Framework Definition & Product Strategy
Distilled complex document-based specifications into validated logic scenarios.
Translated logic scenarios into conditional logic framework
Drove alignment between stakeholders and engineering through prototyping
Task Specifications Analysis - I synthesized complex task specification documents for multiple studies to identify common logic scenarios and outliers (click to enlarge).
System Logic Analysis - I led a client workshop to identify built-in system logic to be excluded from the scope of the conditional logic builder (click to enlarge).
Building the Logic Framework - My detailed logic audit resulted in a list of common logic scenarios. I deconstructed each logic scenario to explore the “If…, then…” framework for user defined logic (click to enlarge).
Driving alignment between stakeholders and engineering through prototyping - I led collaborative sessions and documented input which resulted in agreed-upon conditional logic patterns (click to enlarge).
From concept to design direction - I lead concept assessment with the engineering team, after which the team decided to move forward with the solution (click to enlarge).
Maximizing user experience, design consistency and engineering efficiency
Explored multiple prototypes to improve the user experience
Created AI-assisted prototypes to facilitate user feedback and cross-functional team alignment
Influenced the roadmap by flagging complexities
AI-assisted prototype (lovable.dev) helped bridge the gap between abstract concept and an actionable design direction, validating logic scenarios and testing the desirability and feasibility of the solution.
The AI-assisted interactive prototype allowed exploring:
Logic scenarios
Nested conditions
Placement of buttons
“Dynamic” vs. “Static” value options
Component exploration - the design was further refined to address the need for a static vs. dynamic value selection.
Final Figma prototype utilizing the existing design system.
PROJECT STATUS
Logic Builder development was planned in two phases:
Phase 1 — covering simple conditions that required static values - was successfully completed.
Phase 2 - covering more complex conditions and dynamic values (based on data calculations or data coming from the online forms) was planned for later in the year.