Category: AI Transformation

Business capability management in the age of AI: from static models to decision intelligence 

Posted on May 14, 2026 by - AI Transformation, Enterprise Architecture

Business capability management has long relied on enterprise capability models to describe how an organization works, forming a core pillar of enterprise architecture in AI-enabled environments.  

These models provide a shared view of business capabilities, support investment planning, and align transformation efforts. They are typically owned by centralized enterprise architecture teams and updated through structured cycles. As enterprise architecture AI capabilities mature, these models are becoming more central to how organizations interpret performance and guide decision-making. 

That foundation still matters. What changes in the age of AI is how those models behave, how often they evolve, and how they inform decisions. 

Capability models evolve into AI-enabled capability mapping 

Traditional capability models are built through workshops, curated manually, and revisited periodically. They reflect a point-in-time understanding of the enterprise. 

AI introduces a different operating dynamic. 

This shift enables a form of AI capability mapping, where capabilities are continuously inferred, updated, and connected to real execution data. 

By drawing on process telemetry, system interactions, financial data, customer behavior, and workforce signals, capability models can be continuously informed by how the business actually operates. Instead of relying on periodic interpretation, the model reflects live conditions. 

This shift changes how leaders use enterprise architecture in decision-making. 

  • Capability gaps become visible as they emerge 
  • Redundancy across business units can be identified in real time 
  • Performance degradation surfaces through measurable signals 
  • Automation opportunities become easier to prioritize 
  • Investment scenarios can be explored with greater confidence 

The model becomes a continuously updated representation of enterprise capability, grounded in execution rather than documentation. 

For enterprise architecture, this changes the work itself. The role moves from building and maintaining diagrams to governing how capability intelligence is generated, validated, and used. 

From qualitative assessment to measurable performance 

Capability maturity has often been assessed through qualitative methods. Stakeholder interviews and workshop-based scoring produce heatmaps that reflect perception as much as performance. 

Enterprise architecture AI capabilities enable a different level of precision. 

Capability health can be measured using operational data such as cycle time, error rates, cost-to-serve, automation ratios, and risk exposure. These signals provide a direct view into how capabilities perform under real conditions. 

This changes the questions leadership can ask. 

Instead of relying on subjective assessment, leaders can evaluate the impact of specific changes. 

  • What happens to margin if automation increases in a key process? 
  • Where does performance degrade when demand spikes? 
  • Which capabilities constrain enterprise outcomes today? 

Business capability management begins to support predictive and prescriptive decision-making, not just descriptive modeling. 

New capabilities reshape the enterprise model 

AI does not only improve visibility into existing capabilities. It introduces entirely new ones that must be treated as first-class elements of the enterprise. 

These include areas such as: 

  • Model lifecycle governance 
  • AI risk and ethics management 
  • Data product management 
  • Prompt engineering and human–AI interaction design 
  • Autonomous operations oversight 

These capabilities influence how decisions are made, how risk is managed, and how work is executed. These emerging capabilities also introduce the need for structured AI adoption governance, ensuring that new capabilities are used responsibly, consistently, and at scale across the enterprise. Treating them as technical sub-functions limits their impact. They operate at the level of enterprise capability and require the same clarity, ownership, and investment discipline as any other strategic function. 

The role of enterprise architecture shifts toward governance and decision enablement 

Enterprise architecture does not lose relevance as AI becomes more embedded in the enterprise. Its scope expands. 

The focus shifts toward governing how the organization understands itself and how that understanding informs decisions. 

This includes: 

  • Defining and maintaining a consistent capability ontology 
  • Ensuring semantic alignment across systems and data sources 
  • Clarifying decision rights between human and AI-supported processes 
  • Connecting capability performance to measurable business outcomes 

Architecture becomes a mechanism for decision clarity, not just structural alignment. 

This aligns directly with how modern operating models must function. Enterprise performance depends on how decisions move, how work flows, and how signals translate into action across the organization. 

Why this shift matters for enterprise performance 

Most organizations have already invested in digital platforms, agile delivery models, and AI experimentation. Yet outcomes often lag behind expectations. 

The constraint is rarely the absence of capability. It is the lack of connection between capabilities, decisions, and execution. 

When business capability management remains static, leaders operate with delayed or incomplete insight. Investment decisions rely on interpretation rather than signal. Execution teams absorb the consequences through rework, delays, and misalignment. 

When capability models evolve into continuously informed systems: 

  • Decision-making becomes faster and more grounded in evidence 
  • Investment aligns more directly with measurable outcomes 
  • Execution improves as constraints are identified earlier 
  • AI can support human judgment with relevant, contextual insight 

This is where enterprise architecture connects directly to enterprise value. 

The emerging model: architecture as enterprise cognition governance 

As capability models become continuously informed and decision-oriented, business architecture takes on a new role. 

It governs how the organization understands itself in real time and how that understanding shapes action. 

This includes: 

  • Integrating data, systems, and workflows into a coherent view of capability 
  • Embedding insight into decision flow across leadership layers 
  • Ensuring that AI-generated signals support, rather than replace, human judgment 
  • Maintaining continuity as the organization evolves its operating model 

Architecture becomes part of the enterprise’s execution system. 

When capability models become decision systems 

Business capability management remains essential. What changes is how they are used. 

They move from static representations of structure to continuously informed systems that support decision-making. 

Organizations that make this shift gain the ability to understand, simulate, and adjust how the business operates as conditions change. 

That changes how decisions are made, how work is executed, and how value is realized over time. 

It also marks a broader transition already underway across enterprises. As AI capabilities expand, the limiting factor becomes the operating model that surrounds them. Organizations that adapt how they structure decisions, workflows, and governance convert capability into sustained performance. Those that connect business capability management with enterprise architecture AI, operating model redesign, and AI adoption governance create the conditions for sustained, scalable performance. 

See how your operating model supports AI-enabled execution

Most organizations introduce AI capabilities before they understand whether their operating model can support them at scale. The result is uneven adoption, unclear decision ownership, and stalled outcomes. 

The AI‑First Operating Model Design Assessment helps you identify where decision flow, governance, and workflows constrain performance, and where targeted changes will unlock measurable impact. You gain a clear view of how work, decisions, and accountability need to evolve to support AI-enabled execution. 

Frequently asked questions about business capability management

What is business capability management? 

Business capability management is the practice of defining and organizing what an organization does into structured capabilities. It provides a shared view of how work is performed, enabling leaders to align strategy, investment, and execution across the enterprise. 

How does AI change business capability management? 

AI enables capability models to be continuously updated using real operational data. Instead of static diagrams, organizations can monitor performance, detect gaps, and explore improvement scenarios in real time, making capability management more actionable and decision-focused. 

What is AI capability mapping? 

AI capability mapping uses data from systems, processes, and workflows to dynamically identify and update business capabilities. It connects how work is actually performed to how capabilities are structured, improving visibility into performance, redundancy, and opportunities for automation. 

Why is enterprise architecture important for AI? 

Enterprise architecture ensures that AI capabilities align with how the organization operates. It governs data, systems, and decision structures so AI supports real workflows, improves decision quality, and scales consistently across teams. 

What is AI adoption governance? 

AI adoption governance defines how AI is used responsibly and consistently across the enterprise. It includes policies, decision rights, and oversight mechanisms that ensure AI supports human judgment, reduces risk, and delivers measurable outcomes. 

How does operating model redesign support AI adoption? 

Operating model redesign aligns decision flow, governance, and workflows with AI-enabled execution. Without these changes, AI initiatives often remain isolated or underused, limiting their impact on performance and value realization. 

What Atlassian Team ’26 revealed about the future of AI-native execution 

Posted on May 12, 2026 by - AI Transformation, Organizational Change & Culture, Platform Adoption & Governance

Many enterprises already possess significant AI capability. 

Across the enterprise, the larger barrier to scalable AI value is disconnected execution. 

Work still moves through disconnected systems, fragmented workflows, siloed teams, duplicated processes, and operational handoffs that slow decisions long before AI enters the equation. Knowledge sits inside tools, threads, recordings, pages, tickets, and dashboards that rarely function as one operational system. 

Atlassian Team 2026 made that problem strategically important. 

The strongest signal from the event centered on connected operational context, workflow-native AI, and execution visibility grounded in real enterprise work. 

That is why Teamwork Graph deserves executive attention. Operationally, it functions as an enterprise context layer connecting work, knowledge, teams, goals, services, dependencies, decisions, and delivery history so people and AI can operate with clearer visibility across the business. 

Nearly every major theme at Team ’26 pointed back to the same idea: AI becomes more useful when enterprise work becomes more connected. 

Teamwork Graph revealed the next competitive layer in enterprise AI 

Most enterprise AI conversations still focus on models, copilots, agents, prompts, and automation. Those capabilities matter, but Atlassian Team 2026 emphasized a different layer: the relationships between work. 

Why context quality matters 

The event repeatedly reinforced a broader operational reality. AI becomes substantially more useful when it can operate within connected, high-quality context. 

AI tools can generate responses, summarize activity, recommend next steps, and automate repetitive tasks. But in enterprise environments, the usefulness of those outputs depends on the quality of the surrounding context. An AI assistant that cannot understand how a Jira ticket connects to a Confluence decision, how that decision connects to a product goal, how that goal connects to a service dependency, or how that dependency affects delivery risk will remain limited. It may still save time, but it will struggle to support execution at scale. 

Teamwork Graph points to a broader answer. Operationally, it attempts to connect projects, tickets, documentation, conversations, goals, services, decisions, people, dependencies, and work history into a usable enterprise context layer. That context layer matters because work rarely breaks down inside one tool. It breaks down between teams, systems, decisions, and handoffs. 

AI systems struggle when work is disconnected, context is incomplete, and operational relationships remain invisible. Teamwork Graph represents Atlassian’s attempt to address that fragmentation problem at the level where enterprise work actually happens. 

From tools to operational systems 

This direction also reflects a broader platform shift. Jira, Confluence, Loom, Rovo, Atlas, Focus, and Service Collection are increasingly positioned as connected operational systems rather than isolated tools. 

Each product still serves a clear function, but the larger value emerges when work, knowledge, communication, planning, service delivery, and AI assistance reinforce each other. 

Conversations and demonstrations surrounding Team ’26 reinforced the same pattern. Teamwork Graph repeatedly surfaced as more than an abstract platform concept. Customers responded strongly to practical workflow demonstrations because they could see connected work functioning in real time. The strongest moments were often the moments when attendees connected the demonstration back to familiar visibility gaps inside their own organizations. 

The same pattern appeared around the System of Work Accelerator. When customers saw outputs connected to workflow maturity, collaboration patterns, and operational visibility, the discussion moved quickly from product interest to organizational diagnosis. The question became less about what Atlassian can do in theory and more about where disconnected execution is already limiting the enterprise today. 

One of the clearest shifts emerging from Team ’26 is the market conversation moving beyond the rise of AI agents alone. Enterprise AI value increasingly depends on connected operational context. 

Why disconnected execution is limiting enterprise AI value 

Many enterprises already struggle with: 

  • disconnected workflows 
  • duplicated effort 
  • inconsistent documentation 
  • fragmented service operations 
  • siloed delivery teams 
  • weak execution visibility 

These problems create friction before AI enters the workflow. 

AI does not automatically remove that friction. In many cases, it exposes and amplifies it. 

Connected workflows give AI better operational context. Fragmented workflows force AI to operate around gaps, incomplete relationships, and inconsistent knowledge. That affects trust, usefulness, and adoption scalability. 

The core challenge now centers on whether the operating environment gives AI enough context to support meaningful work. 

Why Rovo reflects the broader shift 

The shift toward connected execution also explains why Rovo generated so much attention throughout Team ’26. 

Rovo is often discussed in relation to enterprise search, agents, summarization, and workflow support. But its strategic relevance is broader than chatbot-style interaction. Rovo becomes more important when it functions as a context-aware workflow layer that helps people find knowledge, understand activity, coordinate execution, and move through work with less friction. 

The highest-value use cases are not limited to individual productivity. They emerge when AI supports the way teams coordinate, plan, deliver, resolve issues, and make decisions across shared systems of work. 

The customer conversations at Team ’26 reinforced this point. Attendees asked practical questions about Rovo usage, adoption, governance, and workflow fit. Interest centered less on AI novelty and more on operational applicability. Demonstrations resonated when they showed AI functioning inside real workflows rather than sitting beside them as another disconnected tool. 

The “make AI real in 90 days” message appears to have resonated for the same reason. It translated AI from an abstract ambition into a near-term operational challenge. Leaders want to know where to start, what workflows to prioritize, what governance must be in place, and how to connect AI to work people already do. 

