Transcripts
AI Enablement Roadmap
We’re already using generative AI to summarize documents, work through spreadsheets, and move faster every day. The problem is that much of it is happening off to the side, where controls drift, definitions stop lining up, ownership gets fuzzy, and good ideas never make it past the experiment stage.
At the same time, data is scattered everywhere, and we need a way to keep moving fast without everything becoming messy. The question becomes how we embrace how people are already using AI while still turning that activity into operational intelligence the business can actually use.
That shift only works when cloud, data, analytics, and AI are treated as one connected approach. It starts with a secure cloud foundation that establishes clear access, visible data flows, shared services, and governance from day one.
On top of that is the stitching layer that connects cloud, internal systems, and third-party tools. It creates repeatable patterns so we can scale up, scale down, build, or buy without constantly reworking everything.
We don’t always need to replace the chat tools people are already using. We just need to put structure around them so the work becomes visible, governed, and reusable.
That usually happens in three steps: first we capture the chats, prompts, replies, and files into managed storage. Then we move into workspaces where activity becomes structured and reusable across teams, before finally connecting into governed APIs, warehouses, and systems of record.
The goal is simple: meet people where they are and move that behavior onto trusted rails. From there, we begin bringing generative AI inside the enterprise through customized AI experiences and product-grade analytics with embedded AI.
One path helps us explore, while the other helps us execute. Both run on the same governed foundation.
As we work across broader generative AI activities, prototyping becomes how we move things forward. The workflows and prompt activity captured from generative applications also become operational insight themselves, helping improve governance, data readiness, and future AI solutions.
That changes what prototyping needs to become. We are no longer just proving something is possible — we need a real path to production.
AI helps accelerate that process by generating code, context, and insight so prototypes become more complete, not just faster. They need to validate business value, architecture, governance, ownership, and cost all at once.
They also need to span multiple use cases so we identify reusable capabilities instead of isolated solutions. That is how we move from experiments to something we can actually reuse and scale.
Once we begin identifying real capabilities, repeatable patterns start to emerge. We see document and pipeline intelligence turning documents, data, and workflow outputs into structured information and grounded natural language interaction.
Over time, those same patterns begin driving intelligence, automation, and multi-step workflows. Not uncontrolled autonomous agents, but practical, well-managed assistants embedded directly into how we operate.
We are not trying to launch a separate AI program. We are building one connected way of operating where cloud, data, governance, analytics, and AI work together.
Everything starts building on itself. Every prompt, file, and interaction adds to something instead of getting lost.
In the near term, that reduces pressure through less shadow IT, clearer ownership, stronger compliance, and faster decisions. Over time, every prototype, integration, and reporting improvement strengthens the foundation.
That is how innovation becomes repeatable, trust develops naturally, and AI becomes something that actually sticks. That is how we make it practical — not by chasing autonomy, but by building on patterns we can reuse.
The Data Enablement Strategy
Before we talk about AI, we need to talk about the foundation underneath it.
Most organizations are not struggling with access to AI. They are struggling with what AI is exposing: fragmented data, poor quality, disconnected systems, and low trust. AI did not create these problems—it magnified them at enterprise scale. Faster decisions require better information, better automation requires stronger control, and better outcomes require greater trust.
This will not be solved with the modern data stack, where vendors are pieced together to create a bloated architecture. It is solved by making the puzzle less complex through a simplified approach that brings speed, confidence, and enterprise value.
It creates clarity across six connected areas: how information moves, where it lives, whether it can be trusted, whether it can be found and understood, how business meaning is standardized, and how leaders interact with insight.
These are not separate investments. They are one connected system.
When they work together, they create a virtuous cycle. Better data creates better insight. Better insight creates better decisions. Better decisions create stronger business performance—and the need for even better insight. AI also strengthens that cycle by helping prepare data for better AI consumption.
Most organizations think AI starts with the model. It does not. It starts with how information moves.
If information is delayed, fragmented, or difficult to trust, AI simply scales the problem. What is needed is coordinated movement across operations, documents, workflows, and decisions.
Information must move reliably. It must be visible. It must be reusable so every new initiative builds on what already exists instead of starting over. This is also where AI creates immediate value—accelerating workflows, reducing manual effort, and shortening time to execution.
The goal is simple: move faster with less friction and more confidence.
Even with strong pipeline capabilities, not all information should be centralized—and in many cases, it is not practical to do so.
Some information must remain close to the teams that use it. Some lives inside operational systems, documents, and local files. Some changes too quickly or too specifically to force into one platform.
But when access becomes fragmented, definitions drift, reports stop aligning, and leadership receives conflicting answers, hesitation follows—and hesitation creates cost.
What is needed is unified access. Not necessarily a centralized platform, but one trusted channel to information. A place where both structured and unstructured information are governed consistently, security is clear, and duplication is reduced.
AI helps accelerate that foundation by defining shared business objects, generating governance and control patterns, and identifying reusable queries and request patterns that improve performance and consistency across disparate sources.
The goal is confidence in the information behind every decision.
Even with strong access, none of it matters if the information cannot be trusted.
Poor quality creates invisible costs: rework, reporting errors, missed opportunities, and operational inefficiency. At AI scale, that risk grows. Mistakes do not stay isolated—they multiply through automation.
Quality must move from cleanup to prevention. From fixing issues after the fact to identifying them before they impact the business.
This means stronger controls around completeness, consistency, and accuracy—and increasingly, using AI itself to improve quality upstream.
Because trust is not built in the presentation. It is built in the process.
Even trusted information has no value if people cannot find it or understand it.
This is where organizations lose speed. People rebuild reports, duplicate effort, and create workarounds because the right information is too difficult to access.
What is needed is clarity. Who owns this information? Where did it come from? Can it be trusted?
A strong catalog creates that visibility. It improves discoverability, lineage, context, and accountability. AI strengthens this even further, making discovery faster and governance stronger.
Even when information is available, another problem appears. Different parts of the business define success differently.
Revenue. Performance. Productivity.
The same words with different meanings.
That creates conflicting reporting and strategic misalignment.
What is needed is consistency—a shared business language.
This is what the semantic layer provides. It standardizes business definitions and simplifies underlying data models so dashboards, analytics, and AI all operate from the same understanding.
AI helps by standardizing metrics, translating technical names into business terms, and simplifying complex joins into clear semantic relationships.
That shared language creates the context LLMs need, improving accuracy, consistency, and trust.
Because the value of AI is not speed alone—it is trusted answers built on the right understanding.
Now that governance is in place, the focus shifts to visibility.
Historically, analytics meant dashboards, reports, and waiting. But business does not wait. Markets move, risk changes, and questions evolve daily.
Leaders need flexibility, not another static report.
Generative analytics changes that. It allows people to ask questions directly in natural language and receive insight grounded in trusted enterprise information—not just charts.
This drives faster decisions and stronger execution.
This is where the system compounds value.
Better insight creates better questions. Better questions improve better information. Better information strengthens the business.
AI is not replacing strategy. It is accelerating it.
Each of these capabilities matters, but the real value is how they work together.
Information moves efficiently. It lives in a governed environment. Its quality improves continuously. It is easy to find and understand. Its meaning is consistent. And it becomes instantly accessible through natural interaction.
That is the shift—from fragmented analytics to a connected intelligent system. From isolated AI use cases to a strategy that compounds value over time.
That is what a 360-degree data strategy enables.
Not just better data—but better decisions, stronger execution, and sustainable enterprise value.
And an added advantage: organizations can use AI to help get there.
Production Ready Prototyping
We’re all experimenting with AI already. For most organizations that are not building their own models, functionality is no longer the bottleneck.
The challenge is moving beyond isolated experiments and one-off prototypes into something scalable, governable, reusable, and capable of driving repeatable enterprise value. We are no longer asking whether AI can work — we are asking how to operationalize it and connect it to trusted data and workflows.
That also means prototyping has to change. Historically, prototypes proved a single use case could work, but today the challenge is proving it can work repeatedly across the enterprise in a trusted, sustainable, and production-ready way.
The real challenge is identifying capabilities that solve multiple use cases as we build. Our prototypes need to create reusable enterprise value, not isolated solutions.
We are not just trying to prove something is possible anymore. We are trying to build in a way that makes the path from exploration to production faster, cleaner, and more scalable while making the next use case easier than the last.
That is where real enterprise value starts. Generative AI creates a major opportunity because it helps us generate code, context, and insight dramatically faster than before.
AI helps generate code, services, workflows, APIs, interfaces, and automation so what once took weeks can now be explored in days. It also helps generate context by summarizing documents, explaining architecture, and aligning business and technical teams faster.
At the same time, AI helps generate insight by identifying patterns, comparing options, and surfacing stronger paths before major engineering investment is made. Together, code, context, and insight compress time and widen exploration.
The same team can evaluate far more possibilities in the same window while building toward reusable enterprise capabilities instead of isolated experiments. But speed alone creates risk.
Rapid prototyping without structure quickly becomes fast chaos. That is why every prototype needs to be anchored in real use cases, workflows, governance boundaries, and measurable business outcomes.
We are not building demos anymore. We are validating scalable enterprise capabilities and real production pathways.
That also means prototyping has to become multidimensional. Engineering, architecture, security, finance, and delivery planning all need to move together from the beginning.
A prototype should not be treated like a disposable experiment. It should be treated like a controlled slice of the future production ecosystem.
Architecture helps us scale it. Security helps us trust it, FinOps helps us sustain it, and delivery planning helps us turn today’s investment into faster progress tomorrow.
This is where capabilities become critical. A capability is not just technology or a business objective — it is the pairing of both.
It is business functionality connected to the technical abilities that make it real. Generative AI becomes especially powerful because it helps us understand not just the code, but also the architecture, relationships, and business functions behind it.
For example, document intake is the business functionality. OCR, contextualization, and governed AI workflows are the technical abilities behind it, and together they become the capability.
When we make those capability pairings explicit, product engineering and finance finally start talking about the same thing. We stop focusing only on tools and platforms and start focusing on the business capabilities we are actually building.
As delivery accelerates, understanding cost becomes just as important. If AI allows us to build faster, we also need to measure, attribute, and govern costs just as fast.
Cloud and token spend cannot become a monthly surprise. We need visibility by application, workload, document, and prototype so we understand where money is going and what value it supports.
When capabilities become the focus, every use case we implement strengthens the next. Future delivery becomes faster, cheaper, and easier while prioritization becomes less political and more effective.
Ultimately, this only works when we stitch capabilities into a shared ecosystem instead of scattered apps and isolated pilots. OCR feeds contextualization, contextualization feeds insight, insight feeds decisions, and every new experience builds on shared architecture instead of starting over.
The value is not in building more prototypes. It is in how the capabilities connect and compose.
That stitching creates the elasticity we need to explore broadly while still deepening intentionally. We can experiment widely without losing enterprise coherence.
This is where generative AI becomes so powerful. Its ability to generate code, context, and insight helps us move faster while building on shared rails instead of rebuilding everything from scratch.
That is the real opportunity. Not faster prototypes in isolation, but broader innovation with reusable capabilities, clear economics, and deliberate paths to production.
That is how AI moves from experimentation to operational intelligence. And it is how organizations move from isolated innovation to sustainable enterprise advantage.
The Stitching
Organizations have always had to make trade-offs between building and buying—custom capabilities or third-party platforms. That is not new.
What has changed is AI.
AI has dramatically increased the speed of innovation, the number of available solutions, and the demand for integration across systems right now. Build, buy, integrate, and innovate are all happening at the same time—and at a much faster pace.
But they are not happening in a coordinated way. Over time, that creates tension, complexity, and fragmentation across the enterprise.
Instead of choosing between speed and control, organizations must follow an evolutionary path. But this path is not rigid—it is elastic.
It expands as new capabilities are introduced and contracts as systems become more aligned. Organizations move from early AI usage, to structured capabilities, to fully governed enterprise integration. Each step builds on the last, strengthening the system without locking it in place.
Fortunately, AI also accelerates the journey itself—allowing organizations to start faster, evolve more quickly, and implement change with far greater precision than ever before.
But this is not a linear progression, and it is not a fixed architecture. It is a system designed to adapt—elastic enough to absorb new tools, new workflows, and new demands without breaking or fragmenting.
Because without elasticity, every new capability creates tension, and that tension leads to complexity.
Beneath this entire evolution is the cloud foundation.
It is the operational backbone where workloads run, data is governed, and access is securely managed. It defines the environment in which AI capabilities scale and remain controlled.
As adoption grows, it keeps the organization stable, secure, and aligned—allowing innovation to accelerate without creating fragmentation, risk, or technical debt.
The foundation provides the structure for sustainable growth. It creates clear boundaries between what is externally accessible and what remains securely governed.
It centralizes shared capabilities like storage, data and document processing, and access control. As the ecosystem expands, it grows within a consistent framework—not as disconnected solutions.
But structure alone is not enough.
The environment is constantly evolving. New tools, new systems, and new integrations are continuously being introduced across the enterprise. Without a consistent way to connect them, flexibility quickly becomes fragmentation.
What should enable innovation instead creates complexity, and the organization begins to lose cohesion.
This is where a critical layer emerges: the stitching.
It sits between the cloud foundation and the internal and third-party systems that power AI across the enterprise. Accelerated by GenAI’s ability to generate code, context, and insight, it is the connective layer that enables growth and adaptation without losing structure or control.
It links systems through consistent patterns and shared standards. It enables integration without constant redesign and ensures governance extends across the entire ecosystem as technology and business needs evolve.
Connection strengthens the ecosystem, but it is not enough.
Integration solves for today—not for what is still missing.
Organizations need the ability to extend capabilities, close critical gaps, and innovate on top of existing platforms. Not everything should be built, and not everything should be limited by what was bought.
The goal is strategic flexibility—the ability to build and buy as needed.
Capabilities can be layered in, evolved, and reduced over time without disrupting the broader architecture. At the same time, none of this works without strong information governance, data quality and management, unified access to data, documents, and information, supported by consistent taxonomy and information organized in business terms.
This makes enterprise systems far more effective for LLM interpretation and stronger decision-making.
Governance does not need to be perfected upfront.
The elasticity of the stitching allows it to begin early and mature over time—strengthening control and trust without slowing innovation.
That elasticity creates a virtuous cycle.
Early exploration drives real learning. That learning shapes strategy: what to standardize, what to scale, and what to govern.
That strategy improves operational processes, creating more consistent and repeatable ways of working.
Those outcomes generate new insight, which fuels the next cycle of exploration.
Over time, exploration becomes more intentional, operations become more effective, and strategy becomes more grounded.
Innovation strengthens governance, and governance accelerates innovation.
Together, the foundation and the stitching create controlled elasticity.
Organizations can evolve continuously as both business needs and technology landscapes change—without losing alignment, governance, or control.
That is what allows AI to scale as a coordinated enterprise capability, not as a collection of disconnected efforts with limited shelf life.
The AI Acceleration Toolkit
We’re already using AI, so adoption isn’t the challenge anymore. The challenge is fragmentation, isolated experiments, disconnected tools, and no clear path from innovation to enterprise impact. And we don’t have the luxury of waiting for a perfect data strategy or fully built AI engineering teams because the pace of change is only accelerating. So the real question becomes: how do we relieve the pressure before it breaks the system without disrupting the long-term strategy?
How do we move from scattered AI activity to something structured, repeatable, and scalable while using those same activities to actually strengthen the strategy over time?
We’ve realized that AI adoption isn’t a single implementation. It’s an evolution. It starts with exploration, then moves into structured workflows, integrated data, and ultimately operational intelligence. And the fastest way to accelerate that strategy is by meeting users where they already are, embracing how they’re already using familiar GenAI platforms while guiding it with governance that strengthens the organization instead of slowing it down.
Starting with a secure cloud foundation in place, we can allow AI initiatives to begin as independent exploration and discovery, giving teams the flexibility to move quickly and capture value. But we also know AI can’t evolve in isolation. It has to be intentionally coordinated and aligned to broader business strategy over time.
That’s where the stitching emerges, a flexible connective layer across AI, data, and systems built on top of the cloud foundation. It’s what allows us to turn independent innovation into cohesive enterprise intelligence.
Early in the evolution, we work in familiar GenAI platforms like Anthropic Claude and OpenAI ChatGPT. But instead of isolated conversations, every prompt, response, file, and interaction is captured with governance behind the scenes, not just for control, but to preserve discovery itself.
That creates structured, observable history with token usage, context, provenance, and a growing record of how teams explore, test, and learn. So experimentation doesn’t disappear, it compounds. Patterns can be reused, successful approaches can be repeated, and exploration becomes a sustained capability instead of a series of disconnected moments, all operating through the stitching on top of the secure cloud foundation, turning informal experimentation into continuous discovery and governable enterprise capability.
As we evolve AI across the organization, a virtuous cycle starts to emerge. Strategic alignment and governance give us visibility, turning experimentation into learning instead of isolated activity. Those learnings help us improve data, strengthen systems, and create reusable capabilities that compound over time. And the stitching allows those insights to connect and flow across the organization so every step builds on the last and accelerates enterprise intelligence.
As we evolve AI, conversations start becoming curated, collaborative workspaces instead of isolated chats. Shared prompts, datasets, and outputs create repeatable workflows that teams can reuse and build on together. The stitching allows context to flow from storage into AI and back again, keeping everything connected behind the scenes. And that’s where we start creating more bounded economics, with curated workspaces improving consistency, reuse, and token efficiency over time, turning individual exploration into collaborative enterprise capability.
As AI usage grows, we create more demand for consistent data and governed system integration. That drives the next evolution, connecting AI to enterprise tools through a single governed surface, improving coordination, consistency, and token efficiency.
Through the stitching and built on the secure cloud foundation, we move from curated workspaces to governed enterprise execution. As AI usage matures, we start learning from real data, governance, and user behavior across the organization, accelerating the strategy through practical experience instead of waiting for perfect conditions.
That maturity allows us to move toward internalized applications with embedded AI, governed data, and purpose-built experiences. Supported by the stitching and secure cloud foundation, AI becomes scalable, reusable, and the foundation for future innovation.
Generative Business Intelligence
Eventually, some organizations outgrow the governed public GenAI strategy.
It is no longer about making public GenAI safer. It becomes about asking: how do we use the insight gained from captured prompts, workspaces, and governed usage to build something more intentional inside the enterprise? And how do we do that without tearing down the data and service infrastructure built to get us here?
Some enterprises simply do not have the appetite to include public GenAI in their strategy at all. Regardless of how the enterprise got here, it must emulate the public GenAI user experience for the implementation to be valuable.
That is where Generative Business Intelligence begins—and where the evolutionary journey continues.
Generative BI must not treat a business question like a chatbot prompt. It must treat it like a managed analytic workflow.
The system plans. It runs structured steps against governed data, and it records what happened.
That includes trusted enterprise sources and the working files teams use every day—the uploaded spreadsheet, the partner extract, the reconciliation file.
This is not moving forward simply because that is what the model answered. It is repeatable, reviewable, and tied to evidence.
That is the difference between generative AI and enterprise decision-making.
To be on par with the public GenAI user experience, the architecture builds on a simple idea: people should be able to ask business questions in the words they already use.
What is driving revenue? Where is risk increasing? Why did exposure move?
The hard part is not the question. It is the answer.
Because real answers live across disparate sources—governed data, operational systems, documents, uploads, and especially the local files people rely on every day.
These local files are often the fastest path to context, even when they have not yet been fully integrated into the broader data strategy.
The business cannot wait for every source to be perfectly integrated, so the goal is one governed path from natural language, across varied sources, to answers people can actually trust.
Whether the stitching was built through the public GenAI journey or is being established now as part of Generative BI, it becomes the foundation—the governance, the semantics, and the trusted path between natural language and enterprise decisions.
Generative BI does not replace the stitching. It depends on it.
It uses the same controls, access, policy, lineage, and shared business definitions. Who is allowed to see the data? Which sources are approved? Which definitions matter? What lineage needs to be preserved?
Just as important, the same words must mean the same thing—and they must be understandable by the business.
Revenue. Risk. Exposure. Loss.
These cannot be reinvented by the assistant each time someone asks, and they cannot depend on technical table names or column labels.
The stitching provides that semantic layer: shared metrics, joins, glossary, and business definitions, so natural language does not become loose interpretation. It becomes a business-friendly path to governed logic that dramatically improves trust and dramatically improves LLM reasoning.
Because without governance and semantics, natural language feels easy—but the answers become unsafe and inconsistent.
That is how the business gets flexibility without creating chaos.
Public GenAI introduced the behavior. Generative BI operationalizes it.
It is not just a prompt window. It is a cohesive workflow to reach the answer—not simply ask and respond, but plan, execute, and refine.
That is the difference between a simple chatbot response and a managed analytic process.
Generative BI does not answer once and move on.
It works across governed data, documents, and local uploads like spreadsheets and reports, giving the business flexibility to work with what exists today—not just what was formally modeled months ago.
That means teams can adapt quickly without waiting for every source to become a formal pipeline. But everything still follows the same structured analytic flow.
The work stays governed. The logic stays traceable. And the answer stays tied to evidence. Narrative follows facts—not the other way around.
Local files can sit beside governed data without becoming a new source of truth.
Finally, the system has to be observable.
Not just what answer came back, but what ran, which sources were used, which rules applied, and what evidence supported the result.
That matters for trust. It matters for cost. And it matters for scale.
Because if hundreds of people are going to ask questions this way, the organization needs more than fast responses. It needs a record.
Generative BI creates that record so the business can move faster while staying accountable.
Generative BI allows three things to strengthen each other: clear definitions, reliable data, and the ability to ask questions naturally while still getting trusted answers.
When people know what the data means, they make better decisions.
When the data arrives consistently, those decisions move faster.
And when better questions are asked, gaps in definitions and quality become visible.
That creates the virtuous cycle—continuously improving the data, improving the decisions, and improving the business over time.