
Sign up to save your podcasts
Or


This episode is for the IT operations teams who keep it all running, work hard to close every ticket, and still watch them coming back.
A lower ticket count can mean nothing got better.
Jaro Tomik spent years as chief technologist at CDW, coaching service management leaders who were firefighting so hard nobody asked why the fires kept starting.
Every ticket, to him, means IT found out too late.
And this inspired me to invite Jaro onto the podcast. We explore his take on “zero tickets.” Most people hear zero tickets and think fewer tickets. That's the version that failed, because fifteen years of portals and chatbots did nothing but hand the work back to the user.
He believes zero tickets was never about handling problems better. It's about there being nothing to report. That only works if IT knows first, which means pulling together signals it already has and acting on them before anyone picks up the phone. Which turns the daily question from how fast did we fix it into why did it happen in the first place. He also walks through how he takes a leader from "keep the integrations running" to "you're retaining talent" in about six questions.
Two commandments run through this episode:
Both sit in the 10 commandments for the ones who keep it running.
What this episode proves: when you do it right, nobody notices.
Here's one of Jaro's quotes that shows how long this has been sitting unsolved:
"Asking end users to raise a ticket each time they have an issue actually does not really make much sense from an enterprise perspective, because I should already know that they need to raise a ticket. I should be well ahead of my game."
4 things you'll take away:
More info on the guest
From the publisher's feed
The real work of running integration and IT operations — from the people who live it.
Some integrations just connect two apps. Others hold an entire enterprise together, and when…