Team and Culture · Published August 12, 2026
A Quarterly Tech Sharing Day
Thirty minutes a week is not always enough, so we take half a day, mute notifications and talk shop properly.
Weekly shares capture daily lessons, but some topics need room: a full architecture refactor, a tooling comparison. This year we started a quarterly half-day sharing session with everyone attending and no client meetings that day.
How the day runs
Topics are voted by the team, usually three: one engineering practice, one deep project review, one open discussion.
Each speaker gets forty minutes plus twenty for questions, and must prepare a working demo. Running code persuades better than slides.
Notifications are muted for the day, with only the on-call phone handling production issues.
A lesson from the first one
We originally scheduled six topics from morning to evening; the last two had almost no audience.
Three topics with a tea break in between is the right size, leaving room for informal exchange.
Materials are archived in the knowledge base so absentees can catch up.
A sharing day is an investment of team time, not an extra burden. Half a day of focus smooths months of collaboration.
← Previous post
Retrospective: A Dashboard Nobody Opened
Next post →
The Real Cost of Xinchuang Adaptation
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →