The AI era is widening the gap between winners and laggards, and the delta is not only determined by who has the most AI but also how deeply AI is embedded into business processes. This according to IBM CEO Arvind Krishna at the Day 1 Keynotes from IBM Think 2026. His talk kept coming back to the operating model change that helps organizations move past experimentation and pilots and into end-to-end workflows where AI changes decisions, cycle times, and outcomes. IBM positioned this as a “day zero” moment – AI is here now, but most enterprises are still using it at the margins, and the opportunity window won’t stay open forever.
Krishna laid out the bridge between the past and the future in three vectors:
Vector 1 – Becoming an AI-first enterprise
One of the keynote segments that resonated the most was Krishna’s operating model argument. IBM’s claim is that AI is shifting from a technology initiative to “the business model,” and that’s why the old internal metrics (budget size, team size) are less important than whether the business is essentially AI-wired; end-to-end. IBM pointed to internal productivity gains ($4.5B) and framed AI as a growth lever, with many organizations intending to reinvest productivity into new products, new services, and new revenue streams.
The customer example IBM put forth was Aramco, positioned as an “AI-first enterprise” that has moved beyond pilots and put AI “in the field.” The emphasis was execution with Aramco saying “we’re not interested in PoCs…” we want to create value in the field. The company is emphasizing domain expertise, training SMEs, and using AI to compress cycle times and drive measurable value.
A recent McKinsey report explored what an AI operating model looks like. Here’s a graphic from that report.
The point is this type of organizational change is non-trivial and will take the better part of a decade to play out. The only firms likely fitting into the new model paradigm are startups.
Vector 2 – Hybrid architecture as the durable foundation
IBM’s hybrid message is that data lives everywhere and as such AI must be brought to the data. Resilience is IBM’s strength and single points of failure are real; so IBM’s hybrid offerings must be exceedingly reliable. The keynote connected hybrid to sovereignty and governance – and to IBM’s portfolio moves with OpenShift, the HashiCorp acquisition and Confluent (6500+ enterprise customers; 40% of the Fortune 500) to pull real-time streaming data into the AI foundation, paired with watsonx.data.
Elevance Health was the operational customer proof point; a member-facing virtual assistant that uses hundreds of data points to help members understand benefits and costs, plus provider interoperability via a data sharing layer (likely Snowflake), and agents monitoring payment integrity (fraud, waste, abuse). The common thread was modernize the data and platform foundation, then embed AI in workflows with governance baked in from ideation through deployment.
Vector 3 – Quantum frontier – Faster than most expect
IBM pushed back on both ends of the conventional wisdom spectrum, from “quantum is sci-fi” to “quantum is oversold” – arguing it has moved from science to engineering. In his keynote, Krishna asserted quantum advantage is approaching quickly and positioned quantum and AI as complements – i.e. quantum helps uncover what AI can’t compute, and AI accelerates progress on algorithms and workflows. Cleveland Clinic was the customer example, with quantum-enabled work on biomedical discovery and simulation at scale, framed as a significant change for understanding biology and therapeutics.
The AI “building blocks” IBM wants to be known for
Krisha gave a nod to a few of IBM’s product announcements that were positioned as enablers of the operating model shift:
- IBM Bob is a full lifecycle developer platform (not just code assist) – planning through deployment – used internally at scale at IBM, tied to measurable productivity and delivery improvements;
- Sovereign Core is IBM’s answer to sovereignty that “holds at runtime” as regulations and geopolitics shift;
- Concert (public preview) is an AI-powered coordination layer as systems get more embedded and complex, shifting from monitoring to coordinated response.
The missing layer – End-to-end integration and an ontology-driven data harmonization story IBM can own
We believe IBM’s opportunity is to turn “AI-first + hybrid + governance” into a single, end-to-end story that closes the gap between AI ambition and operational execution. The keynote narrative pointed at the real barriers, including siloed data, fragmented infrastructure, and “multiple clouds with no coherent operating models” – and it made the claim that “the models don’t really matter unless a foundation is correct.” The missing piece in our view is a Palantir-like harmonization layer that sits above systems of record and above the modern data platform, harmonizes meaning across domains, and becomes the “system of intelligence” feed trusted data to agents that can operate in a governed and safe manner. In plain terms, enterprises need a way to reconcile disparate data into a usable, policy-controlled representation of the business – not another pile of connectors pulled into a data store.
IBM has the ingredients to credibly own that layer, but it has to be articulated as a productized integration story, not a collection of parts:
- Real-time + governed data foundation – The Confluent deal brings “real time streaming data into our data foundation,” and the keynote made the point that AI agents are only going to be as good as the data they can access. That sets up an integration narrative where watsonx.data plus Kafka-class streaming becomes the data supply chain for agents.
- A semantics/ontology layer with governance baked in – The market need in our view is to map and harmonize entities, policies, and processes across apps, clouds, and edge (metadata, underlying application logic and process data). The keynote leaned into the right data architecture, the right governance and the right integration as the key advantage for IBM. The next step in our view is to call out an explicit harmonization layer that can support an enterprise-wide system of intelligence (ontology + lineage + policy + identity) so agents can act with auditability versus retrieving answers.
- Hybrid as the operating architecture is not a compromise – The keynote line that “Hybrid is not a compromise… it allows you to move fast without creating new fragility” is a key value prop IBM is putting forth. The missing piece is to connect that to a concrete end-to-end integration path – e.g. how Red Hat OpenShift + data foundation + ontology/policy layer + agent tooling become one operating model that customers can standardize on.
With its key pieces of the stack, including watsonx.data, IBM can win mindshare by positioning itself as the vendor that operationalizes AI through a governed, context-driven integration layer. It can be a practical bridge between messy enterprise data and agentic aspiration. The keynote showed components and the opportunity is to make the harmonization layer an explicit system of intelligence that delivers unique and powerful value where data, process, identity, and policy come together.
Summary
IBM’s Think 2026 keynote laid out a coherent three-part premise including: 1) An AI-first operating model change; 2) Hybrid as a durable architecture; and 3) Quantum as an engineering timeline, not a science project. The keynote thread was that AI value doesn’t show up at scale until organizations stop treating it as a separate thing – and start treating it as the core of a firm’s operating model. IBM is aiming to be the day zero to scaled deployment partner for enterprises that want to move fast without losing control.
Action Item: CIOs should pick one cross-functional workflow that can deliver substantial value to the business (not a RAG-based chatbot) and run a 60–90 day integration-first sprint to prove you can harmonize data, policy, and execution across systems. The deliverable is an operating capability with a shared data and ontology layer that standardizes entities, permissions, and process context so AI can act safely and repeatably.
Measure success in two ways including: 1) Time-to-outcome improvement (cycle time or cost reduction) and 2) The percentage of the workflow that can run end-to-end with auditability. It’s likely you’ll discover the capabilities to accomplish this are lacking, but it will expose the gaps in your AI tech stack that you can partner with firms like IBM to close.
