Your Writing Is Already a Second Brain...
You Just Haven't Built It Yet
Patrick already told you why we built Second Draft Labs — the founding story, the problem that made it obvious, the decision to actually do something about it. I want to start one level deeper, with an idea that has been stuck in my head as we have been creating this project at warp speed.
The bottleneck in your knowledge work is not writing speed. You already produce enough thinking. The bottleneck is the gap between the moment a question lands in front of you and the moment you can place a specific, already-tested, already-worked-out idea into contact with it.
That gap is where most accumulated thinking goes to waste. Most people never name it correctly, so they solve the wrong problem. We start writing more and more. We have slop galore. And all the while, the gap stays exactly the same size.
So this has been a hunch I’ve been playing with: retrieval speed is the diagnosis for this issue and better infrastructure is the prescription for AI use.
Let’s talk about the idea of a “second brain” for a minute.
Here’s the myth you’ve, probably, been sold about a second brain: capture everything, tag it carefully, and insight will emerge. Build a beautiful Notion dashboard. Organize your bookmarks. Import your PDFs. The filing cabinet is the work.
The thing is, I think this is wrong. I’ve watched genuinely brilliant thinkers spend years assembling gorgeous archives that produce exactly nothing, because they confused storage with computation. A graveyard has excellent organization, too. That doesn’t make it alive and flourishing in any sense that doesn’t give us the heebie-jeebies.
The real issue is that storage is passive. A system designed only to hold your past cannot think alongside your future. What you actually need — and what almost nobody builds — is an architecture designed for collision detection.
This is something more than just bare retrieval. It’s worth dwelling on this for a second. Should I say it again, this is not retrieval.
Collision is about he system’s job: to surface the moment where your 2019 argument about faculty governance crashes into your 2023 argument about AI adoption timelines, and to do it before you sit down to write, not after. That collision is the insight. That’s where original thinking comes from. If AI helps us with that, this is genuinely novel and provides something worth using and developing.
Confusing collision and retrieval as I outlined them is a mistake that compounds. At the institutional level, it looks like the 18-to-24-month editorial cycle (and I’m assuming that isn’t an authentic hallmark of rigor because my own experience is that there is a lot of ‘waiting around’ in this process). Let’s just call that time what it is: rigor theater. By the time a manuscript clears three committee rounds and two rounds of revisions, the technology it describes has moved twice. In AI and higher education, a two-year lag becomes irrelevance, and it is baked into the process at the institutional level. The most important thinking in this field right now is not sitting in a submission queue. It’s publishing live on Substack and LinkedIn, tested against real readers in real time, iterated at the speed of the problem itself.
The gatekeepers aren’t protecting quality. They’re protecting process. Those are not the same thing, and the people still waiting for committee approval to say something important are going to lose the decade.
Here is what I actually built, because theory without architecture is just a longer complaint.
My foundation was not blank. I had a decade of monographs, book chapters, course syllabi, and a smattering of Substack posts. In total it was thousands of hours of ideas already written in my voice, already tested against real audiences. The problem wasn’t volume. I had more than enough work. The problem was really that given the volume the entire archive was static. It was filled with dead weight I couldn’t navigate under deadline. So my conversion task was specific: stop treating the archive as a monument to past effort and start encoding it as an operational system.
For me, that meant two layers. Distinct functions. Separation.
Layer one: an AI-query-able knowledge graph, encoded thematically using embeddings. Embeddings is the important part of this sentence. These are not tags, folders, nor keyword searches. When I draft, the AI queries this graph and surfaces connections I would never have found manually. Not “here is a similar document.” What I mean is: “here is where the argument you made about shared governance in 2021 creates a productive tension with the claim you made about distributed decision-making last fall.” That tension is a paragraph. That paragraph leads to a chapter. The speed everyone notices comes from having those connections pre-built, not from typing faster or letting AI do the writing itself for me.
Layer two: an Obsidian wiki that serves as the spatial visualization layer, and the AI does not touch it. This is a map of how my ideas relate to each other that mimics the structure of the embeddings, but includes hand processed elements I think are important. It is a structure I maintain deliberately, because the act of placing an idea on the map forces a precision that passive tagging never demands. If I cannot decide where something belongs in the map beyond the tagging, I don’t actually understand what the idea is yet. That friction is productive. I’m not trying to eliminate it.
These two layers perform different cognitive functions. One finds connections I can’t see. The other forces clarity I can’t skip. I can use the Obsidian wiki to look for nearest connections that the AI passes over. Using a single system for both jobs, which is the mistake I see most often, is how you end up with an expensive tool that still requires you to do all the thinking.
Your immediate directive is not to write more. It is to encode what you’ve already written in enough semantic depth that a system can do the cross-referencing your memory cannot. Human memory degrades, reorders itself around what feels recent, and loses the peripheral connections that produce non-obvious insight. A well-structured knowledge graph doesn’t. It holds the full map while you focus on the specific corner you’re building today.
The value of an idea is not what it meant when you wrote it. The value is whether it can be deployed at the moment of need, in a form the system can find, against the specific problem in front of you. If your ideas aren’t structured for application, they aren’t yours in any operational sense. They’re just things you once thought.
Patrick saw the output. He couldn’t see this. Build the graph, visualize the network, and stop managing an archive. You’re building a machine.