Information sharing protocols

Your pipeline has no output valve

You have built an impressive information processing system over the last fifteen lessons. You curate your inputs, triage what deserves attention, file what survives into an atomic note system, compress those notes through progressive summarization, and synthesize across domains to produce original insights. Your Zettelkasten is rich. Your understanding is deep. Your private knowledge infrastructure is, by any reasonable measure, working.

And it is entirely private.

The insights you generated in your last synthesis session — the ones that emerged from colliding notes across three different domains, the ones that made you pause and think "that is genuinely new" — are sitting in your note system. They have an audience of one. They will benefit no one besides you. And even the benefit to you is incomplete, because an insight that has never been articulated to another person, never been tested against a different perspective, never been refined by the friction of someone else's understanding, is an insight that has not finished forming.

Your information pipeline has no output valve. Information flows in, gets processed, gets stored, gets synthesized — and then stops. It accumulates. The processing was real, the synthesis was real, but the final stage of the pipeline — the stage where processed knowledge leaves your system and enters the world — was never designed.

This lesson fixes that. Information sharing is not an afterthought to the pipeline. It is the completion of the pipeline. It is the stage where private understanding becomes public contribution, where your processing creates value beyond your own cognition, and where — counterintuitively — the act of sharing deepens the very understanding you are sharing.

Sharing is the final processing step, not a separate activity

Most people treat sharing as something that happens after the knowledge work is done. You learn something, you process it, you understand it, and then — optionally, if you have time, if you feel confident enough — you share it. The sharing is a distribution step, separate from the understanding step.

This framing is wrong, and the research shows exactly why.

In 2014, John Nestojko and colleagues at Washington University in St. Louis conducted a study that demonstrated what educators have long suspected: people who study material with the expectation that they will need to teach it to others learn the material better than people who study with the expectation that they will be tested on it. The researchers called this the "protege effect." Participants who believed they would teach organized the information more coherently, recalled key concepts more accurately, and demonstrated better comprehension on subsequent assessments — even though they never actually taught anyone. The mere expectation of needing to share changed the quality of their processing.

The mechanism is not mysterious. When you process information for yourself, you can tolerate ambiguity. You know what you mean, even if your notes are vague. You can leave gaps because your background knowledge fills them in implicitly. But when you process information for someone else — when you anticipate the moment of sharing — you are forced to close those gaps. You have to make the implicit explicit. You have to structure the information so it is navigable by a mind that does not have your context. You have to answer questions you have not yet asked yourself: What is the core claim? What evidence supports it? What are the limits of this insight? Why should someone care?

This is not extra work layered on top of understanding. It is the final processing step — the step that converts fuzzy comprehension into precise knowledge. Richard Feynman articulated this as a principle: if you cannot explain something in simple terms, you do not understand it well enough. The inability to share is a diagnostic signal. It tells you that your processing is incomplete, that you have aggregated rather than synthesized, that you have stored information rather than genuinely integrated it.

So sharing is not optional, and it is not downstream. It is the last and highest-value operation in the pipeline, because it simultaneously delivers value to others and completes the processing for you.

The knowledge creation spiral

Ikujiro Nonaka and Hirotaka Takeuchi, in their 1995 book "The Knowledge-Creating Company," proposed a model of organizational knowledge creation that maps precisely onto what you are doing with your information pipeline. Their model describes four modes of knowledge conversion, forming a spiral:

Socialization — tacit knowledge transferred through shared experience. You sit with someone and absorb how they think about a problem. No explicit communication is required; the knowledge moves through observation and practice.

Externalization — tacit knowledge converted to explicit knowledge. This is the moment you take what you intuitively understand and articulate it in words, diagrams, or models. You write a note. You explain your synthesis to a colleague. The knowledge moves from inside your head to a format others can access.

Combination — explicit knowledge combined with other explicit knowledge. This is what you did in the synthesis lesson — combining notes from multiple sources to produce new insights. The knowledge is already externalized; you are recombining it.

