The email that started it
I'm a quality and brand compliance manager at Philips Healthcare. Not a salesperson, not an engineer. I'm the person who reads the words before they reach the customer. Roughly 200 documents a year pass through my review queue. Sometimes 180, sometimes 220, depending on how you count translation variants. It is not the kind of job that shows up in the annual report, which is exactly how it should be.
On March 12, 2024, I approved a 43-page guide. It accompanied a hospital's first installation of three Philips Healthcare product lines: patient lifts, fetal monitors, and pulse oximeters. We had checked every specification. Weight limits, sensor accuracy, cleaning methods, battery data. Technically, the guide was correct. Clear enough, if you happened to be a biomedical engineer.
Eleven days later, I got a note from Dana, the hospital's clinical educator. Her message was polite and direct. 'The nurses are not reading this guide. I do not blame them.'
My first reaction was defensiveness. We had spent five weeks on that document. Then I opened the PDF and read it the way her nurses would. The first six pages covered compliance, abbreviations, and system architecture. The word 'patient' did not appear until page 7.
The information was accurate. That was the problem.
Accurate does not mean useful
The patient lift section was a good example. We explained safe working load, sling attachment points, and the charging cycle. All correct. But a nurse using a lift for the first time needs practical answers: how many staff members should be present, which sling works for a patient with limited trunk control, and what to do if the motor stops with the patient halfway up. The answer to that last question was in a troubleshooting appendix on page 31. A busy nurse would not look there.
The fetal monitor section had the same gap. We described how the transducer tracks fetal heart rate and uterine contractions. We did not show what a normal pattern looks like, when a pattern deserves closer attention, or how to explain to a worried mother what the monitor is and is not telling them. That last piece, honestly, is as clinical as anything else in the document.
Then there was oxygen saturation. The onboarding team had asked for 'a short answer to what is spo2.' We gave them a sensor accuracy chart. Precise, and practically useless to someone who had been awake since 6 a.m.
What is SpO2, in the plain-language sense? It is an estimate of how much of the hemoglobin in arterial blood is saturated with oxygen. The probe sends red and infrared light through a fairly translucent part of the body, usually a fingertip, and measures the difference in absorption. Oxygenated hemoglobin and deoxygenated hemoglobin absorb light differently, so the device can estimate the saturation from that difference. It is not the same as a blood gas measurement. Cold hands, poor circulation, movement, some nail polishes, and bright ambient light can all affect the reading.
Here is something vendors do not tell you: most product guides are written from the engineering file outward. They start with what the product does, not with the question the user is asking. Our guide was a perfect product of that process. It answered questions nobody had and ignored the questions nurses brought to work.
I approved that guide. That is on me. I was looking for mistakes instead of looking for usefulness.
The rewrite, and what it taught me
We planned to fix the document in two weeks. We ended up spending the rest of the quarter on it, and I would do it again.
We asked Dana's team what a useful guide would look like. Their answers were practical. First, they wanted service information up front: who installs the equipment, how training works, and who answers the phone when a patient lift stops charging or a fetal monitor probe fails. Nothing in that list was confidential or complicated. The Philips Healthcare services team had always offered that support. The details just lived in contract documents instead of in the guide nurses would actually hold.
Second, procurement raised a topic we had not prioritized. Their value analysis committee now scores every product on expected service life, repairability, energy consumption, and disposal options. They asked for the Philips Healthcare sustainability documentation behind the equipment. We added a short appendix. Expected battery life for the lifts, standby power draw, repairability notes, packaging materials. Those two pages generated more conversation than any clinical chapter.
We also rewrote the clinical sections with a simple rule: every section had to answer three questions. What is this for? What should a normal result look like? What do I do if something looks wrong? We timed ourselves reading each section. If we could not find the answer within a minute, we rewrote it.
One of Dana's trainers said the old guide read like a legal exhibit. The new one read like a colleague explaining things during a handover. That comparison stayed with me.
What I check for now
By September 2024, Dana asked us to adapt the guide for their outpatient rehabilitation team. The same structure, the same plain-language approach. A support coordinator at the hospital told me that the questions coming in about the patient lifts had become less basic, which meant the training was working. I do not have a controlled study to prove any of this. But the pattern has repeated itself enough.
Some people think clear instructions are a nice-to-have, like a friendly tone in an otherwise dry document. The opposite is closer to the truth. Confusion is a form of risk. A nurse who does not trust an SpO2 reading can miss the early signs of deterioration. A caregiver who cannot tell the difference between a patient lift malfunction and a low battery might make a risky decision under pressure.
I still do not have a perfect formula for writing instructions that work for everyone. My best guess is that it comes down to respect: respect for the person who has to act on the information, often at three in the morning, with limited time and a patient who is scared. They do not need us to sound smart. They need us to be clear.
Now, before I approve any document for Philips Healthcare, I ask one question. Would this help a busy, tired person make the right call? The answer has to be yes. If it is not, the document goes back.
