← Back to list

To Trust or Not to Trust: That Is Your Agentic IT Question

A few weeks ago, I caught up with a former colleague — a seasoned IT architect responsible for building internal platforms in a large…

Salil Kulkarni · 2026-04-27 07:00 · 0 claps · 6.6 min read
#agentic-it #cmdb #itsm #itops #digital-transformation
Open on Medium ↗
Wiki topics: AGT · AI Agents BIZ · Business Strategy 🏛️ · Architecture

To Trust or Not to Trust: That Is Your Agentic IT Question

A few weeks ago, I caught up with a former colleague — a seasoned IT architect responsible for building internal platforms in a large, publicly traded company. On paper, his mandate is clear: shape the technology foundation, support innovation, and help the business move faster.

In reality, a large portion of his week is spent doing something very different.

He spends 10–15 hours every week sitting with a business relationship manager just to get his work correctly represented in the company’s IT service platform. Then he invests another 5–8 hours inside the tool himself — reconciling records, nudging workflows forward, and resolving discrepancies so he can actually execute on his responsibilities.

Conservatively, that is 20+ hours of senior leadership time every week lost to navigating workflows, fixing data issues, and compensating for systems that cannot be trusted to reflect reality without human babysitting.

Multiply that across:

  • His peers in architecture and operations
  • The relationship managers assigned to support them
  • The downstream teams that depend on “clean” data to do their jobs

…and you begin to see a massive, unbudgeted cost center. No one calls it out directly. It hides under headings like “collaboration,” “governance,” or “platform enablement,” but in reality, it slows transformation momentum even as it inflates your cost base.

For CIOs, CTOs, CISOs, CFOs, CPOs, and other C‑suite leaders, the question is straightforward:

Is this acceptable?

The illusion of intelligent, agentic operations

We are entering an era where “Agentic IT” is the new North Star. Strategic roadmaps are filled with AI agents, intelligent workflows, and command‑tower concepts designed to orchestrate IT and business operations.

The vision is powerful:

  • A single control layer for AI agents across technology and business domains
  • Autonomous decision‑making with targeted human oversight
  • Standardized policies and guardrails for how AI operates at scale

For executive teams, this sounds like the logical next step in digital transformation. You have already invested in cloud, modern platforms, and automation. Agentic IT promises to move from manual workflows to self‑directing systems that learn, adapt, and act.

But there is a critical dependency that often gets only a passing mention in keynotes and board decks:

Agentic IT is only as effective as the truthfulness of the data it runs on.

If your configuration data is incomplete, your discovery is shallow, and your service maps are out of date or missing, then you are essentially orchestrating AI on a partial, unreliable model of your environment. Your “agents” will take confident actions on untrustworthy inputs.

When that happens, your organization falls back into a familiar pattern:

  • Senior leaders and relationship managers verifying configuration items manually
  • Teams double‑checking change, incident, and asset data against reality
  • Endless cycles of reconciliation to keep reports and dashboards merely “good enough”

The more “intelligent” the platform claims to be, the more human effort you invest behind the scenes to protect the organization from bad decisions driven by bad data. It is an arms race you cannot win.

This is not what executives intended when they approved significant investments in modern IT platforms and AI.

Why “good enough” data is now a board‑level risk

In more traditional IT models, imperfect data was often survivable. Processes were slower. Manual approvals were the norm. Human gatekeepers could intercept many issues before they propagated too far.

Agentic IT changes that equation completely.

When AI agents initiate changes, resolve incidents, route work, or trigger automated remediations, they act at speed and scale. If their understanding of your environment is wrong, they propagate that error faster than any human process can correct it.

From a board and C‑suite perspective, this creates three converging risk categories.

  1. Operational risk

Misrouted incidents, incorrect impact assessments, and flawed change evaluations move from being isolated events to systemic behaviors. The more autonomy you grant your agents, the more these errors compound. What used to be a single misclassified configuration item can now drive dozens or hundreds of incorrect automated actions.

2. Financial risk

You pay twice. First for AI and automation capabilities that promise efficiency and scale. Then again for the human labor required to validate, correct, and override those capabilities when the underlying data is unreliable. The ROI narrative erodes quickly when expensive leaders spend significant time compensating for structural data weaknesses.

3. Governance and security risk

For CISOs and risk leaders, blind spots in asset inventories and service dependencies undermine zero‑trust strategies, vulnerability management, and incident response. If you cannot trust your map of the environment, you cannot trust the controls, policies, and audit evidence built on top of that map.

At this stage, you are not dealing with a “platform problem.” You are confronting a strategic risk to resilience, compliance, and business continuity.

First‑time‑right: why remediation is not a strategy

Most organizations implicitly accept remediation as a way of life. A change is implemented, an incident occurs, data is found to be wrong, and teams rush in to patch, fix, and clean up. Over time, this becomes the default operating model.

Agentic IT exposes why this is no longer viable.

