Team and Culture · Published October 11, 2026
The Thirty-Minute Weekly Share
No new technology, no industry trends. Just the pitfalls of the week and how they were solved.
Three years ago we started reserving thirty minutes on Friday afternoons for one person to present a concrete problem from that week's work. No slides required, no scoring, followed by open discussion. It has become the fastest-growing mechanism in our team.
Only three rules
Present only firsthand experience, not articles you read. Secondhand stories lack detail; the value lies in the review.
Answer three questions: what happened, why, and how to avoid it next time. Twenty minutes to present, ten to discuss.
Nothing needs to be profound. A talk about a naming misunderstanding can be as useful as one about architecture.
What changed
The same mistakes repeat far less often. One person's pitfall becomes everyone's knowledge.
Newcomers speak up. Thirty minutes is low pressure, and the first talk makes later communication easier.
Material accumulates. Many blog posts and internal documents started as a weekly share.
Teams grow through frequent, low-friction steps rather than a single big training. Thirty minutes goes further than expected.
← Previous post
Retrospective: Why Acceptance Took Half a Year
Next post →
The Watershed for Vertical Products: Writing Industry Defaults into the System
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 →