Tideline
Insights
Florida ITSM Meetup · May 2026
1 / 24▾
How IT teams stop reacting and start improving — without adding headcount.
If your hand went up on either of those first two — that pattern has a name. And today you're going to leave with a way to break it.
It has a name: The Continual Improvement Gap.
Not a talent problem. Not a budget problem.
A missing operating practice.
Not methodology problems. Organizational problems.
"Everyone's responsible" means no one is. Without a named owner, it gets scheduled, bumped, and forgotten.
Teams at 100% utilization — all reactive, all the time — have no slack to improve anything. The queue always wins.
Items go in. Nothing comes out. No prioritization, no review. It demoralizes the team and breeds cynicism fast.
47 dashboards, zero consensus on which two numbers actually tell you whether things are getting better.
Budget grows. Outcomes don't. They don't fail loudly — they slowly lose the room until leadership stops asking IT for input.
Talented people leave for organizations that have time to build. You backfill constantly. Recruiting becomes the job.
Same ticket. Different number. Every week. No visible path to more meaningful work. No reason to stay.
The organizations beating you on IT aren't smarter.
They just built in time to improve.
That's the whole secret.
A structured habit of asking "what can be better?" — and actually doing something about it. On a schedule. With an owner. With a measurement.
ITIL 4 formalizes this as the Continual Improvement Management Practice — one of 34 named practices — with defined inputs, outputs, and a practice owner role. It describes CI as the ongoing identification and improvement of services, practices, and any element involved in effective service management.
Not a project. Not a certification. Not a one-time initiative. A management practice.
Your team already does this informally.
CI just makes it systematic.
Deming/Shewhart cycle — adopted directly by ITIL 4. Most organizations do Plan and Do — then stop. Everything that makes CI stick lives in Check and Act.
One process. One owner. 90-day target. Measure the baseline before you touch anything.
Execute. Document as you go. Small enough to finish beats ambitious enough to stall every time.
Compare to your baseline. Did the metric move? This is why the baseline wasn't optional — no baseline, no proof.
If it worked: standardize it. If it didn't: revise and run the cycle again. Either outcome is correct. Skip ACT and nothing ever sticks.
Most efforts die between DO and CHECK. The next slide shows exactly why.
Most common failure: too big, no owner, no metric. The fix is simple: one process, one metric, one person, ninety days.
Most organizations plan big and execute nothing. A finished small improvement beats a stalled large one every single time.
No baseline means no proof you improved. This is the step that makes the whole cycle credible to leadership.
Skip this and your team solves the same problem three times and wonders why nothing ever sticks. Embed what worked.
Link to strategy. No vision, no direction. → vision statement, stakeholder map, and scope.
Establish the baseline. Data, not assumptions. → baseline assessment, maturity rating, and capability gaps.
Set measurable targets. → CSFs, KPIs, and gap analysis. No target = no way to know if you got there.
Build the plan. → SIP, CIR entry, resource model, and risk log.
Execute the SIP. Changes go through Change Enablement. Measure in-flight.
Compare to Step 2 baseline and Step 3 KPIs. → PIR. Document the answer.
Embed in procedures. Update the CIR. Loop back to Step 1.
Teams jump straight to measuring. Without a vision, the metrics never connect to what leadership cares about. Improvement work becomes IT busy-work.
Baseline skipped because teams assume they know the current state. They don't. No baseline = Step 6 is guesswork, not measurement.
The plan finishes. Everyone moves on. Old behavior returns within 6 months because nothing was embedded into procedures. The improvement undoes itself.
Step 7 feeds directly back into Step 1. The output of one cycle is the input of the next. That loop is the practice. Without it, you ran a project — not a CI program.
ITIL 4 names this the Continual Improvement Register (CIR) — a named artifact with one job: make improvement accountable. Most teams have a list. A CIR has six non-negotiables in every entry. Miss one and it becomes a graveyard.
Specific, not vague. "Reduce password reset tickets" — not "improve the service desk."
What does fixing this unlock? Every entry must connect to real impact, not just IT convenience.
Not "the team." One person. They own the outcome — not just the tasks assigned to them.
Impact × Effort. Prioritize — don't just collect. An unranked list is just a slower graveyard.
Without a date it's a wish. With a date it's a commitment. That difference matters.
How will you know it worked? Define this before you start, not after. Non-negotiable.
Not a separate initiative. A recurring ritual. Calendar events — not ad hoc conversations.
Service desk lead reviews top 5 recurring ticket categories. Flags patterns. Updates the register.
IT Manager reviews performance vs targets. Adjusts CI priorities. Removes blocked items.
IT Director presents results to leadership. This meeting justifies the IT budget. Show up with data.
Full portfolio review. Strategic alignment with business direction. This is where IT earns a larger role — or doesn't.
The weekly 15 minutes is the most important. It's the signal that improvement is real — not aspirational.
That's the framework. The question everyone asks next: can we do this with a lean team?
You do not need:
You do need:
"The constraint isn't resources. It's the habit."
The service desk stops being where tickets go to die — and becomes where problems get solved. If you're on the service desk right now — you know exactly which process we're talking about.
From the leadership seat — this is what the room looks like 12 months in.
Show before-and-after data and the CFO stops asking what IT does — and starts asking what you need. Forrester: 195% average ROI. You can't claim it without CI.
Improvement becomes a narrative. Leadership stops seeing IT as a cost center to minimize and starts seeing it as a business driver.
The chaos drops. People have time to think. Morale improves. The best people stop leaving.
I need one volunteer. I'm going to walk you through the 3-Question CI Audit — a framework you can use with your own team next week.
Ground rules: No company names. No private data. No right or wrong answers. Think of any IT process your team runs regularly — we'll score it together.
While we work through it with our volunteer, score your own process in your head. You'll learn more that way anyway.
"Do you know how long it takes? How often it fails? Whether users are satisfied?"
"Not who runs it — who owns making it better? Is there a person who wakes up thinking about how this process could improve? Do they have calendar time for that?"
"Not a complaint in a standup. Not a side conversation. A scheduled moment where someone looked at the data and asked: is this still the right process?"
Max 6 points · 3 questions · Find your band.
Most teams in this room just scored under 4. That's not a capability problem — it's a gap that most organizations have never been shown how to close.
The goal isn't a perfect CI program. It's the first rep.
Name one CI owner — even 10% of an existing role. Schedule a "CI Review" for next week. Pull one metric you're not tracking.
Build your first CI register entry — all 6 fields. Run one PDCA cycle at any scope. One improvement, completed, builds the muscle.
Present your first improvement result to a business stakeholder. Even one data point. One before/after. This is the meeting that changes how IT is perceived.
Take a photo of this. It's the operating model.
Review data, user feedback, and incident patterns. Name the opportunity.
Measure before you change anything. No baseline = no proof.
PDCA. Scoped to 90 days. One owner. Document as you go.
Compare to baseline. Quantify the improvement. What moved?
ACT phase. Embed what worked. Feed learning back. Start the next cycle.
The register is the backlog. The rhythm is the heartbeat. The PDCA cycle is the engine. Together, they're the CI practice.
Start here
Score your process maturity in 10 minutes. Know exactly where your gaps are before you leave today.
Build the business case for your ITSM investment. Numbers your CFO will read.
All articles → tidelineinsights.com/blog
If your score made you uncomfortable — that's the point. Let's talk.
Questions? I'm here until the room clears.