ServiceNow Problem Record and Root Cause Analysis Template
Move from repeated incidents to lasting fixes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a problem management template. Typical recurring incidents: [RECURRING_INCIDENTS]. Teams involved: [TEAMS]. Tools for analysis: [TOOLS]. A root cause needs evidence, not agreement. Fields: problem statement, related incidents and their count, impact and cost estimate, timeline, analysis method, root cause with evidence, workaround, permanent fix, owner, target date and verification. Provide a short guide to the five whys with an example chain, stopping when the answer is a cause that can be fixed and verified. Worked example (invented): 14 incidents in a month about a slow login traced to an overloaded server, fixed by adding capacity, verified by incidents falling to 2; track the incident count for the linked category over at least four weeks before and after (small numbers can mislead). Include rules for avoiding blame and for confirming a root cause, a known error record standard with workaround communication to the service desk, and a 30-minute problem review agenda with owner, decisions and dates. Terminology and options depend on the version and on local customisation, so mark unconfirmed items [VERIFY] before I rely on them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.