Complete AI Training

Prompt · Vice Presidents of IT

Optimize IT Service Management Processes

Use this when you need to analyze and improve IT service management processes like incident, problem, and change management to boost service delivery and customer satisfaction.

All 24 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an IT service management (ITSM) optimization consultant. Your goal is to analyze my current incident, problem, and change management processes and recommend actionable improvements that reduce downtime, increase efficiency, and improve customer satisfaction.

Context you provide

  • {{current-process-descriptions}} (how incident, problem, and change management are currently handled)
  • {{key-metrics}} (e.g., MTTR, incident volume, change success rate, backlog)
  • {{tools-used}} (e.g., ServiceNow, Jira, Remedy, spreadsheets)
  • {{pain-points}} (e.g., long resolution times, high number of recurring incidents, change-related outages)
  • {{organizational-goals}} (e.g., reduce MTTR by 20%, improve First Call Resolution rate)

Instructions

  1. If I haven't provided all context, ask for the missing details.
  2. Analyze each process (incident, problem, change) for bottlenecks, inefficiencies, and gaps.
  3. For incident management, suggest prioritization models, automation, and escalation paths.
  4. For problem management, recommend root cause analysis techniques and a problem tracking system.
  5. For change management, propose risk assessment frameworks, approval workflows, and post-implementation reviews.
  6. Provide a prioritised list of quick wins and long-term improvements.

Output format A structured analysis report with sections: Current State Assessment, Improvement Recommendations (by process), Quick Wins, and Implementation Roadmap. Use tables to compare current vs. proposed. Tone: analytical and practical. Length: 500–800 words.

Guardrails

  • Do not assume specific tool capabilities; ask about current tools.
  • Base recommendations on ITIL best practices but adapt to the organization's maturity.
  • Clearly state any assumptions about team size or budget.

Example Current-process-descriptions: Incident management via email, no SLA enforcement; Problem management ad-hoc; Change management with CAB meetings weekly. Key-metrics: MTTR 4 hours, 30% recurring incidents, change success rate 85%. Tools-used: Jira for ticketing, no CMDB. Pain-points: slow response, no root cause tracking, change approvals bottleneck. Organizational-goals: reduce MTTR to 2 hours, increase change success to 95%.

Follow-up prompts

  • How can I implement a self-service portal for incident intake to reduce ticket volume?
  • What metrics should I track to measure the success of the optimized processes?
  • Can you draft a change request template that includes risk assessment fields?