The organizations that realize the most value from enterprise AI will likely be the organizations that reduce operational fragmentation first. That makes workflow visibility and connected execution increasingly strategic. 

Atlassian is shifting from work management toward execution visibility 

Atlassian began as a platform for organizing and tracking work. Team ’26 revealed how far that positioning has evolved. 

That shift changes the executive conversation. The company is increasingly focused on connecting strategic goals, project delivery, service operations, documentation, communication, AI assistance, and workflow coordination into a more visible operational system. 

The cost of coordination overhead 

That shift reflects a broader enterprise problem: organizations lose significant execution capacity to coordination overhead. Teams spend time searching for information, reconstructing decisions, reconciling reports, and managing dependencies across fragmented systems. Leaders often lack consistent visibility into how work connects across the business. 

Atlassian’s broader System of Work narrative speaks directly to that challenge. The emphasis on connected teamwork, shared visibility, and alignment between strategy and execution reflects where enterprise platform value is moving. 

The same pattern appeared in booth and theater conversations as well. The System of Work Accelerator generated strong engagement because it gave teams a concrete way to examine the maturity of their Atlassian environment. Customers related quickly to identified workflow gaps because those gaps reflected known operating challenges: unclear ownership, fragmented visibility, disconnected workstreams, inconsistent collaboration patterns, and difficulty translating platform usage into business value. 

Theater conversations around operationalizing connected execution also pointed to a broader market need. Leaders are trying to understand how AI fits into real workflows without creating more complexity. They want AI to reduce coordination friction, improve visibility, and support better decisions. They do not want another layer of disconnected experimentation. 

The strongest response at Team ’26 often came from conversations that translated AI into workflow visibility, coordination improvement, and connected execution. This appears to reflect where the market conversation is heading next. 

The next evolution of enterprise platforms will likely center on making enterprise execution more visible, connected, and context-aware. 

Why cloud modernization is becoming a connected execution decision 

Cloud modernization has often been framed as an infrastructure decision. For many Atlassian customers, that framing is becoming too narrow. 

At Team ’26, cloud conversations increasingly centered on: 

  • operational interoperability 
  • governance continuity 
  • AI scalability 
  • ecosystem readiness 
  • execution visibility 

Those concerns extend well beyond hosting. 

For organizations still operating in legacy or highly customized environments, operational fragmentation often persists through outdated integrations, inconsistent workflows, local workarounds, and limited visibility across systems. As AI-enabled workflows become more important, those limitations become harder to ignore. 

Why AI increases modernization pressure 

Rovo and broader AI adoption may accelerate cloud decision-making because AI value depends on connected, governed, and current operational context. If work remains fragmented across outdated systems, AI adoption becomes more difficult to scale and govern effectively. 

This is especially important in regulated industries, where leaders must evaluate accountability, transparency, permissions, data access, human oversight, and operational continuity alongside technical readiness. 

The cloud discussion increasingly centers on operational connectivity, AI-enabled workflows, scalable execution visibility, enterprise interoperability, and future operational capability. 

For many enterprises, cloud modernization increasingly reflects a decision about how connected and operationally visible the organization can become. 

What enterprise leaders should focus on next 

Enterprise leaders should avoid treating AI adoption as a standalone technology initiative. The more strategic move is to improve the operational systems surrounding execution itself. 

Enterprise leaders should focus on: 

  • visibility across execution 
  • coordination friction 
  • workflow governance 
  • operational connectivity 

Atlassian Team 2026 made that priority clearer. AI-native execution requires workflows, knowledge, teams, services, goals, and governance to operate with enough connection for AI to support human judgment inside real work. 

1. Identify visibility gaps across execution 

Leaders should begin by assessing where work loses visibility across the organization. 

Disconnected workflows, siloed operational data, fragmented knowledge systems, duplicated work, and dependency blind spots directly affect AI usefulness, workflow efficiency, operational trust, and adoption scalability. 

The priority is to identify where the organization lacks shared context. Which teams cannot see related work? Which decisions are difficult to trace? Which reports require manual reconciliation before leaders can trust them? 

AI will inherit the quality of the environment around it. If operational visibility remains inconsistent, AI-supported execution will remain inconsistent as well. 

2. Reduce coordination friction inside high-impact workflows 

Enterprise leaders should prioritize workflows where coordination friction slows meaningful work. 

These are often workflows where cross-functional dependencies create delays, visibility is inconsistent, operational handoffs slow execution, or coordination overhead remains high. Product delivery, service operations, onboarding, portfolio planning, and enterprise change initiatives are common examples. 

The objective is to connect work in ways that reduce unnecessary effort and improve decision flow. Leaders should look beyond tool adoption alone and focus on whether teams and AI systems can clearly understand the relationships between goals, decisions, dependencies, risks, and outcomes. 

When those relationships become clearer, AI can support execution with greater reliability and context awareness. 

3. Build governance into connected workflows early 

AI governance cannot remain separate from the workflows where AI will be used. It must be built into the way work moves. 

This requires organizations to define accountability, workflow transparency, operational governance, adoption enablement, human oversight, and sustainable operating practices early. 

Leaders need clear guidance on where AI can support work, where human judgment remains required, and how AI-enabled workflows will be reviewed and measured over time. 

When governance is embedded into connected workflows, adoption becomes more scalable, trustworthy, and sustainable. 

The enterprises that realize the greatest value from AI-native execution will likely be the organizations that build the clearest operational visibility and strongest workflow connectivity first. 

The clearest signal from Atlassian Team 2026 

Atlassian Team 2026 reinforced a broader shift toward connected execution and AI systems grounded in real operational work. 

The next competitive advantage in enterprise AI may come from building operational environments where work, knowledge, decisions, goals, and workflows are connected clearly enough for AI to participate meaningfully inside execution. 

That was the clearest strategic signal emerging from Atlassian Team ’26. 

See where disconnected work is limiting execution visibility

The System of Work Accelerator helps organizations uncover workflow fragmentation, identify operational visibility gaps, evaluate collaboration maturity, and prepare Atlassian Cloud environments for AI-native workflows. 

Use the free assessment to understand how connected your Atlassian workflows really are and where better visibility could improve execution. 

Frequently asked questions about Atlassian Team 2026 

What happened at Atlassian Team 2026? 

Atlassian Team 2026 focused heavily on AI-native execution, connected workflows, and operational visibility. Major announcements highlighted Teamwork Graph, Atlassian Rovo, workflow-native AI agents, and new approaches for connecting enterprise knowledge, services, goals, and delivery workflows into a shared operational context. 

What is Atlassian Teamwork Graph? 

Teamwork Graph is Atlassian’s connected enterprise context layer that links work, people, knowledge, goals, services, and operational history across systems. It helps AI and human teams operate with better context, visibility, and relationship awareness across enterprise workflows. 

Why is Teamwork Graph important for enterprise AI? 

Enterprise AI systems perform better when they can access connected operational context. Teamwork Graph helps AI tools understand relationships between projects, documentation, goals, dependencies, and workflows, which improves coordination, search, summarization, governance, and execution support. 

What is Atlassian Rovo? 

Atlassian Rovo is an AI-powered enterprise search and workflow assistance platform designed to help teams find knowledge, summarize activity, coordinate work, and support execution across Atlassian products and connected enterprise systems. 

How does Atlassian Rovo support enterprise workflows? 

Rovo supports enterprise workflows by helping teams retrieve operational knowledge, surface relevant context, summarize activity, identify relationships between work items, and coordinate execution more efficiently across connected systems and teams. 

Why are connected workflows important for AI adoption? 

Connected workflows improve AI usefulness by giving AI systems access to more complete operational context. Fragmented systems, inconsistent documentation, and disconnected workflows reduce trust, limit visibility, and make enterprise AI harder to scale effectively. 

How is Atlassian changing from work management to execution visibility? 

Atlassian is increasingly positioning its platform around connected execution, shared operational visibility, workflow coordination, and alignment between strategy and delivery. The focus is shifting toward helping enterprises understand how work connects across teams, systems, services, and goals. 

Why does cloud modernization matter for AI-native execution? 

Cloud modernization increasingly affects operational connectivity, interoperability, governance, and AI readiness. Organizations operating in fragmented or heavily customized environments may struggle to scale AI-enabled workflows because disconnected systems limit visibility, context quality, and governance continuity. 

What Knowledge 2026 revealed about the next enterprise AI operating model 

Posted on May 12, 2026 by - AI Transformation, Platform Adoption & Governance

Most events like this are all about announcing new features. And there were some exciting ones, no doubt. But ServiceNow Knowledge 2026 centered on much more important topics: enterprise execution systems, orchestration, governance, and AI-enabled operational coordination across the business. 

The most important conversations in Las Vegas focused on how AI moves through real work: how requests become action, how systems coordinate across platforms, how governance operates inside workflows, and how leaders scale AI without creating more fragmentation than value. 

That marks a meaningful shift. Enterprise AI has moved beyond the stage where isolated copilots, productivity demos, and disconnected experiments can carry the strategy. Leaders now face a more complex question: how do they turn AI capability into governed execution at scale? 

Many organizations already have multiple LLM investments, growing portfolios of AI pilots, and increasing pressure to prove value. 

They also have legacy systems, fragmented knowledge environments, inconsistent employee experiences, and governance models that were designed for slower technology cycles. As agentic AI moves closer to business execution, those operating gaps become harder to ignore. 

Knowledge 2026 brought that reality into focus. The event reflected a market shift toward execution architecture, orchestration, and governance as the foundation for enterprise-scale AI adoption. 

For enterprise leaders, that shift carries a clear implication. The next phase of AI value will depend on how well organizations redesign workflows, decision paths, accountability structures, and adoption systems around AI-enabled execution. 

Enterprise AI is moving from assistance to execution 

The dominant signal from Knowledge 2026 was the movement from AI as an assistance layer to AI as part of the enterprise execution layer. 

ServiceNow’s messaging around the “system of action,” autonomous workforce concepts, agentic business, Action Fabric, AI specialists, and workflow agents all pointed in the same direction. Taken together, these announcements reflected a larger market shift: AI is moving deeper into the systems where work happens. 

That shift matters because the first wave of enterprise AI largely focused on helping individuals move faster. 

Employees could summarize information, draft content, search knowledge, or complete isolated tasks with less manual effort. Those capabilities created useful gains, but they left the larger operating model mostly intact. 

The next wave changes the pattern. AI now sits closer to workflows, approvals, service delivery, employee interactions, and cross-functional coordination. It can move work from request to resolution, guide decisions across systems, and connect intent to action in ways that reshape how organizations operate. 

That shift creates a different standard for enterprise AI maturity. Success increasingly depends on whether AI capabilities function effectively inside the execution systems that determine speed, quality, accountability, and business outcomes. 

That reality showed up clearly in customer conversations at Knowledge 2026. Leaders asked fewer exploratory questions about theoretical AI capability and focused more heavily on operational execution challenges. 

Questions increasingly centered on: 

  • orchestration across systems 
  • governance at runtime 
  • interoperability across AI ecosystems 
  • responsible execution at scale 

Those questions reveal where the market is going. Enterprise buyers increasingly understand that AI value comes from coordinated execution. They want to know how AI fits into the architecture of work and how it interacts with existing platforms. 

The interface is becoming secondary to the execution layer 

The interface also becomes less important in this model. Conversational experiences still matter, especially when they simplify access to information and action. But the more strategic question sits underneath the interface: what execution layer receives the request, interprets the intent, coordinates systems, applies policy, and moves the work forward? 

That is where operating model transformation begins. Organizations seeing the most value are redesigning execution systems around AI-enabled workflows. They are clarifying where automation applies, where human judgment remains essential, how approvals change, how escalation works, and how adoption becomes part of the workflow rather than a separate change effort. 

As enterprises scale AI-enabled execution, another challenge becomes more visible: fragmented AI ecosystems are creating operational complexity. 

Orchestration is becoming the enterprise AI control layer 

One of the most important post-Knowledge 2026 issues is the growing complexity of multi-LLM environments. 

Many organizations now operate in a fragmented AI landscape. They may have investments in OpenAI, Claude, Gemini, embedded AI features inside major enterprise platforms, internally developed agents, and emerging use cases owned by different functions. 

Each capability may create value in isolation. Together, they can create architecture uncertainty, integration fatigue, inconsistent user experiences, and governance gaps. 

Enterprises are accumulating AI capabilities faster than they are building operational coordination around them. 

That creates a strategic problem. Leaders want flexibility, continuity, and coordinated employee experiences across increasingly fragmented AI environments. They also want to preserve existing investments without rebuilding workflows every time the model market changes. 

