Carlos leaned forward. “And the forty-seven-minute crash?”
“That becomes our first Problem ticket,” Maya said. “We find the root cause. We write a fix. We make sure it never happens again.” itil 101 understanding the basics
Maya smiled. “We start with the service desk. One number for everyone to call. One log of every issue. No more sticky notes and whispered favors. Then we define our first three services: order entry, dispatch routing, customer notifications. We design them, set targets, and measure everything.” Carlos leaned forward
Now, CEO Helen was pacing in the conference room. “Maya,” Helen said, not looking up from her tablet, “explain to me why we can’t just fix things?” We write a fix
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.
“Right now,” Maya said, “we handle everything as a crisis. A driver’s app freezes, we reboot. A router fails, we buy a new one. That’s heroics, not strategy. ITIL says: first, define the service . What are we actually providing?”
Maya took a breath. “We’re fixing symptoms, not causes. We need a system. A playbook.”