Dimension 5 of 6
Knowledge Compounding
How your learning, building, and sharing creates durable value beyond yourself — through artifacts others can fork, reference implementations others build on, and knowledge that compounds organizationally rather than staying trapped in your head.
The five levels
Absent
Learns and builds independently. Hasn't yet started sharing work or discovering what others have built. Knowledge stays with the individual — not because of reluctance, but because sharing infrastructure and habits haven't formed yet. (The duplicate-building problem — Emile and Carlos built the same account tracker independently — is a symptom of this, not a personal failing.)
Personal
Shares when asked or when something feels finished. Engages with some shared content (reads #upskilling, attends power hours). But sharing is reactive, not proactive. Learns from pairing sessions but doesn't seek them out.
Systematic
Shares work proactively — posts in channels, presents at sessions, creates documentation. Actively seeks out what others have built. Learns from multiple sources. But knowledge transfer is still social (presentations, Slack posts) rather than artifact-based. Others are aware of their work but may not be building on it.
Expert Exemplar
Creates artifacts that others fork, extend, and build on without needing the original creator. Reference implementations that become standards. Others cite their work, use their tools, build on their patterns. Influence is measurable through cross-references and tool adoption — not just presentation attendance. Also a strong inbound learner — rapidly absorbs others' innovations.
Compounding
Builds the systems that make knowledge compound without relying on individual effort — you personally create the discoverable directory, the capture mechanism, the cross-project learning infrastructure. Designs artifacts specifically for forkability (documented, modular, with clear extension points) rather than just sharing what you built. Actively closes learning loops: when you discover something on one project, you encode it into a shared resource that other projects automatically benefit from. Builds the "bleeding edge → graduated" pipeline where others' work-in-progress is surfaced and matured. Your knowledge infrastructure is the reason the organization learns faster than the sum of its individuals.
Key quotes
“When I think about my workflow, I know my workflow is different than a lot of other people's and I don't necessarily believe that my workflow is the best workflow or is even a good workflow. It works for me... bringing somebody else along and saying, 'hey, this is how I did this' might not really make sense.”
“I just started on Monday. I want to learn how to do shit. And then start demoing... I need to have something that's worth blowing minds with and then making it usable because everyone's going to ask to use it as soon as I do it.”
“If I see something, try something, do something that I think has scalability or applicability to the way in which others work, I'm obviously going to pass that along. Certainly trying to bring more of that to our go-to-market weekly meetings.”
“What I like to do in this situation is just kind of do it once myself and then have a paper trail... Koch is a great example where I could just point someone at the PR and be like, I did this over a year. Can you replicate this for this other project?”
Transitions — what distinguishes each level
The shift is from *isolated* to *connected*. At L2, you engage with what others share and you share when prompted. The gap is between "I don't know what others have built" and "I participate in the knowledge ecosystem, at least passively."
The shift is from *reactive sharing* to *proactive sharing*. At L3, you share without being asked — you present, you post, you document. The gap is between "I share when someone asks" and "I share because it's part of how I work."
The shift is from *social knowledge transfer* to *artifact-based knowledge compounding*. At L3, others know about your work through presentations and posts. At L4, others build on your work through reference implementations and forkable artifacts. The gap is between "people heard about what I did" and "people use what I built as a starting point."
The shift is from *influential artifacts* to *knowledge infrastructure*. At L5, you've built the systems that make discovery and transfer happen automatically — directories, capture mechanisms, learning loops. The gap is between "people build on my work" and "the organization compounds knowledge because of systems I created."