The New Year Ops Reset: A 3-Week Plan

Every January, practices resolve to "get more organized" or "fix billing," and every February those resolutions are gone, because a vague intention has no baseline, no owner, and no end. The reset below is the opposite: three weeks, one measured leak, one fix, made permanent. It uses January's momentum to finish one real thing rather than start many.

Why three weeks, not a resolution

The reason most new-year improvement fails is not lack of effort; it is lack of focus and finish. A practice tries to fix everything at once, spreads itself thin, and completes nothing, so by spring it is running exactly as it did in December. The three-week reset is built to avoid that trap by doing the opposite of a resolution: it insists on one measured problem, one fix, and a hard finish. Three weeks is deliberate, long enough to do real work, short enough to stay inside the burst of January motivation before it fades. And the sequence, measure then fix then systematize, matters, because each week sets up the next: you cannot fix what you have not measured, and a fix that is not systematized will not survive February. Do this once well and you have both closed a real leak and proven a method you can repeat every quarter. It is the tactical kickoff of the one-page annual plan in the 2027 planning guide.

Week 1: Measure

You cannot improve what you have not quantified, so week one is pure measurement, and nothing else. Baseline your core numbers: denial rate, days in AR, no-show rate, and prior authorization hours per physician, the same operational metrics that belong on a weekly dashboard, detailed in the KPI guide. Pull the actual figures, not your impression of them, because the gap between what a practice assumes and what is true is usually where the biggest leak hides. Then compare each against its benchmark, days in AR under 35 to 40, denials under 5%, no-shows under 5 to 7%, and find the widest gap. That gap is your target for the year's first fix. Resist the urge to fix anything this week; the discipline is to measure honestly and pick one leak, using the map in the revenue leakage guide. If you want the fastest path to the number that matters most, the free Leak Audit quantifies your biggest leak with you in fifteen minutes.

Practically, pulling these numbers does not require a data project. Denial rate and days in AR come from your billing system or clearinghouse reports; no-show rate is no-shows over scheduled from your practice management system; prior auth hours you can estimate from a week of honest tracking by whoever handles them. Write the four numbers down in one place with their benchmark next to each, and the picture is usually stark, one or two numbers sit far worse than the rest. That is the leak. Do not overthink the measurement; a rough but honest baseline you can act on this week beats a perfect one you are still assembling in March.

Week 2: Fix one thing

Week two is where the focus pays off: you install one fix for the one leak you found, and you ignore everything else. If denials are your gap, put in the front-end prevention checks that stop the biggest categories, from the denial data. If prior auth is eating hours, stand up a real pipeline with aging alerts, the core of the Zero-Slip system. If no-shows are the leak, install the reminder-and-backfill workflow from the no-show guide. The rule is one fix, fully installed, not three fixes half-started, because a single change carried all the way to done will move a number, while several partial changes move none. It is genuinely better to close one leak completely in January than to dabble at five. Pick the biggest, build it, and get it working before you touch anything else.

Installing a fix in a week is realistic if you scope it tightly, so resist the urge to build the perfect system and build the version that works and can be improved later. If the leak is denials, that might mean adding two front-end checks to the intake routine and assigning them to a specific person; if it is prior auth, standing up a single tracked pipeline with one aging alert; if it is no-shows, turning on a confirm-and-call cadence for the highest-risk visits. Each of those is a week's work, not a quarter's, precisely because you are fixing one leak rather than rebuilding operations. Get the minimum useful version running, watch the number for a few days to confirm it is moving, and refine from there, rather than waiting for a complete solution before you start. Done and improving beats perfect and unstarted, and a fix that is live and rough this week will teach you more than a polished plan still on paper. The momentum of seeing one number actually move is also what carries you into week three with the energy to make it permanent.

Week 3: Systematize

A fix that depends on you remembering to do it is not fixed; it is borrowed time. So week three makes the change permanent by turning it into a system. Write the SOP so the fix is documented and anyone can run it, assign an owner so it is someone's explicit job, and set the cadence, the weekly review that keeps the number you moved from drifting back, tracked on the dashboard from week one. Add the relevant recurring tasks to the recurring tasks tracker and, while you are systematizing, get every renewal date for the year onto the revalidation calendar so credentialing never becomes this year's fire. The test of week three is simple: if you went on vacation next week, would the fix hold? If yes, you have systematized it. If it would quietly revert, it is not done. Systematizing is what separates a January improvement that lasts from one that fades by March.

The mistakes that derail a reset

Four errors turn a promising reset into another abandoned resolution, and all four are avoidable. Skipping the measurement: jumping straight to fixing without a baseline means you cannot tell whether anything improved, and you often fix the wrong leak, the loud one instead of the costly one. Fixing everything at once: the single most common failure, spreading three weeks of effort across ten problems so none gets finished; the discipline of one leak exists precisely to prevent this. Not systematizing: installing a fix but never writing it down or assigning it, so it quietly reverts the moment attention moves on, and by March you are back where you started. And no owner: a fix that belongs to "the practice" belongs to no one, so name a specific person for the SOP and the cadence. Notice that three of the four are about finish, not start, which is the whole point: the hard part of improvement is not having the idea, it is carrying one change all the way to permanent. Avoid these four and the reset holds.

After the reset: keep it going

Three weeks in, you have closed one real leak and built the habit of measure-fix-systematize. The final move is to make it repeatable rather than a one-time January event. Run the same three-week cycle each quarter against your next-biggest leak, and keep the weekly dashboard so you always know which number to aim at next. Over a year, four focused cycles close four real leaks, which is vastly more than a January resolution ever delivers, and each one compounds because a systematized fix keeps paying off while you work on the next. Fold the quarterly cycles into the one-page plan in the annual planning guide, run the daily rhythm with a morning huddle, and the practice improves steadily, on purpose, all year. The point of the new year reset is not a burst of January energy; it is to start a rhythm that outlasts January entirely.

Where to go next

• 2027 Operations Planning for Independent Practices (One-Page Template) live

  A one-page 2027 operations planning template for independent practices: five areas with owners,.

• Practice Manager KPIs: The 12 Numbers to Track Weekly (Dashboard Template) live

  The 12 KPIs a practice manager should track weekly: AR, clean claim rate, denials, no-shows,.

• The 3 Leaks That Never Show Up on Your P&L live

  The three hidden revenue leaks a medical practice P&L never shows: unbilled time, enrollment.

Frequently asked questions