The Care Stack

The case for small, boring wins

Victor Wilson · · 3 min read

Most health system leaders have lived through at least one big data program. A new platform, a new operating model, a roadmap full of arrows. The kickoff is exciting. Two years later, people are still waiting for the part where things get better.

I’d make a different bet. Go after small wins on purpose. The plainer, the better.

What I mean by small and boring

A small, boring win fixes one problem for one team. It moves a number someone already tracks. It ships in weeks. When it works, the people it helps might not even think of it as a data project.

Some examples of the shape:

  • Catching invoices that don’t match the contract price before they’re paid.
  • Flagging one registration error that keeps leading to the same denial.
  • Giving a unit manager an early view of open shifts, in time to fill them without agency staff.
  • Getting the OR case schedule and the supply pick list to agree, so fewer items get opened and thrown away.

None of these would headline a board meeting. Each can save real money or staff time, and someone outside the data team can check the result.

They also point at where the pressure is right now. Kaufman Hall’s October report found that non-labor expense per adjusted discharge is up 6% this year, with supplies up 5% and drugs up 6%. About 43% of hospitals are operating at a loss. In a year like this, a fix that stops overpaying on invoices isn’t a side project.

Why small adds up

Small wins earn trust you can spend later. A CFO who has watched the data team save money a few times will fund the next project without a long debate. A CFO who was promised a transformation and is still waiting will want a business case for everything.

You can tell whether they worked. One team, one number, a short window. With a big program, many things change at once, and nobody can say what caused what.

They’re cheap to get wrong. If one doesn’t pan out, you’ve lost a few weeks and learned something. When a big program misses, it can cost years and a lot of credibility.

They also leave things behind. Each one fixes a slice of data for good, because a real person now depends on it. Each one gives a business leader the experience of working with the data team and getting something back. After a dozen of these, you have cleaner data where it matters and a group of leaders who trust the team. That’s most of what the big program promised in the first place.

Keep them from being dismissed

The risk with small wins is that they look too small. They don’t sound strategic. Sooner or later, someone will ask where the vision is.

Two habits help.

Keep score. Maintain a running list of every small win, the dollars or hours it delivered, and the business owner who signed off on it. Review it with leadership every quarter. After a year, that list makes a stronger case for investment than any roadmap, because every line on it already happened.

Aim them. Small doesn’t mean random. Point your wins at the few areas that matter most to the health system, like denials, supply spend, or labor. A string of small wins in one area starts to look like a strategy, because it is one.

I’ll be honest that not everything can be small. Some work, like replacing an aging platform, takes time. Even then, you can usually break it into pieces that each deliver something a business leader would notice. If a large project can’t show anything useful for a year, take that as a warning.

The same goes for AI. The pull to announce an AI program is strong this year, and the tools to build agents keep getting easier. I’d start smaller. Put one agent on one queue, like checking invoices against contract prices, with a buyer approving every change. Measure it the way you’d measure any small win. If it saves money, add it to the list. If it doesn’t, you’ve lost a few weeks, not a year.

There’s a cultural benefit too. Teams that finish things get better at finishing things. They learn to keep scope tight and to find the business owner early. Those habits carry into every bigger project you take on later.

So here’s the ask. Go to your data leader and ask for one problem that can be fixed in the next 30 days, owned by one team and measured by a number that team already tracks. Fund it. When it lands, add it to the list, and ask for the next one.

Discussion

    Join the discussion