A Front Desk Team Starts a Decision Log: A Short Story

Healthcare IT

The people in this tale are invented, yet anyone who has worked in a busy patient-facing office will recognise it. A small administrative team ran the front end of an online consultation service: answering scheduling questions, routing messages, sending reminders. Nothing clinical, just the paperwork and process around it. One quiet Monday, the team lead asked a simple question in the weekly meeting: “Why do we send reminders the way we do?” Nobody could answer. That moment started the team’s decision log, and this story follows what happened over the next few months. It is an illustration of a decision journal for administrative teams, with no medical content and no advice of any kind.

The question nobody could answer

The reminder process had been set up a year earlier by someone who had since moved to another department. It worked well enough, but it had grown odd quirks. Reminders went out at a fixed hour, in a fixed order, with a fixed wording that nobody dared touch. When a newer team member asked whether it could be changed, three colleagues said “probably not” and none could explain why.

The team lead realised that the real loss was not the process itself but the reasoning behind it. Someone had once weighed options and made a call. That thinking had evaporated, so now the process was a rule without a reason.

The experiment: write it down this time

She proposed a trial. For the next quarter, every time the team changed how it handled routine admin, someone would write a short entry in a shared document. The entry would cover what they changed, what alternatives they had considered, why they chose this one, and what they expected to see afterwards. A review date would be set. The rule had one safeguard: entries were for learning, never for blame.

The team shrugged and agreed. It sounded like a small ask.

The first entry

The first real decision arrived within a week. Staff were spending a lot of time answering the same scheduling question by message, so the team wondered whether a short written guide on the service’s own pages might cut down the repetition. The entry read: “Decision: publish a short how-it-works guide for scheduling. Alternatives: a canned reply, or leave things as they are. Reasoning: a guide can be linked from any message and updated in one place. Expectation: fewer repeated questions about the same topic within a month.”

For the sort of plain-spoken page such a guide might point to, see our explainer on what an online ear, nose and throat consultation involves shows the style of plain explanation the team aimed for. The journal entry did not copy any of its content, of course. It just recorded why the team chose to write a guide at all.

The review that surprised everyone

A month later, the team opened the entry. The expectation was a drop in repeated questions. In fact the volume of that question had barely changed, but a different kind of message had gone down: follow-ups from people confused by the wording of the reminder. The guide had helped, just not in the way predicted.

That finding mattered. Because the prediction was written down, the team could see exactly where reality departed from it. Had they relied on memory, they would probably have said “the guide worked” and moved on without noticing that it worked for a different reason. The conversation that followed led to a rewrite of the reminder wording, which in turn became the second entry in the log.

A lesson about non-obvious benefits

The team added a habit after that. For each review, they wrote two lines: “what we predicted” and “what we noticed instead”. The second line turned out to be the more useful of the two. Many of the best discoveries came not from predictions that held, but from small surprises that suggested a better question.

The entry that nobody wanted to write

Around month two, the team faced a call that went badly. A change to how messages were assigned left one queue overloaded for a week. Several people felt uneasy about writing it up. The team lead wrote the entry herself, in the same flat tone as the others: what was decided, what was expected, what happened, and where the reasoning had been thin. Her colleagues noticed that nothing terrible followed. The entry was read, a small adjustment was agreed, and the meeting moved on. That moment, more than any rule, made the log feel safe, and the entries that followed grew noticeably more honest.

Over the weeks, the log also gave the team a gentle vocabulary for disagreement, since anyone could point at a line and ask a specific question instead of a general complaint.

Sorting luck from judgement

A few entries later, the team faced a quieter test. They had changed the order in which incoming messages were sorted, expecting faster replies. For two weeks, replies were slower. The easy conclusion was that the change had failed. But the entry noted that the period included an unusually busy stretch caused by a system outage on the partners’ side. The team marked the entry “reasoning sound, result unclear” and kept the change for another month. By the next review, the numbers had improved. Without the written context, the change would likely have been reversed.

That is the real discipline of a decision journal. It lets you judge a choice by how well it was reasoned, with the outcome as a separate piece of evidence rather than the final verdict.

Shared money, shared reasoning

The team’s own budgeting for small office costs eventually joined the log too. One member wrote a short entry about dividing a modest shared expense among colleagues, drawing on our article about a tidy way to divide bills among several people. Again, the entry captured why a particular approach was picked and what the writer expected, not the details of anyone’s finances.

A small bridge to everyday choices

As the habit spread, a few people began using it at home. One colleague wrote about how she planned to get around on a rare day off and mentioned in her notes that she had browsed MotoShareGo, a web marketplace where motorbikes and scooters are listed for hire and sharing, with sign-in run by a central account service. Her entry was not an endorsement. It simply logged why she looked, what she compared and what she expected, which is exactly what the journal is for.

Where the team stood after three months

The weekly meeting changed first. Instead of arguing from memory about why things were done a certain way, people opened the log and read. New joiners caught up in an afternoon rather than a month. And the question that started everything, “Why do we send reminders the way we do?”, finally had an answer, one with a date and a reason attached.

Perhaps the most telling shift was in tone. People stopped saying “that never works” and started saying “what did we expect?” The second question invites evidence; the first invites argument.

Take the idea back to your own team

No special occasion is needed. Choose one routine process in your office. Write down what you know about why it exists. Where the reasoning is missing, make a note of the gap, and from now on record every change with the same four fields: what you chose, what you passed over, why, and what you forecast. Set review dates, read them honestly, and never rewrite an old entry.

The team in our story never became perfect. They still made poor calls, still ran into surprises. But they stopped losing their reasoning, and in an administrative job that is the difference between a process you inherit and one you understand.