[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-continuous-feedback-en":3,"blog-adjacent-continuous-feedback-en":30,"blog-related-continuous-feedback-en":66},{"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},96,"continuous-feedback","Feedback Should Not Wait for Year-End","Criticism first heard in a year-end review is already six months late.","\u003Cp>In one annual review a colleague said: I actually thought that approach was wrong early on, but planned to mention it at year-end. That sentence made us realise how much value deferred feedback loses.\u003C\u002Fp>\n\u003Ch2>Make feedback small\u003C\u002Fh2>\n\u003Cp>After each collaboration, spend two minutes on one specific good thing and one specific improvement, aimed at work, never at the person.\u003C\u002Fp>\n\u003Cp>Project retrospectives include a fixed collaboration-feedback segment: whose work helped you, and where you got stuck.\u003C\u002Fp>\n\u003Cp>Managers hold a twenty-minute monthly chat with everyone about state and growth, not task status.\u003C\u002Fp>\n\u003Ch2>What the receiver does\u003C\u002Fh2>\n\u003Cp>Say thank you first, and resist explaining. Explanations teach people to stop telling you things.\u003C\u002Fp>\n\u003Cp>Decide within a week whether to adopt it, and tell the giver. Adopt and change, or decline with a clear reason.\u003C\u002Fp>\n\u003Cp>Publicly credit useful feedback. Make truth-telling cheap.\u003C\u002Fp>\n\u003Cp>Feedback decays with time. One sentence said the same day beats three pages written in December.\u003C\u002Fp>","","teal","佳益方圆团队","2026-07-19T16:31:00+08:00",1,false,[16,17,18],"Team Culture","Feedback","Communication",{"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":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},77,"compressed-schedule-cost","Retrospective: The Cost of Compressed Testing","To hit a client's opening date we cut testing from three weeks to one, then spent six weeks fixing production.","slate","2026-07-21T16:31:00+08:00",[39,40,41],"Retrospective","Schedule","Quality",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"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":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},115,"miniapp-ecosystem-next","The Next Phase of the Mini Program Ecosystem","With traffic dividends gone, mini programs shift from acquisition tools to retention and efficiency.","cyan","2026-07-17T16:31:00+08:00",[57,58,59],"Industry Watch","Mini Programs","Ecosystem",{"id":61,"parentId":21,"slug":62,"name":57,"description":63,"icon":64,"cover":9,"tone":26,"kind":27,"sortOrder":65,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20,[67,77,87],{"id":68,"slug":69,"title":70,"excerpt":71,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":76},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,74,75],"Knowledge Sharing","Growth",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":86},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.","2026-09-29T10:13:00+08:00",[16,84,85],"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":88,"slug":89,"title":90,"excerpt":91,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":92,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":96},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.","2026-09-17T11:26:00+08:00",[16,94,95],"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}]