Translating clinical trial workflows into a usable digital system — for users who were expert, time-poor, and had a paper process they already trusted.
This case study picks up after a requirements reset on a clinical trials digitisation project — the analytical groundwork had been done, the workflows were properly mapped, and the brief was sound. The UX challenge was distinct: designing a system that three different clinical user types would actually adopt, in an environment where the paper alternative was familiar, fast, and trusted.
If it slows me down, I'll go back to the forms.
— Clinical researcher, workflow sessionThat comment shaped every design decision that followed. The paper workflow wasn't just habit — it was a known quantity in a compliance-sensitive environment. Any digital replacement had to earn its place by being immediately legible to people who hadn't asked for it.
Direct access to end users was limited throughout. A Senior Lab Technician served as the primary operational contact, which meant design decisions were often validated through one person's interpretation of three distinct roles rather than by the users themselves. That filter was managed by structuring reviews around specific, role-bounded questions — but it remained a constraint worth naming.
Recording observations under time pressure, often away from a desk. Any friction in the data entry flow would be abandoned in favour of paper. Familiarity at first glance was non-negotiable.
Primary consumer of captured data. High analytical literacy and zero tolerance for ambiguous or incomplete records — a system that accepted partial data was worse than no system at all.
The operational centre — scheduling, cross-role communication, exception handling. Most motivated to see the paper system replaced, and most dependent on real-time visibility of flags and handoffs.
Observation entry screen — mid-fidelity wireframe with design rationale annotations. Layout mirrors the paper form sequence. Exception flags replace the verbal coordinator handoff. Each annotation corresponds directly to a user story acceptance condition.
Rather than a formal design system, the project ran on four working principles derived from the user research. These were used as a practical filter at every wireframe review.
Screens were organised around how users thought about their work — by trial, by patient, by observation event — not around how the system stored data. Clinical logic, not technical logic.
Language was drawn directly from the paper forms. A clinician should read a field label and recognise it immediately, not translate it. Nothing was relabelled to match generic UX conventions where the organisation's own terminology was more precise.
Exception flows were treated as primary design territory — not edge cases. The coordinator role depended on them. Validation errors stated exactly what was missing and how to fix it. No vague states, no apologetic copy.
UX artefacts were produced in parallel with the rebuilt requirements set — each wireframe paired with the user stories and acceptance criteria it corresponded to. Development received a coherent, traceable package.
The single thing this project changed about how I approach clinical UX: familiarity is a feature. Mirroring the paper form's sequence was the most effective trust-building decision made — users recognised the screen before they read it.