Why orchestration is becoming strategic infrastructure 

ServiceNow’s orchestration direction speaks directly to this pressure. Action Fabric, workflow orchestration, execution coordination, and platform-of-platforms architecture all point toward a model where ServiceNow helps coordinate action across systems rather than forcing every piece of work into one isolated environment. 

That idea resonated because many organizations have learned that modernization cannot depend on endless migration projects. Large enterprises already have valuable content, data, workflows, and knowledge stored across environments such as SharePoint, Confluence, ServiceNow, HR systems, IT systems, and other business platforms. Moving everything into one place can create disruption, cost, and resistance. 

A more practical model is emerging: 

  • preserve existing systems that still create value 
  • orchestrate workflows across environments 
  • leave knowledge where it already lives 
  • reduce unnecessary migration friction 
  • create more unified employee experiences 

In this model, organizations can modernize execution without forcing large-scale reconstruction projects that disrupt users, workflows, and operational continuity. 

This is a critical implementation insight. AI operating model maturity will increasingly depend on orchestration layers that support flexible model integration, federated knowledge architectures, and long-term operational adaptability. 

Organizations that coordinate orchestration strategically can reduce integration risk, preserve architectural flexibility, and create more durable foundations for AI-enabled execution. Organizations that deploy AI initiatives independently across functions often create rising complexity, duplicative effort, uneven adoption, and weaker governance. 

The next enterprise AI advantage may come less from the models organizations buy and more from how effectively they orchestrate execution around them. A strong orchestration layer stabilizes how work gets done across changing AI ecosystems, allowing organizations to integrate multiple models, connect existing platforms, apply governance consistently, and preserve operational continuity as underlying technologies evolve. 

That orchestration challenge naturally raises a second-order issue. As AI systems begin acting inside workflows, governance must move closer to execution. 

Governance is becoming operational infrastructure 

Governance emerged as one of the defining enterprise AI themes at Knowledge 2026 because agentic AI changes the risk profile of AI adoption. 

When AI primarily generated content or surfaced insights, governance could focus heavily on acceptable use, data handling, model access, and review processes. Those controls remain important. But AI-enabled execution introduces a broader challenge: how do organizations govern systems that can trigger actions, route work, recommend decisions, escalate issues, and coordinate across business processes? 

That question moves governance from policy documentation into operational infrastructure. 

Governance now operates inside workflows 

ServiceNow’s emphasis on Control Tower, runtime governance, AI oversight, policy enforcement, auditability, operational controls, and governed autonomy reflects this shift. 

Enterprise AI governance now needs to operate directly in the flow of work. 

That includes: 

  • defining when humans intervene 
  • clarifying escalation paths 
  • logging decisions and actions 
  • enforcing operational policy 
  • maintaining accountability for outcomes 

That requires organizations to extend governance across compliance, risk, legal, data, workflow design, platform architecture, role definition, service delivery, and adoption planning so operational controls function inside the execution system itself. 

The reason is simple: autonomous and semi-autonomous systems can create operational risk when accountability remains unclear. A workflow agent may accelerate work, but leaders still need to know what decisions it can make, what evidence it uses, when it stops, when it escalates, and who owns the business result. 

Conversational interfaces may improve employee access and workflow speed, but enterprises still need controls around sensitive data, role-based access, approved actions, and escalation paths. 

Governance and orchestration therefore become inseparable. Orchestration determines how work moves. Governance determines how that movement remains safe, accountable, transparent, and aligned to enterprise policy. 

Human accountability remains essential 

Human judgment remains central to this model. AI can support decision flow, reduce manual effort, surface context, and coordinate action, but organizations still need people to define priorities, resolve ambiguity, manage exceptions, and own business accountability. Effective governance clarifies that relationship rather than treating automation as a substitute for responsibility. 

This also has direct implications for adoption. Employees need to understand where AI fits, when to trust it, when to intervene, and how their roles change as workflows become more AI-enabled. Leaders need enablement systems that help people use AI with confidence while maintaining the judgment and accountability their work requires. 

AI is changing how enterprises think about operating capacity 

Knowledge 2026 also reflected a more direct conversation about operating capacity. Executives are increasingly evaluating AI through the lens of scalability, productivity economics, service demand, and workforce leverage. In many functions, the question is becoming more concrete: how can the organization handle more work, faster response expectations, and greater complexity without expanding headcount at the same rate? 

That shift requires careful leadership. AI-enabled execution can reduce repetitive work, improve service speed, and help teams focus human effort where judgment matters most. It can also reshape job design, staffing assumptions, governance expectations, and workforce adaptation priorities as enterprises redesign workflows around AI-supported execution. 

The market is competing on execution systems 

This is why ServiceNow’s Knowledge 2026 direction matters. The announcements collectively pointed toward execution coordination, governed AI systems, workflow integration, and enterprise-scale orchestration. The strategic message was larger than any one product feature: the enterprise AI market is moving from isolated AI experiences toward coordinated systems of action. 

That shift changes how leaders should think about competitive advantage. Enterprise value will increasingly depend on the operating systems that turn AI capability into coordinated execution. Organizations that build governance into execution systems can move faster with more control, scale AI use cases with clearer accountability, and adapt operating models without destabilizing the business. 

This is the emerging AI operating model: flexible at the model layer, stable at the orchestration layer, governed at runtime, and grounded in human accountability. 

Enterprises increasingly need implementation partners who understand orchestration strategy, workflow integration, governance architecture, operating model design, and adoption support as interconnected parts of the same transformation. 

That shift creates practical priorities for leaders now. 

What enterprise leaders should prepare for now 

Knowledge 2026 gave enterprise leaders a clear view of what comes next. The organizations that move effectively will prepare their architecture, governance, workflows, and workforce for AI-enabled execution rather than treating agentic AI as another application rollout. 

CIOs and technology leaders: build for orchestration early 

Technology leaders should assume multi-LLM environments will become the norm. A durable AI strategy needs room for multiple models, embedded AI capabilities, changing vendor relationships, and evolving enterprise platforms. 

That means orchestration strategy should begin early. 

Technology leaders should prioritize: 

  • interoperable workflow infrastructure 
  • multi-LLM flexibility 
  • governance embedded into execution systems 
  • scalable integration patterns 
  • architecture that supports operational adaptability 

Leaders also need to identify where AI-enabled work will cross systems, where existing architecture creates friction, and where fragmented AI deployments could create inconsistent experiences and disconnected governance. The goal is to establish architecture patterns that can scale across business functions as AI ecosystems continue evolving. 

Operations and delivery leaders: redesign workflows around human-AI collaboration 

Operations and delivery leaders should focus on how AI changes the movement of work. 

Agentic AI creates value when it reduces decision friction, accelerates resolution, improves service consistency, and helps teams act with better context. That requires workflow redesign. Leaders need to examine where work stalls, where handoffs break down, where approvals create delay, and where employees lack the information needed to act confidently. 

Modern execution systems should clarify the relationship between human and AI work. AI can route, summarize, recommend, retrieve, trigger, and coordinate. People still guide priorities, resolve exceptions, apply judgment, and own outcomes. That division of responsibility must be designed intentionally rather than left to informal adoption. 

Operationalizing governance also becomes part of workflow modernization. Controls, escalation paths, audit trails, and approval logic should live inside the execution flow so teams can move faster without creating unmanaged risk. 

Transformation and workforce leaders: make adoption part of the operating model 

Transformation and workforce leaders have a central role in this next phase because AI-enabled execution changes behavior, roles, decision patterns, and trust. 

Adoption requires practical enablement that helps people understand how AI fits into their work, what decisions remain human-led, and how accountability evolves as workflows become more automated. Leaders should prepare operating models for continuous adaptation through updated role definitions, governance participation, feedback loops, and measurement systems tied to business outcomes. 

Across all leadership roles, the direction is consistent: AI value now depends on implementation discipline. Organizations need orchestration expertise, governance frameworks, workflow redesign, and operating model support to operationalize these changes successfully. 

Knowledge 2026 pointed to a new operational phase of enterprise AI 

Knowledge 2026 revealed an enterprise AI market moving toward operational systems built around orchestration, workflow integration, governance, and execution architecture. 

That shift changes the competitive landscape. Enterprises will increasingly differentiate through their ability to coordinate AI-enabled execution across systems, govern workflows responsibly, and adapt operating models without disrupting the business. 

For many organizations, that will require practical guidance across orchestration strategy, governance design, workflow modernization, and enterprise adoption. The next competitive advantage may come from how effectively enterprises orchestrate execution around AI. 

Prepare your enterprise AI operating model for what comes next

/imagServiceNow Knowledge 2026 made one thing clear: enterprise AI value now depends on more than deploying new capabilities. Leaders need orchestration strategies, governance models, workflow integration, and operating models that support AI-enabled execution at scale. 

The AI Strategy and Transformation Workshop helps enterprise leaders assess readiness, identify high-value opportunities, and define a practical path for responsible AI transformation across real workflows. 

Frequently asked questions about ServiceNow Knowledge 2026 

What happened at ServiceNow Knowledge 2026? 

ServiceNow Knowledge 2026 focused heavily on agentic AI, orchestration, governance, and AI-enabled execution systems. The event highlighted how enterprises are moving beyond isolated AI tools toward coordinated workflows, runtime governance, and operational models designed to support AI at enterprise scale. 

What is agentic AI in ServiceNow? 

Agentic AI refers to AI systems that can coordinate actions, complete multi-step workflows, retrieve information, and support execution across enterprise systems. At Knowledge 2026, ServiceNow positioned agentic AI as part of a broader operational framework focused on orchestration, governance, and workflow integration. 

Why is orchestration becoming important in enterprise AI? 

Enterprises increasingly operate across multiple AI models, platforms, workflows, and data environments. Orchestration helps coordinate those systems so organizations can maintain operational continuity, reduce fragmentation, apply governance consistently, and support AI-enabled execution without rebuilding workflows around every technology change. 

What is ServiceNow Action Fabric? 

ServiceNow Action Fabric is an orchestration framework designed to connect AI agents, workflows, and enterprise systems across different platforms. It supports coordinated execution and interoperability without requiring organizations to migrate every workflow or knowledge source into a single environment. 

Why are enterprises concerned about multi-LLM environments? 

Many organizations already use multiple AI providers such as OpenAI, Claude, and Gemini alongside embedded AI capabilities inside enterprise platforms. That creates concerns around interoperability, governance, architecture complexity, employee experience consistency, and long-term operational adaptability. 

What is AI Control Tower in ServiceNow? 

AI Control Tower is ServiceNow’s governance and oversight framework for enterprise AI operations. It focuses on runtime governance, policy enforcement, operational visibility, auditability, and accountability across AI-enabled workflows, agents, and execution systems. 

How is AI changing enterprise operating models? 

AI is changing how enterprises design workflows, coordinate decisions, manage governance, and scale execution across the organization. Many leaders are redesigning operating models around AI-enabled workflows, orchestration layers, and governance structures that support responsible automation and human accountability. 

What should enterprise leaders prioritize after Knowledge 2026? 

Enterprise leaders should prioritize orchestration strategy, governance integration, interoperable workflow infrastructure, and operating model readiness. Organizations that prepare early for AI-enabled execution can adapt more effectively as enterprise AI ecosystems continue evolving. 

AI adoption ROI: why adoption determines enterprise performance 

Posted on May 6, 2026 by - AI Transformation, Platform Adoption & Governance

AI adoption ROI is under scrutiny as investment accelerates, yet enterprise performance is not improving at the same rate. The gap is structural. Organizations are investing in AI, but they are not changing how work executes. 

AI has moved from experimentation to executive accountability. CEOs and CFOs now expect measurable returns tied to operational KPIs and financial outcomes. At the same time, most organizations continue to treat AI as a tool layer rather than an execution capability embedded within workflows. 

The result is a persistent disconnect between spend and outcomes. 

Across client environments, a consistent pattern emerges. Significant investment is in place, but leadership cannot tie that investment to cycle time, cost efficiency, quality, or revenue impact. 

Consider a global insurer deploying AI copilots across underwriting teams. Usage is high. Activity increases. Underwriting cycle time and loss ratios remain unchanged. The system absorbs AI without changing how decisions are made or how work flows. 

The issue centers on how success is defined and measured. 

AI usage vs business outcomes: the measurement problem 

Most organizations rely on usage metrics to signal progress: 

  • Licenses deployed 
  • Frequency of AI use 
  • Number of pilots or use cases 

These indicators measure activity. They do not show whether work executes faster, better, or more reliably, or how it connects to enterprise performance and financial outcomes. 

