What is how to share knowledge with your team?

How to share knowledge with your team is a concept in personal epistemology: Define how you share processed information with others efficiently.

Example: You spent three weeks researching a complex regulatory change that affects your team's product roadmap. You have thirty-seven notes in your Zettelkasten, six synthesis notes, and a deep understanding of how the regulation interacts with your existing architecture. A colleague asks: 'What do we need to know about the new regulation?' You could forward all thirty-seven notes. You could dump your synthesis notes into Slack. Instead, you apply your sharing protocol. For this audience (product team, time-constrained, needs actionable implications not legal nuance), the correct format is a one-page structured memo: top-line impact in one sentence, three specific implications for the roadmap, two recommended actions, and a link to your full notes for anyone who wants to go deeper. You write the memo in twelve minutes because you already did the processing. Your colleague reads it in three minutes and knows exactly what to do. The thirty-seven notes were for you. The one-page memo is for them. The protocol is the bridge between your deep processing and their need for actionable clarity.

This concept is part of Phase 43 (Information Processing) in the How to Think curriculum, which builds the epistemic infrastructure for information processing.