Internalization — explicit knowledge absorbed back into tacit knowledge. You read someone else's synthesis, and through practice and reflection, it becomes part of how you think. This is learning.

The critical insight from Nonaka and Takeuchi is that these four modes form a spiral, not a line. And the spiral does not turn without all four modes operating. If you skip externalization — if you never share your tacit knowledge and your syntheses — the spiral stalls. Your knowledge stays tacit, gets combined only within your own system, and never enters the social loop where others can internalize it, develop their own tacit understanding, and externalize new knowledge back to you.

Sharing is not the end of the pipeline. It is the mechanism that turns the pipeline into a cycle. Your synthesis becomes someone else's input. Their response becomes your new data. The cycle accelerates. Knowledge compounds.

What sharing actually requires: the protocol

A protocol is a defined procedure for how information moves between systems. In networking, protocols specify the format, the sequence, the error-handling, and the expected response for every message exchanged. TCP/IP does not send data in whatever format feels natural at the moment. It follows a protocol — a set of agreements about how communication will be structured — so that any system on either end can reliably send and receive.

Your information sharing needs the same thing. Not because human communication should feel mechanical, but because without a protocol, sharing defaults to whatever is easiest in the moment — which is almost always the wrong format, at the wrong depth, for the wrong audience.

A sharing protocol answers five questions:

1. Who is the audience? Not "everyone" — a specific person or a specific group with a specific context. Your team lead who has five minutes between meetings. Your colleague who is deep in the same domain and wants technical nuance. Your friend who is curious but has no background in the topic. Each audience needs a different share.

2. What is their context? How much do they already know? How much time do they have? Are they looking for a decision, an understanding, or an action? Are they reading on their phone or at a desk? Context determines format.

3. What is the core insight? Not everything you know about the topic — the one thing they need to take away. Barbara Minto's Pyramid Principle, developed at McKinsey and now taught in business schools worldwide, provides the structure: lead with the answer. The single most important insight goes first. Supporting arguments come second. Evidence and detail come third. If the reader stops at any point, they have already received the most valuable information. This is the inversion of how most people share — most people build up to the insight, starting with context and evidence and arriving at the conclusion. The Pyramid Principle says: start with the conclusion. Let the reader decide how much supporting detail they need.

4. What is the appropriate format? A Slack message, a one-page memo, a five-minute conversation, a structured document, a voice note, a thread on a forum? The format should match the audience's context and the complexity of the insight. Amazon's six-page memo format — structured written narrative, no slides, read in silence at the start of a meeting — exists because Jeff Bezos recognized that complex ideas require complete sentences and logical structure, not bullet points and presenter charisma. But a six-page memo is wrong for a quick status update. The protocol matches format to purpose.

5. What context wraps the share? This is the difference between sharing and forwarding. Forwarding is sending a link. Sharing is sending a link with a frame: "I read this and the key insight for our project is X, because it suggests Y about our assumption Z. The full article is worth reading if you want the supporting evidence, but the core implication is in the first sentence of this message." The frame is the value-add. It is the product of your processing. Anyone can forward a link. Only you can provide the frame that your specific processing and synthesis produced.

Five sharing modes, from lightweight to heavyweight

Not every share requires a structured memo. The protocol should include multiple modes, deployed based on the situation.

Mode 1: The annotated forward. The lightest share. You send a link, an article, a note — but with two to three sentences of context explaining why it matters and what the recipient should take from it. This takes thirty seconds and transforms a content dump into a curated share. The annotation is your processing made visible.

Mode 2: The structured summary. A paragraph to a page, following the Pyramid Principle. Lead with the insight, support with two to three key points, link to sources for anyone who wants more. This is the workhorse format for sharing with colleagues and teams. It respects their time while delivering the full insight.