This creates a false signal of progress. High usage is interpreted as success even when operating performance remains unchanged. This gap between AI usage vs business outcomes distorts how progress is understood at the executive level. 

A SaaS company may report 80 percent adoption of AI coding assistants. Release frequency, defect rates, and cycle time remain unchanged. Leadership cannot attribute measurable business value to AI. 

This misalignment distorts decision-making. Investment continues to scale without clear evidence of impact. This is where most enterprise AI adoption strategies begin to break down. 

If usage does not determine value, behavior becomes the constraint. 

Behavior change as the driver of AI adoption ROI 

AI adoption ROI depends on how work changes, not how tools are deployed. 

The primary constraint is behavioral, not technical. 

Common failure patterns reinforce this: 

  • Teams use AI as a search tool rather than embedding it into workflows 
  • Managers maintain legacy performance expectations 
  • Pilots remain isolated and fail to scale 
  • AI is layered onto existing processes, accelerating inefficiency 

Behavior change must be defined operationally. 

  • Decisions are made faster and with better information. 
  • Workflows are redesigned to reduce handoffs and ambiguity. 
  • Roles evolve so that humans focus on judgment while AI handles repeatable execution. 

Organizations often invest in enablement and tooling while leaving workflows unchanged. In that scenario, AI increases activity but does not improve performance. 

A healthcare provider may introduce AI into patient intake. Staff continue to validate and re-enter data manually. Cycle time and administrative cost remain constant because the workflow itself has not changed. 

AI implementation best practices consistently point to redesigning how work executes as the starting point for value realization. Without that, adoption cannot translate into measurable outcomes. 

Trust, literacy, and reinforcement: the conditions for adoption 

Behavior change does not occur through exposure or training alone. It depends on three conditions: trust, literacy, and reinforcement. 

Trust: reliability and control 

AI must be reliable enough to influence decisions. When outputs are inconsistent or opaque, teams disengage quickly. 

Trust is built through: 

  • Accuracy validation against real scenarios 
  • Clear articulation of limitations 
  • Human-in-the-loop controls for oversight 

Literacy: role-based capability 

Surface-level familiarity does not translate into execution. Teams need role-specific clarity on where AI fits within their workflows. 

Generic training does not change behavior. Context-specific application does. 

Reinforcement: system alignment 

Behavior change persists only when the system reinforces it. 

KPIs, incentives, and management cadence must align with AI-enabled execution. When legacy metrics remain in place, teams revert to previous ways of working. 

A bank may deploy AI for fraud detection support. Analysts distrust outputs and revert to manual review. The system lacks transparency and reinforcement, so behavior does not change. 

These conditions must be designed into how the organization operates. 

Designing an enterprise AI adoption strategy into the operating model 

Adoption is not a training outcome. It is a function of the operating model. 

How work flows, how decisions are made, and how performance is measured determine whether AI changes execution. 

In many organizations: 

  • Governance sits outside execution 
  • Decision rights are unclear 
  • Workflows are not redesigned for AI 
  • Performance systems emphasize activity rather than outcomes 

An effective enterprise AI adoption strategy addresses these gaps. 

  • Human and AI roles are clearly defined 
  • End-to-end workflows are redesigned for integrated execution 
  • Governance is embedded within daily operations 
  • KPIs are tied to outcomes rather than activity 

Organizations that succeed treat adoption as a system design problem. They redesign workflows and decision systems rather than expanding tooling. 

A retail organization embedding AI into demand forecasting may clarify decision rights and connect forecasts directly to inventory actions. Forecast accuracy improves and stockouts decline because the system supports the behavior change. 

This alignment between operating model and execution is central to AI governance and risk management. Controls must exist within workflows, not outside them. 

Measuring what actually drives AI adoption ROI 

AI adoption ROI is determined by operating performance, not activation. 

A structured measurement model clarifies how value is created and where it breaks down. 

Enterprise outcomes 

These are the metrics leadership ultimately cares about: 

  • Revenue growth and margin expansion 
  • Cost efficiency 
  • Customer experience and retention 
  • Workforce productivity 
  • Risk posture 

These outcomes anchor AI investment to CFO- and CEO-level priorities. If AI cannot be tied to one or more of these dimensions, it remains a cost center rather than a performance driver. 

Operating performance drivers 

These metrics explain how outcomes are produced: 

  • Capacity across workflows 
  • Cost-to-serve 
  • Cycle time from intent to outcome 
  • Quality and rework levels 
  • Risk and operational reliability 

These are the levers through which AI creates value. Capacity reflects how much work can be completed. Cost-to-serve reflects efficiency at the unit level. Cycle time reveals how quickly decisions translate into outcomes. Quality and risk determine whether speed creates value or instability. 

These metrics apply across all functions, not only product development. They define how the business operates. 

For example, reducing onboarding cycle time in HR improves productivity and accelerates revenue contribution per employee. The value comes from faster integration into productive work, not from the use of AI itself. 

Adoption and execution signals 

These are leading indicators of behavior change: 

  • Adoption within workflows rather than tool usage 
  • Time reinvestment into higher-value work 
  • Degree of workflow integration 
  • Scale across teams and functions 

These signals indicate whether AI is changing how work executes. Workflow-level adoption shows whether AI is embedded into real processes. Time reinvestment shows whether capacity is being redirected toward higher-value work. Scale reveals whether success is repeatable or isolated. 

Without these signals, organizations cannot distinguish between experimentation and operational change. 

Trust and governance signals 

These metrics support AI governance and risk management: 

  • Accuracy and success rates 
  • Escalation frequency to human intervention 
  • Variance over time 
  • Auditability and control coverage 

These determine whether AI can be relied on in execution. Accuracy and success rates indicate whether outputs are usable. Escalation rates show where human judgment remains necessary. Variance highlights instability. Auditability ensures decisions can be traced and governed. 

Together, these signals define whether AI can operate safely at scale. 

Behavioral diagnostics 

These explain root causes: 

  • Literacy 
  • Attitude 
  • Aptitude 
  • Compliance 

These factors explain why adoption is progressing or stalling. Literacy determines whether teams know how to use AI in context. Attitude reflects willingness to change. Aptitude reflects the ability to redesign workflows. Compliance ensures usage remains safe and governed. 

Without diagnosing these layers, organizations treat symptoms rather than causes. 

Clarifying risk 

AI introduces three interconnected risk dimensions: 

  • Operational risk through execution failure or rework 
  • Governance risk through compliance gaps or unsafe usage 
  • Strategic risk through slower adoption relative to competitors 

AI amplifies existing weaknesses in execution systems. Poor workflows create more errors at higher speed. Weak governance increases exposure. Slow adoption compounds competitive disadvantage. 

Organizations that measure across these layers manage AI as a performance system rather than a technology initiative. 

Activation metrics are transient. Capability metrics reflect durable change in how work executes. 

Measuring sustained capability, not activation 

AI adoption ROI emerges from sustained capability, not initial activation. 

Capability reflects durable change: 

  • Repeatable execution across workflows 
  • Reliable outcomes at scale 
  • Continuous improvement through feedback loops 

Sustained capability requires: 

  • Ongoing measurement embedded in workflows 
  • Continuous learning cycles 
  • Active optimization of workflows and decision systems 

A logistics company may initially improve routing efficiency with AI. Without reinforcement, teams revert to manual overrides. Gains erode because capability was not institutionalized. 

Executives should frame the distinction clearly: 

Adoption reflects repeatability of outcomes. 
Capability reflects reliability at scale. 

Adoption as the determinant of AI ROI 

Technology is increasingly accessible. Execution is the differentiator. 

Organizations that redesign work and embed AI into workflows create compounding advantages. Those that rely on usage metrics remain stalled regardless of investment levels. 

Across client environments, a consistent pattern holds. Organizations that integrate AI into workflows, reinforce behavior through operating models, and measure performance outcomes realize value. Others remain in pilot cycles, reporting activity without impact. 

AI adoption ROI is determined by whether the enterprise can execute differently, consistently, and at scale. 

AI ROI is a performance system design problem. 

Adoption determines whether value is realized, sustained, and scaled. 

See where your AI adoption ROI is breaking down

If your organization reports strong AI usage but cannot connect it to business outcomes, the constraint likely sits within workflows, decision systems, or operating model design. 

Our AI in the Workplace Assessment identifies where adoption is stalling across literacy, behavior, workflow integration, and governance, giving you a clear view of what is limiting ROI and where to act first. 

Frequently asked questions about AI adoption ROI 

What is AI adoption ROI? 

AI adoption ROI refers to the measurable business value created when AI changes how work executes. It focuses on outcomes such as cycle time, cost efficiency, and quality rather than tool usage. The concept emphasizes performance improvement, not just deployment or experimentation. 

Why is AI adoption ROI difficult to measure? 

AI adoption ROI is difficult to measure because most organizations track activity instead of outcomes. Metrics like usage rates and number of pilots do not reflect operational performance. Without linking AI to cycle time, cost, and quality, leaders lack a clear view of impact. 

What is the difference between AI usage and business outcomes? 

AI usage measures how often tools are used, while business outcomes measure how work improves. High usage can exist without better performance. Outcomes such as faster delivery, reduced cost, and improved quality determine whether AI is creating real value. 

What are AI implementation best practices for driving ROI? 

AI implementation best practices focus on redesigning workflows, not just deploying tools. This includes embedding AI into decision-making, defining roles clearly, and aligning KPIs to outcomes. Without these changes, AI increases activity but does not improve performance. 

How does an enterprise AI adoption strategy improve results? 

An enterprise AI adoption strategy improves results by aligning workflows, decision rights, and performance systems around AI-enabled execution. It ensures adoption occurs within real processes, making outcomes repeatable and scalable across teams rather than isolated in pilots. 

What role does AI governance and risk management play in adoption? 

AI governance and risk management ensure AI can be used safely and consistently at scale. They provide controls, auditability, and oversight within workflows. Without embedded governance, organizations face higher operational, compliance, and strategic risk as AI usage increases. 

How can organizations tell if AI is actually improving performance? 

Organizations can assess AI impact by tracking operating metrics such as cycle time, capacity, cost-to-serve, quality, and risk. Improvements in these areas indicate that AI is changing how work executes, rather than simply increasing activity. 

Why do AI initiatives stall after initial success? 

AI initiatives often stall because behavior does not change or is not reinforced. Teams revert to legacy workflows when trust, incentives, and governance are not aligned. Without sustained capability, early gains fade and performance returns to baseline. 

AI implementation challenges: Why AI pilots fail to scale 

Posted on May 4, 2026 by - AI Transformation, Organizational Change & Culture

AI investment is accelerating across every industry. Pilots are everywhere. Early wins are easy to find. Yet measurable enterprise impact remains inconsistent. 

According to PwC’s 2026 Global CEO Survey, 56% of CEOs report no revenue or cost benefits from AI despite increased investment. 

This gap defines the current moment. AI is working in pockets, but it is not translating into enterprise performance. 

The core challenge is turning isolated AI success into repeatable value across the enterprise. 

The pilot paradox: proof of concept is not proof of value 

Most organizations treat pilot success as evidence that scaling is simply a matter of replication. That assumption breaks down quickly. 

Only 12% of CEOs report both revenue growth and cost reduction from AI. 

Pilots operate in controlled conditions. They bypass the constraints that define real execution. Governance is simplified. Dependencies are minimized. Decision latency is reduced. Success criteria are narrow and often tied to speed or output rather than outcomes. 

Enterprise value operates under different conditions. 

Enterprise value is the measurable, repeatable improvement in how an organization performs across its operating system. It shows up in financial outcomes, execution speed, decision quality, and sustained adoption across teams. 

A pilot proves that AI can work. It does not prove that the organization can produce these outcomes consistently. 

Local wins vs enterprise constraints 

Teams can achieve meaningful gains within their own scope. They reduce manual work. They accelerate tasks. They improve individual productivity. 

These are local wins. 

Enterprise outcomes depend on how work flows across teams, how decisions move through the organization, and how systems interact. When those structures remain unchanged, local improvements do not scale. 

Research shows that up to 95% of AI projects fail to deliver measurable ROI at scale. 

This reflects a systems-level issue rather than a capability gap. 

AI amplifies the environment it enters. When workflows are fragmented and decision paths are unclear, AI increases the speed of fragmentation rather than resolving it. 

Portfolio sprawl and lack of prioritization discipline 

As pilots multiply, a new constraint emerges. Organizations accumulate use cases faster than they can evaluate or scale them. 

Leaders report difficulty moving beyond pilots into enterprise-wide deployment. This creates portfolio sprawl. 

Multiple teams pursue similar initiatives without coordination. Funding spreads across too many efforts. Success metrics vary by team. Low-value pilots persist because there is no clear mechanism to stop them. 

