[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-internal-training-design-zh-CN":3,"blog-adjacent-internal-training-design-zh-CN":30,"blog-related-internal-training-design-zh-CN":64},{"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},102,"internal-training-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-05-08T14:49: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},4,0,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users","blue","article",30,{},{"previous":31,"next":48},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},83,"handover-without-docs","团队交接复盘：文档缺失的一个月","核心开发离职，接手的人花了一个月才敢改第一行代码。","2026-05-10T14:49:00+08:00",[38,39,40],"复盘","交接","团队",{"id":42,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},121,"rpa-and-workflow","RPA 与流程自动化：被高估与被低估的部分","RPA 演示效果很好，但企业真正跑通的不多。被高估的是技术，被低估的是流程梳理。","2026-05-06T14:49:00+08:00",[55,56,57],"行业观察","RPA","流程自动化",{"id":59,"parentId":21,"slug":60,"name":55,"description":61,"icon":62,"cover":9,"tone":26,"kind":27,"sortOrder":63,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20,[65,74,85],{"id":66,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":73},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,72,18],"技术分享",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":75,"slug":76,"title":77,"excerpt":78,"content":9,"cover":9,"tone":79,"author":11,"publishedAt":80,"updatedAt":80,"readingMinutes":13,"featured":14,"tags":81,"category":84},90,"what-code-review-is-for","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,82,83],"代码评审","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":86,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":90,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":95},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,93,94],"文档","知识管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]