Mode 3: The working-out-loud post. John Stepper, in his 2015 book "Working Out Loud," describes a practice of making your work visible as it happens — sharing not just finished insights but the process of developing them. You post a question you are grappling with. You share a half-formed synthesis and ask for pushback. You document what you are learning as you learn it. This mode is not about polished output; it is about making your thinking observable so that others can contribute to it while it is still forming. The open source movement operates on the same principle. Eric Raymond, in "The Cathedral and the Bazaar," articulated Linus's Law: "Given enough eyeballs, all bugs are shallow." Applied to knowledge sharing, the principle is: given enough perspectives on your half-formed idea, the flaws become obvious and the refinements become available. Working out loud invites those perspectives.

Mode 4: The teach-back. You take a concept you have processed and synthesized and explain it to someone else as if you are teaching a short lesson. This is the protege effect in action. You choose an audience — a colleague, a mentee, a friend — and walk them through the idea from scratch. You discover the gaps in your understanding in real time, because the questions they ask are the questions you failed to ask yourself. The teach-back is not primarily for the student's benefit, though they do benefit. It is the highest-quality processing operation available to you — the final pass that converts knowledge from "I think I understand this" to "I can make someone else understand this."

Mode 5: The structured document. A long-form write-up — a memo, a blog post, an internal document, a report — that fully externalizes your synthesis on a topic. This is the most expensive mode in terms of time, but it is also the most durable. A structured document can be read by people you never meet, referenced months later, and built upon by others. It is the mode that contributes most to the collective knowledge base and the mode that most thoroughly completes your own processing.

The curator's mindset

There is a subtle but important distinction between being an information source and being an information curator. A source generates original content. A curator selects, contextualizes, and presents information in a way that makes it more useful than the raw material.

You are both.

When you share a synthesis — an insight that emerged from combining multiple sources in your Zettelkasten — you are a source. That insight is original. It did not exist before you created it. But when you share someone else's article with your annotation explaining why it matters for a specific project, you are a curator. And curation is not lesser work. In a world drowning in information, the person who can reliably say "this is the one thing you should pay attention to, and here is why" provides enormous value.

The curator's contribution is threefold. First, selection: out of the hundreds of inputs you processed this week, you chose this one to share. That selection reflects your judgment, your processing, and your understanding of what matters. Second, contextualization: you did not just pass along the information; you explained its relevance to a specific audience and a specific purpose. Third, timing: you shared it when it was useful, not when you happened to encounter it. The gap between "I read an interesting article last month" and "Here is something directly relevant to the problem you are working on right now" is the gap between hoarding and sharing.

The best knowledge workers in any organization are not the ones who know the most. They are the ones who share the most — who consistently surface the right information, at the right depth, for the right people, at the right time. They are running a sharing protocol, whether they call it that or not.

The compound returns of consistent sharing

Sharing compounds in ways that private processing does not.

When you share a synthesis, three things happen that cannot happen in a closed system. First, you receive feedback — corrections, extensions, counterarguments — that refine the synthesis beyond what you could achieve alone. Your insight about the relationship between remote work and deep work productivity (from the synthesis lesson) might get refined by a colleague who points out a third variable you missed. That refinement would never have reached you if the synthesis had stayed in your Zettelkasten.

Second, you build a reputation as someone who processes and shares reliably. Over time, people start sending you information proactively — "I saw this and thought of your work on X" — which enriches your input stream with curated, relevant material. Your sharing creates a feedback loop that improves your inputs.

Third, you create an external knowledge base that others can build on. Your shared synthesis becomes a node in a larger network of knowledge. Someone reads your synthesis, combines it with their own processing, produces a new insight, and shares it back. The compound returns are not just personal — they are networked. The value of your sharing multiplies as others build on it.

Nonaka and Takeuchi observed this dynamic in the organizations they studied. The companies that created the most new knowledge were not the ones with the most individual experts. They were the ones with the most active knowledge-sharing cultures — environments where externalization was the norm, where people routinely made their tacit knowledge explicit and shared it across teams and domains. The spiral turned fastest where sharing was habitual.

Your Third Brain: AI as sharing accelerator

