BestCardiacHospitalsGet Free Quote

Five Myths About Rereading Your Admin Goals Every Month

Health Technology

Busy teams in any health-related setting carry a long list of routine goals for the administrative side of their work: tidier records, smoother scheduling, better handovers of paperwork. This article is strictly about that non-clinical side and offers no medical advice. Many teams skip a regular look at those goals because of beliefs that sound reasonable but do not hold up. Below are five myths about rereading admin goals monthly, each followed by what usually holds true.

Myth one: “We are too busy for a monthly reread”

Busy teams feel this one most strongly, and it is understandable. But the reread is short by design: half an hour at most, and often less. The real comparison is not between thirty minutes and nothing. It is between thirty minutes now and the hours that disappear later into chasing outdated goals, redoing work that a stale goal prompted, or sitting in meetings about priorities nobody agrees on. A brief, regular look is usually cheaper than the confusion it prevents. If thirty minutes truly cannot be found, begin with fifteen and a list limited to the most important goals.

Myth two: “Goals do not change that quickly”

It is tempting to assume that administrative goals are stable. In practice, the context around them moves constantly. Staff rotas change, a shared system is updated, a supplier alters its process, a new colleague points out a better route. A goal written to fit last quarter’s circumstances can look odd by the next. Even when little has changed, the reread confirms it, and a confirmed goal is easier to commit to than one nobody has checked. So the question “has anything moved?” is worth asking monthly, even if the usual answer is “not much”.

Myth three: “Rereading means rewriting everything”

Teams sometimes imagine the monthly reread as a full redesign of the list, which sounds exhausting. It is not. Each goal gets one of three quick verdicts: it stays as written, it is reshaped slightly, or it is released. Most goals stay. A typical sitting changes just a few lines. Treat any urge to overhaul the entire list as a sign that the review has been postponed for too long, and return to the small-change rhythm next month.

Myth four: “Dropping a goal means we failed”

This myth does the most quiet damage, because it makes teams cling to goals that no longer help. Releasing a goal is a decision, not a defeat. Perhaps the problem was solved some other way, or the priorities shifted, or the goal was too ambitious for the resources available. Recording a one-line reason makes the decision visible and dignified. A parked page, where released goals rest, removes the sting further, since nothing is erased and anything can return if circumstances change.

Myth five: “We need special software for this”

No software is required. A shared document, a notice-board sheet or a page in a folder will do. Tools can be convenient, but they also tempt teams into building elaborate trackers that take more time than the review itself. A better rule is to use whatever the team already opens every day. If you want to think about household-scale organisation as an analogy, one write-up on budgeting your earliest pay packets with a money-tracking app shows how a simple tool and a clear routine can work together, even though it concerns personal money and not office administration.

A passing mention of learning-style sites

Some people on these teams also keep personal learning goals, and browse general sites for ideas on how topics can be grouped. One such site is AirCrewU, an independent site with online courses and articles for aviation professionals, as it describes itself. It has nothing to do with health administration, and this article takes no view on its content.

The plain version of the habit

Stripped of the myths, the habit is plain. Once a month, the team reads each administrative goal aloud, asks whether it still fits, and records a verdict. The sitting is brief, friendly and written down. A named role owns each remaining goal. A single follow-up action closes the session. That is it. Nothing about the routine calls for expert skills, special budgets or a change in how the team delivers its core services.

Bonus misunderstanding: “A reread replaces proper planning”

A sixth belief sometimes sneaks in: that the monthly reread is a substitute for formal planning. It is not. The reread does not set budgets, define policy or settle compliance questions; those belong to the people responsible for them and to whatever procedures already exist. What the reread does is keep a routine goal list honest between larger planning cycles. Think of it as light maintenance, not as a governing document.

What each myth costs a team in practice

It is worth looking at what the myths do when they go unchallenged. A team that believes it is too busy tends to accumulate a growing list that nobody trusts, so every new initiative starts with an argument about what is really in scope. A team that believes goals are stable discovers the mismatch only when a colleague returns from leave and asks why a certain task is still listed. A team that thinks rereading means rewriting avoids the sitting entirely and ends up with the oldest goals. A team that equates dropping with failure keeps carrying commitments that nobody can explain. And a team that waits for software spends months choosing a tool instead of using a page of paper.

Each of those costs is modest on its own, which is exactly why they go unnoticed. Together, they produce a quiet drag on morale: people sense that the list is out of touch, and they stop paying attention to it. A short monthly sitting restores some credibility, and credibility is what makes a goal list worth maintaining at all.

A small story of a first sitting

Consider a small administrative team that tries its first reread with low expectations. They find ten goals. Four are still relevant, so they stay. Two are reshaped, one because it was too large and one because its wording confused a newer colleague. Three have been overtaken by events, and the team releases them with a laugh. The tenth belongs to a role that no longer exists, so it is handed to someone new. The whole sitting takes twenty-five minutes. Afterwards, one team member remarks that the list finally looks like the actual week. Nobody had to change how they deliver their work; they simply tidied the paperwork about it.

How to test the habit for three months

  1. Pick a recurring date and a thirty-minute slot, and put it in the shared calendar.
  2. Gather every routine administrative goal onto a single page.
  3. At each sitting, record a verdict and a one-line reason for every goal.
  4. After three sittings, read the reasons together and note any repeating patterns.
  5. Decide whether to keep the habit, adjust the timing or change the format.

Trying it for a defined period removes the pressure of committing forever. If after three months the team finds no value, it can stop. Most teams find at least one benefit: a shorter list, clearer ownership or fewer forgotten tasks.

Another angle for curious readers

People who think about how skills and routines fit together sometimes enjoy reading about structured practice plans, such as the round-by-round practice schedule for technical interviews on this site. It concerns a different subject entirely, but its emphasis on regular, small steps echoes the spirit of the monthly reread.

Limits worth stating clearly

The habit covers routine, non-clinical administration and nothing more. It carries no medical, legal or financial advice and leaves untouched any clinical or regulatory process. If a goal touches on patient care or on rules that apply to your organisation, leave it to the responsible staff and to official guidance.

Wrapping up

Each of the five myths is a reason to postpone a habit that costs little and returns clarity. The busy-team myth overlooks how cheap the reread is. The stability myth overlooks constant change. The rewriting myth overlooks how small the edits are. The failure myth overlooks the value of letting go, and the software myth overlooks how simple the tools can be. Pencil in the first sitting for this week and keep it brief. Afterwards, ask the team a single question: is the list closer to the real week than it was before? If the answer is yes, the habit has already paid for itself, and the second sitting will feel easier than the first.