Читать книгу Fostering Innovation - Andrew Laudato - Страница 16

Оглавление

6 Keep the Lights On (KTLO)

At Pier 1 Imports, we got so good at the foundation level of the Laudato Hierarchy of IT Needs, KTLO, as shown in Figure 6.1, that I had to fight with my HR business partner to keep it as a metric. Because we consistently maintained 99.9% uptime, he argued that KTLO was solved, and we shouldn't be rewarded for it. I've had a CFO tell me that KTLO is table stakes, and it really “doesn't count” toward CIO effectiveness. CIOs have told me they leave this to their VP of Infrastructure so they can go off and be strategic.

Figure 6.1 Laudato Hierarchy of IT Needs

Wrong, wrong, wrong!

The moment you get good at KTLO is when you need to double down on it. Complacency is the number-one enemy of reliability. You can only go without air for five minutes, water for three days, and food for maybe a month. If you run out of water, your needs become more desperate, and falling in love goes out the window. If your customer relationship management (CRM) system gets hacked, I promise it's going to occupy your life around the clock until it's resolved. When your engineers are up all night fighting bugs, they're not much use during working hours.

In my blog post “Why CIOs Need to Pour Concrete,”⁶ I wrote, “CIOs who understand the need to build upon a concrete foundation will eschew the ‘sexy' until their platform is robust, and only then will they create a beautiful and glamorous digital experience built to stand the test of time.” KTLO is the key to innovation. It's the foundation upon which it rests.

Once the systems are robust, it's time to move up the Laudato Hierarchy of IT Needs pyramid and create a lean and efficient organization.

Note

1 6. A. Laudato, “Why CIOs Need to Pour Concrete,” (Heller Search Associates, May 27, 2020), https://www.hellersearch.com/blog/why-cios-need-to-pour-concrete.

Подняться наверх