Dinesh is thirty-four, works in logistics and has a free window of about twenty minutes at lunch. His mother has had back trouble for months, an appointment at a spine hospital is booked for next week, and he is the family member who will take her. He types a question into a search bar: what should we expect at a first spine hospital visit? What he finds is a wall of text addressed to “patients” in general. This piece compares two ways of writing that same visit guide, one for everyone and one for Dinesh, and shows why the second is shorter, calmer and more useful.
A quick boundary first. Everything here is general information about how a visit tends to run. It is not medical advice, it says nothing about which treatment is right for anyone, and the hospital team and your family’s own doctor remain the people to ask about the person you love.
The brief we are comparing against
Both versions answer the same practical question for a spine hospital visit guide: what happens between the front door and the car park, and what should a relative do? The difference lies in who the writer imagines on the other side of the page.
- Version A imagines a crowd. It lists every department, every possible test, every possible outcome, and ends with a reminder to “consult your physician”.
- Version B imagines Dinesh: twenty minutes, a mother who does not like fuss, a phone with a cracked corner, and a general wish not to look unprepared at the desk.
Round one: length and order
Version A opens with the structure of the spine, moves through categories of conditions and closes with a long section on “types of specialists”. It is accurate and nobody reads it to the end. Dinesh scrolls, finds nothing about the actual morning, and closes the tab.
Version B opens with the morning. Arrive early enough for registration. Bring the referral letter if there is one, along with identity papers, any scans, reports and the current medicine list, in a single folder. Expect a conversation about history before any examination. Expect to wait. That is the first page, and Dinesh can screenshot it. The longer background reading sits below, for the evening, where it belongs.
Verdict: B wins on order. The reader’s next hour determines the structure, not the writer’s table of contents.
Round two: vocabulary
Version A uses clinical terms from the first paragraph and defines them later, if at all. Version B uses the words Dinesh’s mother already uses (“the pain in my lower back”, “it shoots down my leg”) and introduces a hospital term only when he is likely to hear it, with a plain gloss beside it. When he later reads about how back pain is generally assessed, he arrives with enough footing to follow. For that deeper reading, our piece on the everyday reasons people end up with back pain is a gentle place to start, and the guide to when specialist spine care enters the picture explains the general pathway without telling any individual what they need.
Verdict: B wins again, and for a plain reason. Words a person already owns are quicker to read than words they must look up.
Round three: the emotional temperature
This is where the two versions differ most. Version A is neutral to the point of coldness, since it assumes nobody in particular is frightened. Version B knows Dinesh is a little worried that his mother will downplay her pain in front of the doctor, and that he wants to help her speak without taking over. So it offers him one small practical idea: before the visit, ask his mother to describe, in her own words, what a bad day looks like, and jot it down. He is not diagnosing anything. He is simply helping a person tell her own story clearly to a professional.
That is a kinder piece of writing, and it is also shorter, because it leaves out everything he does not need.
Verdict: B, by a distance.
Round four: what each version asks of the reader
Version A asks Dinesh to figure out what applies to him. Version B asks for three small actions: pack the folder, write down the bad-day description, and decide who will do the talking at the desk. There is no heroic act in any of them, which is exactly why he will do them.
Put side by side, the pattern is easy to see.
- Opening: A explains anatomy; B explains the morning.
- Language: A borrows the hospital’s words; B borrows the family’s.
- Length: A tries to be complete; B tries to be finished.
- Ending: A repeats a disclaimer; B offers a next step Dinesh can take before dinner.
Round five: after the appointment
Most visit guides stop at the hospital door, which is a pity, because that is when Dinesh has his next set of questions. Version A has nothing to say about the drive home. Version B does: before leaving the building, ask for the name of the department to call with questions, ask how reports and results will reach the family, and write down the date of any next visit while the desk is still in front of you. On the way home, he can ask his mother what she remembers being told, and add his own notes beside hers. Two memories are better than one, and nobody leaves with a vague sense that something was missed.
He might also keep a single page in the folder headed “questions for next time”. It costs nothing, takes no medical knowledge and makes the second visit calmer than the first.
Verdict: B again, and by now the scoreboard is lopsided for a simple reason. A guide that follows one real reader through a whole day always has more to say about the parts that matter to that reader.
Where writers practise this
The habit of writing to one named reader is easier to build away from the pressure of a hospital website. Some people try it on a personal blog, and iBlogUp is a blogging platform where a writer’s stories live under a personal address and readers can follow by RSS. Writing a few posts there to a single imagined friend, perhaps the sibling who lives in another city, is a good rehearsal before drafting patient information. The practice is the same: choose the reader first, then choose the words.
A quick method you can reuse
If you write health information, or you simply want to explain something to your own family, try these steps before you draft.
- Give your reader a first name, an age and a job. Choose someone real if you can, or a composite who feels real.
- Write down how many minutes this person has and where they are reading. A phone in a corridor is a different page from a laptop at home.
- List the three questions they would ask if you were sitting next to them. Answer those first.
- Cut every sentence that exists only to protect the writer. Keep the single plain note that a clinician must make the decisions.
- Read the draft aloud to someone. If you stumble, the reader will too.
A note on fairness to Version A
Version A is not useless. A library of reference material is valuable, and some readers will want the long form. The point is that it should sit behind a short, human front door. Dinesh will happily read the long version after his mother’s appointment, once the immediate panic has passed. What he should not have to do is wade through it first, standing in a car park with a lunch hour ticking away.
Writing for one person is not a loss of rigour. Every fact in Version B is the same as in Version A, so nothing was invented or dropped; the order and the voice changed. A site that serves patients and families well does not need more pages. It needs pages in which each reader can hear their own question being asked.
The practical takeaway
When Dinesh walks into that spine hospital next week, he will have a folder, a handwritten note in his mother’s words and a clear idea of who will speak first. Everything beyond that is for the clinicians to explain. If you are the Dinesh in your family, take the same three steps. If you are the writer, picture him before you type the first line.
