Skip to content
All work

Enterprise engagement · Healthcare · Enterprise collaboration

Clinical Review — Digital Document

Turning a fragmented, invisible clinical review process into a trackable digital workspace

Workflow designCollaborationPersonasBefore / afterEnterprise UX

Overview

The review process was fragmented, invisible and impossible to track: documents circulated as attachments, feedback arrived in several formats, and no one could see status without asking.

The redesign centralises review so the document, its feedback and its decisions live together — with ownership and progress visible to everyone involved.

Problem

Fragmented, invisible, impossible to track

Reviewers worked on local copies, replied by email and relied on someone to consolidate the result by hand. Version confusion made it unclear which feedback still applied, and approval was recorded outside the artefact.

Discovery

Two questions drove the work

How do reviewers actually move through a document, and where does the process stop being visible? Mapping the current journey exposed the handoffs where feedback and accountability disappeared.

Personas & journey

Two roles with different definitions of done

The reviewer needs to read, annotate and finish without losing context. The operations owner needs to know status, ownership and what is blocked — mapped stage by stage from assignment through to approval.

Key features

One workspace, one source of truth

Structured digital review of the document with inline, anchored comments; side-by-side comparison; assignments with explicit ownership and status; version history with change context; and an activity trail that makes the review auditable.

Before / after

From attachments to a workflow

Before: parallel versions, feedback split across annotations, email and chat, no per-reviewer ownership. After: a single workspace where reading stays dominant, review surfaces are collapsible, threads resolve in place and approval is captured with the artefact.

Reflection

Collaboration is a state problem

Once review state became explicit — who owns what, on which version, and whether it is resolved — most of the coordination overhead disappeared from the process itself.

Next case study

SecureVault — Enterprise Identity & Access, without the friction

Enterprise SaaS · Security & Governance

Contact

Let’s talk about the problem, not just the solution.

I’m open to senior product design, UX leadership, design systems, and AI-native product opportunities.

Get in touch