Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.

Situation. The way things were done internally had accumulated the usual cruft — software architecture that had grown by accretion rather than design, systems that worked but not efficiently, scheduling that left people either waiting or slammed. None of it was on fire, which is exactly why it had been left alone, but it was quietly costing a lot of time.

Task. The aim was to overhaul those processes — to go find the waste and take it out rather than keep paying for it.

Action. The internal processes got reworked across three fronts: the software architecture, so it was something you could reason about and build on instead of work around; the systems, streamlined so the routine work stopped taking longer than it should; and the scheduling, so capacity was actually matched to the work. And the changes were made to stick — embedded in how the team operated rather than left as a memo everyone nodded at and forgot — because process improvements that aren’t made permanent just decay back to the old way.

Result. The overhaul saved roughly 8,000 hours by making the architecture, systems and scheduling meaningfully more efficient. That’s capacity that went straight back into higher‑value work instead of into overhead nobody had thought to question.