Michael Emerick
Data and AI
Building a Hybrid Cloud Foundation with HPE GreenLake.
Executive summary
Operationalizing AI requires focused use cases, aligned stakeholders, governed infrastructure, disciplined economics, and continuous human feedback.
Operationalizing AI requires enterprises to move beyond technical experimentation and address the organizational conditions that determine whether a solution can scale. The discussion emphasized that many initiatives fail because teams begin with an overly broad scope, unclear success criteria, or insufficient stakeholder alignment. Effective programs start with a focused use case, involve business, technology, security, and operations teams early, and use rapid iteration to uncover performance, compliance, and infrastructure issues before wider deployment.
As AI adoption expands, cost and infrastructure decisions are becoming more strategic. Token consumption may be acceptable during an initial learning period, but production systems require visibility into usage, model selection, latency, and long-term economics. Depending on the workload, enterprises may need to balance public cloud scalability with self-hosted or on-premises capabilities that provide greater control, predictable throughput, and stronger protection for sensitive data.
The discussion also reinforced that AI cannot replace human judgment in high-risk or emotionally sensitive interactions. Customer-facing systems require clear escalation paths, controlled rollouts, and experienced users who can identify hallucinations or inappropriate responses. Organizations that combine strong governance, secure data environments, measurable outcomes, and continuous human feedback will be better positioned to move AI safely from pilot to production.
Moderator & panel
The panel examined how enterprises can align stakeholders, govern sensitive data, manage AI economics, and preserve human oversight as systems move into production.
Key themes
The conversation consistently returned to five requirements for scaling AI safely, economically, and with measurable business impact.
Many failures begin with unclear requirements or decisions that have not been communicated across the teams responsible for delivery, security, and adoption.
Regulated organizations need layered access controls, data masking, secure environments, and review processes that are built into the solution from the start.
Early experimentation may prioritize usage and learning, but production requires disciplined management of tokens, models, infrastructure, and operational costs.
AI can assist employees and improve efficiency, but humans are still needed to manage exceptions, provide empathy, validate outputs, and intervene in sensitive situations.
Successful initiatives are evaluated through time saved, customer experience, accuracy, adoption, productivity, and business impact rather than AI usage alone.
Actionable takeaways
These actions translate the discussion into practical decisions for business, technology, security, compliance, infrastructure, and operations leaders.
Avoid launching broad AI programs before the business problem, intended user, required data, and expected outcome are clearly defined.
Bring business owners, engineering, infrastructure, security, compliance, operations, and end users into the planning process early.
Establish measurable thresholds for accuracy, latency, cost, adoption, customer experience, and regulatory compliance.
Treat unsuccessful versions as learning opportunities and document why each attempt failed before moving to the next iteration.
Include different locations, customer types, authorized users, regulations, and data conditions rather than relying only on straightforward scenarios.
Begin with experienced employees or a small percentage of users, compare multiple variants, and expand only when performance and compliance targets are met.
Preserve a reliable non-AI process or previous product version so teams can pause or reverse deployment when results fall below expectations.
Define when AI should stop and transfer the interaction to a person, particularly when a customer requests assistance or the system detects uncertainty.
Use masking, automated scanning, read-only access, secure enclaves, and production-like test environments to reduce exposure.
Give teams realistic environments for scale and performance testing without exposing live customer or regulated information.
Compare the AI-enabled workflow with the current approach to determine whether it improves speed, quality, cost, or customer outcomes.
Give teams enough freedom to understand the tools and develop valuable workflows before imposing aggressive cost restrictions.
Route tasks to the right-sized model, create reusable workflows, reduce unnecessary context, and monitor token consumption by user, agent, and project.
Compare cost, performance, security, data movement, power, cooling, and operational capacity rather than assuming one environment is always preferable.
Where direct revenue is not the goal, use time savings, employee experience, service quality, and mission effectiveness as primary indicators.
Event moments
The evening combined executive networking, dinner and wine tasting, and a practical discussion about moving AI safely and economically from pilot to production.
Event sponsor
Unlock your organization’s next phase of innovation with HPE GreenLake, the edge-to-cloud platform designed for the AI era. HPE GreenLake brings cloud agility to applications and data wherever they live, combining scalable infrastructure, built-in security, and intelligent operations. With deep expertise across AI, cloud, and networking, HPE helps enterprises turn data into insight, improve performance, and operate with greater speed and control. Backed by decades of innovation, HPE GreenLake enables organizations to modernize, scale, and lead with confidence.
Learn more about HPE GreenLake ↗