Without prioritization discipline, AI remains a collection of experiments rather than a coordinated system of value creation. 

Enterprise value requires clear sequencing, shared criteria for success, and active governance of the portfolio. 

Missing runbooks and operational governance 

Even when organizations identify promising use cases, scaling exposes another gap. There is no defined way of working for human and AI execution. 

Governance is often external to execution. Controls, monitoring, and accountability sit outside the workflow instead of being embedded within it. 

Organizations that embed AI into workflows, products, and services are two to three times more likely to see returns. 

This difference is operational. 

Scaling requires clear decision rights, defined escalation paths, validation mechanisms, and runbooks that guide how AI is used in daily work. Without these, trust erodes, adoption slows, and outcomes remain inconsistent. 

Failure patterns: why pilots stall at scale 

Across industries, the same patterns appear. 

  • Pilots remain isolated and never reach production workflows. 
  • Initial adoption fades as teams revert to familiar ways of working. 
  • Governance slows progress rather than enabling it. 
  • Trust declines when outputs are inconsistent or difficult to validate. 
  • Portfolios expand without focus, diluting impact. 

These issues follow predictable patterns within operating systems that have not evolved to support AI-enabled execution. 

What scaling actually requires 

Organizations that scale AI successfully shift their focus from experimentation to execution systems. 

  • They move from pilots to coordinated programs. 
  • They redesign workflows so AI is embedded in how work gets done. 
  • They clarify decision flow so insights translate into action. 
  • They embed governance into execution rather than layering it on afterward. 
  • They establish prioritization discipline so resources concentrate on the highest-value opportunities. 

Companies that build these foundations are significantly more likely to generate returns from AI. Then value begins to compound. 

The real constraint 

The limiting factor in AI value is the way the organization operates. 

AI exposes the gaps in decision flow, governance, workflow design, and adoption systems. When those gaps remain, pilots succeed but value does not scale. 

The organizations that move ahead are not those with the most pilots. They are the ones that redesign how work, decisions, and adoption operate together. 

They turn isolated success into repeatable performance. 

That is what separates experimentation from enterprise value. 

See where AI breaks down in your operating model

Most AI implementation challenges do not start with the technology. They emerge from how work flows, how decisions are made, and how governance is applied in daily execution. 

The AI-first operating model design assessment identifies where your current operating model limits scale, surfaces gaps in workflow, governance, and decision flow, and shows how to move from isolated pilots to coordinated execution. 

Frequently asked questions about AI implementation

What are the most common AI implementation challenges? 

The most common AI implementation challenges include unclear ownership of outcomes, weak governance, fragmented workflows, and lack of prioritization. Organizations often deploy AI without redesigning how work flows, which limits impact and prevents consistent value from scaling across teams. 

Why do AI projects fail to scale in enterprises? 

AI projects fail to scale in enterprises because pilots operate in isolation from real operating conditions. When expanded, they encounter governance gaps, cross-team dependencies, and unclear decision structures, which prevent repeatable execution and reduce overall business impact. 

What is the difference between an AI pilot and enterprise AI value? 

An AI pilot demonstrates that a use case can work under controlled conditions. Enterprise AI value requires repeatable performance across workflows, with measurable outcomes in cost, speed, quality, and adoption sustained over time across multiple teams and functions. 

What are AI scaling challenges in large organizations? 

AI scaling challenges in large organizations include portfolio sprawl, inconsistent workflows, lack of governance embedded in execution, and low adoption. These challenges prevent organizations from moving beyond isolated successes to coordinated, enterprise-wide impact. 

How do you scale AI in enterprise environments? 

Scaling AI in enterprise environments requires redesigning workflows, clarifying decision rights, embedding governance into execution, and prioritizing high-value use cases. Organizations must align operating models to support consistent, repeatable execution rather than relying on isolated experimentation. 

What is an AI governance framework and why does it matter? 

An AI governance framework defines how AI is controlled, monitored, and used within workflows. It matters because governance ensures trust, accountability, and consistency, enabling organizations to scale AI safely while maintaining performance, compliance, and decision integrity. 

How can organizations overcome AI implementation challenges? 

Organizations overcome AI implementation challenges by aligning their operating model to AI-enabled execution. This includes embedding governance, redesigning workflows, establishing clear ownership, and building adoption systems that reinforce new ways of working across teams. 

Why is AI adoption important for scaling value? 

AI adoption is critical because value only materializes when people consistently use AI within real workflows. Without sustained adoption, even well-designed solutions fail to deliver impact, and organizations remain stuck in pilot stages without achieving enterprise outcomes. 

AI transformation strategy: why programs outperform projects 

Posted on April 30, 2026 by - AI Transformation, Organizational Change & Culture

Why AI transformation strategy needs programs, not projects 

Enterprise AI investment continues to climb. The returns remain uneven. Even when experimentation succeeds, enterprise scale often remains elusive. 

The primary constraint is structural. Model quality continues to improve, but most organizations still run AI as a series of discrete projects. Discrete projects can deliver useful outputs, but they rarely create the continuity required for compounding enterprise value. The unit of execution is misaligned with how AI value is created. 

An effective AI transformation strategy needs a program model built for continuity, adoption, and sustained performance. The distinction matters because AI value depends less on whether a capability launches and more on whether the organization keeps improving how people use it, govern it, and measure it. 

Projects optimize scope. Programs optimize sustained outcomes A project is bounded by scope, timeline, and deliverables. That model can work for a warehouse build or a payroll rollout. It breaks down when leaders use it as the default structure for AI transformation. 

AI value rarely lives inside a single deliverable. 

Analysts need to trust the output. Governance needs to keep pace with model updates. Adoption needs to hold after the launch team moves on. None of those conditions closes on a delivery date. 

Programs are built to persist. They ask a better question: “Did performance improve, and is it still improving?” That question changes how leaders fund, govern, and measure AI work. A project-based AI rollout often tracks deployment milestones and usage counts. 

A program tracks performance metrics: cycle time reduction, cost-to-serve improvement, quality variation, risk exposure, and depth of role-based adoption. The inputs may look similar, but the operating discipline is different. 

That distinction is central to program management vs. project management in AI work. 

Why AI value realization stalls between funding cycles 

When AI is funded as a series of projects, momentum often resets every cycle. Each new funding cycle requires a new justification. Learning often stays with the team that ran the last initiative. 

Adoption gets treated as a post-delivery activity rather than a design requirement. Governance often trails capability deployment, creating a widening gap between what AI can do and what the organization is prepared to govern. 

The issue is not simply that individual projects end. The issue is that their learning, governance, adoption patterns, and value measures often end with them. 

MIT’s Project NANDA research shows a similar pattern. The research points to a deeper operating constraint: many enterprise AI systems do not learn, retain context, or adapt over time. 

For enterprise leaders, that is a continuity problem expressed through technical symptoms. AI initiatives can run long enough to consume budget, but still fail to build sustained confidence. Long enough to consume budget, but short enough to weaken confidence in the next AI initiative. 

For finance and portfolio leaders, this is a familiar governance problem showing up in a new context. Board conversations return to the same issue: funded initiatives that cannot be traced to measurable outcomes. 

Without continuity, leaders lack a reliable way to see which investments are compounding and which have stalled. The CFO lacks defensible value visibility. The CIO lacks a credible basis for prioritizing the next round of AI investment. 

Continuity as a structural design principle 

Continuity is the missing design element in many AI execution models. Leaders create continuity when strategy, execution, adoption, and measurement connect across initiatives instead of resetting with each one. 

In practice, continuity means the right elements persist between cycles: 

  • Outcome definitions tied to business performance 
  • Measurement frameworks that track performance over time 
  • Adoption models that reinforce how work actually gets done 
  • Governance cadence that supports decisions to scale, pause, or retire a capability 

Other elements evolve as the program matures: 

  • The model version or AI capability in use 
  • The workflows where AI is applied 
  • The specific teams and roles involved 

When they are absent, each cycle starts cold. Workflow changes get reopened. Metrics change definitions. Teams relearn what the last group already knew. 

McKinsey’s State of AI research helps illustrate the gap. Adoption is broad, while enterprise-scale continuity remains much less common. 

How continuous improvement in AI compounds performance 

Programs improve outcomes because they give insight a place to accumulate. 

Every cycle generates signals about what works, where users push back, which workflows absorb AI cleanly, and which workflows need redesign first. 

A project often leaves that learning in a closeout report after the team has moved on. A program carries it forward. 

That is continuous improvement in AI as an operating discipline. 

  • The compounding should show up in operational measures. 
  • Cycle time for AI-assisted decisions can drop as workflows are refined. 
  • Cost-to-serve can decrease as manual effort is removed. 
  • Quality can improve as variation is identified and reduced. 

Adoption can stabilize at higher levels when role-based enablement is built into execution from the start. 

McKinsey data suggests that organizations with higher AI maturity are nearly three times more likely to redesign workflows around AI instead of placing AI on top of existing processes. 

That redesign creates durable value only when it is sustained. One-time workflow changes tend to decay. Continuous improvement allows the gains to compound. That compounding effect requires an execution model designed to preserve what the organization learns. 

What program-based AI execution looks like in practice 

Program-based AI execution has observable properties that distinguish it from project-based work: 

Outcomes define the work 
The program is built around a measurable business outcome. AI capabilities are selected because they support that outcome. 

Measurement is continuous 
Investment, work, and results connect through one measurement spine. 

Execution is integrated 
Execution connects workflows, teams, and platforms. AI is embedded into real work instead of added as a separate layer. Product, operations, and governance stay coordinated throughout the program. 

Adoption is designed from the start 
Role-based enablement, behavior change, and reinforcement are part of the program plan from the beginning. McKinsey’s March 2026 analysis reinforces this point. The highest-performing organizations focus less on isolated AI deployment and more on embedding AI into how work actually runs. 

Governance operates within the cadence of the work 
Decision rights, escalation paths, and review cadences are defined early and adjusted as the work evolves. 

Learning loops are embedded 
Learning loops are embedded into the workflow. The program captures those signals as part of normal execution. 

What enterprise leaders need to change 

The leadership implication is specific. 

Leaders need to organize the portfolio around sustained outcomes instead of isolated initiatives: 

  • Funding should follow sustained outcomes rather than discrete initiatives 
  • Stage gates should carry learning into the next cycle 
  • Governance should sustain continuity across cycles 
  • Metrics should track sustained performance rather than delivery milestones 
  • Adoption and enablement should be embedded into execution 

AI should be treated as part of operating model evolution rather than a series of capability deployments. That shift creates the foundation for a durable AI transformation strategy. 

Closing the gap 

AI often stalls because the execution model was built for delivery completion rather than sustained adoption, governance, and performance improvement. 

The organizations pulling ahead are organizing AI around programs that sustain learning, adoption, and value realization across cycles. They design for continuity so results can compound. 

AI adoption is where value either compounds or stalls

AI value breaks down when teams do not change how work gets done. Adoption and change coaching embeds new behaviors into real workflows so results can scale and hold. 

Start with clarity before you scale.

Frequently asked questions about AI transformation strategy 

What is the difference between program management and project management in AI? 

Project management focuses on delivering defined outputs within a fixed scope and timeline. Program management focuses on sustained outcomes over time, connecting multiple initiatives, governance, and adoption into a continuous system that improves performance rather than resetting after each delivery cycle. 

Why do AI projects fail to deliver long-term value? 

AI projects often fail because they treat deployment as the finish line. Without sustained adoption, governance, and performance tracking, value does not persist. Learning is lost between cycles, and organizations struggle to connect AI capabilities to measurable business outcomes over time. 

What is an AI program and how does it work? 

An AI program is a structured, ongoing approach to embedding AI into workflows, governance, and decision-making. It connects strategy, execution, and measurement across cycles so improvements compound, enabling organizations to continuously refine performance and sustain value rather than restarting with each initiative. 

How do you measure AI value at scale? 

AI value at scale is measured through operational outcomes such as cycle time, cost-to-serve, quality, risk, and adoption depth. These metrics are tracked continuously across workflows, allowing leaders to see whether performance is improving over time rather than relying on one-time delivery milestones. 

Why is AI adoption critical to ROI? 

AI adoption determines whether capabilities translate into real performance improvements. If teams do not change how they work, AI remains underutilized. Embedding adoption into workflows ensures that tools are used consistently, enabling organizations to realize and sustain measurable business value. 

What does continuous improvement in AI mean? 

Continuous improvement in AI refers to using each execution cycle to refine workflows, models, and behaviors. Instead of treating AI as a one-time deployment, organizations build feedback loops into daily work so insights accumulate and performance improves steadily over time. 

