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