Maya took a breath. “We’re fixing symptoms, not causes. We need a system. A playbook.”
“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.”
“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.” itil 101 understanding the basics
She looked around the room. “Right now, Bloom & Co. is running on chaos and good intentions. ITIL won’t make us perfect. But it will make us predictable . And predictable means trust. From our drivers, our customers, and yes—from you, Helen.”
The operations lead, a skeptical veteran named Carlos, snorted. “We promise ‘as fast as possible.’ Which is never fast enough.” Maya took a breath
Helen finally looked up. “A playbook? For IT? We’re florists, not the Patriots.”
She was the new IT Manager at Bloom & Co., a mid-sized floral delivery company. Her first week had been a cascade of small fires. This morning, the entire East Coast dispatch system had crashed for forty-seven minutes. Forty-seven minutes where no flowers were routed, no drivers notified, and dozens of birthday bouquets wilted in a warehouse. A playbook
Finally, Helen said, “What’s the fifth slide?”