How should leaders fund AI initiatives? 

Leaders should fund AI initiatives based on sustained outcomes rather than isolated projects. This means aligning funding with measurable performance improvements, maintaining continuity across cycles, and ensuring that learning, governance, and adoption persist instead of resetting with each new investment. 

What role does governance play in AI programs? 

Governance ensures AI operates safely and effectively within real workflows. In program-based execution, governance is embedded into daily operations, with clear decision rights, escalation paths, and review cadences that evolve alongside the work to support continuous performance improvement. 

How do you move from AI pilots to enterprise scale? 

Moving from pilots to scale requires shifting from isolated experiments to program-based execution. Organizations must connect workflows, embed adoption, track outcomes continuously, and carry learning forward so each cycle builds on the last rather than starting from scratch. 

Adoption gaps are the hidden barrier to Atlassian Cloud value realization 

Posted on April 24, 2026 by - AI Transformation, Platform Adoption & Governance

Most organizations approach Atlassian Cloud value realization as a licensing exercise. They review user tiers, consolidate instances, and look for ways to reduce spend. On paper, those efforts can produce cleaner numbers and tighter controls. 

In practice, they rarely address the deeper issue. 

The larger cost does not appear in a licensing report. It shows up in how the platform is used, how work moves through it, and how consistently teams adopt the capabilities already available to them. 

The expected Atlassian Cloud ROI is not in question. A recent Forrester Total Economic Impact study found organizations can achieve up to 230% ROI with a payback period of less than six months when the platform is used effectively. Those outcomes are real, but they are not typical. 

Most organizations never fully capture them. 

Why migration does not guarantee Atlassian Cloud value realization 

Migration is often treated as a finish line. The project is scoped, executed, and closed, with success measured by whether teams go live on time and without disruption. Once that milestone is reached, attention shifts elsewhere. 

Then a different question emerges. 

Are teams working better? 

For many organizations, the answer is difficult to quantify. Workflows may look familiar, even after the move to cloud. Jira often reflects legacy processes with minimal change. Confluence contains information, but not always information that teams rely on when making decisions. New capabilities exist, yet they are not consistently part of how work gets done. 

The platform has changed. The Atlassian Cloud adoption strategy has not. 

That disconnect explains why expected ROI does not materialize. The technology can deliver value quickly, but only when the surrounding behaviors evolve alongside it. Without that shift, the organization carries forward the same inefficiencies, now operating on a more capable platform. 

Migration completes a technical milestone. Value realization depends on what follows. 

Atlassian Cloud adoption gaps as structural friction 

Low adoption is frequently framed as a user issue. Teams need more training. Features are not fully understood. Communication could be clearer. 

Those explanations are convenient, but they are incomplete. 

Adoption gaps are structural. They emerge from how work is organized, how decisions are made, and how systems either reinforce or undermine consistent behavior. When those elements are misaligned, friction becomes unavoidable. 

That friction shows up in ways leaders recognize immediately: 

  • Work is tracked, but not clearly tied to strategic goals 
  • Teams use Jira differently, making cross-team coordination harder than it should be 
  • Knowledge exists, but finding the right information at the right moment is inconsistent 
  • Manual effort persists, even where automation is available 

These patterns are not isolated. They reflect a system that has not been designed to take advantage of the platform. 

As friction builds, adoption becomes uneven. As adoption becomes uneven, utilization declines. Over time, the cost of the platform begins to outpace the value it delivers. 

This is where the hidden cost takes shape. 

Where underutilization hides in Atlassian Cloud 

Most organizations capture only a portion of the value available to them. Internal benchmarks show that 30 to 40 percent of platform value is typically left unrealized. 

That gap is not random. It follows consistent patterns across Jira, Confluence, and Jira Service Management. 

Jira: activity without alignment 

Teams are active, and work is moving forward, but alignment is often unclear within the broader Atlassian Cloud adoption model. Tasks may be completed efficiently, yet remain disconnected from vital business objectives. 

Automation is available but inconsistently applied. Reporting reflects activity levels rather than meaningful progress. From a leadership perspective, visibility exists, but it does not always translate into insight. 

The result is a system that captures motion more effectively than impact. 

Confluence: knowledge without trust 

Confluence frequently grows into a repository of information that is difficult to navigate and even harder to rely on. Content accumulates, ownership becomes unclear, and the signal-to-noise ratio declines over time. 

When teams cannot quickly determine what is current and relevant, they turn to informal channels instead. Knowledge exists, but it does not consistently support decision-making or execution. 

Without trust, usage declines, regardless of how much content is created. 

Jira Service Management: workflows without efficiency 

Service workflows are in place, but they do not always deliver the efficiency they promise. Manual triage remains common. Automation is underused or inconsistently configured. AI-assisted capabilities may be enabled, yet rarely embedded into daily operations. 

The system processes requests, but it does not consistently reduce effort or improve outcomes. 

In each case, the issue is not capability. It is utilization. 

Behavior change vs. feature enablement 

When these gaps become visible, the instinct is to enable more features. Organizations invest in automation, expand access, and introduce AI capabilities in the hope that usage will follow. 

Sometimes it does, but usually in isolated pockets. 

Recent data highlights the limitation of this approach. Employees report productivity gains of roughly 30 percent when using AI tools, yet 96 percent of organizations are not seeing meaningful AI ROI at scale. 

At first glance, that seems contradictory. In reality, it reveals the core issue. 

Tools can improve individual performance. They do not automatically change how an organization operates. 

Feature enablement creates potential. Behavior change determines whether that potential translates into measurable Atlassian Cloud ROI. Without consistent integration into workflows, even the most advanced capabilities remain underutilized. 

The result is a growing gap between what the platform can do and what it actually delivers. 

Designing adoption at scale 

An effective Atlassian Cloud adoption strategy does not emerge as a byproduct of implementation. It must be designed deliberately, with attention to how work is structured and how teams interact with the platform over time. 

When adoption is approached this way, the difference is noticeable. 

Work begins to follow consistent patterns across teams. Knowledge is maintained as part of execution rather than as an afterthought. Automation reduces manual effort in repeatable processes, freeing teams to focus on higher-value work. AI capabilities, instead of sitting on the sidelines, become embedded in decision-making. 

None of these outcomes come from configuration alone. They require alignment between the platform and the way the organization actually operates. 

Measurement becomes essential to any Atlassian Cloud adoption strategy at this stage. Without visibility into how the platform is used, improvement efforts rely on assumptions rather than evidence. Organizations that treat adoption as a measurable system are able to identify friction points, prioritize changes, and track progress over time. 

Adoption becomes sustainable when it is reinforced through structure, not left to chance. 

The connection between adoption and cost optimization 

Cost optimization is often approached with a narrow lens. Reduce licenses where possible, eliminate redundancy, and control spend through governance. 

Those actions can produce short-term gains, but they do not address the underlying drivers of cost. 

The primary driver of Atlassian Cloud ROI is how effectively people use the platform. Efficiency, consistency, and alignment determine whether each user contributes to measurable outcomes. 

When adoption improves, three things happen in parallel. 

First, waste becomes easier to identify and remove. Unused licenses and redundant tools stand out clearly once usage patterns are visible. 

Second, value per user increases. Teams complete work more efficiently, with fewer handoffs and less manual intervention. 

Third, ROI becomes easier to defend. Leaders can connect platform usage directly to business outcomes, rather than relying on assumptions. 

This changes the nature of the conversation. Cost optimization shifts from reduction to alignment, where spend, usage, and outcomes reinforce each other. 

In that environment, expansion becomes a strategic decision rather than a risk. 

Adoption, AI, and the next phase of value 

AI introduces another layer of complexity. Many organizations have already enabled AI capabilities within Atlassian Cloud, yet adoption remains uneven. In many cases, AI is used for isolated tasks rather than integrated into workflows. 

The same pattern repeats. 

Without structured adoption, AI amplifies existing inconsistencies instead of resolving them. Data quality issues limit its effectiveness. Fragmented workflows prevent it from influencing decisions in meaningful ways. 

AI does not change the fundamentals. It increases the importance of getting them right. 

What leaders should evaluate next 

For CIOs and Platform Owners, progress begins with clarity rather than additional tooling. 

A few questions can reveal where value is being constrained: 

  • Where is platform usage inconsistent across teams? 
  • Which capabilities are enabled but rarely used? 
  • How is adoption measured today, if at all? 
  • Can we connect platform usage to business outcomes with confidence? 

These questions shift the focus from configuration to performance. They also establish a foundation for accountability, where adoption and outcomes can be tracked and improved over time. 

The hidden cost becomes visible 

The cost of Atlassian Cloud is easy to measure. Value realization is harder to define, especially when adoption varies across the organization. 

Adoption gaps sit between those two realities. They reduce utilization, weaken ROI narratives, and create pressure to justify spend without clear evidence. 

When adoption is treated as a system, that gap becomes visible. Once visible, it can be addressed with precision. 

Organizations that close this gap do more than reduce cost. They increase the value created by every user, every workflow, and every decision supported by the platform. 

That is how Atlassian Cloud delivers its full value and measurable ROI. 

Continue the conversation 

This topic will be explored in more depth at Atlassian Team ’26, including how organizations are moving beyond migration to build measurable, compounding value.

If this challenge is relevant, it is worth continuing the conversation. Or, if we won’t see you at the event, you can move right to the self-assessment and we’ll talk afterward

Frequently asked questions 

What is Atlassian Cloud value realization? 

Atlassian Cloud value realization refers to the measurable business outcomes an organization achieves after migration. It goes beyond deployment to include improved productivity, alignment, and decision-making. Real value emerges when teams consistently use the platform to support how work actually flows across the organization. 

Why do organizations struggle to achieve Atlassian Cloud ROI? 

Most organizations struggle because migration changes tools, not behavior. Without a structured adoption strategy, teams continue working the same way they did before. This leads to underutilized features, inconsistent workflows, and limited visibility, all of which prevent ROI from scaling across the enterprise. 

How does adoption impact Atlassian Cloud cost optimization? 

Adoption directly affects cost optimization by determining how much value each user generates. When adoption is low, organizations pay for capabilities they do not use. When adoption improves, waste decreases, productivity increases, and leaders can justify spend based on measurable outcomes rather than assumptions. 

What are common signs of low Atlassian Cloud adoption? 

Common signs include inconsistent Jira workflows, limited use of automation, outdated or unused Confluence content, and manual processes in Jira Service Management. Leaders may also struggle to connect work to strategic goals or gain clear visibility into progress across teams. 

How can organizations improve Atlassian Cloud adoption? 

Organizations improve adoption by designing how work should flow within the platform, not just configuring tools. This includes standardizing workflows, embedding knowledge into execution, enabling automation, and continuously measuring usage patterns to identify and address friction points over time. 

How is AI adoption connected to Atlassian Cloud ROI? 

AI adoption depends on the same foundations as overall platform adoption. Clean data, consistent workflows, and structured processes are required for AI to deliver value. Without these elements, AI capabilities remain underused and fail to contribute meaningfully to enterprise-level ROI. 

What should CIOs evaluate after migrating to Atlassian Cloud? 

CIOs should evaluate how consistently teams use the platform, which features remain underutilized, and whether platform usage can be linked to business outcomes. Ongoing measurement of adoption and performance is critical to ensuring that value continues to grow after migration is complete.

AI adoption strategy: what leaders must do after AI go-live 

Posted on April 24, 2026 by - AI Transformation, Organizational Change & Culture, Uncategorized

AI go-live creates visibility. It does not create value. 

After launch, teams experiment, attend training, and generate early activity. Yet despite rising investment, 56% of CEOs report no profit gains from AI over the past year (PwC Global CEO Survey, 2026). 

Why? 

Momentum fragments. Usage becomes uneven, managers revert to familiar rhythms, and governance drifts back to periodic review. Employees either use AI casually, avoid it, or work around it. In fact, 54% of executives cite culture and behavior as the primary barrier to scaling AI (Mercer, 2024). 

This is a structural issue, not a problem with motivation. When the operating system around AI does not change, adoption decays. 

A strong AI adoption strategy starts after go-live. Leaders must align incentives, embed governance in execution, redesign workflows, and make outcomes visible so AI becomes part of how work moves. 

Launch is not adoption 

Adoption is often misread. 

  • Logins show access. 
  • Training shows exposure. 
  • Prompt libraries show enablement. 

None confirm that work has changed. This gap between access and value is widespread: only 14% of CFOs report clear, measurable ROI from AI investments (RGP + CFO Research, 2026). 

