[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-internal-training-design-en":3,"blog-adjacent-internal-training-design-en":30,"blog-related-internal-training-design-en":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","Designing Internal Training That Works","Training that ends in forgetting is a ritual, not training. We send people in with a problem and out with an artefact.","\u003Cp>Our old training was two-hour lectures: the speaker worked hard and little stuck. Then we rebuilt it around a real task that must be completed by hand before the session ends.\u003C\u002Fp>\n\u003Ch2>The current structure\u003C\u002Fh2>\n\u003Cp>Preparation: a two-page primer with concepts and one or two questions, sent a week ahead.\u003C\u002Fp>\n\u003Cp>Session: twenty minutes of core concepts, the rest spent building a realistic scenario hands-on.\u003C\u002Fp>\n\u003Cp>Wrap-up: everyone submits an artefact and gets individual feedback. No submission means no attendance.\u003C\u002Fp>\n\u003Ch2>Why it works better\u003C\u002Fh2>\n\u003Cp>Retention from doing far exceeds listening. Where people get stuck is exactly where understanding matters.\u003C\u002Fp>\n\u003Cp>Outputs go straight to work: the debugging checklist from a performance session became a team standard.\u003C\u002Fp>\n\u003Cp>Instructors prepare harder. Designing exercises and feedback forces real mastery of the material.\u003C\u002Fp>\n\u003Cp>Training aims at behaviour change, not information transfer. Only content usable on the job deserves work hours.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-05-08T14:49:00+08:00",1,false,[16,17,18],"Team Culture","Training","Growth",{"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","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","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","Retrospective: A Month Lost to Missing Documentation","The core developer left and the successor spent a month before daring to change a line.","2026-05-10T14:49:00+08:00",[38,39,40],"Retrospective","Handover","Team",{"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","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","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 and Workflow Automation: Overrated and Underrated","RPA demos well, but few enterprises get it running. Technology is overrated; process analysis is underrated.","2026-05-06T14:49:00+08:00",[55,56,57],"Industry Watch","RPA","Process Automation",{"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","In-depth analysis of internet, software and digital industry trends with our own point of view.","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","The Thirty-Minute Weekly Share","No new technology, no industry trends. Just the pitfalls of the week and how they were solved.","2026-10-11T09:00:00+08:00",[16,72,18],"Knowledge Sharing",{"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","What Code Review Is Really For","Review is not fault-finding. It is letting another mind walk through your code.","cyan","2026-09-29T10:13:00+08:00",[16,82,83],"Code Review","Engineering Practice",{"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","Documents Start With Templates","People avoid writing docs mostly because they do not know where to start. A template solves most of it.","teal","2026-09-17T11:26:00+08:00",[16,93,94],"Documentation","Knowledge Management",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]