Rekha ran the patient liaison desk at a mid-sized eye hospital, with two colleagues and a shared inbox that never quite emptied. She had a feeling that something about the hospital’s printed information was off, but she could not put a name to it until a Tuesday afternoon, when a man called Sunil stood at her desk holding a leaflet and said, quietly, “I read all of this. I still do not know what I am supposed to do tonight.” The people and the hospital in this story are invented, a way of illustrating a real editorial lesson. Nothing here is medical advice, and no treatment is judged or recommended.
The leaflet that said everything
The leaflet Sunil held was thorough. It had been written by a committee, checked by clinicians and approved by administration. It described what to expect after an eye procedure in careful, balanced paragraphs addressed to “patients and their families”. Every sentence was true. Every sentence was general.
Sunil’s mother had come home that afternoon. He was her only family nearby, he was anxious, and the leaflet gave him a great deal to read and very little to hold on to. He wanted to know, in plain terms, who to call if he had a question after the desk closed and what the evening should look like. The leaflet answered neither, because it was not written for Sunil. It was written for everybody.
Rekha’s small experiment
That evening, Rekha did something unplanned. She wrote a single page for Sunil, as if he were sitting across from her. She began with the line he had said to her: “You do not need to read all of this tonight.” Then she wrote what she would say aloud: who to call, at what number, at what hours, and what the desk could and could not answer. She left out the clinical detail, because that was for the treating doctor to explain to the family, and she added a line saying so.
The page was half a side long. She left it at the desk with a note for Sunil, who collected it the next morning and told her, a little awkwardly, that it was the first thing that had made him feel less alone.
Why it worked, as the team understood it
Rekha took the page to her two colleagues, Jaya and a part-time coordinator, and the three of them talked through why it had landed. They arrived at three observations, none of them technical.
- It answered the question he actually had. Not “what is post-operative care in general”, but “what do I do this evening”.
- It was written for a single voice. The tone was that of a person speaking to a person, which made it easier to trust.
- It said where it stopped. By naming what the desk could not answer, the page made the rest believable.
Jaya pointed out that none of this contradicted the leaflet. The leaflet was still the reference. What Sunil needed was a first page, a human doorway into it.
Looking at what was already out there
The team spent an afternoon reading how the hospital’s own published guides handled the same moments. Some did well. A piece on what families are told about care after cataract surgery gave general orientation clearly. Another, on how children’s eye hospitals support young patients after an operation, spoke to a parent’s anxieties directly. Both were useful, both were general by design, and both left room for a short, personal first page of the kind Rekha had written.
It was a reminder that the aim was not to replace published guidance. The aim was to put a person at the front of it.
Spreading the habit
Rekha did not want a policy. She wanted a habit. Over the following weeks, the team tried a modest routine: when a relative asked a question at the desk, one of them wrote a short reply as if for that person, then asked whether it could be shared in anonymised form as a model. They called these “first pages”. Within a couple of months, the desk had a small collection of them, each written for a different worry: a daughter flying in from abroad, a husband who could not take leave, a grandson who had never seen the inside of a hospital.
The collection was not a leaflet. It was closer to a set of letters, each shaped for someone, and staff began to borrow phrasing from them when speaking to families in person.
What happened when they tried to publish
The hospital’s management liked the idea, with one concern: privacy. The team agreed on firm rules. No names, nothing that points to a real patient or household, no clinical claims, and a clinician’s read-through before anything went public. They also agreed that every first page would say plainly that it was information, not advice, and would name who to ask for anything medical.
When the team looked for a gentle home for the more reflective notes, the short observations about what worried relatives ask and why, they discovered iBlogUp, a place whose blogs each get a personal address, and a feed that readers can subscribe to when they like what they find. It suited the quieter, non-clinical writing, while the hospital’s own site kept the official pages. Keeping the two apart mattered to Rekha: reflection in one place, information in the other.
The hard parts nobody tells you about
The story would be too neat if it ended there. Three things were genuinely hard.
- Resisting the urge to add. Each first page wanted to grow. A well-meaning clinician would suggest one more caution, one more definition. The team learned to hold a firm limit: half a page, one worry.
- Staying out of clinical territory. It was easy to slide from “here is what the desk does” into “here is what you should do”, which crosses into advice. Jaya acted as the guardian of that line.
- Keeping them current. This is the dull, necessary part. Phone hours change, procedures change, staff move. Every page carried a review date and a name.
A word from Jaya on tone
Jaya, who had spent years on the telephones, kept one rule for the written pages: if you would not say it in that tone across the desk, do not write it. She disliked exclamation marks and the word “journey”. She liked short verbs and the second person. Her test was whether a tired man at nine in the evening would feel spoken to or spoken at. Most of the edits the team made to early drafts were simple cuts of the second kind of sentence.
Sunil, a few months later
Sunil came back to the hospital in the spring, this time to thank Rekha rather than to ask for help. His mother had managed well, in his words, and the page he had been handed in the first week had stayed on the kitchen shelf for a month. He had taken a photograph of it and sent it to a cousin who was nervous about her own father’s appointment. “Is there one like this for her?” he asked. There was, because by then the desk had written one for nearly every kind of relative it met.
What the case suggests for other teams
A story is not an experiment, and Rekha’s team would not claim that one anecdote proves a law. But the pattern fits what many patient-communication teams report. Information written for a broad audience is accurate and unread. Information written for one imagined person is shorter, kinder and passed along. The difference lies less in talent than in whom the writer pictures.
If you work on a liaison desk, start the way Rekha did. Take the next real question, write the answer as if to that one person, keep it to half a page, and say where it ends. Then see what happens when you hand it over. A page for everybody reaches nobody in particular, and in an eye hospital, where a nervous relative may be waiting to hear what to do tonight, a single clear page written for one person can matter far more than a thorough leaflet written for all.
