AI Agents Beyond the Hype: Lessons from Enterprise Deployments With JP Morgan & Chase

AI Agents Beyond the Hype: Lessons from Enterprise Deployments With JP Morgan & Chase — Ai4

Ai4

AI-assisted summary of AI Agents Beyond the Hype: Lessons from Enterprise Deployments With JP Morgan & Chase — original source. Check the original for full context.

Source published:

Detailed notes

## Background This talk was delivered by Koosha Golmohammadi (Global Head of Applied AI/ML - Corporate Tech at JP Morgan & Chase) and published on YouTube by Ai4 on August 15, 2026. According to the video description, the session explores practical lessons and strategies for transitioning AI agents from compelling prototypes to reliable, business-aligned, enterprise-scale deployments in complex, regulated environments.

## TL;DR The presentation examines why promising AI agent prototypes often fail in production and highlights why full autonomy should not be the primary goal for enterprise deployment. It addresses key topics such as defining capability frontiers, establishing concrete business KPIs, and managing human-AI collaboration dynamics. Additionally, the talk outlines production architecture layers, critical security vulnerabilities like prompt injection and excessive agency, and a governance framework mapping risk against observability to guide safe enterprise adoption.

## Atmosphere & style The session carries an authoritative, pragmatic, and highly analytical tone, reflecting the perspective of a seasoned practitioner in a highly regulated enterprise setting. Rather than leaning into futuristic hype, the presentation feels grounded, structured, and realistic, using visual matrices and field studies to systematically dismantle common misconceptions about AI autonomy. It maintains a disciplined, strategic, and advisory mood throughout, emphasizing caution, rigorous control, and verifiable business value over unbridled technological optimism.

## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=4s) The Spectrum of Agentic AI and the Fallacy of Full Autonomy

The conversation around Agentic AI spans a wide spectrum within enterprises and research. At one end of the spectrum, agentic capabilities function simply as minor features within an application—such as a user pressing a button to trigger an LLM-driven entity extraction, tagging, or summarization task. Moving further along the spectrum, agentic AI encompasses complex workflow orchestration, where multiple models and specialized capabilities coordinate to complete an overarching task. At the far end of the spectrum lies full autonomy, where the AI system makes decisions independently. Extreme examples of full autonomy include executing financial decisions, such as automatically issuing a credit loan via a background agentic architecture.

Organizations must clearly define where on this spectrum they intend to operate. A foundational thesis for enterprise deployment is that full autonomy should not be the ultimate goal.

``` +---------------------------------------------------------------+ | Spectrum of Agentic AI | +-------------------------------+---------------+---------------+ | Feature Level | Workflow | Full Autonomy | | (Summaries, Tagging, Entities)| Orchestration | (Independent | | | (Multi-model) | Decisions) | +-------------------------------+---------------+---------------+ ```

[02:10](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=130s) Enterprise Value, KPIs, and the Frontier of Capability

The most significant business value and impact from agentic applications are realized when they are directly embedded into business workflows. Effective deployments grant agents explicit tool access, memory, and stringent permission and access controls defining which databases and tools they can query. Furthermore, enterprises must establish clear KPIs to measure the value generated by these solutions. Rather than relying on vague or imaginary targets—such as a broad desire for "improved customer experience" that is difficult to translate into a concrete dollar value—KPIs should be derived directly from existing business metrics. Concrete examples include reducing wait times or increasing automated incident resolution in customer support operations.

When evaluating potential applications, organizations must recognize the distinction between tasks inside and outside the "frontier" of capability. This frontier is defined by the combined capabilities of the agentic solution and the underlying frontier LLM. Pushing an agentic system to handle tasks outside its frontier causes performance and quality metrics to degrade significantly.

``` +---------------------------------------------------------------+ | Capability Frontier | +-------------------------------+-------------------------------+ | Inside Frontier | Outside Frontier | | - Defined workflows | - Overly complex reasoning | | - High-quality outcomes | - Performance degrades | | - Measurable business KPIs | - Quality drops | +-------------------------------+-------------------------------+ ```

- A Harvard and Boston Consulting Group (BCG) study demonstrates that forcing agentic systems into tasks beyond their frontier results in worse performance. - A Procter & Gamble (P&G) field study revealed that a full-time employee (FTE) utilizing AI was, on average, more effective than two FTEs combined. - Working with AI reduced the burden of inter-team communication in the P&G study while improving output quality and overall well-roundedness.

[05:46](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=346s) Human-AI Collaboration and Optimal Division of Labor

Adding a human to an LLM or agentic workflow does not automatically guarantee better outcomes. In certain scenarios, an end-to-end automated AI process or an entirely human-driven process yields higher quality and better results than a joint human-plus-AI approach. The effectiveness of human-AI collaboration depends heavily on the specific nature of the task:

- **Creation & Segmentation:** Scenarios such as customer segmentation based on internal metrics work exceptionally well when combining human oversight with AI execution. - **Deepfake Identification:** AI acting alone outperforms human-plus-AI teams when detecting deepfakes in video media. - **Financial Analysis:** Unassisted human analysis can outperform a human-plus-AI team. When analyzing mixed financial data (documents, spreadsheets, and text), LLMs often miss non-numerical signals found in text analyses or interviews. Humans relying on these incomplete AI outputs frequently produce lower-quality or incorrect results.

Humans should be deployed specifically where judgment, explicit exception handling, and accountability are required. Human oversight ensures ownership over final decisions in high-stakes scenarios where business trust is paramount.

[08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) Architecture of Production Agentic Systems

A successful production-grade architecture for enterprise agentic AI requires significantly more structure than a simple model paired with a basic prompt loop. A real-world example of scalable deployment is Thomson Reuters' CoCounsel, an agentic legal platform utilized across more than 100 countries by over one million users. Robust enterprise systems integrate three primary structural components:

