In January 2025, location teams reported that some of our administrative service labels reflected internal organisation more clearly than the questions people brought to them. Marketing proposed shorter labels for twelve common routes. Marcus Fenlow asked that the work preserve distinctions that clinical colleagues considered necessary, while operations wanted a naming system that staff could explain consistently. I commissioned an eight-week, A$125,000 review rather than approve a purely editorial simplification.
The work brought clinical and operational owners together with twenty selected participants reviewing fictional administrative tasks. We did not collect diagnoses, treatment histories or opinions about the quality of care. The participants helped identify where a label failed to explain the next administrative action; the specialists determined whether a proposed change preserved the intended meaning. Eight labels were rewritten and four retained after review. The count describes decisions on wording, not an improvement score or evidence that all future readers would interpret the terms identically.
The retained labels mattered as much as the revised ones. In some cases, replacing a specific term with a friendlier phrase would have made the route less precise. We added supporting explanation where appropriate instead of treating shorter wording as an absolute objective. Each revised label had a documented owner and a route back into review if the underlying service changed. The work did not recommend a test, imply that treatment was needed or allow marketing to settle a clinical question through the choice of a heading.
The concession was a less uniform vocabulary than the first creative proposal. Some routes needed more explanation, and the review took time from colleagues whose main work was elsewhere. I accepted that cost because the purpose was useful understanding, not a naming system that looked simplest in a design file. The result was twelve reviewed decisions with their reasons retained. It reinforced a practical distinction for my team: plain language should make the appropriate action easier to identify while preserving the professional meaning on which that action depends. When those two aims conflict, the answer may be a fuller explanation rather than a more confident headline.