Adoption exists when AI is used inside real workflows to improve outcomes. It shows up in how teams prepare decisions, analyze information, manage handoffs, resolve exceptions, and review results. 

Shift the question from “Are people using AI?” to “Where has AI changed how work moves?” 

For enterprise contexts, four expectations should be explicit: 

  • Roles: where human judgment remains essential and where AI supports analysis, synthesis, or routine execution 
  • Decisions: how AI-supported inputs are reviewed, trusted, challenged, and acted on 
  • Governance: controls that operate inside workflows, not outside them 
  • Reinforcement: how teams improve usage over time 

This is where AI change management moves beyond communication into behavior change in the work itself. 

Why post-launch decay happens 

Decay is predictable when AI is introduced into operating models designed for earlier ways of working. 

Four conditions drive it: 

1) Incentives reward the old workflow 

If goals still reward manual effort, activity volume, or legacy reporting, AI-enabled behavior remains optional. Teams experience AI as added work. 

What to change: connect AI-supported behaviors to the outcomes teams already own (cycle time, quality, cost, risk, experience) and remove or redesign outdated tasks. 

2) Leaders do not model the change 

If executive forums run the same way, the signal is clear: AI is optional. 

What to change: require AI-supported analysis in decision forums and demonstrate how human judgment validates and improves AI outputs. 

3) Governance sits outside execution 

Policy and committees cannot carry day-to-day decisions. 

What to change: define decision rights, validation standards, and escalation paths inside workflows so teams can move with clarity and control. 

4) Workflows are unchanged 

Layering AI onto inefficient processes limits value. 

What to change: redesign where AI supports preparation, analysis, communication, and exception handling; clarify where human ownership remains. 

What leaders must do differently 

After go-live, leadership behavior determines whether AI becomes embedded or ignored. 

At this stage, employees are not looking for messaging. They are looking for signals. What leaders ask for, inspect, and reward becomes the operating reality. 

Reinforce adoption by: 

  • Using AI-supported analysis in decision forums so teams see it as expected input 
  • Asking where AI changed outcomes, not where it was used 
  • Aligning performance objectives with AI-enabled work so behavior has consequences 
  • Removing redundant tasks made unnecessary by AI so capacity is not artificially constrained 
  • Making validation and oversight part of the work so trust increases over time 

Don’t undermine adoption by: 

  • Treating AI as optional productivity 
  • Adding expectations without adjusting capacity 
  • Demanding ROI while preserving legacy execution 
  • Leaving policy unclear, driving shadow AI 
  • Measuring activity instead of outcomes 

The difference is practical accountability at the level of work. Leaders do not need to control every use case, but they must define what good looks like and reinforce it consistently. 

Make value visible: incentives, metrics, modeling 

Adoption does not scale without reinforcement. Reinforcement requires visibility into what matters and why it matters. 

Three levers carry most of the weight. 

Incentives 

Incentives translate intent into behavior. If AI-enabled work does not influence how performance is evaluated, it will remain secondary. 

Avoid narrow usage targets. Those drive superficial adoption. Instead, connect AI-supported behavior to outcome movement such as reduced cycle time, improved quality, faster response, or clearer risk visibility. 

The practical test is simple: can a team explain how using AI changed their results, not just their activity? 

Metrics (AI ROI measurement) 

Measurement closes the loop between adoption and value. 

Many organizations track tool activity but cannot show operational impact, which aligns with broader market signals that only a small minority of organizations can clearly tie AI usage to financial outcomes (RGP + CFO Research, 2026). A stronger approach is to build a KPI spine that links AI use to performance indicators already owned by the business. 

This allows leaders to answer two questions at the same time: where AI is being used and whether it is improving how work performs. 

Executive modeling 

Modeling turns expectations into visible practice. 

When leaders require AI-supported preparation in reviews or use AI-generated scenarios to evaluate decisions, they show how AI fits into judgment and accountability. This removes ambiguity for teams and accelerates consistent adoption. 

Embed governance at the speed of work 

Governance is often treated as a separate layer. That approach slows adoption and creates confusion, while also increasing the risk of unmonitored “shadow AI” usage across teams—one of the fastest-growing enterprise AI risks. 

AI operates inside daily workflows. Governance must do the same. 

Embedding governance means defining how decisions are made, validated, and escalated within the work itself. Teams should not need to leave their workflow to determine what is allowed or how to proceed. 

Embed: 

  • Decision rights for AI-supported workflows so ownership is clear 
  • Validation standards for outputs so trust is earned, not assumed 
  • Monitoring for drift, misuse, and quality issues so risks are visible early 
  • Runbooks for escalation, rollback, and improvement so teams know how to act 
  • Feedback loops to update workflows as risks evolve so governance improves over time 

This approach increases both speed and control. Teams move faster because expectations are clear, and leaders maintain oversight because governance is built into execution. 

Build reinforcement loops 

Adoption is sustained through repetition, not initial enthusiasm. 

Reinforcement loops ensure that AI use improves over time rather than degrading after launch. These loops must be grounded in real work, not abstract training programs. 

Focus on: 

  • Role-specific expectations so each function understands how AI applies to its decisions 
  • Continuous enablement tied to real workflows so learning is immediately usable 
  • AI embedded in ceremonies and operating rhythms so usage becomes routine 
  • Manager coaching to help teams replace old behaviors with more effective ones 
  • Feedback channels to capture friction, trust issues, and improvement ideas 
  • Regular value reviews linking adoption to outcomes so progress is visible 

Programs outperform projects because they maintain these loops. A project introduces capability. A program ensures that capability evolves and compounds. 

Early warning signs of decay 

Leaders can detect adoption issues early by observing how work is actually happening. 

Watch for: 

  1. Usage concentrated in a few champions, indicating lack of role-based adoption 
  1. Meetings and decision forums unchanged, showing AI has not entered execution 
  1. Inability to link AI use to performance movement, revealing weak measurement 
  1. Governance questions slowing or stopping usage, indicating unclear boundaries 
  1. ROI requested after the fact rather than managed in-flight, showing a missing measurement system 

These signals are not failures. They are diagnostics that show where reinforcement and design need to improve. 

What changes when leaders take ownership 

When leaders actively own post-launch adoption, the organization moves from experimentation to discipline. 

Workflows become clearer. Decision-making accelerates because inputs are better prepared. Governance becomes more practical because it is embedded. Performance improves because outcomes are measured and managed consistently. 

This shift does not require perfect technology. It requires consistent alignment between how work is designed, how decisions are made, and how performance is evaluated. 

A practical AI adoption strategy after go-live 

A post-launch strategy should translate intent into operating design. 

Answer six questions: 

  1. Which workflows will change because of AI? 
  1. Which roles need new decision rights or validation responsibilities? 
  1. Which legacy tasks can be reduced or removed? 
  1. Which KPIs will show performance movement? 
  1. Which controls must operate inside the workflow? 
  1. Which reinforcement loops will sustain improvement? 

These questions provide a direct path from concept to execution. They also ensure that adoption and measurement are designed together, rather than addressed separately. 

Turn go-live into sustained value 

After launch, responsibility increases. 

Employees look for cues. Managers decide what matters. Governance moves from theory to practice. Leaders need evidence of impact. 

Start with diagnosis. Identify where adoption is weakening, which workflows need redesign, and how leadership can reinforce change. 

AI Adoption and Change Coaching helps leaders diagnose friction, rethink workflows, build role-based competency, and embed reinforcement systems. Where broader constraints exist, AI-First Operating Model Design aligns decision flow, KPI systems, governance cadence, and portfolio discipline. 

If AI has created activity without behavior change, act now to redesign how work runs so decisions, incentives, and governance drive measurable outcomes every day. 

See where your AI adoption strategy is breaking down

Technology is rarely the problem. Most organizations have an adoption gap hidden inside their workflows, incentives, and governance. In one week, you’ll get a clear view of where AI is failing to change how work gets done, and exactly what to fix first to start driving measurable outcomes.

Frequently asked questions 

What is an AI adoption strategy? 

An AI adoption strategy is the system of incentives, workflows, governance, and reinforcement that determines whether AI changes how work is performed after launch. It focuses on embedding AI into decision-making and execution so usage translates into measurable improvements in cycle time, quality, cost, and risk. 

Why does AI adoption fail after go-live? 

AI adoption often fails after go-live because the surrounding operating model does not change. Incentives, workflows, governance, and leadership behaviors remain aligned to pre-AI ways of working. As a result, teams revert to familiar patterns and AI becomes optional rather than embedded in daily execution. 

How do you measure AI ROI in the enterprise? 

Measure AI ROI by linking AI usage to operational KPIs such as cycle time, throughput, quality, cost-to-serve, and risk. Build a KPI spine that connects AI-supported workflows to business outcomes, allowing leaders to see both where AI is used and whether it improves performance. 

What is the difference between AI usage and AI adoption? 

AI usage reflects access and activity, such as logins or prompts. AI adoption occurs when AI changes how work is performed inside workflows. Adoption shows up in improved decisions, reduced handoffs, faster execution, and better outcomes rather than increased tool activity alone. 

What role do leaders play in AI adoption? 

Leaders shape adoption by defining expectations, modeling behavior, and aligning incentives. When leaders require AI-supported inputs in decisions and measure outcomes instead of activity, teams adopt AI more consistently. Without leadership reinforcement, adoption remains fragmented and declines over time. 

How should AI governance be structured? 

AI governance should be embedded within workflows, not managed as a separate layer. It must define decision rights, validation standards, autonomy boundaries, monitoring, and escalation paths so teams can use AI confidently while maintaining control and compliance at the speed of work. 

What are the early signs of AI adoption failure? 

Common signs include usage concentrated among a few individuals, unchanged meetings and decision processes, inability to link AI to performance improvements, governance confusion, and delayed ROI measurement. These signals indicate that adoption has not been embedded into workflows or reinforced effectively. 

How do incentives impact AI adoption? 

Incentives determine behavior. If performance systems reward legacy activities, AI-enabled work remains secondary. Align incentives with outcomes such as speed, quality, and efficiency improvements so teams see clear value in adopting AI-supported ways of working. 

What is post-launch AI change management? 

Post-launch AI change management focuses on reinforcing behavior after deployment. It includes role-based enablement, workflow redesign, governance integration, and continuous feedback loops to ensure AI becomes part of daily execution rather than a one-time implementation effort. 

How long does it take to see value from AI adoption? 

Initial value can appear quickly in targeted workflows, but sustained impact requires continuous reinforcement. Organizations that align incentives, governance, and workflows early can see measurable improvements within weeks, while broader enterprise value compounds over months as adoption scales. 

The Next Evolution of Employee Experience Is Already Here: Inside ServiceNow EmployeeWorks

Posted on April 21, 2026 by - AI Transformation, Employee Experience (EX), Service Management

Employee expectations have reset around speed, simplicity, and immediacy. The way people interact with technology in their personal lives has shaped how they expect work to happen. They ask, they get answers, and tasks move forward without delay.

Enterprise service models have struggled to keep pace.

Traditional HR and IT portals require navigation, form submission, and waiting. Employees must understand where to go, how to ask, and which system owns the request before work can begin. That friction slows execution and creates unnecessary dependency on service teams.

The result shows up in everyday work. Employees spend a meaningful portion of their time searching for information or figuring out how to complete basic tasks.  

This gap between expectation and experience has become structural. Employee service can no longer operate as a separate layer that responds to requests. It must become part of how work moves across the organization.

AI assistants are becoming the new interface for work

A new interaction model is emerging inside the enterprise.

Employees increasingly expect to ask for what they need in natural language and have the system respond with context, clarity, and progress. This shift moves the interface from navigation to conversation.

ServiceNow’s integration of Moveworks capabilities brings this model directly into enterprise workflows. Conversational AI, enterprise search, and workflow execution now operate within a single interaction layer.

This changes how work begins and how it progresses.

Instead of searching across systems, employees describe intent. The system interprets that intent, identifies the relevant context, and initiates the appropriate workflow. Information and action exist in the same interaction, which reduces the gap between knowing and doing.

This is a shift in how employees engage with systems. The interface becomes a point of coordination between human intent, enterprise knowledge, and workflow execution.

What EmployeeWorks changes

ServiceNow EmployeeWorks introduces a new model for employee service, built around a single principle: work should move from request to outcome within one continuous flow.

AI assistants embedded into employee workflows

EmployeeWorks provides a single conversational interface that spans HR, IT, finance, procurement, and other domains. Employees interact in natural language across web, mobile, and collaboration tools, without needing to switch systems.

This interface carries context. It understands the employee’s role, permissions, and prior interactions, which allows responses and actions to remain relevant and secure.

The interaction becomes part of the workflow itself rather than a separate step before work begins.

