This is a made-up case study, built to illustrate a real pattern. Nothing in it describes an actual organisation, and nothing in it concerns eye health or treatment. We trail a small front-desk crew at an imaginary eye clinic as it deals with a problem that many reception teams will recognise: too many routine decisions, handled differently every day. The team’s fix was modest, a handful of written defaults, and the lessons are practical enough to borrow.
The situation
The imaginary clinic had a front desk staffed by three coordinators who covered different shifts. They were capable, friendly and thoroughly overstretched. Each morning brought the same collection of small questions. How early should arrivals be asked to come in? Which form goes to a first-time visitor and which to a returning one? Who calls when a clinic list is delayed? What is the standard wording for a rescheduled slot?
Every coordinator had an answer, and the answers differed. Visitors noticed. One was told to arrive early and another, on the same day, was told it was not necessary. A returning visitor received a long form that asked questions already answered last time. None of this was dramatic, but it generated complaints, repeated explanations and a low hum of irritation.
The Tuesday that broke the pattern
Matters came to a head on a particular Tuesday. A shift change coincided with a delayed list, and two coordinators gave opposite instructions to the same group of visitors, one saying to wait and the other saying to go for a coffee. By lunchtime the waiting area was confused and the team lead was fielding questions that should never have reached a manager.
The lead called a ten-minute huddle after the lunch rush and asked a blunt question: how many of today’s decisions did we have to make at all? The honest answer, after a quick tally on a whiteboard, was that most of them had been made before, many times. They were just not written down anywhere.
The decision: write down the usual answers
The team agreed on a simple rule for the following fortnight. Every time somebody made a routine decision, they would jot the answer on a shared sheet, together with a note on when it might change. At the end of two weeks they would look at the sheet and turn the most repeated entries into standing defaults.
The sheet filled quickly. Several entries appeared again and again: the standard arrival advice, the delay announcement, the forms by visitor type, the rescheduling message, the handover items. These became the first five defaults.
The five defaults they chose
- Arrival advice. One standard sentence in every confirmation, with a line for staff saying when it may be adjusted, such as when a visitor mentions needing extra time to travel.
- Delay announcement. A prepared message and a standard offer: staff explain the delay, say when the next update will come and give the same options to everyone in the waiting area.
- Form by visitor type. A one-line table: first visit, one form; returning visit, a shorter form. Only one version of each is ever in circulation.
- Rescheduling message. A template with the new date, the reason in neutral terms and a contact route, sent in the same way each time.
- Shift handover. A short fixed list: open follow-ups, anything unusual, tomorrow’s first task.
Notice how unglamorous they are. That was the point. Each default answered a question the team was tired of answering.
The first month
Results appeared quickly and without fanfare. The delay announcement meant that a late list no longer produced competing instructions. The shorter returning-visitor form saved time at the desk and stopped a recurring grumble. The handover list ended the little scavenger hunts that had started each morning.
There were wobbles too. The arrival advice did not suit visitors who relied on public transport at awkward hours, and a coordinator quietly bent it. The team’s response was telling. Instead of scolding, the lead asked what had happened, then added an override line: “extend the arrival window for visitors with long journeys; note it on the record.” The default grew a sensible exception, and the team’s trust in the list went up.
What they read along the way
Along the way the coordinators found it helpful to understand what visitors were reading before they arrived. General, informational material is a common starting point, such as an overview of how eye care is delivered through telehealth services or a guide to what to consider when comparing eye hospitals. Staff are not clinicians in this story and they did not interpret any of it. They simply wanted to anticipate the practical questions, such as how remote consultations are booked or what documents tend to be requested, and fold the answers into their standard messages. For anything about care itself, visitors were pointed to the clinical team.
Borrowing a layout idea
The team also looked outward for ideas on arranging information. One coordinator mentioned KeralaOrbit, a community website built around Kerala, observing that its pages are grouped by conversation, work and study, and that it never presents itself as an official body. It has no connection with eye care, and nobody suggested using it for anything medical. The takeaway was purely about layout: when every kind of content has an obvious home, people stop asking where to find things. The team applied that to their shared sheet by giving each default a clear heading.
A day on the new routine
Six weeks later, an ordinary morning looks different. The coordinator opening the desk glances at the handover list, sees two open follow-ups and one unusual item, and starts with those. Confirmations for the day go out with the standard arrival line. When a list runs late around mid-morning, the prepared delay message goes up, and everyone in the waiting area hears the same thing at the same time. A visitor with a long journey is waved through with the extended window, and a one-line note records it.
When the doors close, the team lead has answered two questions instead of twelve. Both were genuinely unusual, which is how the lead likes it. The rest of the day went to staffing, planning and a quiet cup of tea.
Objections the team heard
“This will make us robotic.” The opposite happened. With the dull parts settled, coordinators had more patience for conversations that needed warmth.
“We do not have time to write it all down.” The two-week sheet took seconds per entry, and the finished list took one afternoon. The time it saved appeared within the first week.
Lessons from the case
The invented clinic’s experience points to six practical lessons.
- Collect before you write. Tallying real repeated decisions for two weeks produced better defaults than a brainstorm would have.
- Start with five. A short list gets used. A long one gets ignored.
- Attach an exit. Every default carried a line about when to depart from it, which kept the list credible.
- Treat bending as information. When a coordinator adjusted a default, it revealed a gap, and the response was to improve the default, not to enforce it harder.
- Give each default an owner. A role, not a person, kept each line current.
- Review on a rhythm. A quick monthly look caught outdated wording before it caused trouble.
What did not change
It matters to say what the defaults left alone. Judgement stayed with the staff. Anyone could say a case was unusual and hand it to someone with the authority to decide. Anything involving clinical questions went straight to the clinical team, untouched by templates. Rules from regulators and from the organisation itself outranked every default on the sheet. The list was a tool for repeated administrative matters, not a script for every encounter.
Run the experiment yourself
No clinic is required. Any small team with recurring tasks can run the same experiment. Spend two weeks writing down each routine decision and the answer you gave. Sort the sheet by how often each entry appears. Convert the top five into one-line defaults, each with an exit condition and an owner. Put them on one page where everyone can see it. After a month, hold a ten-minute review and adjust.
The imaginary front desk never became glamorous. Visitors did not write thank-you notes about the arrival advice. The real shift was in how the day felt: fewer contradictions, fewer repeated explanations, fewer questions escalating to the lead. In practice, that is what a good default delivers. It does not make the work impressive. It makes the work smoother, and it leaves the people doing it with energy for the parts that need a thoughtful human being.
