Is Your IT Team Guilty of “Innocence”?
Consider this scenario: One of your clients, a multimillion-dollar company, has experienced a major event. There’s been a data breach, big outage, or an asset has been compromised. The client had to shut down a line of business until the problem is resolved. As the CIO, your client is in trouble. You need to have answers within 24 hours as the monetary damages could be in the millions.
Mean Time To Innocence Meeting
You call a Priority One meeting with your top IT people at the table or on the phone. So, you go “around the room” to see what happened and where the hole is.
- Service? Check.
- Cloud? Check.
- Assets? Check.
- Networks? Check…
Everything checks out, except your client experienced a major incident. So how is that possible?
Your MTTR (Mean Time to Repair) meeting just became an MTTI—Mean Time to Innocence meeting. Your IT teams are very loyal to their tools. Their jobs depend on the tools working. Each IT team assumes their tool is working fine, or that’s what they claim.
Are IT Leaders able to access more than anecdotal information?
Each IT team in the meeting looks at their own data, saying “yes” my systems are healthy, it’s not them and to check other systems. While this might be an amusing scenario, it’s not amusing to a CIO who has to face a large, panicking client and immediately find the root cause of the problem among all the finger-pointing.
As the CIO, you are ultimately responsible for technology coming out of your company and every solution provided to the client. You’re responsible for the hardware, applications, networks, data, security from the biggest and farthest server all the way to end user’s experience. The CIO cannot possibly identify every piece of hardware and software, every network, know what it does, know how assets and tools integrate, and track all of the issues.
Or can you?
Enterprise-wide Visibility to IT Tools
RedMonocle asserts that this is not only a common problem, but a global problem.
An IT executive at a current RedMonocle client admitted attending frequent IT meetings. A IT tool problem comes up every time he meets with his IT teams, but he has no idea what the IT tools do. When the finger-pointing starts, he had no way to assess which IT tools helped to address the issue and which IT tools caused the issue.
To solve issues caused by IT silos and job protectionism, RedMonocle brings immediate and real-time insights into enterprise architecture to research IT tool integrations. The RedMonocle knowledge base brings empirical data that informs CIOs, providing real-time status and activity of all tools and infrastructure.
Now, a CIO can have the real-time data to solve the crisis and have IT teams stay at the table.