1

Incident Problem Manager Jobs in Michigan (NOW HIRING)

Guide and enforce that the Incident Managers to recognize situations where they should open Problem Tickets * Periodically audit Incident records and coach the Incident Management staff to * Insure ...

... Problem Tickets Periodically audit Incident records and coach the Incident Management staff to Insure that 'ticket hops' are reduced to the minimum Avoid possible misuse of 'Pending' status by ...

Examples: Incident, Change, Problem. Will act as Incident Manager with day-to-day responsibility for investigating and coordinating resolution actions for severity incidents. Departmental ...

Lead daily incident review meetings with the operations team to ensure accurate prioritization and ... Own recurring off-board and on-board issues through the Problem Management process, including ...

Key Responsibilities AMS Operations & Service Cloud Maintenance Incident & Problem Management: Lead the triage, root-cause analysis, and resolution of complex Tier 2/3 Service Cloud issues (Omni ...

Participate and/or lead incident, problem, change and service request-related activities. Includes root cause analysis. Includes proactive problem management/defect prevention activities. * Delivery ...

Participate and/or lead incident, problem, change and service request-related activities. Includes root cause analysis. Includes proactive problem management/defect prevention activities. * Delivery ...

Participate and/or lead incident, problem, change and service request-related activities. Includes root cause analysis (RCA). Includes proactive problem management/defect prevention activities.

Participate and/or lead incident, problem, change and service request-related activities. Includes root cause analysis (RCA). Includes proactive problem management/defect prevention activities. Our ...

next page

Showing results 1-20

Incident Problem Manager information

How does an Incident Problem Manager typically collaborate with technical and non-technical teams during major incidents?

Incident Problem Managers play a critical role in bridging communication between technical teams (like IT support, network engineers, or developers) and non-technical stakeholders (such as business unit leaders or customer service). During major incidents, they coordinate response efforts, facilitate status updates, and ensure all parties are aligned on next steps and remediation plans. Effective collaboration involves translating complex technical issues into clear, actionable information for non-technical audiences, managing expectations, and driving post-incident reviews to prevent recurrence. This cross-functional coordination is essential for minimizing business impact and ensuring swift resolution.

What is the difference between Incident Problem Manager vs Incident Coordinator?

AspectIncident Problem ManagerIncident Coordinator
Primary RoleManages the lifecycle of incidents and problems to minimize impact and prevent recurrenceCoordinates incident response activities, ensuring timely resolution and communication
CertificationsITIL Foundation, Problem Management certificationsITIL Foundation, Incident Management certifications
Work EnvironmentTypically in IT service management teams, focusing on problem analysisOperational teams, focusing on incident handling and communication

While both roles are involved in incident management, the Incident Problem Manager focuses on identifying root causes and preventing future issues, whereas the Incident Coordinator handles day-to-day incident response and communication. Both roles are essential for effective IT service delivery but differ in scope and responsibilities.

What does an Incident Problem Manager do?

An Incident Problem Manager is responsible for overseeing the process of identifying, investigating, and resolving incidents and underlying problems within an organization's IT systems. They work to minimize the impact of disruptions, coordinate responses to incidents, and analyze root causes to prevent future occurrences. This role often involves collaborating with technical teams, managing communication with stakeholders, and ensuring that procedures are followed according to IT service management frameworks like ITIL. Their goal is to improve IT service reliability and reduce downtime for the business.

What are the key skills and qualifications needed to thrive as an Incident Problem Manager, and why are they important?

To thrive as an Incident Problem Manager, you need strong analytical skills, IT service management knowledge, and experience with incident and problem resolution processes, often supported by ITIL certification. Familiarity with ITSM tools like ServiceNow, Jira Service Management, or BMC Remedy is typically required. Exceptional communication, leadership, and critical thinking abilities enable effective coordination and root-cause analysis across teams. These skills are crucial to minimizing downtime, ensuring service continuity, and driving long-term improvements in IT operations.
What are popular job titles related to Incident Problem Manager jobs in Michigan? For Incident Problem Manager jobs in Michigan, the most frequently searched job titles are:
What job categories do people searching Incident Problem Manager jobs in Michigan look for? The top searched job categories for Incident Problem Manager jobs in Michigan are:
What cities in Michigan are hiring for Incident Problem Manager jobs? Cities in Michigan with the most Incident Problem Manager job openings:
Infographic showing various Incident Problem Manager job openings in Michigan as of June 2026, with employment types broken down into 89% Full Time, and 11% Contract. Highlights an 73% In-person, 16% Hybrid, and 11% Remote job distribution.

Incident Manger

Hmg America Llc

Jackson, MI โ€ข On-site

Full-time

Posted 7 days ago


Key responsibilities

  • Conduct trainings on Incident Management process and tool for Steady State Operations staff.

  • Manage Incident Management process set-up data in Service Management Tools, ensuring ongoing alignment with organizational needs.

  • Periodically audit Incident records and coach Incident Management staff to improve process efficiency and quality.


Job description

Job Title : Incident Manger
Location : Jackson, MI
Duration : Full-Time (Perm.)
Job Description:
  • Conduct trainings on Incident Management process and Tool within the Steady State Operations staff to insure that they understand their respective responsibilities
  • Insure that the Service Desk analysts, Service Desk Manager, Critical Incident Manager and Incident Managers understand their specific responsibilities in Incident Management process
  • Manage Incident Management 'Process Set-up data' in the Service Management Tools - this includes SLAs, OLAs, Notifications, automatic escalations, user feedback surveys etc. Changing needs of the process in the organization and the process data in the tool need to be aligned on an ongoing basis. Rarely does it happen that the Incident Manager raises an RFC on the Service Management Tool to make changes in the tool data to add/modify/improve the way the tool should support the changing needs of the Process.

  • Provide adequate means for efficient handling of Critical Incidents, example: IVR updates, Operations Bridge, Contact lists, 'War Room' etc
  • Work with the Event Management Process owner to optimize the interfaces between Event Management and Incident Management process and tools. Help the Event Management Process to mature by providing inputs on :
    • False positives because of which Incident tickets were opened wrongly
    • Incidents which the Event Management process and tools missed and should be included in the purview of Event Management going forward
  • Continually improve the alignment of Incident Priorities by improving communication with those responsible for planning and managing service availability management and improvement initiatives (rarely do we find a named Availability Manager in the organizations - Normally this is a reactive, distributed responsibility across various tracks)
  • Guide and enforce that the Incident Managers to recognize situations where they should open Problem Tickets
  • Periodically audit Incident records and coach the Incident Management staff to
    • Insure that 'ticket hops' are reduced to the minimum
    • Avoid possible misuse of 'Pending' status by resolving groups
    • Enforce the use of available knowledgebase, Configuration Management Database and Known Error Database for quicker resolution of Incidents
    • Quality of updates being made into the Incident Records

  • Devise, measure, report, monitor and improve the internally designed KPIs to improve the efficiency of Incident Management process. Example: Ticket hops, Incidents per staff, Incidents resolved using KB etc.
  • Detect Incidents that were solved but not logged. These will always exist, irrespective of the maturity of an organization. VIP Incidents are a classic example. Even if VIPs don't log their own Incidents, the IT staff should log them on behalf of the VIPs. Policy makers themselves are, most conveniently, the policy breakers!
  • Explore the opportunities for using 'self-help' tools in the interest of process efficiency