She clicked to the first slide: Service Strategy .
“It’s called ITIL,” Maya said, clicking a slide onto the screen. “Information Technology Infrastructure Library. Before your eyes glaze over—think of it as the grammar for how we deliver technology services.”
“The most important one,” Maya said. “CSI. We never stop getting better. Every incident, every change, every success—we ask: what worked? What didn’t? How do we raise the bar next month? ITIL isn’t a rulebook. It’s a feedback loop.” itil 101 understanding the basics
“This is the 24/7 heartbeat,” Maya said. “The service desk. Incident management. Problem management. Notice the difference: an incident is ‘the app is slow.’ A problem is ‘the database query is inefficient, causing the slowness every Tuesday at 2 PM.’ Fixing incidents puts out fires. Fixing problems prevents the fires from starting.”
Helen crushed the wilted peony in her fist, then dropped it in the trash. “Do it,” she said. “Teach us the grammar. Let’s stop being florists who happen to have computers—and start being a company that delivers happiness, reliably.” She clicked to the first slide: Service Strategy
Carlos nodded slowly. “Change management.”
The operations lead, a skeptical veteran named Carlos, snorted. “We promise ‘as fast as possible.’ Which is never fast enough.” Before your eyes glaze over—think of it as
“No,” Maya said gently. “We provide happy customers . The app, the dispatch system, the website—those are just tools. ITIL forces us to see the whole picture. Who are our users? What do they need? What are we willing to spend to keep them smiling?”