Humanising Healthcare at Scale

The Situation

1,450 physician bios. No single owner. No shared process.

The client was a large healthcare network running a website overhaul across multiple hospital brands. At the centre of the effort was a deceptively simple deliverable: biography pages for every physician in their network. 1,450 of them. Each one needed to be accurate, compliant with brand guidelines, and written in a voice that made the doctor feel like a human being rather than a credential list.

When I joined the programme, what existed was a fragmented set of pods working independently. Different writers, different intake formats, different review chains. No shared workflow, no agreed quality bar, no visibility into what had been completed, what was in progress, and what hadn't been touched. The launch date was fixed. The volume was not going to shrink. Something had to change.

Building the Framework

One intake form. One tracker. One quality standard.

The first thing I did was stop the existing process and map what was actually happening. Each pod had developed its own interpretation of the brief. Some were writing long-form narrative bios. Others were producing bulleted credential summaries. A few had gone off-brief entirely, building content structures the CMS couldn't even accommodate. None of it was wrong in isolation. None of it would work together at scale.

I built a standardised intake template: a structured form that captured the physician's credentials, specialties, clinical philosophy, and patient-facing tone. I paired it with a style guide that defined what humanising language looked like in practice — with before-and-after examples. I then set up a shared tracker in Asana with clear ownership columns, status stages, and a weekly reporting cadence so leadership had live visibility without requiring status meetings.

The Turning Points

When compliance added a new review gate, and when the doctors pushed back.

Midway through production, the legal and compliance team introduced a mandatory secondary review for all physician bios before they could be published. It was a reasonable requirement. It was also a process that had not been factored into the timeline. Rather than absorbing the delay passively, I restructured the production queue to front-load bios by specialty grouping, so that review batches aligned with the compliance team's own scheduling. We absorbed the new gate without extending the overall launch date.

The harder moment was feedback from a subset of physicians who felt the bios did not sound like them. A few had received drafts that were technically accurate but clinically sterile — the kind of bio that could belong to anyone with the same qualifications. I built a revision brief that went back to each flagged doctor with two alternative versions, giving them something concrete to react to. Most issues were resolved in a single round of revision. The lesson was straightforward: at this volume, you cannot treat revisions as exceptions. You have to design for them.

"A physician bio is not a credential list. It is the first impression a patient forms of the person they are about to trust with their health."

What Came Of It

1,450 bios published. On time. To brand standard.

The programme delivered every bio before the site went live. But the more lasting output was the workflow itself: the intake template, the style guide, the tracker structure, and the revision brief became the operating model for the client's ongoing content maintenance programme after the engagement closed.