Book Appointment

Case Study: A Patient Services Team Learns to Say Not Now

Healthcare IT

What follows is an invented scenario assembled from the sort of pressures that any hospital patient-services team recognises. The team in it handles scheduling letters, records requests and family queries for an oncology centre. It never touches clinical decisions, and nothing here is medical advice. What it does show, in practical terms, is how a not-now parking list can take the sting out of a workload that never stops arriving.

The team and its trouble

The patient-services group had six people and one shared inbox. Mornings began with a queue of appointment confirmations and travel letters. By ten, the queue had been joined by side requests: could the waiting-area signage be updated, could the standard letter be reworded, could someone look at why a particular form kept coming back incomplete.

The lead coordinator was practical to the point of bluntness. She did not want a productivity philosophy; she wanted fewer dropped jobs. When she audited a typical week she found that the urgent work was nearly always done on time. The casualties were the improvement jobs and courtesy follow-ups, which were started eagerly and abandoned whenever a phone rang.

The decision to try a parking list

The coordinator had read about the habit in a trade newsletter and decided to test it for four weeks with a clear boundary. Her instruction at the Monday huddle ran to a few sentences. Urgent items stay on the main task board. Anything that affects a family’s near-term arrangements gets handled the same day. Everything else, if it is not what you are doing right now, goes on the not-now sheet with your initials and a review date.

She made the sheet physical to start with, a laminated page on a clipboard, because the team distrusted another app. A column on the right held the review date, and every Thursday afternoon at a fixed hour the six of them stood around the clipboard for twenty minutes.

What week one looked like

Week one was messy. Two team members parked things that should have gone straight on the task board, including a records request with a looming deadline. The coordinator caught it at the first review and used it as a teaching point rather than a reprimand. They drew up a short list of examples of what must never be parked, taped it above the clipboard and moved on.

The sheet itself filled up fast. By Thursday it held nineteen lines, which felt alarming until the group worked through them. Six were duplicates of one another. Four had already been resolved by somebody else. Five could be done in a few minutes each, and the remaining four needed owners and dates. The meeting ended with an empty sheet and a short, clear action list.

The turning point

The change the coordinator valued most showed up in an unexpected place. One of the longest-serving team members, a person who had always answered every ping instantly, said she had completed a long reconciliation of appointment letters in a single sitting for the first time in months. The pings still came. She simply wrote them down and kept going.

That moment illustrates the principle at the heart of the method. A parked request is not abandoned; it is held safely until a better moment. The team’s trust in that promise depended entirely on the review happening on schedule. In week three the Thursday meeting was cancelled because of a staffing gap, and by Monday two people had quietly gone back to remembering things in their heads. The coordinator rescheduled the review for the following morning and added a rule that it could only be moved, never skipped.

Practical rules the team settled on

  • Every line gets a requester, a one-sentence description and a review date.
  • The sheet has a visible cap: if it exceeds one page, that is a workload conversation, not a reason to start a second sheet.
  • At review, each line ends in one of five outcomes: done, handed over, merged, scheduled or crossed off.
  • Crossed-off lines get a short note, so the requester can see their idea was weighed fairly.
  • Anything unclear is clarified with the requester during the review, not at the moment it arrives.

A parallel from engineering

When the coordinator described the method to her cousin, who works on a software release team, he said his group had been doing the same thing for years. During a deployment they keep a scratch note of tangents, such as a script worth rewriting or a naming inconsistency, and only look at it once the release is out. He mentioned a website called Reloqui, which talks about stitching together planned work, merged code, builds and deployments so that each release can be explained, as an example of the clear-eyed record keeping his field is moving toward. The coordinator did not need the details. What stayed with her was how often careful people in very different jobs land on similar habits, and how readily a good habit travels between them when someone takes the time to explain it over a cup of tea.

Handling the awkward cases

Not everything fits tidily. The team met three awkward situations during the trial, and how they handled them is worth recording.

First, a senior manager asked for a change to a standard letter and expected it that afternoon. The coordinator explained, politely and without drama, that it would be looked at in Thursday’s review unless it was truly urgent, and asked him whether it was. It was not, and it was done on Thursday.

Second, a colleague parked something that was more sensitive than it appeared, a complaint from a family. The group agreed afterwards that anything touching a family’s wellbeing or trust gets a human response the same day, even if the fix takes longer.

Third, the list began to attract wishful thinking, large ideas such as a complete redesign of the intake form. These were moved to a separate planning document so the sheet stayed focused on small, doable items.

What the four weeks produced

At the end of the trial the coordinator asked each person for one sentence on what had changed. The answers were modest and consistent. Fewer jobs were left half done. Interruptions felt less personal. The Thursday review had become the part of the week they trusted most, because it was the moment where loose ends were finally tied off.

She also noticed that the team spoke about requests differently. Instead of “I can’t, I’m swamped”, people said “I’ve put that on the list for Thursday”. It sounds like a small change in phrasing, yet it kept relationships friendly and set honest expectations.

Where to read more

Teams that support patients and families often want reference material that explains how hospitals plan and organise care in general terms. This site has an overview of how personal treatment plans are put together at cancer hospitals, and a second article on the role accreditation plays for people weighing cancer hospitals in other countries. These are general articles, and each reader’s own care team is the right source for anything personal.

Taking the case study into your own office

You can copy this experiment in an afternoon. Choose a trial period of a few weeks. Agree a short list of things that must never be parked. Put a sheet where everyone can see it, set a fixed review hour that can move but never vanish, and nominate one person to keep the rhythm going. When the trial ends, ask the team the same question the coordinator asked and listen to the answers.

The method is not clever, and that is its strength. It simply gives non-urgent requests a safe place to wait, and gives busy people permission to finish what is already in their hands.