``` +---------------------------------------------------------------+ | Enterprise Agentic AI Architecture | +---------------------------------------------------------------+ | Oversight & Quality Control | | (Auditability, Action Tracing) | +-------------------------------+-------------------------------+ | Context & Data Layer | Core Engine Layer | | (Customer/Business Data) | (LLMs & Multi-Agent Loops) | +-------------------------------+-------------------------------+ ```

1. **Context & Data Layer:** Feeds enterprise and customer data into the active workflow. 2. **Core Engine Layer:** Houses the underlying LLMs and multi-agent orchestration logic. 3. **Oversight & Quality Control Stack:** Sits on top of the system to log, audit, and trace every decision and step taken by the agents.

[10:09](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=609s) Failure Patterns: Output Quality and Production Adoption Gaps

Despite widespread industry interest, many agentic AI projects fail in enterprise settings, primarily due to inconsistent output quality. In highly regulated sectors like law and finance, "good enough" performance is unacceptable. As noted in industry discussions, "if you are incorrect 20% of the times, you are useless 100% of the times."

While executive surveys frequently report high rates of agentic AI usage (with roughly 50% of executives claiming adoption), in-depth research from McKinsey indicates that true enterprise-scale integration remains significantly lower than reported. This disparity highlights a gap between superficial testing and deep operational deployment.

[12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) Security Risks in Agentic Systems

As system agency increases, security risks compound exponentially because the outputs of one module serve as the inputs for downstream modules. Four major security vulnerabilities impact agentic deployments:

- **Prompt Injection:** An agent processing an email inbox could be tricked by a malicious incoming email into searching internal systems and leaking confidential information in its response. - **Insecure Outputs:** Errors or sensitive data leaked by one agent propagate through subsequent modules in a multi-agent system, amplifying the compromise. - **Insecure Plugins:** Unvetted third-party plugins used to extend agent capabilities introduce security flaws that propagate across the entire application. - **Excessive Agency:** Granting agents broader permissions than necessary elevates operational and security risks across the enterprise.

[14:24](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=864s) Governance, Permission Frameworks, and Risk Mapping

To mitigate security and operational risks, organizations should adhere to the principle that "every degree of agency needs to be earned by that solution." Systems must start from a baseline of least privilege, incorporating explicit governance rules, specific tool access controls, and deep integration into existing business workflows.

Agentic applications can be categorized by their level of permission and risk:

1. **Read-Only Agents:** Search and research tools for legal, sales, or support staff that present minimal risk. 2. **Reversible Action Agents:** Systems that draft documents or perform preliminary tasks without executing final actions (e.g., without issuing loans or making binding investment decisions). 3. **High-Agency Systems:** High-risk systems capable of executing unmonitored, autonomous actions.

``` +---------------------------------------------------------------+ | Observability vs. Risk Matrix | +-------------------------------+-------------------------------+ | High Risk / High Observability| High Risk / Low Observability | | (Apply Guardrails & Control) | (STAY AWAY - DO NOT DEPLOY) | +-------------------------------+-------------------------------+ | Low Risk / High Observability | Low Risk / Low Observability | | (Target Production Zone) | (Low Value - Deprioritize) | +-------------------------------+-------------------------------+ ```

Deployments should evaluate project viability by balancing risk against verifiability and observability:

- **Low Risk / High Observability (Target Zone):** Ideal candidate use cases for enterprise deployment. - **High Risk / High Observability:** Viable only if governance metrics are strengthened and strict guardrails are applied. - **Low Risk / Low Observability:** Typically low-value cases that should be deprioritized. - **High Risk / Low Observability (Red Zone):** High-risk applications lacking step-by-step tracing must be completely avoided.

Ultimately, enterprise success depends on establishing governability, discipline, and verifiable controls rather than pursuing full autonomy for its own sake.

## Video description Koosha Golmohammadi - Global Head of Applied AI/ML - Corporate Tech (Compliance and Risk), JP Morgan & Chase

AI agent demos can be compelling and inexpensive to build, but deploying agents reliably at enterprise scale is far more difficult. I will share practical lessons from implementing agent-based AI systems in highly regulated and operationally complex environments.

The talk will examine why promising prototypes often struggle in production and how data quality, orchestration, workflow design, human oversight, governance, and uncertainty management determine success. The session will offer a strategic perspective on selecting the right opportunities, anticipating common barriers to production, and assessing value beyond technical performance. It is designed for AI leaders and practitioners navigating the transition from compelling demonstrations to scalable, reliable, and business-aligned AI agent deployments.