As the volume and velocity of automated actions increase, the cost of “fix it after the fact” grows exponentially. There is simply not enough human capacity to review every agent decision, inspect every dependency, and manually correct every data defect.

A first‑time‑right mindset becomes non‑negotiable.

This does not mean perfection; it means designing your environment so that:

  • The data your agents rely on is accurate enough and current enough that most actions are correct by default.
  • Exceptions and anomalies are surfaced early, with clear context, so human oversight can be applied where it has the highest leverage.
  • The organization systematically reduces reliance on reactive remediation and instead invests in the foundational integrity of its operational truth.

At its core, first‑time‑right in Agentic IT is a data and context problem — not just a process problem. You cannot process‑optimize your way out of a fundamentally untrustworthy information foundation.

What trusted Agentic IT actually looks like

So what does it mean in practice to have a Trusted Source of Truth for Agentic IT?

It starts with an unglamorous but essential capability: continuously accurate understanding of what exists in your environment and how it is connected.

In a mature model, that looks like this:

  • Continuous discovery

Your systems maintain an ongoing, automated understanding of assets across on‑prem, hybrid, cloud, and multi‑cloud landscapes. Discovery is not a one‑off project; it is a persistent function with strong normalization and deduplication.

  • An always‑current configuration store

Your configuration data reflects what is actually running today, not the state of the world at the last major transformation program. Changes to infrastructure, applications, and services are reflected in near real‑time.

  • Live service mapping

Dependencies between infrastructure components, applications, and business services are automatically maintained as things change. Blast radius analysis, impact forecasting, and root cause investigations are grounded in reality, not assumptions.

This foundation serves both human operators and autonomous agents.

In that model:

  • Agents can act with confidence because they are grounded in accurate, contextual data.
  • Command‑tower‑style oversight is governing real conditions, not an outdated abstraction.
  • Senior leaders spend their time making strategic decisions and managing risk — not babysitting workflows or cleaning data.

The organization does not have to choose between human control and machine autonomy; it can have both, because both operate from a shared, trusted foundation.

Foundational ways to increase efficiency and get it right the first time

For executive teams looking to move from aspiration to execution, the priority is not another AI agent or dashboard. The priority is establishing and maintaining a Trusted Source of Truth for Agentic IT.

That requires a set of foundational shifts.

  1. Treat operational truth as a strategic asset

Stop thinking of configuration data, inventories, and service maps as technical artifacts. They are strategic assets, on par with financial ledgers and customer data. Assign clear ownership, metrics, and governance at the executive level.

2. Invest in continuous, automated accuracy — not periodic cleanups

Budget for ongoing, automated discovery and reconciliation efforts rather than sporadic “CMDB cleanup projects.” Periodic initiatives create brief moments of clarity followed by long stretches of drift. Agentic IT requires sustained accuracy.

3. Align incentives to first‑time‑right outcomes

Evaluate teams and programs on the quality and reliability of the operational truth they produce, not just on speed of delivery. Encourage practices that reduce rework, avoid manual reconciliation, and minimize human “shadow processes” outside official systems.

4. Design oversight for exceptions, not everything

Use your Trusted Source of Truth to narrow where human oversight is required. Instead of reviewing every automated action, focus human review on areas with higher risk or unusual patterns. This is how you scale governance without drowning in approvals.

5. Integrate truth across organizational boundaries

Agentic IT rarely stays confined to one function. Ensure that your trusted operational truth spans infrastructure, applications, security, finance, and procurement. Fragmented truths will recreate the very inefficiencies you are trying to eliminate.

6. Make “truth debt” visible

Just as you track technical debt, track truth debt — the gap between your current operational data quality and the standard required for Agentic IT. Quantify its impact in terms of rework, incident cost, and leadership time. Executives respond to what is measured.

A simple question for executive teams

The market will continue to accelerate around agentic capabilities, AI agents, and command‑tower concepts. Roadmaps will become more ambitious. Demos will become more impressive.

Before you green‑light the next wave of automation, ask one deceptively simple question:

What is the trusted source of truth for the agents you are about to unleash?

If the honest answer involves senior leaders and specialists spending 20+ hours a week manually reconciling data, then the core issue is not your AI strategy. It is your foundation.

Agentic IT without trusted truth is an elaborate stage set — impressive from a distance, fragile up close. Agentic IT with a Trusted Source of Truth becomes a genuine force multiplier for the business, enabling first‑time‑right execution at scale.

For high‑performing organizations that intend to rely on agentic AI solutions, establishing that foundation is not optional. It is elemental.


메타데이터
post_id
03e89e80c0ab
slug
to-trust-or-not-to-trust-that-is-your-agentic-it-question-03e89e80c0ab
url
https://medium.com/@saliljk/to-trust-or-not-to-trust-that-is-your-agentic-it-question-03e89e80c0ab
canonical_url
https://medium.com/@saliljk/to-trust-or-not-to-trust-that-is-your-agentic-it-question-03e89e80c0ab
author_url
https://medium.com/@saliljk
status
ok
fetched_at
2026-06-15 20:49:13