Back to blog

Mean Time to Innocence

April 16, 2019

Mean Time to Innocence (MTTI)

You’ve heard of the term MTTR—Mean Time to Repair. When there’s an IT incident—like an outage—you look at all your systems and figure out how quickly you can fix and repair the problem.

MTTR meetings often turn into an MTTI meeting—Mean Time to Innocence. IT personnel are loyal to their tools, and they will claim tool “innocence.” As you’re trying to assess your systems related to that IT incident, each IT team is trying to figure out how quickly they can prove that it wasn’t their tool’s fault, so they can leave the meeting.

RedMonocle created the MTTI terminology because so many CIOs experience this issue. MTTI sounds amusing, because it is. Imagine IT leaders in a Priority One meeting all claiming their systems work, and suggesting the blame lies elsewhere.

More importantly, MTTI causes a lot of division and makes life harder for the CIO to get to the truth—especially when there’s a crisis to solve. A Priority One problem might require 15 people to figure out the issues. Instead of solving the problem, they’re all looking at their individual data and playing the blame game.

The #1 value of a CIO in these meetings is to see the real cause of the problem. If everyone claims “innocence” with no data to backup what anyone states in strategy meetings, how can the CIO know which statements are true and accurate? The job of the CIO is to assure all systems are operating at their most efficient. If everyone says “My stuff works”, the CIO can’t get rid of slower, overwhelmed legacy systems nor see the functional gaps or overlaps.

Reduce MTTR

RedMonocle offers real-time feedback on all systems. This is feedback on spending, assets, system redundancies, and general empirical data on the state of your infrastructure—hardware, software, tools, security, assets, storage, data integration—all of it.

So the next time you call a Priority One meeting, you can see through the MTTI and actually figure out MTTR. You’ll be able to solve the problem that the meeting was called to solve. What a concept.