Operations | Monitoring | ITSM | DevOps | Cloud

AI is quickly becoming part of the engineering workflow. Teams are experimenting with assistants and agents that can answer questions, investigate incidents, suggest changes, and automate parts of software delivery. But there is a problem hiding underneath all of that momentum. Most engineering environments were not built to give AI the context it needs. In many organizations, the service catalog lives in one place. Deployment data lives in another. Incident history sits in a separate system.

Self-service infrastructure replaces ticket queues with controlled, automated workflows so developers can get what they need safely and on demand. Policy-as-code, standardized templates, and an Internal Developer Portal (IDP) provide guardrails that maintain security, compliance, and cost control. You can demonstrate ROI in 90 days by starting with a single golden path and measuring adoption, speed, and policy outcomes. If platform teams are buried in tickets, they are not operating a control plane.

Your developers are buried under tickets for environments, pipelines, and infra tweaks, while a small platform team tries to keep up. That is not developer self-service. That is managed frustration. If 200 developers depend on five platform engineers for every change, you do not have a platform; you have a bottleneck. Velocity drops, burnout rises, and shadow tooling appears. Developer self-service fixes this, but only when it is treated as a product, not a portal skin.

At SREday NYC 2026, the ShipTalk podcast spoke with Phil Christianson, Chief Product Officer at Xurrent, for a leadership perspective on the intersection of product strategy, engineering investment, and platform reliability. While many of the conversations at the conference focused on tools, automation, and incident response, Phil offered a view from the C-suite level, where decisions about engineering priorities and R&D investment ultimately shape how reliability practices evolve.

When AI agents operate across a multi-module platform like Harness (from CI/CD to DevSecOps to FinOps), the number one goal is to give you answers that are correct, consistent, and grounded in real data. Getting there requires a deliberate architectural choice: when a question can be answered from structured platform data, the agent should use a schema-driven Knowledge Graph rather than raw API calls via MCP. The principle is simple: if the data is modeled, retrieval should be deterministic.

‍Why 90% of AI prototypes never make it to production, and what to do about it. Every week, someone on my team shows me a demo that looks incredible. An agent that writes deployment pipelines. A chatbot that triages incidents. A copilot that generates test cases from Jira tickets. The demo takes 20 minutes. The audience claps. Everyone leaves convinced we're six weeks from shipping it. We're not.

If DevOps teams mix up the roles of Ansible and Terraform, deployment pipelines can become unreliable. Manual handoffs slow down changes, and audits may find gaps where responsibilities overlap. Each tool solves different problems, so using them correctly avoids delays and compliance risks. Are you dealing with scattered provisioning and configuration workflows?

Innovation is moving faster than ever, but software delivery has become the ultimate chokepoint. While AI coding assistants have flooded our repositories with an unprecedented volume of code, the teams responsible for actually delivering that code, our Platform and DevOps engineers, are often left drowning in manual toil. If you’re managing Argo CD at an enterprise scale, you’re painfully familiar with the "Day 2" reality.

‍ Let's get something out of the way: authentication and authorization are not the same thing. We know, we know. People swap the two terms constantly. And honestly, it's easy to see why. They both start with "auth," they both deal with security, and they often show up in the same conversations on access control. But if you build or secure software, blurring the line between authentication and authorization is how you end up with a system where everyone is logged in and everyone is an admin.

Modern CI/CD platforms allow engineering teams to ship software faster than ever before. Pipelines complete in minutes. Deployments that once required carefully coordinated release windows now happen dozens of times per day. Platform engineering teams have succeeded in giving developers unprecedented autonomy, enabling them to build, test, and deploy their services with remarkable speed. Yet in highly regulated environments-especially in the financial services sector-speed alone cannot be the objective.