[Source](https://www.youtube.com/watch?v=V7e7JDgTnm0)

中文简报

走出AI Agent炒作:摩根大通企业级落地的经验启示 本演讲深入探讨了极具前景的AI Agent原型为何往往在生产环境中受挫,并强调完全自主不应成为企业级部署的首要目标。内容涵盖了界定能力边界、确立具体业务KPI以及管理人机协作动态等核心议题。此外,演讲还概述了生产级架构分层、提示词注入与过度授权等关键安全漏洞,并提出了一套将风险与可观测性相映射的治理框架,以指导企业实现安全稳健的落地应用。 企业级 Agentic AI 落地不应将完全自主作为终极目标,业务价值的关键在于将 Agent 嵌入既有工作流,并通过可量化的现有业务指标(KPI)来衡量成效,而非追求模糊体验。 (0:04) 人机协同并非在所有场景下都能产生最优解:AI 单独识别 Deepfake 效果优于人机协作,而在混合财务分析中,过度依赖遗漏关键文本信号的 LLM 反而会导致人类决策质量下降。 (5:46) 生产级 Agent 系统需具备数据上下文层、核心引擎层与全链路审计监控层,尤其在金融等高合规领域,因输出质量不稳定导致的“错误率 20%”往往会使系统整体失去可用价值。 (8:38) 随着 Agent 自主权提升,提示词注入、不安全输出传播、漏洞插件与过度授权等安全风险呈指数放大;企业应践行“自主权需按需争取”原则,从只读与可逆操作切入并严格避开高风险低可观测性场景。 (12:19)

Reading summary

Full autonomy is a flawed objective for enterprise agentic AI; sustainable business value relies on integrating models into existing workflows, defining clear boundaries within capability frontiers, and enforcing stringent governance. Autonomy Limits and the Capability Frontier (0:04) Agentic AI spans a spectrum ranging from basic application features (such as entity extraction or summarization) to multi-model workflow orchestration and independent decision-making. Operating under the thesis that full autonomy should not be the end goal, organizations see the strongest returns when embedding agents into workflows governed by clear tool access, memory, and permissions. Deployment value must be tied to established business metrics—such as reduced customer wait times or higher automated incident resolution—rather than ambiguous targets like general customer experience. Enterprise tasks must stay within the system's "capability frontier," defined by the combined limits of the agent architecture and underlying foundation models. A joint Harvard and Boston Consulting Group (BCG) study showed that pushing agentic systems beyond this frontier sharply degrades output quality. Conversely, keeping tasks within bounds yields notable productivity gains; a Procter & Gamble (P&G) field study found that a single full-time employee using AI outperformed two employees combined, while also lowering inter-team communication friction and improving output quality. Selective Division of Labor in Human-AI Teams (5:46) Adding a human into an AI workflow does not inherently improve accuracy. Effective human-AI division of labor varies significantly by task type. While human oversight paired with AI execution works effectively for creative tasks like customer segmentation, other domains perform better without joint interaction. In deepfake detection, AI models operating independently outperform mixed human-AI teams. In contrast, unassisted human analysis outperforms human-plus-AI setups when reviewing complex financial data across documents, spreadsheets, and text. In financial contexts, LLMs frequently miss qualitative, non-numerical cues found in text or interview transcripts, leading humans who rely on these incomplete AI summaries to produce lower-quality conclusions. Consequently, human involvement should be targeted specifically toward areas requiring explicit exception handling, judgment, and high-stakes accountability. Production Architecture and the Enterprise Adoption Gap (8:38) Production-grade enterprise agents require more than simple prompt loops. Proven deployments, such as Thomson Reuters' CoCounsel platform serving over one million users across 100 countries, depend on a three-tier architecture: a Context and Data Layer to ingest enterprise information, a Core Engine Layer for model orchestration, and an Oversight and Quality Control Stack to audit and trace agent decisions. Architectural rigor is essential because enterprise tolerance for error is minimal, particularly in legal and financial contexts where an error rate of 20% can render an application unusable. This reliability hurdle explains the persistent adoption gap: while approximately 50% of executives report adopting agentic AI in surveys, research from McKinsey reveals that actual enterprise-scale integration remains considerably lower, exposing widespread friction between surface-level experimentation and deep production deployment. Compounding Security Risks and Tiered Governance (12:19) Because outputs from one agent module serve as inputs to downstream components, security vulnerabilities multiply as agency expands. Primary threats include prompt injection via untrusted inputs (such as malicious emails triggering unauthorized data exfiltration), insecure output propagation, unvetted third-party plugins, and excessive permissions granted to the agent. To counter these threats, enterprises must enforce the principle that every degree of agency must be earned, beginning with least privilege. Frameworks categorize systems across three risk tiers: Read-Only agents (research and search tools), Reversible Action agents (preliminary drafting without binding execution), and High-Agency systems (autonomous, unmonitored execution). Viability is determined via a risk-observability matrix: organizations should focus deployments on low-risk, highly observable workflows, apply strict guardrails to high-risk observable use cases, and entirely avoid high-risk systems that lack step-by-step tracing. Enterprise viability for agentic AI hinges on verifiable auditability, disciplined permission models, and targeted workflow placement rather than pursuing unconstrained autonomy.

精炼阅读摘要

行业专家在本次讨论中指出,企业部署智能体人工智能(Agentic AI)的核心不应是盲目追求完全自主性,而在于将其嵌入业务流程并锚定可量化的现有业务指标。企业必须正视智能体系统的能力边界、复合安全风险以及落地现实,通过严密的权限控制与可观测性架构稳健地获取商业回报。 摒弃完全自主与厘清能力边界 (0:04) 在企业与研究语境中,智能体人工智能横跨从基础功能(如点击触发实体抽取、摘要生成)、复杂工作流编排(多模型协同完成全局任务)到完全自主决策(如系统在后台独立决策并自动发放信贷)的光谱。讨论明确指出,追求完全自主决策对企业而言是一个误区,部署的首要命题应是找准自身在光谱中的定位,专注于高价值的工作流编排。为了衡量解决方案的实际成效,企业必须设定源自既有业务的量化KPI,例如缩短客户等待时间或提升客服自动化故障解决率,而非诉诸“改善客户体验”这类难以转化为财务价值的模糊预期。 在评估具体应用时,企业必须严格区分位于“能力边界(Capability Frontier)”之内与之外的任务,该边界由底层大语言模型与智能体方案的综合能力界定。哈佛大学与波士顿咨询公司(BCG)的研究显示,强行让智能体系统处理边界之外的任务会导致性能与输出质量大幅退化。而在能力边界之内,宝洁公司(P&G)的一项实地研究表明,一名借助AI工作的全职员工其平均产出效率超过两名员工的协同产出,在降低跨团队沟通负担的同时,显著提升了工作成果的质量与全面性。 人机协作效益视任务性质而定 (5:46) 在智能体或LLM工作流中盲目加入“人机协同(Human-in-the-loop)”并不能自动保障更优结果。研讨强调,人机协作的实际效果高度取决于任务类型,在特定场景下,端到端全自动AI或纯人工流程的表现反而胜过人机结合。例如,在视频深度伪造(Deepfake)识别任务中,独立运行的AI系统准确率优于人机混合团队;而在处理包含文档、表格与文本的多源财务分析时,无辅助的纯人工分析往往优于人机协作,因为当前的LLM容易遗漏财务文本或访谈记录中的非数值关键信号,导致依赖AI片面输出的人类分析师做出劣质或错误的结论。 相较之下,在依据内部指标开展客户分群等创造与细分任务中,人类监督与AI执行的协同展现出了极佳效果。因此,企业对人力资源的投入必须高度审慎,应将人类精确部署在需要主观价值判断、明确异常处理以及承担最终决策责任的环节。在商业信任至关重要的高风险场景中,人类介入的核心意义在于确立对最终结果的所有权与责任归属。 生产级三层架构与落地认知差距 (8:38) 构建生产级企业智能体系统需要严密的工程架构,远非简单的提示词循环(Prompt Loop)所能支撑。以在100多个国家服务超过100万用户的法律智能体平台汤森路透CoCounsel为例,健壮的企业级方案通常包含三个核心架构层:负责引入企业与客户数据的“上下文与数据层(Context & Data Layer)”、封装底层LLM和多智能体编排逻辑的“核心引擎层(Core Engine Layer)”,以及位于顶层负责记录、审查和追溯系统全部决策与操作步骤的“监督与质量控制层(Oversight & Quality Control Stack)”。 许多企业智能体项目未能成功投产,主因在于输出质量的不稳定性。在法律和金融等受强监管约束的垂直领域中,“基本可用”的容错逻辑无法立足,正如行业讨论所言:“如果系统有20%的概率出错,那么它在商业上就等于100%无用。”此外,行业内存在显著的认知差距:尽管约50%的企业高管在问卷中宣称已采用智能体AI,但麦肯锡的深入研究揭示,真正实现深度企业级规模化集成的比例远低于宣称水平,这表明表层技术试探与深度业务集成之间仍横亘着巨大的鸿沟。 安全级联扩散与权限分级治理 (12:19) 随着智能体自主性的提升,前序模块的输出直接成为下游模块的输入,导致安全隐患呈指数级级联放大。当前系统面临四大典型威胁:提示词注入(Prompt Injection,如恶意邮件诱骗处理收件箱的智能体检索内部系统并外泄机密)、不安全输出(Insecure Outputs,单点错误在多智能体系统中层层扩散)、不安全插件(Insecure Plugins,未经验证的第三方插件引入全局漏洞),以及过度授权(Excessive Agency,赋予智能体超出必需的操作权限而加剧运营风险)。 为抵御此类风险,企业应当遵循“智能体的每一度自主权都必须依靠系统表现逐步赢取(every degree of agency needs to be earned)”的治理原则,坚持最小权限基准。根据权限与风险等级,应用可划分为:风险最低的“只读智能体(Read-Only Agents)”、执行草拟但无权做出最终决定的“可逆操作智能体(Reversible Action Agents)”,以及风险极高的“高自主权系统(High-Agency Systems)”。在部署考量上,企业需依据风险与可观测性矩阵进行筛选:重点投产“低风险、高可观测性”的目标场景;对“高风险、高可观测性”场景施加严密护栏;对低价值场景降权;并坚决禁止缺乏完备追踪能力的“高风险、低可观测性”危险应用。 本场讨论的结论表明,企业落地智能体AI的关键在于摒弃全面自主化的虚名,转而聚焦于能力边界内的业务工作流、严密的三层生产架构以及基于可观测性的最小权限治理。不过,在复杂受限的商业场景中,如何彻底切断多智能体间的错误级联扩散,以及在高风险决策链路中如何长期明确人机责任边界,仍是企业规模化推广时必须持续探索的难题。

Detailed notes — zh

## Background 本内容由 Ai4 频道于 2026 年 8 月 15 日在 YouTube 平台发布,演讲者为摩根大通(JP Morgan & Chase)企业科技合规与风控应用 AI/ML 全球主管 Koosha Golmohammadi。视频围绕 AI 智能体(AI Agents)超越技术炒作、在高度监管与复杂业务环境中实现企业级规模化落地的实战经验与治理策略展开探讨。 ## TL;DR 演讲指出企业不应盲目追求智能体的完全“自治”,而应将重点放在系统与现有业务工作流的深度嵌入及可治理性上。讲者深入剖析了“能力边界法则”与人机协同的局限性,强调在强监管与高容错要求领域,输出质量缺乏一致性是导致原型走向生产失败的核心原因。同时,针对 Prompt 注入与过度代理权等安全隐患,企业必须坚持“最小权限”原则与风险-可观测性象限评估,确保智能体的每一度自主权都建立在严格的审计追踪与合规防护栏之上。 ## Atmosphere & style 整场演讲风格严谨务实、理性冷静,充满了来自金融巨头一线实战沉淀出的工程纪律与风控思维。讲者摒弃了行业中常见的激进炒作叙事,用尖锐的行业洞察和详实的多维度矩阵,直击智能体落地中的安全短板与架构难点,为技术决策者带来了一种极具清醒感与工业级厚重感的听会体验。 ## Key takeaways - [00:04](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=4s) 智能体(Agentic AI)存在从简单功能调用到全自动决策的技术光谱,但自治决策(Autonomy)绝非终极目标,盲目追求无人干预往往会脱离业务实际与合规约束。 - [02:10](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=130s) 智能体创造实际价值的前提是深度嵌入既有工作流,且业务 KPI 必须严格锚定客观可量化的财务与运营指标,而非模糊的体验类描述。 - [02:10](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=130s) 遵循能力边界(Frontier)法则:智能体方案在舒适区外强行应用会导致性能断崖式下滑,必须严格框定任务范围。 - [04:51](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=291s) “人机协同必然最优”是认知误区:如伪造检测由 AI 独立完成更准,复杂金融分析中纯人类专家反而因不受模型片面初筛误导而表现更好。 - [04:51](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=291s) 人类在智能体系统中的真正定位应聚焦于主观价值判断、极端长尾异常处理以及承担最终业务责任(Accountability)。 - [08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) 成熟的企业级生产架构必须包含端到端的监督与质检控制栈(Oversight Stack),对全流程决策链路进行追踪、合规过滤与审计。 - [08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) 原型走向生产失败的首要原因是质量一致性不足;在强监管场景下,20% 的不准确率就等同于 100% 不可用。 - [12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) 智能体扩大了安全攻击面,面临 Prompt 注入、多智能体下游输出污染、不安全插件及过度代理权四大突出风险。 - [12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) 遵循最低权限原则进行治理:系统的每一度自主权限都必须由其在稳定性与合规性上的长期可靠表现凭实力争取而来。 - [15:09](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=909s) 依据“业务风险”与“可观测性”构建二维决策矩阵:高可观测性且低风险场景为最佳切入点,高风险且黑盒(低可观测性)场景应绝对禁止进入生产。 - [15:09](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=909s) 企业在规划智能体蓝图时,应当将建设重心从盲目追求全自动“自主性”转向建立严谨的“可治理性”(Governability)与工程纪律。 ## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=4s) Agentic AI 的光谱与炒作:自治并非终极目标 在当前企业界与学术界围绕智能体(Agentic AI)的讨论中,存在着极宽的技术光谱与过度炒作的现象。在光谱的一端,智能体仅仅体现为应用程序中的某个简单功能——用户点击一个按钮,后台调用大语言模型(LLM)完成实体识别、打标签或文本摘要;在光谱的中间,是复杂的多模型工作流编排(Workflow Orchestration),系统协同调度多种能力来完成端到端任务;而在光谱的最极端一端,则是完全自主决策(Full Autonomy),例如由后台的智能体架构直接做出发放贷款或授信等金融决策。 企业在推进技术落地前,必须首先在组织内部厘清自身究竟希望切入光谱的哪一段。核心论点在于:"自治或许从来都不是终极目标"(autonomy is not the goal)。盲目追求无人干预的全自动决策,往往会忽视业务场景的实际约束与风险。 ```mermaid flowchart LR accTitle: Agentic AI Spectrum subgraph S1["低复杂度"] A["单点功能<br/>(总结/实体提取)"] end subgraph S2["中复杂度"] B["工作流编排<br/>(多模型协作)"] end subgraph S3["高风险/高复杂度"] C["完全自主决策<br/>(如信贷审批)"] end A --> B --> C ``` --- ### [02:10](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=130s) 业务价值释放与能力边界(Frontier)法则 智能体技术能够产生最大业务价值与实际影响的切入点,在于将其深度嵌入既有的业务工作流中。这要求赋予智能体特定的工具访问权限(Tool Access)、上下文记忆能力(Memory),并施加明确的数据与接口权限访问控制(Access Controls)。更为关键的是,评估智能体成效的 KPI 指标绝不能凭空捏造,必须锚定在企业已有的客观业务指标上,例如客户服务场景中的等待时间缩减、事件解决率提升或故障自动化修复率,而不是使用“改善客户体验”这类难以直接转化为财务价值的模糊概念。 哈佛商学院与波士顿咨询公司(BCG)的研究提出了“能力边界”(Frontier)的概念。每个前沿大模型与智能体方案都存在其能力边界范围内的任务与范围外的任务。研究表明,如果强行将智能体技术套用到其能力边界之外的任务中,系统的实际表现不仅无法提升,反而会急剧恶化,导致输出质量与关键指标显著下滑。 - **高价值落地要素**:工作流深度嵌入、工具调用能力、长期/短期记忆机制、基于角色的最小权限访问控制。 - **KPI 锚定原则**:必须直接挂钩可量化的财务与运营指标(如响应延迟、自动化工单解决率),拒绝不可衡量的模糊体验指标。 - **边界法则(Frontier Concept)**:严格将应用约束在模型能力的舒适区之内,强推越界应用会导致性能断崖式下跌。 --- ### [04:51](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=291s) 人机协同的迷思与人类介入的最佳定位 宝洁(P&G)的一项实地现场研究表明,在特定业务场景中,一名配备了 AI 工具的全职员工(FTE)平均综合产出可以超过两名传统员工。这一方面得益于跨团队沟通负担的减轻,另一方面也提升了产出内容的全面性与质量。然而,“只要在 LLM 链路中加入人类就能解决问题”的假设并不成立。在部分实验场景中,完全交由人类独立完成,或者完全交由 AI 独立完成,其最终质量与效果反而高于“人类 + AI”的人机协同模式。 ```mermaid flowchart TD accTitle: Collaboration Modes Performance subgraph Optimal["人机协同高效区"] A["内容共创 / 客户分群分析"] end subgraph AI_Only["AI 独立表现更优"] B["Deepfake 伪造视频检测"] end subgraph Human_Only["人类独立表现更优"] C["复杂金融综合分析<br/>(需捕捉非结构化潜台词)"] end ``` 在 Deepfake 辨识场景中,纯 AI 模型的检测准确率显著击败了人机协同;而在复杂的金融分析场景中,单兵作战的人类分析师反而胜过了人机组合。这是因为在处理包含财报、访谈记录与多源文档的复杂信息时,模型往往会过滤或忽略非结构化文本与访谈中的微妙潜台词,过度依赖模型初筛结果的人类分析师会被带偏,从而导致分析结论失真。 - **人类介入的真正定位**: - **主观价值判断(Judgment)**:处理模糊或涉及商业伦理的高阶决策。 - **显式异常处理(Explicit Exception Handling)**:接管能力边界之外的长尾极端工况。 - **最终责任归属(Accountability & Ownership)**:为最终业务结果承担兜底责任,以此维系组织与客户之间的信任。 --- ### [08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) 企业级生产架构与质量失败根因 在企业级规模成功落地的智能体架构,通常包含三个核心支柱:上下文与数据接入层(Context & Data Layer)、底层核心模型与引擎(Core LLM Engine),以及覆盖全流程的监督与质量控制栈(Oversight & Quality Control Stack)。以汤森路透旗下覆盖 100 多个国家、服务超百万用户的法律智能体 CoCounsel 为例,其成功证明了仅靠简单的“Prompt + 循环调用”无法支撑严苛的业务需求,必须对系统运行中的每一步决策链路进行端到端追踪与审计。 ```mermaid flowchart TD accTitle: Enterprise Agent Architecture subgraph ContextLayer["数据与上下文层"] D["企业内部数据 / 客户上下文 / 知识库"] end subgraph EngineLayer["核心推理引擎"] E["底层 LLM / 工具调度 / 规划器"] end subgraph OversightLayer["监督与质检控制栈"] O["决策链路追踪 (Tracing) / 安全合规过滤 / 质量验证"] end D --> E E --> OversightLayer ``` 智能体试点项目在走向生产时遭遇失败的首要原因在于“质量缺乏一致性”,且无法满足强监管要求。在法律、金融等合规严苛领域,“差强人意”(Good enough)等同于完全不可用。正如业内所言:"如果你在 20% 的情况下是不准确的,那么你在 100% 的情况下都是毫无价值的"(if you are incorrect 20% of the times, you are useless 100% of the times)。此外,麦肯锡与普华永道(PwC)、Google Cloud 等机构的调研数据形成了鲜明对比:尽管约 50% 的高管声称已经引入了智能体,但真正深入业务核心的大规模生产级部署比例依然极低。 --- ### [12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) 企业级安全风险与最低权限治理原则 随着智能体自主程度的提升,企业面临的安全攻击面呈指数级扩大。目前最为突出的四大安全风险包括: 1. **Prompt 注入(Prompt Injection)**:以监控并自动回复企业收件箱的智能体为例,恶意邮件中夹带的隐藏指令可能会诱骗智能体检索敏感内网,并在回信中外泄机密数据。 2. **不安全输出传播(Insecure Outputs)**:在多智能体流水线中,上游模块的不安全或错误输出会被下游模块直接作为输入,导致数据污染或安全漏洞在整个拓扑链条中层层放大。 3. **不安全插件(Insecure Plugins)**:智能体依赖的第三方插件难以实现全面审计,插件自身的漏洞会直接渗透进宿主系统。 4. **过度代理权(Excessive Agency)**:授予智能体超出实际业务需要的系统读写与调用权限。 企业治理的核心准则可以凝聚为一句话:"系统的每一度自主权,都必须由其稳定性与合规性凭实力争取而来"(every degree of agency needs to be earned by that solution)。构建智能体应用必须以最低权限(Least Privilege)为设计原点,先通过严格的上下文隔离与工作流绑定验证其可靠性,再逐步开放更高权限。 --- ### [15:09](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=909s) 风险与可观测性象限:从代理自主走向治理纪律 评估智能体落地场景时,可以依据业务操作的不可逆程度划分为三个等级:仅供检索调研的只读型(Read-only,适用于律师或销售调研);可生成文档或物料但未正式执行动作的可逆型(Reversible actions);以及直接进行信贷审批、投资划扣或直接面向客户履约的不可逆高风险型。 通过**可观测性/可验证性(Observability / Verifiability)**与**业务风险(Risk)**构建的二维矩阵,能够为企业的技术选型与优先级排序提供清晰的指引: | 象限分布 | 场景特征 | 应对策略 | |:--- |:--- |:--- | | **低风险 × 高可观测性(绿区)** | 决策步骤高度透明,失误业务影响小 | **理想落地切入点**,优先推进规模化部署 | | **高风险 × 高可观测性** | 业务影响重大,但具备完整的全链路决策审计能力 | **加强防护栏(Guardrails)**,严控准入指标并保留人工复核 | | **低风险 × 低可观测性** | 黑盒运作,但业务价值与潜在破坏性均有限 | **降低优先级(Deprioritize)**,投入产出比低 | | **高风险 × 低可观测性(红区)** | 黑盒运作且牵涉重大资产或合规风险 | **绝对避开(Stay away)**,禁止进入生产环境 | 企业在规划 AI 智能体蓝图时,不应盲目执着于追求全自动的“自主性”,而应将核心精力倾注在系统的“可治理性”(Governability)与工程纪律的建立上。 ## Notable quotes > [00:04](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=4s) 自治或许从来都不是终极目标 — Koosha Golmohammadi > [00:04](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=4s) autonomy is not the goal — Koosha Golmohammadi > [02:10](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=130s) 如果强行将智能体技术套用到其能力边界之外的任务中,系统的实际表现不仅无法提升,反而会急剧恶化 — Koosha Golmohammadi > [04:51](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=291s) 只要在 LLM 链路中加入人类就能解决问题 — Koosha Golmohammadi > [08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) 如果你在 20% 的情况下是不准确的,那么你在 100% 的情况下都是毫无价值的 — Koosha Golmohammadi > [08:38](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=518s) if you are incorrect 20% of the times, you are useless 100% of the times — Koosha Golmohammadi > [12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) 系统的每一度自主权,都必须由其稳定性与合规性凭实力争取而来 — Koosha Golmohammadi > [12:19](https://www.youtube.com/watch?v=V7e7JDgTnm0&t=739s) every degree of agency needs to be earned by that solution — Koosha Golmohammadi ## Mentioned Koosha Golmohammadi, JP Morgan & Chase, Harvard Business School, Boston Consulting Group (BCG), Procter & Gamble (P&G), Thomson Reuters, CoCounsel, McKinsey, PricewaterhouseCoopers (PwC), Google Cloud ## Video description Koosha Golmohammadi - Global Head of Applied AI/ML - Corporate Tech (Compliance and Risk), JP Morgan & Chase AI agent demos can be compelling and inexpensive to build, but deploying agents reliably at enterprise scale is far more difficult. I will share practical lessons from implementing agent-based AI systems in highly regulated and operationally complex environments. The talk will examine why promising prototypes often struggle in production and how data quality, orchestration, workflow design, human oversight, governance, and uncertainty management determine success. The session will offer a strategic perspective on selecting the right opportunities, anticipating common barriers to production, and assessing value beyond technical performance. It is designed for AI leaders and practitioners navigating the transition from compelling demonstrations to scalable, reliable, and business-aligned AI agent deployments. [Source](https://www.youtube.com/watch?v=V7e7JDgTnm0)

Source quotes

[0:04] Koosha Golmohammadi: 自治或许从来都不是终极目标 [0:04] Koosha Golmohammadi: autonomy is not the goal [2:10] Koosha Golmohammadi: 如果强行将智能体技术套用到其能力边界之外的任务中,系统的实际表现不仅无法提升,反而会急剧恶化 [4:51] Koosha Golmohammadi: 只要在 LLM 链路中加入人类就能解决问题 [8:38] Koosha Golmohammadi: 如果你在 20% 的情况下是不准确的,那么你在 100% 的情况下都是毫无价值的 [8:38] Koosha Golmohammadi: if you are incorrect 20% of the times, you are useless 100% of the times [12:19] Koosha Golmohammadi: 系统的每一度自主权,都必须由其稳定性与合规性凭实力争取而来 [12:19] Koosha Golmohammadi: every degree of agency needs to be earned by that solution

Original transcript

[0:04] Today I'd like to talk about uh three topics.  First uh what is the spectrum of Agentic AI, where [0:11] the hype is coming from. Um second is uh where  we see the most value and what are the uh risks. [0:23] Um and the third is what are some of the failure  patterns and mitigation approaches to get around [0:30] that ultimately is going to lead us to think about  the operating model. Now today we are not going to [0:39] unpack a full operating model. Uh but  those are uh hopefully some of the tips [0:45] uh that you can think about the operating  model. So about um the hype um when you look at [0:53] um different enterprises or if you look at  the research out there today the conversation [0:59] around agentic AI seems to be um covering a very  large spectrum from things that are a feature in [1:08] an application. You press a button, it gives  you some entities, some tagging, some summary [1:14] which is using an LLM behind the scene to serve  that capability to uh workflow um orchestration [1:23] where there are multiple capabilities, multiple  models orchestrating to accomplish a task to full [1:31] uh autonomy where the decision is at play.  Um the most extreme uh cases would be for [1:38] example taking a decision financial decision  on issuing a credit loan um using an agentic [1:45] architecture behind the scene. So wide range and  perhaps uh this is the first thing that has to be [1:53] u crystallized in the organization that  which of these u you want to be part of and [2:02] the thesis today is perhaps autonomy is  not the goal u and we will talk about it [2:10] now um where do we see u the largest value  uh and business impact. If you look at um [2:21] enterprise applications or research out  there, the biggest value is when you have [2:27] agentic applications embedded into workflows  and uh you give these agents um tool access. [2:36] uh you give them memory um and there  are explicit permission access controls [2:43] around it in terms of what databases, what  tools they can access and most importantly [2:51] the KPIs metrics that you have to measure how  these solutions are producing value. These KPIs [3:01] should not be imaginary. These KPIs should be  either coming from existing business. So the [3:07] application is for example customer support. It is  reducing the wait time. Um improving um incident [3:16] uh resolution or automated uh incident resolution.  So they have to be existing uh metrics that the [3:24] business has um and they have to be crisp. So  measures like improved customer experience. Sure [3:32] it's good but how do you translate it to  dollar value? Uh it might be difficult. [3:41] There is a concept and uh that concept is um  where we are within the frontier or outside [3:51] the frontier. That concept is tasks and  um goals, objectives, business processes [3:59] that are achievable with the capability of the  agentic solution as well as the frontier model [4:06] that you use behind the scene and there are tasks  and processes that will be outside of that. Uh so [4:14] it turns out that if you force agentic solution  in a place that is outside of that frontier [4:23] the performance is actually worse. Uh there are  some numbers some research on that. Um I think the [4:29] important point is the performance the quality  those metrics that I mentioned they will go down. [4:37] So the the point from this Harvard um  BCG business consulting group research is [4:45] to make sure that you are within  that frontier for the application. [4:51] Um there is uh other research uh from a field  study that PNG uh ran and they show that [5:02] a an a full-time employee with AI is more  effective than two FTEEs in average in aggregate [5:11] looking at their study. Now you can argue this  this could be biased uh but they show that [5:19] um within their use cases this is happening. Um  they also say uh claim that because uh when they [5:28] have one full-time employee working with um using  AI the burden of communication with other teams [5:37] reduces the quality of outputs in  terms of well-roundedness goes up. [5:46] Now should we assume that okay you just add  human uh to your LLM application or agentic [5:55] solution and the problem is solved and the answer  is no. Uh it turns out that for some experiments [6:05] actually if you lead leave it to uh a human to  do that process end to end or uh an AI to do that [6:16] process end to end. It is more effective higher  quality better outcome compared to a human and AI. [6:26] Um this is heavy on uh when you have creation use  cases. Um this is my data do customer segmentation [6:38] uh or you build this feature into an  application that data from customers come in [6:46] um and some metrics internal metrics you have you  want to do u segmentation that's an example of um [6:54] um AI and human they work well uh but on the  other side if you look at identify classify I fake [7:04] uh deep fakes from um real videos. It turns out  that AI by itself outperforms human plus AI. [7:15] Uh if you look at financial um analysis um  it turns out in some cases human by himself [7:24] outperforms a human plus AI. And the  reason sometimes for that just briefly is [7:31] uh a lot of times when you have a wide range  of data for financial analysis, documents, [7:37] spreadsheets and so on. Um some of the uh  signals that might be in text, interviews, [7:45] analyzis, not in the numerical data will  be zoned out uh by the model. So the human [7:53] uh that is relying on that output will produce  u low quality and sometimes incorrect results. [8:02] Um so where do we put uh human? Uh we put human  where we need judgment when we need explicit [8:11] exception handling. This is going back to the idea  of frontier cases um tasks goals that cannot be [8:20] accomplished uh with the uh model or agentic  solution and accountability uh for the human [8:28] to be accountable and own that final decision  uh because of the trust uh with the business. [8:38] Now if you look at um a successful um  architecture for implementing agentic AI solutions [8:46] uh in production perhaps it has these three  components. Um if you want to think about a [8:53] successful agentic AI application at an enterprise  scale perhaps you can think about examples like uh [9:03] co-consel from Thompson Reuters. um it is a  solution that is used in over a 100 countries [9:10] uh by over a million uh people. Now if you look at  that architecture uh it has different elements um [9:21] and that's the idea of like a simple uh  model with some prompting and some loop [9:28] u to accomplish a task is not enough. Um you you  have to think about how you think about context, [9:36] the data that you have for customers or your  business, how that feeds into the process. [9:42] Of course, you have an underlying core engine uh  behind the scene. You have your LLM and you have [9:49] your oversight uh quality control stack built on  top of all of this, which we will get into this a [9:57] little bit more. And the idea here is to track  everything that is happening all the decisions [10:02] that are uh made. So if we know the recipe uh  and everything that I told you probably a lot of [10:11] people know it's based on industry research. Why  is it that so many projects agentic AI projects [10:20] fail? Uh it turns out the um top factor is  quality. when you measure quality objectively [10:31] um it is not consistent and sometimes it is u  it doesn't pass the uh regulatory requirements. [10:42] So if you think about legal, if you look  think about financial uh sector, these are [10:48] uh areas that good enough doesn't work. Um it  has to be correct. The answer has to be correct. [10:57] And uh I think one of the speakers yesterday  was talking about if you are incorrect uh [11:04] 20% of the times uh you are useless 100% of the  times. And that's I think uh very true especially [11:13] for regulated environments. Um one other thing um  if you look at um the research from industry or [11:25] surveys from executives a lot of them talk about  we have agentic AI and they do have agentic AI. uh [11:33] but if you look at the depth of uh these solutions  at enterprise scale the numbers are not that [11:41] appealing uh right now so McKenzie's research is  actually kind of contradictory with PWC with some [11:50] of the Google cloud some of the other research  that is out there uh they uh argue that uh the [11:58] actual adoption at enterprise scale is much lower  than expected. So those 50% uh we have 50% of [12:08] executives saying that we are using agentic they  may not be u a fair representation of adoption. [12:19] The outside of uh quality of outputs um  the second concern big concern is security [12:29] and um this is an area that is uh there is a lot  of work uh happening in this area. Um perhaps uh [12:39] four categories of uh issues are prompt injection.  You're familiar with this. you have built an [12:45] application that is monitoring emails to an inbox.  Uh you want to um automatically respond to these [12:54] emails. There could be a malicious email that is  coming in. It is uh searching uh the email pulling [13:03] um maybe confidential um information sending  it uh in the response. That's an example of [13:09] uh prompt injection. Insecure outputs. If  you have multiple agents, as you increase [13:16] the level of agency, the level of risk goes up.  Why? Because um in different steps that you have, [13:25] the output of one component, one module is used  by one or more other uh modules. As a result, uh [13:34] when you have an incorrect or insecure output,  it includes uh some information that it is not [13:42] supposed to for the next agent, for next module,  that um issue propagates in the uh system. [13:51] Insecure plugins um u for building um and  deploying agents. Of course, people use a lot [13:58] of plugins. um it's very difficult to monitor  all of these plugins. So if the pl plugin is [14:05] has some security issue likely it's going  to prop propagate uh into your solution. [14:12] And we talked about excessive a agency as  the uh agency uh goes up um risk goes up. Now [14:24] if we wanted to think about all of the governance  ideas around governance tools around governance [14:32] I think in one sentence the idea is every degree  of urgency needs to be earned by that solution. [14:42] So the starting point is least  privilege um to build that solution [14:48] and those are some of the uh components that uh we  talked about u that you want to have a specificity [14:56] uh of course you have u governance around  your agentic solution and we talked about [15:03] workflow integration which is the baseline  that is where the most value is coming in. [15:09] So thinking about u this u autonomy and  how you can think about it um you can [15:17] think about use cases and agents in categories.  So categories where the readonly is good enough. [15:24] It's an agentic solution for research, for  your sales staff, for lawyers. It's read only. [15:31] Um reversible actions, actions that u some file,  some um documents, some material is produced [15:39] but the full action is not executed. There  is no credit or loan issued. There is no [15:46] interaction with the client or customer. there is  no investment decision that is made and the last [15:53] one is of course the highest risk where you have  the highest level of agency for your solution. [16:00] Now if we put together all of these ideas um  we talked a lot about two concepts the concepts [16:10] the concept of observability or verifiability.  How do we verify that the solution is producing [16:18] high quality uh outputs? We have security in  place. We can trace the decisions that are [16:27] made in the uh agentic solution each step  of the way to produce that final outcome. [16:34] And we talked about risk uh what is the risk of  this uh use case uh and application. Of course, [16:42] you want to be in green. You want to be low risk,  high observability. But the idea is um here there [16:50] will be use cases that might be high risk um high  uh observability. You those are the cases that you [16:58] want to bump bump up uh the governance metrics,  bring in more guard guard rails or you have [17:07] low observability, low risk. Typically  uh these are lower value uh use cases. Um [17:17] perhaps they have to be dep prioritized uh because  of the value and the red is uh where you want to [17:23] stay away uh from use cases environments where you  have the most risk and the lowest observability. [17:34] So uh with that I'd like to uh wrap up u  the idea hopefully is uh to think about [17:41] where you can bring the most discipline um and the [17:47] most um governability to the solutions rather than  focusing on autonomy for the solutions. Thank you.