Seeking Insights: Problem Management, Roles and Responsibilities (Ownership, Accountability)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2025 05:53 AM
Hello everyone,
I'm a Product Owner for IT Problem Management at a multinational company with teams across AMS, EUR, and AOA. I'm looking for some guidance on the optimal timing for creating a Problem Record in ServiceNow.
Specifically, I'm interested in:
Market best practices: Are there any widely accepted industry best practices or common triggers for when a Problem Record should be logged in ServiceNow?
Problem Record initiation: Who is typically responsible for opening a Problem Record after a related incident has been resolved?
Assignment after incident resolution: To whom is a Problem Record usually assigned immediately after its corresponding incident has been resolved?
Any insights or experiences you can share would be greatly appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 10:45 PM
on https://www.servicenow.com/community/itsm-articles/it-service-management-knowledge-amp-troubleshooti... I have curated some resources which might help you.
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 11:37 PM
I am not sure whether you have access to assets in nowcreate, you can find useful information about problem management in below link. Also attaching you the process guide which may be helpful for you.
For your first question, I suggest reviewing the ITIL course : below are some practices when a problem record will be created.
1. Recurring incidents : Multiple incidents with similar symptoms or categories over a defined time frame.
2. High Impact or Major Incident : A Major Incident is declared that disrupts critical business operations.
3. Root cause unknown : An Incident is closed with a workaround but without identifying the root cause
4. Repeated Workarounds : Incidents are consistently resolved using the same workaround
5. Monitoring Alerts or Trend Analysis : Proactive detection from monitoring tools, AIOps, or analytics dashboards showing potential failures
6. Significant SLA Breaches : Repeated SLA breaches for similar issues
If my response solves your query, please marked helpful by selecting Accept as Solution and Helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2025 07:44 AM
The best way to start is by going to Now Create → Assets → and searching for "Problem Management".
You'll find the process workshop and blueprint there, which will give you much more clarity on the entire flow.
Highly recommended for a structured understanding!
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************