The following case study is fictional: a composite team and invented events, offered to illustrate a real operational problem. It follows a small care-coordination team at a surgery-abroad facilitator that discovered, during one awkward fortnight, how much of its pre-departure routine lived in a single coordinator’s memory. Everything described is logistics and administration. No clinical decisions, procedures or recommendations appear, and none should be inferred.
The setting
A six-person team arranged travel logistics for international patients: collecting documents the receiving hospitals request, confirming dates, booking transfers and accommodation, and keeping families informed. The team’s most experienced coordinator, whom we will call Leila, handled the trickiest cases. Her colleagues often said she “just knew” what needed to happen before a patient flew. That sentence, repeated cheerfully for years, turned out to be the problem.
The fortnight everything wobbled
Leila was admitted to hospital herself for a minor, planned procedure and was away for two weeks. Three trips were in progress. Her colleagues stepped in with goodwill but without her mental checklist. One family arrived without a document the receiving hospital had asked to see in advance. Another traveller was met at the airport by a driver holding the wrong name board. A third received two conflicting confirmation emails. None of it was catastrophic, and all of it was avoidable.
When Leila returned, the team lead, Omar, resisted the urge to blame anyone. He did what a good operations lead does: he treated the wobble as data. The question was not “who forgot?” but “which steps existed only in a head?”
Looking at the evidence
Omar asked each team member to list every action they took on a typical case, from first enquiry to the courtesy message after the patient got home. He then compared the lists. Of the actions that appeared on only one person’s list, nearly all belonged to Leila. The pattern was clear: the work was repeatable, but only by her. The team agreed on a short experiment: write a runbook for the pre-departure stage, use it for the next five trips, and review how it performed.
Omar had read about this practice in writing aimed at data engineers; a blog such as TheDataOps.org keeps returning to the idea that routine work should be documented so that anyone on the team can carry it out. The team’s world was far from data pipelines, yet the principle was identical.
What went into the runbook
Leila dictated, Omar typed, and the others asked questions until every step was clear. The result was a two-page routine with seven sections.
- Intake and consent. Confirm the contact preferences and who may receive updates on the patient’s behalf.
- Document pack. The list of papers requested by the receiving hospital, a place to log each as received, and a rule that nothing is “assumed on its way”.
- Itinerary confirmation. One written itinerary, sent once, with changes issued as a replacement and the older version clearly marked withdrawn.
- Ground arrangements. Driver details, the exact name on the board, a phone number for the family, and a back-up transfer.
- Hospital liaison. A named contact at the receiving hospital, and confirmation that the hospital has the arrival details.
- Family briefing. A short, plain-language message about what happens on arrival day, with a reminder that medical questions go to the hospital’s clinical team.
- Hand-over note. What is done, what is open, who owns the next action.
How the team tested it
For the next five trips, a different coordinator ran each pre-departure stage using only the page. Leila observed without intervening. The team recorded every point where the runbook was unclear. By the third trip the list of corrections had dwindled to cosmetic edits. By the fifth, a coordinator who had joined only two months earlier ran a case from start to finish with no questions to anyone. Omar was careful to describe this as an observation, not a proven result: five cases is a small sample, and the team made no claims about percentages.
Linking the routine to what families read
The runbook also standardised the reading the team shared. Rather than improvising explanations, coordinators attached the same general resources for families preparing to travel, such as the guide to the questions worth raising with a hospital before going abroad, and the explainer on how to look into a hospital’s accreditation overseas. The runbook’s wording makes clear to staff that these are general information pieces and that every personal question belongs with the treating team.
What the case teaches
Four lessons emerge, and none depends on the specifics of surgery travel.
- Admire expertise, but write it down. Skilled people are the best source of a first draft, and the draft is the best thanks you can give them.
- Treat a wobble as evidence. A rough fortnight shows where the single points of dependence are.
- Hand it to a beginner. If just the person who wrote the page can use it, the page is unfinished.
- Keep the boundary visible. Logistics staff should have a written phrase for redirecting clinical questions.
Where the team is now
The routine has since been reviewed twice, and each review added or removed a line or two. Leila has trained two colleagues using the page and now spends part of each month improving it. When she next takes leave, the team expects to handle her cases without drama, though they will be the first to admit that expectation is not yet proven. The real change is cultural: the phrase “she just knows” has been replaced by “it is on the page, and if it is not, we add it.”