Record Learnings

Why Record Learnings

We want team members to grow, and team members want to grow too. But without recording and sharing, there's no process of reflection. Learning happens in the doing, but growth happens in the reflecting.

The idea is simple: give everyone a place to post bite-sized learnings anytime, and make it visible to the whole team.

How It Works

A Shared Space for Micro-Sharing

• Set up a dedicated channel or space (e.g., a Slack channel, Notion page, or internal feed) where anyone can post a learning at any time
• Posts should be short and low-effort — a few sentences is fine. Examples:
  • "TIL that git stash --keep-index only stashes unstaged changes"
  • "Found that adding an index on the created_at column cut our query time by 80%"
  • "Learned about the Strangler Fig pattern for migrating legacy systems — seems promising for our refactor"
• No formatting requirements, no review process — just share what you learned

Make It Rewarding

• The team periodically (e.g., monthly) selects the person who shared the most learnings during that period
• Reward them with something small but meaningful: a book, a gift card, or public recognition
• The reward isn't the point — it's about reinforcing the habit and signaling that the team values continuous learning

Why Bite-Sized Works

• Low barrier — Writing a few sentences takes seconds, not hours. People actually do it
• Builds reflection habits — The act of writing down what you learned forces you to articulate it, which deepens understanding
• Compounds over time — One micro-learning per day is 250+ learnings per year from one person. Multiply by the team size and you have an incredible knowledge base
• Improves team culture — When everyone can see what others are learning and discovering, it creates a culture of curiosity and openness
• Cross-pollination — A frontend developer's learning might spark an idea for a backend developer. Visibility creates unexpected connections

What People Might Share

• A useful command, shortcut, or tool they discovered
• A debugging technique that saved them time
• An insight from reading documentation or source code
• A pattern or anti-pattern they noticed in the codebase
• Something they learned from a code review, a conversation, or a mistake
• An interesting article, video, or conference talk

Tips

• Lead by example — managers and senior members should post first and regularly
• Don't judge or critique people's posts — the goal is to encourage sharing, not to gatekeep
• Periodically highlight particularly useful or interesting posts to the team
• Consider creating a searchable archive so learnings can be referenced later