思想领袖
AI试点之外：将客户数据转化为规模化的个性化商业
在 Google 上的首选来源中添加 Unite.AI
企业对AI的热情超过了企业的成果。 斯坦福的2026年AI指数报告，88%的组织在2025年使用AI，然而AI agents的通过却停留在几乎每个业务职能的单个数字中。 实验与价值之间的距离仍然很大，在客户经验中非常明显和具体。 在试图理解为何存在这一差距时，有两个关键问题需要考虑。
首先是AI的组织成熟。 多数公司仍处于“个人生产力”阶段，努力建立治理的可扩展基础、数据准备状态和已证实的使用案例组合。 在进入“自主”阶段之前，他们还有很长的路要走，AI agents可以在固定的护栏内运作，人们专注于监督和例外处理。 达到人工智能成熟的这一阶段是尝试“人工智能本土操作模式”的基础。 以后再谈这个
第二是数据与AI主导的业务决策之间的业务差距。 大多数组织在数据和系统方面已有投资。 他们积累了客户数据、采用营销自动化、迁移到云层，即使如此，客户仍然满足了无关的建议，断开频道，服务互动忽略了企业已经知道的。
这很少是一个模型问题。 更经常的是，AI只是揭露了已经破碎的东西：零散的数据、不明确的所有权、断开的工作流程、技术债务以及从未转化为可计量的使用案例的商业目标。 前进的道路并非从更大的AI倡议开始。 它从几个精心选择的客户决定开始，一个清晰的操作模式，一个可以将智能转化为行动的架构。
对于试图从孤立的飞行员转向可重复系统的领导人，少数优先事项比其他优先事项更重要。
从决定开始，不是能力
第一个问题是，“我们需要改进哪个客户的决定？航空公司希望在中断期间给乘客更好的选择。 一个零售商想帮助一个shopper选择正确的产品而不驱动回报。 银行希望服务代表解决一个复杂的问题而不在系统之间打猎每一个名字都有一个决定，一个人，一个结果，它又告诉你需要什么数据，应该如何衡量成功。 从这里开始也帮助领导人说不。 如果一个应用想法或agent请求不能与一个真正的决定和可衡量的结果挂钩，那么它就不值得优先考虑。
“利用大赦国际改进经验”的范围太广。 它产生演示，而不是操作能力。
当一个消费电子零售商新增是今天的“AI购物助理”，这意味着一个通用的聊天员，由多少人使用它来判断。 被重新设定为帮助跳跃者选择合适的笔记本电脑的决定，它的目标是更高的转换率和更少的回报率。 因此，它成为一个工具，用活谱来更好地了解shopper的需求，成功与否以销售、回报和满意度来衡量。 同样的想法，真正的结果。
将统一数据视为一种能力，而不是数据库项目。
“360度客户观点”常常被描述为数据集中的努力。 在实践中，它是关于身份、同意、所有权、质量和关键事件含义的组织协议。 浏览会话是否属于已知客户，家庭，还是匿名设备？. 哪种制度对同意具有权威性？服务互动在另一频道的表面必须有多快？没有这些答案，集中数据就会产生没有可靠性的整合的外观。 更有成效的举动是针对每个优先使用案例的共享数据合同，涵盖所需的领域和活动，其权威来源，可接受的耐久性，允许使用，以及团队对质量负责。 目标并非全部数据。 这是正确数据
一个汽车零售商想问候一个回归的在线游艇他们正在配置的准确型号。 今天，这破裂了，因为配置者，经销商CRM和金融系统各自持有不同的客户版本，并不同意一个三周前的租赁报价是否仍然有效。 重新设定为一条有明确数据规则的旅程，解决了谁拥有什么：配置器是构建的真相来源，财务数据带有明确的同意和过期，存货饲料在几分钟内刷新，所以shoper从未看到过经销商刚刚出售的汽车。 比“统一所有客户数据”简单得多
设计个性化为连续决策系统。
许多程序仍然是竞选引擎。 团队定义一段，准备内容，并发送一个时间表。 基因AI产生更多的变体，但模型保持不变。 了解背景的经验是不同的。 它观察客户当前的情况，决定可用的行动，在业务和政策限制范围内选择一个，通过正确的渠道交付，然后从反应中学习。 关键是，有时，正确的行动是标准的信息，是人类的交接，或者完全没有。 有效的个性化不是用产生的变体来衡量的。 衡量标准是该组织是否对客户作出更相关的决定，以及该组织在这样做时是否尊重客户的期望。 信任属于经验范围，而不是在事后启动的合规审查中。
银行通知客户反复检查抵押利率。 今天，一个竞选引擎在下一次预定发送时把它们扔进“首次购买者”电子邮件系列。 系统被重新设定为一个持续的决定，它读到一个瞬间：有人在中途购物，还是仅仅好奇的几个月前？不肯定，它采取限制行动，显示“想探索你能承受得起什么？” 如果他们参与，它就会学习和适应。 如果没有，它会退缩。 有时，最相关的决定是最安静的决定，这种克制是维护信任的因素。
在您加速前先修正内容和架构限制。
Generative AI可以以显著的速度创建复制品和图像，但应用到破碎内容操作中的速度只是将瓶颈从创建转移到审查和治理上。 内容营销研究所发现75%的企业营销员使用AI，但只有15%与它融合到日常工作流程中。 结构化，可重复使用的内容，意思是经批准的事实和组件可以跨渠道组装，让AI在不发明基本真理的情况下适应。 同样的学科适用于技术堆栈。 与其重新设计以“可构成”为旗号的一切，不如绘制与优先使用案例挂钩的几条路程图，找出遗留系统产生延迟或阻碍获取数据的地方，并围绕这些制约因素逐步实现现代化。 进步并非所采用技术的数量。 能够安全快速地改变顾客行程
一名零售商在撰写4万件物品的描述时指出AI. 今天，洪水的法律审查，因为声称和保修条款需要检查每一个物品。 重新定义后，定格不是一个更快的模型，而是一个受支配的来源：PIM 持有经批准的规格，声称
同样的逻辑适用于堆栈。 团队不但没有重新设定一切平台，而是将老旧的库存系统现代化，从而阻挡了实时“在你附近”的库存，使稳定的系统单独存在。 进展正在迅速改变，而不是增加工具。
将治理纳入交付和计量价值作为组合。
在已经作出难以逆向的选择之后，治理被视为最终的大门来得太晚了。 NIST AI风险管理框架等框架在一开始就塑造一个使用案例时最有用，涵盖隐私、偏见、品牌完整性、可靠性和可追溯性，控制范围可扩大至互动风险。 同时，价值很少是一个大数字。 它分布在客户结果之间，如满意度、任务完成和保留、周期和分辨率时间和再利用等业务结果、转换、成本对服务器和寿命价值等商业结果，以及错误率、投诉和超标等风险结果。 应根据基线和规模运作的全部费用净额来衡量所有费用。
一家航空公司经营AI agent处理中断。 今天，回答“我的航班推迟了吗？” 是低调的，完全自动化的。 重新预订乘客或向人发放固定金额路线以上的旅行信贷，因为打错电话费用高昂。 重新界定，价值是按重要结果衡量的：在中断期间更快的恢复，保护高价值忠诚成员的重新预订，以及密切注视投诉。 处理得好，中断会变成一个保留传单而不是失去传单的时刻，这就是真正的终身价值的胜利之处。
摩诃衍问。
创造持久价值的企业不会是进行最多实验的企业。 他们将是一个可以重复的方式连接客户需求、可信数据、管理智能、可重复使用的内容和可衡量的结果，以及诚实地知道他们在今天的曲线上的位置。 大多数组织比其试点活动表明的要落后。
AI-本土组织是一个将AI编织在它运作和竞争的每一个层面的组织。 操作模式本身不是对现有流程进行扩充，而是围绕AI设计的，以智能为核心业务能力。
因此，对于一位领导人来说，更有用的问题不再是“我们在哪里可以添加AI?” “什么样的决定可以改进，什么样的决定才能以负责任的方式扩大？”
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Thought Leaders
Beyond the AI Pilot: Turning Customer Data into Personalized Commerce That Scales
Add Unite.AI to your preferred sources on Google
Enterprise enthusiasm for AI has outrun enterprise results. Stanford’s 2026 AI Index reports that 88% of organizations used AI in 2025, yet adoption of AI agents stayed in the single digits across almost every business function. The distance between experimentation and value remains wide, and it is very visible and tangible in customer experience. There are two key points to consider when trying to understand why this gap exists.
The first is organizational maturity on AI. Most companies are still at an “individual productivity” stage, working toward building scalable foundations of governance, data readiness and a portfolio of proven use cases. They have a long way to go before they reach an “autonomous” stage where AI agents can operate within defined guardrails and people focus on oversight and exception handling. Reaching this stage of AI maturity is foundational for attempting an “AI-native operating model.” More on this later.
The second is the operational gap between data and AI-led business decisioning. Most organizations have existing investments in data and systems. They’ve accumulated customer data, adopted marketing automation, migrated to the cloud, and piloted generative AI. Even so, customers still meet irrelevant recommendations, disconnected channels, and service interactions that ignore what the business already knows about them.
This is rarely a model problem. More often, AI simply exposes what was already broken: fragmented data, unclear ownership, disconnected workflows, technical debt, and business goals that were never translated into measurable use cases. The path forward doesn’t start with a bigger AI initiative. It starts with a few well-chosen customer decisions, a clear operating model, and an architecture that can turn intelligence into action.
For leaders trying to move from isolated pilots to a repeatable system, a few priorities matter more than the rest.
Start With a Decision, Not a Capability.
The first question isn’t “where can we deploy generative AI?” It’s “which customer experience decision do we need to improve?” An airline wants to give passengers better options during a disruption. A retailer wants to help a shopper choose the right product without driving up returns. A bank wants a service rep to resolve a complex question without hunting across systems. Each of those names a decision, a person, and an outcome, which in turn tells you what data is required and how success should be measured. Starting here also helps leaders say no. If an application idea or an agent request can’t be tied to a real decision and a measurable outcome, it doesn’t deserve priority.
“Use AI to improve experience” is too broad. It produces demos, not operational capability.
When a consumer electronics retailer adds an “AI shopping assistant” today, that means a generic chatbot judged by how many people use it. Reframed as a decision helping a shopper pick the right laptop, it targets higher conversion and fewer returns. It thus becomes a tool that uses live specs to better understand the shopper’s needs, with success measured by sales, returns and satisfaction. Same idea, real outcome.
Treat Unified Data as a Capability, Not a Database Project.
A “360-degree customer view” is often described as a data-centralization effort. In practice it is an organizational agreement about identity, consent, ownership, quality, and the meaning of key events. Does a browsing session belong to a known customer, a household, or an anonymous device? Which system is authoritative on consent? How fast must a service interaction surface in another channel? Without those answers, centralizing data creates the appearance of integration without the reliability. The more productive move is a shared data contract for each priority use case, covering the required fields and events, their authoritative sources, acceptable latency, permitted uses, and the team accountable for quality. The goal isn’t all the data. It’s the right data, trustworthy at the moment a decision is made.
An auto retailer wants to greet a returning online shopper with the exact model they were configuring. Today that breaks, because the configurator, the dealer CRM, and the finance system each hold a different version of the customer and disagree on whether a three-week-old lease quote still stands. Reframed as one journey with clear data rules settles who owns what: the configurator is the source of truth for the build, the finance data carries a defined consent and expiry, and the inventory feed refreshes within minutes, so the shopper never sees a car the dealer just sold. Far simpler than “unify all customer data,” and the greeting really works.
Design Personalization as a Continuous Decision System.
Many programs are still campaign engines. Teams define a segment, prepare content, and send on a schedule. Generative AI produces more variants but leaves the model unchanged. Context-aware experience works differently. It observes the customer’s current context, determines the available actions, chooses one within business and policy constraints, delivers it through the right channel, and then learns from the response. Crucially, individualizing every interaction isn’t the aim. Sometimes the right action is a standard message, a human handoff, or nothing at all. Effective personalization isn’t measured by variants generated. It is measured by whether the organization made a more relevant decision for the customer, and by whether it respected that customer’s expectations while doing so. Trust belongs inside the experience, not in a compliance review bolted on afterward.
A bank notices a customer repeatedly checking mortgage rates. Today, a campaign engine drops them into a “first-time buyer” email series on the next scheduled send. Reframed as a continuous decision, the system reads the moment: someone rate-shopping mid-purchase, or just curious months ahead? Unsure, it takes the restrained action, showing a helpful “want to explore what you could afford?” prompt rather than a premature “get pre-approved today” push that misreads where they are. If they engage, it learns and adapts. If not, it holds back. Sometimes the most relevant decision is the quietest one, and that restraint is what preserves trust.
Fix the Content and Architecture Constraints Before You Accelerate.
Generative AI can create copy and imagery at remarkable speed, but speed applied to a broken content operation just moves the bottleneck from creation to review and governance. The Content Marketing Institute found 75% of enterprise marketers using AI, but only 15% with it integrated into daily workflows. Structured, reusable content, meaning approved facts and components that can be assembled across channels, lets AI adapt without inventing the underlying truth. The same discipline applies to the tech stack. Rather than redesigning everything under the banner of “composable,” map the few journeys tied to priority use cases, find where legacy systems create latency or block access to data, and modernize incrementally around those constraints. Progress isn’t the number of technologies adopted. It’s the ability to change a customer journey safely and quickly without redoing the same integration work each time.
A retailer points AI at writing descriptions for 40,000 items. Today, that floods legal review, because claims and warranty terms need checking on every item. Reframed, the fix isn’t a faster model but a governed source: a PIM holding approved specs, claims, and warranty language as reusable components the AI assembles from, so it adapts tone without inventing facts.
The same logic applies to the stack. Rather than re-platforming everything, the team modernizes only the aging inventory system blocking real-time “in stock near you” personalization and leaves the stable systems alone. Progress is changing a journey quickly, not adding tools.
Build Governance Into Delivery and Measure Value as a Portfolio.
Governance treated as a final gate arrives too late, after hard-to-reverse choices are already made. Frameworks like the NIST AI Risk Management Framework are most useful when they shape a use case from the start, covering privacy, bias, brand integrity, reliability, and traceability, with controls scaled to the risk of the interaction. Value, meanwhile, is rarely one big number. It is distributed across customer outcomes such as satisfaction, task completion and retention, operational outcomes such as cycle and resolution time and reuse, commercial outcomes such as conversion, cost-to-serve and lifetime value, and risk outcomes such as error rates, complaints and overrides. All of it should be measured against a baseline and net of the full cost to operate at scale.
An airline runs an AI agent to handle disruptions. Today, answering “is my flight delayed?” is low-stakes and fully automated. Rebooking a passenger or issuing travel credit above a set amount routes to a human, because a wrong call there is costly. Reframed, value is measured across the outcomes that matter: faster recovery during disruptions, rebooking that protects high-value loyalty members, and a close watch on complaints. Handled well, a disruption becomes a moment that retains a flyer rather than losing one, which is where the real lifetime value is won.
The Maturity Question.
The enterprises that create durable value won’t be the ones running the most experiments. They’ll be the ones with a repeatable way to connect customer needs, trusted data, governed intelligence, reusable content, and measurable outcomes, along with the honesty to know where they sit on that curve today. Most organizations are further back than their pilot activity suggests.
An AI-native organization is one where AI is woven into every layer of how it operates and competes. Rather than augmenting existing processes, the operating model itself is designed around AI, with intelligence as a core business capability.
So, the more useful question for a leader is no longer “where can we add AI?” It’s “which decisions can we improve, and what has to be true for that improvement to scale responsibly?”
Auto-fetched and translated by AI Atlas. All rights belong to the original author.