← All case studies
Case study · Work System

From 135 recurring issues to sustained periods with zero

The platform hospitals depended on was unstable, hard to scale, and drifting toward a compliance problem. The assumption was that this was a technical fix.

Healthcare technology company Work System · Work Routine
135 → 0
Recurring operational issues
40+
Leaders trained in the method
0
New issues through sustained periods

Where it started

This company provides automated health survey platforms to hospital systems across the country. The platform is the product, and it had become unstable, difficult to scale, and exposed on security and compliance.

One hundred and thirty-five recurring operational issues were in play. The reasonable first assumption was that this was an engineering problem requiring engineering fixes.

Looking at it more closely, the pattern was different. Workflows were inconsistent between teams. There was no clear process for how an issue got identified, who owned it, and when it got reviewed. Problems were found late, which meant they were found expensively.

What we did together

We worked on how IT work was managed rather than only on the defects themselves.

Workflows defined, with clear responsibility at every stage of delivery
A regular review routine so issues surfaced early and got resolved while they were small
Standard work and best practice documented, which cut the variation between teams
Leadership capability built across more than forty leaders, so the routine did not depend on any one person

As stability improved, the same structure was pointed at compliance and scalability, which had been impossible to address while the team was absorbed in firefighting.

What changed

Recurring issues went from one hundred and thirty-five to sustained periods with zero new issues.

The platform became materially more stable, more secure, and able to scale with the hospital systems relying on it. Compliance performance strengthened and regulatory exposure came down.

Because more than forty leaders were trained rather than a handful, the improvement held. Roles were clearer and accountability sat with the people closest to the work.

What this means for leaders

Technical instability is usually a symptom. When there is no shared way to surface and own problems, defects accumulate faster than any team can fix them, regardless of how good the engineers are.

More case studies

Seventy-six measures became fourteen
Read →
A $75M backlog cleared and a $12M investment avoided
Read →
Product development cut from eighteen months to six
Read →

Is this your problem too?

Thirty minutes with a founder. We’ll tell you where the work is stuck, and whether we’re the right help.