AI is exceptionally useful at the sharing stage of the pipeline, because much of the work involved in sharing is translation — converting your understanding from the format in which you hold it (dense, contextual, full of implicit connections) to the format in which someone else can receive it (clear, structured, appropriately scoped).

Audience adaptation. You have a synthesis note written in your own shorthand, dense with domain-specific references. You need to share it with three different audiences: your technical team, your non-technical manager, and a public audience on LinkedIn. Give the AI your synthesis note and ask it to draft the share for each audience at the appropriate level of depth and jargon. You edit the drafts — the AI does not know your specific audience the way you do — but the structural translation from "my level of understanding" to "their level of context" is exactly the kind of task where AI saves significant time.

Pyramid structuring. You have a complex insight with multiple supporting arguments. Ask the AI to help you identify the single top-line claim and organize the supporting points in descending order of importance. The AI is good at identifying which elements of your thinking are supporting evidence and which are the core claim — a distinction that is often blurry when you are deep inside your own reasoning.

Gap detection in your explanation. Before you share a teach-back or a structured document, ask the AI to read it as a skeptical outsider and identify where the reasoning has gaps, where jargon is unexplained, or where a claim is unsupported. The AI simulates the "fresh eyes" that Feynman's principle demands — eyes that have not walked the same processing path you walked and therefore notice the jumps you skipped.

Format conversion. You have a long-form synthesis. You need a three-sentence Slack summary, a one-paragraph email brief, and a full memo. The AI can generate drafts of each format from the same source material. You refine, you add the curator's context that only you can provide, but the mechanical work of reformatting is handled.

The boundary remains the same as in every AI-assisted stage of the pipeline: the AI handles format and structure; you provide judgment, context, and the curator's frame. The AI does not know why this particular insight matters for this particular audience at this particular moment. That is your contribution — the product of all the processing you did in the fifteen lessons that precede this one.

The bridge to overload

There is a shadow side to information sharing, and it arrives at the receiving end.

When you share effectively — when you consistently externalize processed, contextualized, well-structured knowledge — you contribute to a world that has more information in it. You are, in a real sense, adding to the river that everyone else is trying to drink from. The paradox of good sharing is that it works best when the recipients also have functional processing pipelines. If they do not — if they are already overwhelmed by unprocessed inputs — your beautifully structured memo becomes one more item in an overflowing inbox.

This is the setup for the next lesson. Information overload is not primarily an input problem — it is a processing problem. When your pipeline cannot keep up with the volume, the solution is not to process faster. It is to declare information bankruptcy: to stop, clear the backlog, rebuild your input sources from scratch, and restart with a curated set of streams that your pipeline can actually handle.

But before you learn to recover from overload, internalize this: the output stage of your pipeline is not optional. Information hoarded is value unrealized. Your syntheses, your curated shares, your teach-backs, your structured memos — these are the products of your cognitive infrastructure. They are the evidence that the pipeline works. And they are the mechanism by which your private understanding becomes a public good that compounds beyond anything you could achieve alone.

Define your protocol. Start sharing.

---

Sources:

1. Nestojko, J. F., Bui, D. C., Kornell, N., & Bjork, E. L. (2014). "Expecting to teach enhances learning and organization of knowledge in free recall of text passages." Memory & Cognition, 42(7), 1038-1048.
2. Nonaka, I., & Takeuchi, H. (1995). The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press.
3. Minto, B. (1987). The Pyramid Principle: Logic in Writing and Thinking. Minto International.
4. Raymond, E. S. (1999). The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary. O'Reilly Media.
5. Stepper, J. (2015). Working Out Loud: For a Better Career and Life. Ikigai Press.
6. Feynman, R. P. (1985). "Surely You're Joking, Mr. Feynman!": Adventures of a Curious Character. W. W. Norton & Company.
7. Bezos, J. (2018). Annual Letter to Amazon Shareholders. Discussions of the six-page memo format.
8. Forte, T. (2022). Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential. Atria Books.