[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-approval-flow-design-zh-CN":3,"blog-adjacent-approval-flow-design-zh-CN":30,"blog-related-approval-flow-design-zh-CN":67},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},57,"approval-flow-design","审批流：别把组织问题做成系统问题","审批链路过长，往往不是流程设计得不好，而是权责没有理清。","\u003Cp>很多客户提出要做审批流时，给出的要求是“按现有制度来”。但把现有制度画成流程图之后，常常会发现某个环节有五个审批人，谁都不清楚自己该看什么。\u003C\u002Fp>\n\u003Ch2>先问清楚三个问题\u003C\u002Fh2>\n\u003Cp>每个审批节点在判断什么？如果答不出，这个节点可能只是形式。\u003C\u002Fp>\n\u003Cp>驳回之后谁负责修改？很多流程在驳回环节卡住，因为没人接手。\u003C\u002Fp>\n\u003Cp>紧急情况怎么走？没有例外通道，业务会绕开系统，最终系统形同虚设。\u003C\u002Fp>\n\u003Ch2>系统能做什么\u003C\u002Fh2>\n\u003Cp>把审批意见结构化，要求选择原因而不是自由输入，便于统计高频问题。\u003C\u002Fp>\n\u003Cp>支持代理与转交，处理请假和岗位变动，这比增加审批层级更有效。\u003C\u002Fp>\n\u003Cp>保留完整的审批历史，用于事后复盘和审计。\u003C\u002Fp>\n\u003Cp>审批流是组织规则的镜像。规则混乱时，系统只能放大混乱，不能自动理顺。\u003C\u002Fp>","","indigo","佳益方圆团队","2026-07-23T16:31:00+08:00",1,false,[16,17,18],"审批","流程","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","blue","article",50,{},{"previous":31,"next":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":38,"readingMinutes":13,"featured":14,"tags":39,"category":42},9,"tech-open-day-2026","技术开放日：把架构决策讲给客户听","把内部评审开放给客户，用他们能听懂的语言讲清取舍，是建立长期信任的一部分。","teal","2026-07-24T16:30:00+08:00","2026-10-18T15:58:14.758+08:00",[40,41],"技术开放日","客户交流",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"count":21},4,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users",30,{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":60},77,"compressed-schedule-cost","赶工期复盘：压缩测试的代价","为了赶上客户的开业时间，我们压缩了两周测试，结果上线后修了六周。","slate","2026-07-21T16:31:00+08:00",[57,58,59],"复盘","工期","质量",{"id":61,"parentId":21,"slug":62,"name":63,"description":64,"icon":65,"cover":9,"tone":26,"kind":27,"sortOrder":66,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[68,78,87],{"id":28,"slug":69,"title":70,"excerpt":71,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":77},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[74,75,76],"需求","产品方法","风险管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":82,"updatedAt":83,"readingMinutes":20,"featured":14,"tags":84,"category":86},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[85,18],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":88,"slug":89,"title":90,"excerpt":91,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":92,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":95},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[94,75,74],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]