Most teams already have standups. Standups are for coordination. They are not for learning.
What raised the teams I led was a different ritual: a weekly development meeting where people shared something real. A bug that taught a lesson. A pattern that worked. A tool that saved time. A mistake worth not repeating. No deck theater. No status reading from Jira.
Sharing is how individual learning becomes company capability.
Why weekly beats “whenever we remember”
Ad hoc knowledge sharing dies under deadline pressure. A fixed weekly slot makes teaching normal instead of optional.
Thirty to forty-five minutes is enough if the format is tight:
- one or two short shares (5-8 minutes each)
- questions and pushback
- one takeaway captured in a doc or channel
- done
If nobody has a polished talk, good. Raw notes from a production incident beat a perfect slideshow that never ships.
What people should share
The best shares are close to the work:
- a Shopify extension gotcha that burned two days
- a Terraform module boundary that clarified ownership
- a PR review comment that should become a team rule
- a debugging path that made logs useful
- a customer constraint that changes how we design
Avoid generic “news from the internet” unless it maps to a decision the team must make soon.
Sharing lowers the cost of the next person
When only one engineer knows why a sync worker fails closed, every similar ticket routes through them. When they share that model in the weekly meeting, the next three engineers stop rediscovering the same cliff.
This is mentoring at team scale. One share, many listeners, repeated every week.
Make it safe or it becomes performance
People will not share half-finished thinking if the room punishes uncertainty. Leaders set the tone:
- thank the share before critiquing it
- ask clarifying questions before correcting
- celebrate “I was wrong and here is what I learned”
- never turn the meeting into public ranking
Psychological safety is not soft. It is how you get honest signal while the lesson is still cheap.
Keep an artifact, or the meeting evaporates
A weekly meeting without a written trail becomes vibes. Keep a living note:
- title of the share
- the decision or pattern
- link to PR, doc, or runbook
- owner if follow-up is needed
That note becomes onboarding fuel and review fuel.
Leadership takeaway
If your team only talks about tickets, your team only gets better at tickets. A weekly development meeting where people share craft is how judgment spreads.
Protect the slot. Keep it short. Capture the lesson. Watch the average engineer get stronger without waiting for another hiring cycle.