[{"data":1,"prerenderedAt":426},["ShallowReactive",2],{"insight-digital-80-percent":3,"insight-related-digital-80-percent":157},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":7,"slug":9,"date":10,"duration":11,"category":12,"author":13,"tags":14,"body":18,"_type":151,"_id":152,"_source":153,"_file":154,"_stem":155,"_extension":156},"\u002Finsights\u002F09-digital-80-percent","insights",false,"","数字化的 80% 不在系统，而在组织","digital-80-percent","2025-07-04",9,"业务咨询","浩途方法论",[15,16,17],"数字化转型","组织","变革管理",{"type":19,"children":20,"toc":144},"root",[21,29,43,47,52,87,90,96,115,124,127,132],{"type":22,"tag":23,"props":24,"children":26},"element","h2",{"id":25},"引子",[27],{"type":28,"value":25},"text",{"type":22,"tag":30,"props":31,"children":32},"p",{},[33,35,41],{"type":28,"value":34},"10 年交付下来，看到太多\"系统功能没问题但用不起来\"的案例——客户预算花了、上线了、\n培训也做了，3 个月后就废弃了。问题几乎都出在",{"type":22,"tag":36,"props":37,"children":38},"strong",{},[39],{"type":28,"value":40},"组织没有为新系统做对应的调整",{"type":28,"value":42},"。",{"type":22,"tag":44,"props":45,"children":46},"hr",{},[],{"type":22,"tag":23,"props":48,"children":50},{"id":49},"数字化失败的三个组织症结",[51],{"type":28,"value":49},{"type":22,"tag":53,"props":54,"children":55},"ol",{},[56,67,77],{"type":22,"tag":57,"props":58,"children":59},"li",{},[60,65],{"type":22,"tag":36,"props":61,"children":62},{},[63],{"type":28,"value":64},"责任未重分配",{"type":28,"value":66},"：流程换了但 KPI 没换，员工继续按老 KPI 干活",{"type":22,"tag":57,"props":68,"children":69},{},[70,75],{"type":22,"tag":36,"props":71,"children":72},{},[73],{"type":28,"value":74},"数据未透明",{"type":28,"value":76},"：上级不愿放下\"信息差\"权力，系统再透明也被绕开",{"type":22,"tag":57,"props":78,"children":79},{},[80,85],{"type":22,"tag":36,"props":81,"children":82},{},[83],{"type":28,"value":84},"激励未对齐",{"type":28,"value":86},"：用系统的人没收益，绕过系统的人有收益",{"type":22,"tag":44,"props":88,"children":89},{},[],{"type":22,"tag":23,"props":91,"children":93},{"id":92},"浩途的应对交付-陪跑",[94],{"type":28,"value":95},"浩途的应对：交付 + 陪跑",{"type":22,"tag":97,"props":98,"children":99},"ul",{},[100,105,110],{"type":22,"tag":57,"props":101,"children":102},{},[103],{"type":28,"value":104},"交付期：和客户一起识别\"流程换了但组织没换\"的环节",{"type":22,"tag":57,"props":106,"children":107},{},[108],{"type":28,"value":109},"陪跑期（3-6 个月）：每月一次复盘，看真实使用率而非签字接收",{"type":22,"tag":57,"props":111,"children":112},{},[113],{"type":28,"value":114},"关键人物：找到客户内部的\"系统拥护者\"，给他们提供成功证据",{"type":22,"tag":116,"props":117,"children":118},"blockquote",{},[119],{"type":22,"tag":30,"props":120,"children":121},{},[122],{"type":28,"value":123},"（组织变革陪跑的具体动作清单后续展开）",{"type":22,"tag":44,"props":125,"children":126},{},[],{"type":22,"tag":23,"props":128,"children":130},{"id":129},"写在最后",[131],{"type":28,"value":129},{"type":22,"tag":30,"props":133,"children":134},{},[135,137,142],{"type":28,"value":136},"软件公司谈\"功能\"，浩途多谈一步\"组织\"。",{"type":22,"tag":36,"props":138,"children":139},{},[140],{"type":28,"value":141},"数字化的 80% 不在系统",{"type":28,"value":143},"——这是浩途\n\"长期主义\"价值观的来源之一。",{"title":7,"searchDepth":145,"depth":145,"links":146},2,[147,148,149,150],{"id":25,"depth":145,"text":25},{"id":49,"depth":145,"text":49},{"id":92,"depth":145,"text":95},{"id":129,"depth":145,"text":129},"markdown","content:insights:09-digital-80-percent.md","content","insights\u002F09-digital-80-percent.md","insights\u002F09-digital-80-percent","md",[158,277],{"_path":159,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":160,"description":7,"slug":161,"date":162,"duration":11,"category":12,"author":163,"tags":164,"featured":169,"body":170,"_type":151,"_id":274,"_source":153,"_file":275,"_stem":276,"_extension":156},"\u002Finsights\u002F02-system-selection-trap","为什么\"先选系统\"几乎总是失败的开始？","system-selection-trap","2026-03-02","浩途咨询团队",[165,166,167,168],"信息化","流程","ERP","OA",true,{"type":19,"children":171,"toc":267},[172,177,182,185,191,196,214,217,223,228,231,237,242,245,250,262],{"type":22,"tag":23,"props":173,"children":175},{"id":174},"一个常见的开局",[176],{"type":28,"value":174},{"type":22,"tag":30,"props":178,"children":179},{},[180],{"type":28,"value":181},"\"我们想上一套 ERP，请你来给推荐几个候选厂商。\"——这是浩途收到客户咨询时最常见的开场白之一。\n但凡这句话出现，我们基本能预判后续会遇到三个坑。",{"type":22,"tag":44,"props":183,"children":184},{},[],{"type":22,"tag":23,"props":186,"children":188},{"id":187},"坑一当前流程没盘清",[189],{"type":28,"value":190},"坑一：当前流程没盘清",{"type":22,"tag":30,"props":192,"children":193},{},[194],{"type":28,"value":195},"任何企业都有一套\"事实上的运行规则\"——纸面上的流程图与实际执行常常对不上。\n直接让一套通用 ERP 套上来，三个月后会发现：",{"type":22,"tag":97,"props":197,"children":198},{},[199,204,209],{"type":22,"tag":57,"props":200,"children":201},{},[202],{"type":28,"value":203},"业务部门绕过系统在用 Excel",{"type":22,"tag":57,"props":205,"children":206},{},[207],{"type":28,"value":208},"关键审批流没人理",{"type":22,"tag":57,"props":210,"children":211},{},[212],{"type":28,"value":213},"数据口径打架",{"type":22,"tag":44,"props":215,"children":216},{},[],{"type":22,"tag":23,"props":218,"children":220},{"id":219},"坑二把管理变革和系统建设混为一谈",[221],{"type":28,"value":222},"坑二：把\"管理变革\"和\"系统建设\"混为一谈",{"type":22,"tag":30,"props":224,"children":225},{},[226],{"type":28,"value":227},"\"上 ERP\" 本质上是一次管理变革——重新定义职责边界、流程、数据口径。\n但很多企业把它当成 IT 项目交给信息部，结果是 IT 撂挑子，业务部反对，老板买单。",{"type":22,"tag":44,"props":229,"children":230},{},[],{"type":22,"tag":23,"props":232,"children":234},{"id":233},"坑三选型先于需求确认",[235],{"type":28,"value":236},"坑三：选型先于需求确认",{"type":22,"tag":30,"props":238,"children":239},{},[240],{"type":28,"value":241},"\"功能模块越多越好\"是采购方常见误区。结果买回来 80% 用不上、20% 不够用。",{"type":22,"tag":44,"props":243,"children":244},{},[],{"type":22,"tag":23,"props":246,"children":248},{"id":247},"浩途的做法",[249],{"type":28,"value":247},{"type":22,"tag":30,"props":251,"children":252},{},[253,255,260],{"type":28,"value":254},"我们坚持：\"",{"type":22,"tag":36,"props":256,"children":257},{},[258],{"type":28,"value":259},"敲下第一行代码之前，先把业务图画清",{"type":28,"value":261},"\"。",{"type":22,"tag":30,"props":263,"children":264},{},[265],{"type":28,"value":266},"具体执行上：先做 2-3 周的业务诊断，输出现状流程图与目标流程图，\n让客户的业务部门、IT 部门、决策层在同一张图上对齐——再谈系统选型，\n往往会发现：\"其实只需要做 A 与 B，C 完全没必要\"。",{"title":7,"searchDepth":145,"depth":145,"links":268},[269,270,271,272,273],{"id":174,"depth":145,"text":174},{"id":187,"depth":145,"text":190},{"id":219,"depth":145,"text":222},{"id":233,"depth":145,"text":236},{"id":247,"depth":145,"text":247},"content:insights:02-system-selection-trap.md","insights\u002F02-system-selection-trap.md","insights\u002F02-system-selection-trap",{"_path":278,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":279,"description":7,"slug":280,"date":281,"duration":282,"category":12,"author":13,"tags":283,"featured":6,"body":286,"_type":151,"_id":423,"_source":153,"_file":424,"_stem":425,"_extension":156},"\u002Finsights\u002F08-business-graph","业务图谱：在写代码之前，先把业务画清","business-graph","2025-09-12",10,[284,285,12],"业务图谱","方法论",{"type":19,"children":287,"toc":417},[288,292,304,307,312,365,368,373,391,399,402,406],{"type":22,"tag":23,"props":289,"children":290},{"id":25},[291],{"type":28,"value":25},{"type":22,"tag":30,"props":293,"children":294},{},[295,297,302],{"type":28,"value":296},"客户找浩途时，需求往往以\"做一个 XX 系统\"开头。我们的回答多数是：",{"type":22,"tag":36,"props":298,"children":299},{},[300],{"type":28,"value":301},"\"先别写代码。\n先用 2 周把业务画清。\"",{"type":28,"value":303}," 这是浩途方法论里\"业务先行\"原则的具体落地——业务图谱。",{"type":22,"tag":44,"props":305,"children":306},{},[],{"type":22,"tag":23,"props":308,"children":310},{"id":309},"业务图谱要画哪些层",[311],{"type":28,"value":309},{"type":22,"tag":53,"props":313,"children":314},{},[315,325,335,345,355],{"type":22,"tag":57,"props":316,"children":317},{},[318,323],{"type":22,"tag":36,"props":319,"children":320},{},[321],{"type":28,"value":322},"角色层",{"type":28,"value":324},"：谁参与，每个角色的目标和约束",{"type":22,"tag":57,"props":326,"children":327},{},[328,333],{"type":22,"tag":36,"props":329,"children":330},{},[331],{"type":28,"value":332},"流程层",{"type":28,"value":334},"：业务从触发到结果的关键节点",{"type":22,"tag":57,"props":336,"children":337},{},[338,343],{"type":22,"tag":36,"props":339,"children":340},{},[341],{"type":28,"value":342},"数据层",{"type":28,"value":344},"：每个节点流转的数据是什么、归属谁",{"type":22,"tag":57,"props":346,"children":347},{},[348,353],{"type":22,"tag":36,"props":349,"children":350},{},[351],{"type":28,"value":352},"决策层",{"type":28,"value":354},"：哪些节点是\"判断分叉\"，规则怎么写",{"type":22,"tag":57,"props":356,"children":357},{},[358,363],{"type":22,"tag":36,"props":359,"children":360},{},[361],{"type":28,"value":362},"异常层",{"type":28,"value":364},"：常见的不顺、回退、人工介入路径",{"type":22,"tag":44,"props":366,"children":367},{},[],{"type":22,"tag":23,"props":369,"children":371},{"id":370},"画完之后能做什么",[372],{"type":28,"value":370},{"type":22,"tag":97,"props":374,"children":375},{},[376,381,386],{"type":22,"tag":57,"props":377,"children":378},{},[379],{"type":28,"value":380},"看出哪些环节根本不需要系统化（用一个表格就够）",{"type":22,"tag":57,"props":382,"children":383},{},[384],{"type":28,"value":385},"看出哪些环节是真正的瓶颈，值得投入 80% 的资源",{"type":22,"tag":57,"props":387,"children":388},{},[389],{"type":28,"value":390},"看出系统边界——什么是 in scope，什么是别的系统的事",{"type":22,"tag":116,"props":392,"children":393},{},[394],{"type":22,"tag":30,"props":395,"children":396},{},[397],{"type":28,"value":398},"（配套模板与真实项目案例后续展开）",{"type":22,"tag":44,"props":400,"children":401},{},[],{"type":22,"tag":23,"props":403,"children":404},{"id":129},[405],{"type":28,"value":129},{"type":22,"tag":30,"props":407,"children":408},{},[409,411,416],{"type":28,"value":410},"代码贵的从来不是写代码本身，而是\"业务理解错了又写一遍\"。",{"type":22,"tag":36,"props":412,"children":413},{},[414],{"type":28,"value":415},"业务图谱不是浪费时间，\n是省时间的方式",{"type":28,"value":42},{"title":7,"searchDepth":145,"depth":145,"links":418},[419,420,421,422],{"id":25,"depth":145,"text":25},{"id":309,"depth":145,"text":309},{"id":370,"depth":145,"text":370},{"id":129,"depth":145,"text":129},"content:insights:08-business-graph.md","insights\u002F08-business-graph.md","insights\u002F08-business-graph",1780542368916]