IT Management: How much time do you spend turning operational data into management reports?
I’m exploring a problem that I suspect many ServiceNow / IT operations teams deal with, and I’d like to validate whether it’s actually painful before building anything.
Operational information is often spread across ServiceNow, Jira, email, Teams, etc.
For example, ServiceNow might contain the incident, Jira contains the engineering work, and an email thread contains an escalation or decision that never makes it back into either system.
Someone then has to piece everything together to answer:
- What are our biggest operational risks right now?
- Which incidents actually need attention?
- Are any upcoming changes at risk because of unresolved Jira issues?
- Are there recurring incidents we're not noticing?
- What changed since yesterday/last week?
- What does management actually need to know?
I'm considering building a small AI-based tool that connects ServiceNow + Jira initially and does two things:
Detects potential operational risks by correlating information between the systems.
Automatically produces an evidence-backed daily/weekly briefing for IT operations leadership.
For example:
🔴 Release risk detected
> ServiceNow change CHG001234 is scheduled for tomorrow, but related Jira issue APP-482 is still marked Critical/Open.
> Recommended action: Review APP-482 before approving the change.
Every finding would link back to the underlying records rather than just having an LLM generate a vague summary.
But before writing much code, I'd rather understand how teams actually handle this today.
For those working with ServiceNow in Incident / Problem / Change / Service Delivery / IT Operations:
How do you prepare daily or weekly operational reports today?
How much manual work is involved?
Do you regularly need information from Jira, email, Excel, Teams, etc. alongside ServiceNow?
And most importantly: would automatic cross-system risk detection actually solve a problem for you, or is this a solution looking for a problem?
Feel free to tear the idea apart. Negative feedback would actually be useful at this stage.