Operating example
When deferred maintenance consumed the capacity it was supposed to protect
What was happening: Production ran across hundreds of servers with abandoned patching, no active endpoint protection, unsupported firewalls, and aging storage.
What kept causing it: The issues looked technical and separate. No one owned how the work moved from start to finish.
What changed: The work started with a documented baseline, endpoint protection, patching, and ownership. Modernization followed after the operating problem and cost model were clear.
Read the exampleOperating example
When the company sold faster than it could deliver
What was happening: Contracts were multi-year with annual value, and invoicing did not begin until go-live. Implementations waited roughly a year before kickoff, then took another four to eight months to reach go-live. Sales kept closing while delivery throughput stayed comparatively flat, so the queue grew and each new contract sat farther from invoicing.
What kept causing it: Scope entered after the sale. Teams accepted new starts before earlier implementations had exited stabilization. Sales, delivery, support, and product used different definitions of ready and done. The constraint was implementation throughput, not sales.
What changed: The delivery model was rebuilt around lifecycle, capacity discipline, clearer scope, go-live limits, and a defined end to stabilization. Stale signed-contract backlog fell from roughly $22M to roughly $8M while ARR grew from $3.4M to $13.8M in 2020.
Read the exampleOperating example
When the budget showed transactions but not decisions
What was happening: Capital and operating spend was spread across hundreds of lines with no usable budget structure.
What kept causing it: Depreciation, assets, licensing, support, and lifecycle decisions lived in separate sources.
What changed: A consolidated cost model reduced the budget to a manageable structure and translated infrastructure into unit costs leaders and engineers could use for decisions.
Read the exampleOperating example
When recurring incidents kept returning because the work never converged
What was happening: Major incidents repeated, broad incident resolution was slow, service-desk response was weak, and cross-team troubleshooting kept climbing management layers before the right people could work the problem together.
What kept causing it: Technical silos, weak service ownership, inconsistent queue discipline, and problem reviews that did not reliably become prevention.
What changed: Named services and owners, disciplined triage and WIP limits, weekly problem review, RCA follow-through, and peer-level troubleshooting. Major incidents fell 60% year over year; broad incident MTTR fell 79%; service-desk answered rate moved from about 58% to 99.6% within six months.
Read the example
