KTLO: When All of Your IT Budget Goes to Standing Still
TL;DR:
KTLO stands for Keep The Lights On: the work that keeps what you already have running. Patching, password resets, the printer, the same ticket every Tuesday.
Think of it like bailing a boat. You can bail fast enough to stay afloat indefinitely. You will also never row anywhere, because both hands are permanently full.
On a good day nobody notices KTLO, which is the point of it. On a bad day it is the reason the project you approved in March has not started, the upgrade keeps slipping, and every conversation about improving something ends with someone saying they would love to once things calm down. Things do not calm down on their own.
Beyond the Basics:
Here's the shift: KTLO is not a line item anyone chooses. It is what a week becomes when nothing forces the choice.
Maintenance work has a structural advantage over improvement work. It arrives with a person attached, it is urgent, and finishing it is visible. Improvement work has none of those and loses every time the two compete for the same hour. So it does not get cut in a meeting, it just never starts.
- Reactive work consumes the calendar first. Tickets interrupt, and an interrupted hour is not half an hour of project work, it is closer to none.
- Deferred upgrades compound. Every skipped version widens the gap, and the eventual migration costs more than the four smaller ones would have.
- Security drifts to whatever shipped by default. Nobody decided to skip conditional access. There was simply never a quiet week to configure it.
- Planning never happens, so nothing changes. Getting out requires uninterrupted time, which is precisely what the state removes.
The compounding is the part that matters. KTLO does not hold steady, it grows, because each deferral makes the next task larger. That accumulation has a name of its own, and it is why a business can feel busy and stuck at the same time.
The way out is not more effort, it is deleting the recurring work. Autopilot and Intune are the obvious examples in a Microsoft environment: device setup and policy stop being an afternoon per machine and become a profile applied automatically. Every hour removed that way is permanent, which is what makes it different from working faster.
Here's the catch: nobody hands you the hours back. Automation projects have to be scheduled against the pressure that created the problem, and the first one has to come out of a week that is already full. That is the price of admission, and paying it once is cheaper than paying the interest forever.