Automated task execution across systems

EmployeeWorks connects conversational interaction directly to enterprise workflows.

Requests trigger actions across systems, including approvals, updates, and multi-step processes. Routine work progresses automatically where appropriate, while exceptions route to the right people with full context.

This creates a continuous flow from intent to execution. Employees no longer track tickets or chase updates. Work advances with visibility, and outcomes become the primary measure of service.

Unified employee service experience

EmployeeWorks unifies search, knowledge, and execution into a single experience.

Employees can find information across hundreds of systems and act on it within the same interaction. Context remains intact as work progresses, which removes the need to repeat inputs or navigate between tools.

This unified layer reduces fragmentation across service functions. HR, IT, and other teams operate within a shared model where employee requests translate into coordinated execution.

The experience reflects how work actually happens across the enterprise rather than how systems are organized behind the scenes.

What early adopters are discovering

Organizations that adopt this model are seeing changes in how service operates and how work flows.

Faster resolution of employee requests

Requests move forward immediately once intent is captured. Many common service interactions resolve within the initial exchange, which reduces delays and shortens time to outcome.

Reduced HR and IT service backlog

Automation removes repetitive requests before they enter queues. Service teams focus on higher-value work that requires judgment, while routine tasks progress without manual intervention.

Improved employee satisfaction

Employees experience progress instead of waiting. They interact with a system that responds in context and moves work forward, which reduces frustration and increases confidence in internal services.

A first-mover perspective

INRY, a Cprime company, serves as an early global adopter of EmployeeWorks.

This experience highlights a critical point. The technology alone does not create value. Outcomes depend on how workflows, decision paths, and governance evolve to support this new interaction model.

Organizations that align EmployeeWorks to real workflows, define where automation applies, and reinforce adoption across teams see consistent results. Those that treat it as a surface-level enhancement struggle to realize its full potential.  

What we’re demonstrating at ServiceNow Knowledge 2026

At ServiceNow Knowledge 2026, the focus is on showing how this model operates in a real environment.

Attendees will see how EmployeeWorks:

  • Translates employee intent into coordinated workflow execution
  • Surfaces the right information and actions within a single interaction
  • Connects enterprise systems through a unified conversational layer
  • Enables employees to complete tasks without navigating multiple tools

The demonstration reflects a working system rather than a conceptual future. It shows how employee service, workflow execution, and AI interaction operate together in practice.

Key takeaways

Employee experience is entering a new phase defined by how work moves, not how systems are accessed.

AI-mediated interaction is becoming the standard interface for employee service. Employees expect to ask, receive context-aware responses, and see work progress without friction.

Embedding AI into enterprise workflows enables this shift. It connects intent to execution, which reduces delays and improves how decisions translate into action.

EmployeeWorks brings these elements together into a single model. It unifies conversational interaction, enterprise search, and workflow execution so employee service becomes part of everyday work rather than a separate process.

Organizations that adopt this model early position themselves to improve productivity, reduce service friction, and create more consistent employee experiences across the enterprise.

The shift is already underway. The advantage comes from how quickly organizations adapt their workflows, decision paths, and adoption systems to support it.

Enterprise AI agents: How organizations operationalize AI at scale

Posted on April 17, 2026 by - AI Transformation, Organizational Change & Culture

FAQ: What are AI agents?

AI agents are software systems that can perform tasks by interpreting input, making decisions within defined rules, and taking action. In enterprise environments, AI agents operate inside workflows to move work forward using governed data, permissions, and process logic.

FAQ: What are enterprise AI agents?

Enterprise AI agents are AI systems designed to operate within business workflows. They execute defined tasks, interact with enterprise systems, and follow governance rules, which allows organizations to move from AI-generated outputs to real work being completed inside operational environments.

For the past few years, most enterprise AI initiatives have centered on assistance. Copilots drafted emails, summarized documents, and generated code. They improved productivity at the edge of work, but they rarely completed work inside the systems where execution happens.

That boundary is starting to shift.

Enterprise AI agents are extending AI beyond generation and into execution. Instead of stopping at recommendations, these systems can trigger actions, move work forward within approved boundaries, and complete defined tasks inside workflows.

This shift changes how work moves from recommendation to execution.

Organizations are moving from isolated AI experiments to embedded operational capabilities. Prompt-based interactions are giving way to workflow-driven execution. Output generation is giving way to task completion.

The focus is shifting from what AI can produce to what AI can complete.

This shift matters because leaders are now evaluating how AI participates in real execution, not just how it improves individual productivity. The conversation is moving from access to models toward integration into the systems where work actually happens.

That raises a more practical question.

If AI can now participate in execution, where can that execution happen reliably and under control?

Why workflows are the natural environment for AI agents

FAQ: Why are workflows critical for enterprise AI agents?

Workflows provide the structure AI agents need to operate reliably inside real business processes. They connect data, approvals, and execution steps, which allows AI to move work forward instead of stopping at recommendations. Without workflows, organizations must manually coordinate actions across systems.

FAQ: Can AI agents work without workflow automation?

AI agents can generate outputs without workflows, but consistent execution depends on workflow automation. Workflows define process steps, permissions, and governance, which allow agents to complete tasks inside enterprise systems instead of relying on manual follow-through.

AI struggles to deliver consistent results when it sits outside the workflows where work is governed. Without structure, AI outputs still require people to coordinate systems, approvals, and next steps by hand.

Many early AI initiatives stall at this point.

When AI sits outside workflows, four constraints appear quickly:

  • Reliable access to governed enterprise data
  • Defined process steps, dependencies, and escalation paths
  • Clear ownership, approvals, and accountability
  • Connected execution paths across systems

The result is fragmentation. AI may generate useful output, but people still have to carry work across systems and teams.

Workflows address this problem by giving AI a governed place to operate.

They provide the structure AI agents need to operate reliably:

  • Structured processes with defined steps and owners
  • Embedded business logic, decision rules, and approvals
  • Secure, permissioned access to enterprise systems
  • Built-in governance, traceability, and auditability

Most importantly, workflows connect intent to action inside systems that can govern the result. They turn recommendations into executable steps and decisions into tracked outcomes.

This is why AI workflow automation is emerging as a practical foundation for enterprise AI execution.

Within these environments, AI agents can participate directly in real work. Workflow platforms become the coordination layer because they connect process logic, enterprise data, permissions, and approvals in one execution system. This is where platforms such as ServiceNow can support AI agents at scale because execution remains connected to real workflows, data, and controls.

With that structure in place, the next question is practical:

What do enterprise AI agents actually do inside those workflows?

What enterprise AI agents actually do

FAQ: What do enterprise AI agents actually do in business workflows?

Enterprise AI agents execute defined tasks inside workflows by triggering actions, moving work through process steps, and coordinating across systems. They reduce manual effort by handling routine activities such as data updates, service requests, and operational coordination within governed environments.

FAQ: How are AI agents different from AI copilots?

AI copilots generate suggestions or content to support individual users, while AI agents participate in execution inside workflows. Agents can trigger actions and progress tasks within defined processes, whereas copilots rely on users to carry work forward into enterprise systems.

The value of enterprise AI agents comes from how they reduce coordination overhead and move work through real processes. Their impact becomes visible when you look at how work moves across systems, approvals, and teams.

Workflow automation

AI agents can execute defined multi-step processes that previously required people to coordinate them manually.

In those workflows, agents can:

  • Trigger approved workflows
  • Move tasks through defined stages
  • Handle routine dependencies automatically

This expands AI workflow automation from isolated task handling into managed flow across the work itself.

Data enrichment

Enterprise decisions depend on context, and that context is often scattered across systems.

In structured workflows, AI agents can help by:

  • Pulling data from multiple connected systems
  • Validating records and reconciling inconsistencies
  • Updating records as workflows progress

This reduces manual lookups and gives downstream decisions better context.

Service request fulfillment

Internal and customer-facing requests often span multiple teams and systems.

In those scenarios, AI agents can:

  • Interpret the request
  • Route the request into the appropriate workflow
  • Complete defined parts of the process across the workflow

This can reduce resolution time and lower manual effort in routine scenarios.

Operational coordination

Many enterprise processes begin with an event, trigger, or exception.

In those environments, AI agents can respond by:

  • Starting the right workflow
  • Coordinating across teams
  • Pushing actions forward within defined timelines and escalation rules

This supports faster, more consistent execution across complex environments.

The human-in-the-loop reality

AI agents operate inside boundaries set by people, approvals, and policy.

Those boundaries typically include:

  • Escalation points
  • Approval thresholds
  • Exception handling

This creates a hybrid execution model in which AI accelerates routine action while people retain decision authority. This keeps execution governed, auditable, and aligned with business intent.

From capability to execution: Where AI agents are already operating

FAQ: Where are enterprise AI agents used today?

Enterprise AI agents are used in workflow-heavy environments such as IT service management, HR onboarding, customer support, and security operations. These use cases rely on structured workflows where agents can access data, follow process rules, and execute tasks within defined permissions.

FAQ: What does AI agents in production mean?

AI agents in production refers to agents that operate inside live enterprise systems and workflows. These agents execute real tasks, interact with governed data, and follow defined processes, which allows organizations to move from experimentation into consistent execution.

AI agents are already moving into production in workflow-heavy enterprise environments.

Current deployments tend to concentrate in workflows such as:

  • IT service management processes
  • HR request and onboarding workflows
  • Customer support operations
  • Security and incident response

In these environments, AI agents do not operate in isolation. They participate in execution inside systems that already manage requests, approvals, and data.

These deployments sit inside operational systems where AI can participate in execution under defined controls. Their effectiveness depends on how tightly they are integrated into workflows rather than how advanced the underlying models are.

In environments with mature workflow orchestration, ServiceNow AI agents help show how AI can operate within real enterprise constraints, including:

  • Access to governed enterprise data
  • Execution within structured processes
  • Operation within defined permissions and approval paths

These implementations represent early execution patterns that can scale across functions. They show how AI begins to add value when it is embedded in governed workflows rather than left at the edge of work.

As these patterns expand, the question shifts from where AI can operate to how organizations adapt their execution systems to support it.

What organizations can expect next

FAQ: What is an agentic AI enterprise?

An agentic AI enterprise embeds AI agents into workflows to support execution, coordinate operations, and assist decision-making inside governed systems. This approach focuses on integrating AI into how work happens rather than treating it as a standalone tool.

FAQ: How should organizations prepare for enterprise AI agents?

Organizations should focus on redesigning workflows, defining decision boundaries, integrating systems, and embedding governance into execution. Preparation requires aligning operating models with how AI participates in work rather than only deploying new tools.

As adoption expands, enterprise AI agents will begin to influence more of the execution system around them.

Expansion into complex decision flows

AI agents will increasingly participate in:

  • Multi-step decision processes
  • Cross-functional workflows
  • Dynamic, event-driven execution

This expands automation into more adaptive execution systems that can respond to changing conditions within defined boundaries.

Emergence of hybrid execution models

Future workflows will increasingly combine:

  • Human judgment
  • System logic
  • AI-driven action

This layered model will shape how work moves across the enterprise.

Operating model transformation

To scale this shift, organizations will need to redesign how work, decisions, and governance are structured.

Key changes include:

  • Defining decision boundaries between humans and AI
  • Embedding governance directly into workflows
  • Designing workflows and escalation paths that accommodate agent participation

This is where operating model design becomes critical. The focus broadens beyond deploying AI tools and toward designing execution systems that support sustained, governed use.

A broader definition of automation

This expands the meaning of automation. It changes how decisions are made, how actions are triggered, and how work is completed.

Execution becomes more continuous, more coordinated, and more responsive within defined limits.

The next phase of enterprise execution

The evolution of AI in the enterprise is increasingly defined by execution.

Enterprise AI agents expand AI’s role from assisting work toward completing defined work inside governed workflows. Their value emerges when they are embedded within execution systems that:

  • Provide structure
  • Coordinate execution across systems
  • Maintain governance and auditability

Organizations that integrate AI into these execution systems can move faster, reduce operational friction, and deliver more consistent outcomes.

Organizations that remain focused on experimentation will struggle to translate AI potential into business impact.

The next phase of enterprise AI will be shaped by which organizations can operationalize AI effectively inside real execution systems.

Continue the conversation

This shift toward execution-driven AI is becoming central to how enterprise leaders think about workflow design, governance, and the future of execution.

The most useful insights come from seeing how AI agents operate inside real workflows under real constraints.

At ServiceNow Knowledge 2026, these execution patterns are moving from concept to practice, with real examples of how AI agents are operating inside enterprise workflows.

That is where the next phase of enterprise execution is starting to take shape.