The most expensive mistake an IT executive can make in the next twenty-four months is to treat AIOps as a tooling decision. AIOps is not a product category, even though every analyst report packages it that way. AIOps is an operating-model decision the organization either earns the right to make or does not. The organizations that earn the right have clean CMDBs, mature problem management, reliable telemetry, and a culture that trusts data. The organizations that do not earn the right will spend the next two years discovering that the platform they bought cannot fix the operating model they have.

This essay is the readiness test I run before I let any IT organization I advise sign an AIOps contract. Five questions. Answer honestly. The answer tells you whether AIOps is your next investment or your second-to-next investment.

Fig. 1 · The AIOps readiness spectrum
Five stages. Most organizations sit between Aware and Foundational. AIOps investments succeed at Operational. Scoring three of five yes on the questions below puts you at the threshold.
Not ready Aware Foundational Operational AIOps-native threshold: 3 of 5 yes 01 02 03 04 05
Source. Maria Siegel, AIOps readiness framework, 2025.

Why AIOps is an operating-model question

AIOps platforms are sold as if they solve operational complexity. They do not. AIOps platforms surface operational complexity. The platforms only produce value to the extent that the underlying data they consume is trustworthy, the configuration management they depend on is accurate, the problem management function they feed is mature, and the operations team they assist is willing to act on what they say. If any of those four conditions is missing, the platform produces noise the organization then has to discount, which results in a worse outcome than not having the platform at all because the team learns to distrust automated signals on principle.

The successful AIOps deployments I have seen had clean prerequisites. The unsuccessful ones tried to acquire the platform first and the prerequisites second. The second sequence does not work. AIOps does not fix the data hygiene problems underneath it. AIOps amplifies them.

The five questions

Five questions. Each one resolves to a yes or a no. There are no partial answers. If you find yourself constructing a careful, qualified answer to any of these, write down "no" and move on. The qualified answer is the no.

Fig. 2 · The readiness test
Five questions, in the order I ask them. Three yes answers means AIOps is a real next move. Below that, it is a prerequisite, not an investment.
01
Can you explain what lives in your CMDB without caveats?
If the answer involves the phrase "for the most part" or "the high-value ones," the answer is no. AIOps consumes the configuration management database as truth. If your truth has caveats, the platform will reproduce the caveats at scale.
02
Does your problem management function produce more than tickets?
A healthy problem management function produces named patterns, documented root causes, and changes to the environment that trace back to specific incident clusters. If yours produces only tickets and post-mortems, it is incident management wearing a different hat.
03
Is your telemetry signal or noise?
If your operations team routinely silences alerts to keep their inbox manageable, your telemetry is noise. AIOps does not solve this problem. AIOps requires this problem to be solved.
04
Do your service owners trust the data your operations org produces?
Trust is the precondition for action. If your service owners discount or recompute the metrics your operations team reports, an AIOps platform will produce a third set of numbers that the service owners will also discount.
05
Does your team want AIOps, or do they fear it?
The cultural question is the one most leaders skip. If the operations team is reading the AIOps deployment as a precursor to layoffs, the platform will be quietly undermined regardless of what the contract says. Adoption is consent. Consent is built in advance, not assumed afterward.
Source. Maria Siegel, AIOps readiness framework, drawn from advisory engagements 2023 to 2025.

What "yes" actually requires

The five questions look simple on paper. The work behind getting to yes is not. Cleaning a CMDB to the point where you can talk about it without caveats is a six-to-twelve-month project for most large IT estates. Standing up a problem management function that produces real patterns rather than tickets takes about the same. Tuning telemetry from noise to signal is an ongoing operational practice, not a one-time fix. Building trust between service owners and operations data is a multi-year cultural project. Earning consent from the operations team to bring in automation is a leadership project that cannot be delegated.

If you walk through the five honestly, you will notice that the prerequisites have very little to do with AIOps and almost everything to do with operational maturity. That is the point. AIOps is a maturity multiplier. It multiplies what you have. If you have nothing, the multiplier produces nothing.

AIOps is not your next investment if you cannot answer yes to three of five. It is your second-to-next investment. The next investment is the operating model that makes AIOps worth buying.

What I would do this quarter

If you answered yes to three or more, you are ready for a real AIOps pilot. Start with a contained, well-instrumented service. Set a six-month evaluation horizon. Measure the AIOps platform against the operational metrics that matter to your business, not the marketing claims of the vendor. You will know in six months whether the platform is multiplying your maturity or revealing its limits.

If you answered yes to two or fewer, do not buy AIOps yet. Pick the weakest of the five and invest the budget you would have spent on the platform into the prerequisite. The prerequisite will produce more value in the next two years than the platform would have, and you will be ready to revisit AIOps when the prerequisite is sound. That is not a delay. That is the work the platform was going to require anyway. You are just doing it in the right order.

The honest part

The reason most AIOps deployments underperform is not the platform. It is the sequence. The leaders who treat AIOps as the destination buy it last and earn the benefits. The leaders who treat AIOps as the path buy it first and discover that the destination is not on the path. The five-question test exists to keep you in the first group.

Answer them honestly. If you cannot answer yes to at least three, AIOps is not your next investment. It is your second-to-next.