[{"data":1,"prerenderedAt":23},["ShallowReactive",2],{"dbop:article:why-ai-pilots-stall-at-business-units":3},{"id":4,"category":5,"title":6,"slug":7,"cover":8,"summary":9,"author":10,"source":11,"tags":12,"publishedAt":16,"isTop":17,"views":18,"eventStartAt":18,"eventEndAt":18,"eventLocation":8,"eventSignupUrl":8,"updatedAt":19,"content":20,"seoTitle":21,"seoDescription":22},2,"insight","AI 试点做了不少，为什么落到业务单元就断档","why-ai-pilots-stall-at-business-units","","企业的 AI 试点多半停在技术验证，真正的断点在业务单元：谁来改流程、谁来担指标、谁来验收成效。本文从三个断档位置谈起。","学院研究组","DBOP 行业洞察",[13,14,15],"AI 落地","业务单元","组织能力",1787187600,false,0,1788811489,"\u003Cp>过去两年，我们在与企业交流中反复看到同一个形态：技术侧的 AI 试点跑得很顺，模型指标漂亮，演示会开得热闹；但把它交到某个业务单元手上，就再没有下文。\u003C\u002Fp>\u003Ch3>断档一：没有人为业务指标负责\u003C\u002Fh3>\u003Cp>试点归数字化部门，指标归业务部门。模型上线之后没人回答「这个月的库存周转到底动了没有」。\u003C\u002Fp>\u003Ch3>断档二：流程没有跟着改\u003C\u002Fh3>\u003Cp>AI 给出的建议进不了既有审批流，只能靠人另开一个表格手工搬运，两周后就没人再打开它。\u003C\u002Fp>\u003Ch3>断档三：能力没有沉淀到岗位\u003C\u002Fh3>\u003Cp>试点期间靠外部顾问，顾问一走能力也走了。这正是 DBOP 认证按 L1 从业级 \u002F L2 专业级 \u002F L3 专家级分层度量的原因——能力要落在岗位上，而不是落在项目上。\u003C\u002Fp>","AI 试点为什么落到业务单元就断档 | DBOP 行业洞察","企业 AI 试点停在技术验证的三个断点：没人为业务指标负责、流程没跟着改、能力没沉淀到岗位。",1788942341124]