
We’re back with the second installment of PulseCheck, a new way for us to check in regularly with you and the broader THWACK community. Every two weeks, we’ll post a question on a topic that matters to IT pros. Sometimes serious, sometimes light, but always focused on capturing your perspective.
If you’re new to PulseCheck, here’s how it works. Each poll is open for just under two weeks. Once it wraps, we’ll post the results, share some of the themes from the discussion, and introduce the next question. You’ll earn 150 THWACK points just for voting, and if you leave a comment that sparks conversation, you could be awarded an additional 300 points. If you participate in eight or more PulseChecks, you’ll unlock a limited-edition achievement badge.
This week’s question focuses on alert resolution. When an alert hits your system, how long does it typically take your team to respond and resolve the issue?
"While we still have to deal with those nasty major problems occasionally, the average time to resolve an alert/incident (MTTR) should be lower compared to a few years back. Our tools improve; we route alerts to the resolver group instead of everyone, and some things benefit from an automated fix. But now, let's talk about the real world. MTTR is essential, but what about MTBON, the mean time before others notice? And why does it always take MTBON+1 before we can resolve an alert? It's shocking."
@saschg
Now, let’s look at how our first PulseCheck played out.
We launched the first PulseCheck two weeks ago with a question about AI budgets in 2026. We asked whether AI was already a strategic priority for your organization, whether it is still under consideration, or whether it is not yet on the radar. It was clear from the responses that the conversation around AI is still evolving. While some organizations actively invest and build strategies, others are in early discussions or cautious about jumping in too soon. A few key themes stood out:
- Many teams are still working on integrating AI while protecting corporate data safely.
- There's a growing need for clear ownership of AI use cases, from development to decommissioning.
- Environmental impact, internal knowledge gaps, and industry-specific concerns, particularly in highly regulated fields, shape how and when AI gets adopted.
- For some, AI is already a valuable tool for scripting and code generation, but broader implementation is still a work in progress.
Here’s how the numbers broke down:
AI Budget PulseCheck Results
- It's in discussion, but no formal budget yet — 40%
- We've already allocated budget, and it's a strategic priority — 36%
- There's interest, but it's more hype than plan — 34%
- Still on the sidelines with no real momentum yet — 14%
- Not a focus for us at all right now — 13%
Thanks again to everyone who joined in. Whether you voted, commented, or followed along, we’re glad you’re part of this.
Looking forward to seeing your take on this week’s question.