Implementing Major Incident - MIM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
I am currently working on implementing Major Incident Management (MIM). For those who have implemented this within their organizations, I would appreciate any insights on what contributed to a successful implementation and what challenges you encountered.
We are a large organization, and management is concerned that we may not be fully ready to implement MIM, even though there is a clear need for it.
Additionally, is it possible to implement MIM successfully without Microsoft Teams integration? For an MVP approach, I am considering launching without Teams integration initially and then adding it later to enable a dedicated “war room” collaboration space during major incident
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
39m ago
Hi @Folac ,
When we first implemented MIM, the biggest win came from agreeing upfront on what counts as a major incident. Without that, every high‑priority ticket risked being escalated, and the process lost credibility. Once we nailed that definition, things started flowing smoothly.
We also learned that having a named Major Incident Manager during each crisis was critical. When something blew up, everyone knew who was steering the ship, which cut down on confusion and finger‑pointing. Communication was the other game‑changer—sending structured updates at regular intervals kept leadership calm even when fixes took longer than expected.
Agree on what’s “major”: If everything is flagged, nothing feels urgent.
Give someone the wheel: A Major Incident Manager keeps things moving and avoids chaos.
Talk, talk, talk: Clear updates beat silence every time. Even if the fix takes hours, people stay calm when they know what’s happening.
Learn after the storm: Do a quick post‑mortem to capture lessons and prevent repeats.
Challenges:
At first, teams resisted the “extra process” because they felt it slowed them down. We also had a tendency to over‑escalate incidents until we tightened the criteria. And management had to be coached that MIM isn’t about instant fixes—it’s about structured response and visibility.
Teams not used to the new process.
Over‑escalating too many incidents.
Stakeholders expecting miracles instead of structured response.
As for Microsoft Teams integration: we didn’t have it at launch. We ran MIM successfully using ServiceNow notifications and conference bridges. Teams integration came later, and yes, it made collaboration slicker with dedicated “war rooms,” but the core process worked fine without it. Starting simple was actually the right move—it let us prove the value of MIM before layering in extra tools.
