Loading Events
Post-Event Recap

From AI Pilots to Production

Building a hybrid cloud foundation for enterprise AI with HPE GreenLake.

Executive summary

What leaders discussed

The path from AI experimentation to repeatable business value depends on operational discipline, workload-aware infrastructure, trusted context, and continuous governance.

Enterprise AI initiatives often stall between proof of concept and production because organizations underestimate the operational work required to scale them. The discussion highlighted several recurring barriers: unclear problem statements, inflated ROI expectations, insufficient reliability engineering, fragmented data, weak observability, and governance processes that are introduced too late. Successful programs begin with a measurable business problem and move through controlled release stages that allow teams to test quality, performance, risk, and adoption before expanding access.

AI infrastructure decisions are also becoming more workload-specific. Public cloud, private cloud, on-premises systems, and edge environments each play a role depending on data sensitivity, latency, scale, capacity, and economics. Leaders emphasized that the model itself is only one part of the architecture. Reliable AI depends equally on trusted enterprise data, the application or agent framework surrounding the model, and continuous monitoring after deployment.

The broader takeaway is that AI must be managed as a living production capability, not a one-time implementation. Models drift, business conditions change, costs grow, and employee behavior evolves. Organizations that combine executive sponsorship, workforce education, responsible governance, and strong contextual data will be better positioned to move beyond experimentation and deliver repeatable business value.

Moderator & panel

Perspectives from the room

Technology leaders examined how enterprises can move AI into production while balancing reliability, data, governance, infrastructure, economics, and workforce adoption.

Headshot of Kyle Lindquist
Moderator

Kyle Lindquist

Sales Director, PC AI

HPE
Headshot of Vijay Narayanan
Panelist

Vijay Narayanan

Engineering Leader – VP

U.S. Bank
Headshot of Elias Alagna
Panelist

Elias Alagna

Chief Technologist

HPE
Headshot of Tarik Hammadou
Panelist

Tarik Hammadou

Director, Developer Relations, AI for Retail & CPG

NVIDIA
Headshot of Hagay Lupesko
Panelist

Hagay Lupesko

Senior Vice President, AI Inference

Cerebras Systems

Organizations represented

A cross-industry peer group

Leaders from 29 organizations joined the conversation, bringing perspectives from financial services, technology, healthcare, higher education, transportation, and the public sector.

SAP
Altera Corporation
First Citizens Bank
Sycomp
Robert Half
LinkedIn
eBay
Coupang
U.S. Bank
Synopsys
Zscaler
Cohesity
Wells Fargo
Roche
SFO
Rivian
Microsoft
DoorDash
Stanford University
Uber
Ericsson, Inc.
Neyon
Nokia
County of Santa Clara
Meta
Rubrik
Airbnb
Snap Inc.
Majesta

Key themes

What shapes production-ready AI

The conversation consistently returned to five requirements for moving beyond isolated pilots and building AI capabilities that can be trusted, operated, and expanded.

01 / OUTCOMES

Clear Business Problems Drive Production Success

AI initiatives are more likely to scale when they begin with a measurable operational or financial problem rather than a general mandate to use AI.

02 / RELIABILITY

Production AI Requires Reliability and Observability

Teams need release gates, service-level expectations, monitoring, recovery plans, and ongoing quality evaluation before expanding access.

03 / INFRASTRUCTURE

Hybrid Infrastructure Is Becoming the Default

Workload placement increasingly depends on latency, data sensitivity, compute capacity, security, and long-term economics.

04 / CONTEXT

Context and Data Matter More Than Model Size

Enterprise agents need access to trusted documentation, operational knowledge, data models, and current business context to perform reliably.

05 / ADOPTION

AI Adoption Is a Workforce and Governance Challenge

Executive sponsorship, employee training, embedded technical support, and responsible AI frameworks are essential to sustained adoption.

Actionable takeaways

What enterprise leaders can do next

These actions translate the discussion into practical decisions for business, technology, data, risk, and operations teams.

Start with a measurable problem statement

Tie each initiative to a defined business outcome such as inventory reduction, faster customer service, improved branch experience, lower operational cost, or reduced risk.

Use staged production releases

Move from limited private previews to broader testing and then general availability as reliability, adoption, and controls improve.

Calculate the full lifecycle cost

Include infrastructure, model usage, engineering support, monitoring, upgrades, drift management, and retraining when estimating ROI.

Choose the simplest appropriate technology

Not every workflow requires an autonomous agent or frontier model. Consider traditional automation, classical machine learning, or smaller models where they can produce the required outcome.

Measure impact instead of activity

Focus on faster feature delivery, fewer incidents, improved customer outcomes, reduced risk, and financial value rather than lines of code, prompts, or tool logins.

Design observability into the architecture

Track latency, errors, usage, cost, output quality, user satisfaction, and model behavior continuously after deployment.

Build model and cost constraints into agent workflows

Define budget limits, stopping conditions, escalation rules, and outcome targets so multi-agent systems do not operate indefinitely or unpredictably.

Place workloads according to business requirements

Run latency-sensitive workloads near the data source, protect sensitive data appropriately, and use cloud elasticity where flexibility matters most.

Create a trusted contextual data layer

Give agents controlled, read-only access to current documentation, runbooks, repositories, operational systems, and enterprise knowledge sources.

Plan for model and process drift

Reassess deployed systems regularly as users, data, models, regulations, and business requirements change.

Provide role-specific AI education

Train employees on how to use approved tools, choose models, control costs, evaluate outputs, and recognize where human review is required.

Embed technical expertise within business teams

Use centers of excellence or forward-deployed engineers to connect operational knowledge with AI architecture and implementation skills.

Establish responsible AI review early

Define ethics, privacy, security, and human oversight requirements before development rather than introducing them after the solution is built.

Event moments

Inside the conversation

The evening combined a moderated panel with candid peer discussion, giving attendees space to compare strategies, challenges, and operating realities.

Leaders gathered for a private executive dinner and peer exchange.
Leaders gathered for a private executive dinner and peer exchange.
Peer discussion continued around the dinner tables.
Peer discussion continued around the dinner tables.
The panel explored the operational realities of production AI.
The panel explored the operational realities of production AI.
Attendees brought practical questions from their own environments.
Attendees brought practical questions from their own environments.
The format encouraged candid, participant-led conversation.
The format encouraged candid, participant-led conversation.
HPE GreenLake welcomed leaders from across the technology ecosystem.
HPE GreenLake welcomed leaders from across the technology ecosystem.