>
> # My Second Brain Playbook
>
> Method
>
> I recently read [Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential](https://www.amazon.com/Building-Second-Brain-Organize-Potential/dp/1982167386) by Tiago Forte. It was pretty good! But one thing that was missing for me was a clear operating procedure for how to interact with my second brain. This post outlines how I use my second brain.
>
> ☀️ **Daily (morning).** Start each day by asking: What do I want to accomplish today?
>
> 🌙 **Daily (evening).** End each day by asking: Did I accomplish today's goal? Capture any ideas that will help tomorrow.
>
> 💡 **In the moment.** When a thought or to-do pops up, capture it in my second brain and stay focused on the task at hand.
>
> 🗓️ **Weekly.** Block out thirty minutes to process my inbox, organize notes, review active projects, and check that my areas of responsibility are getting attention.
>
> 🚀 **When starting a new project.** Create a project file with the goal and target completion date.
>
> 📚 **After finishing a book or article.** Add a resource entry with key takeaways and any quotes that might be useful in the future.
>
> ⏱️ **Ongoing.** Add time estimates to to-dos and track how long things actually take. That feedback will help me estimate more accurately.
>
> I'd love to hear your thoughts!
>
>
5021
>
> ## Comments
>
> > **u/bobiq_ai** · 8 · Jun 20, 2026
> >
> > You skip the takeaway step because you've set it up as a separate chore that starts after you're already done and checked out. That's a timing problem, not a discipline one.
> >
> > Catch the takeaway when you react, not after. A line makes you stop, so you highlight it and add one sentence on why it hit you or what it connects to. That sentence is the takeaway, and it's cheap because you're still in the moment.
> >
> > Automating raw capture won't rescue this. Highlights and screen grabs aren't takeaways, the synthesis is, and it doesn't survive being deferred. Sit down to summarize a whole book later and the context that made each bit matter is already gone.
>
> > > **u/andrewmarder · _OP_** · 3 · Jun 20, 2026
> > >
> > > Great tip, writing down why I was motivated to highlight part of a book will be much easier in the moment when it's fresh, if I wait until after I've finished the book then it becomes much harder.
>
> > > **u/Fuzzy-Radio6153** · 1 · Jun 22, 2026
> > >
> > > True 👍
>
> > **u/Emergency_Lemon_8659** · 5 · Jun 19, 2026
> >
> > I find whenever I finish a book or article, im rarely doing the necessary step of recording the key takeaways.
> >
> > Is this a discipline issue? Should I try to find ways to automated?
> >
> > Would be great to know how you're managing that part.
>
> > > **u/andrewmarder · _OP_** · 1 · Jun 19, 2026
> > >
> > > I'm also struggling with that step. In the past, I found it helpful to write public book reviews on Goodreads. Overall, I do think it's about getting into the habit. My other plan is to export highlights from my kindle into my second brain but I haven't been doing that yet.
>
> > **u/secondgamedev** · 2 · Jun 19, 2026
> >
> > Hey I am trying to understand PKMS myself is it a knowledge base like Wiki? Or is it a workflow management tool like Jira?
>
> > > **u/LowkeyHooligan** · 3 · Jun 19, 2026
> > >
> > > It is whatever system works best for you personally to manage whatever knowledge that is important to you. That could be knowledge about yourself (e.g. your skills, habit tracker, journal of your thoughts) or external knowledge (you read an article/watch a video and want to remember some or all of it, you want to record some kind of facts/statistics from the world, a bird sighting journal, whatever).
> > >
> > > The idea of PKMS is pretty vague. There’s no one singular system, you can adopt multiple ones: physical bullet journal notebook, PARA email inbox, Johnny.Decimal for files on your computer. PKMS is more like a state of mind, but best manifested by having some sort of structured system. Which may involve using a particular tool, but it’s never about the tool, it’s about the system.
>
> > > **u/andrewmarder · _OP_** · 2 · Jun 19, 2026
> > >
> > > I think it can be whatever you want. Personally, I probably lean more towards task management than knowledge building.
>
> > **u/WillGreenAI** · 2 · Jun 22, 2026
> >
> > Obsidian + claude code for me has worked like a treat. I have a complete Personal OS, I run my business using obsidian and my personal life. It tracks my gym workouts, runs, finances, books and then I have Agent employees that run my business from inside obsidian. I've grown so much frmo it
>
> > **u/Mark_Considus** · 2 · Jul 3, 2026
> >
> > Love that! But there does appear to be one part missing, when do you delete?
> >
> > From your post, your weekly slot is all processing and organising, nothing about throwing anything away. To my mind, that's the part that keeps a second brain usable instead of just big. Capturing is cheap and it never stops, so without a regular clear-out you end up with a beautifully organised pile you can't see through. In that weekly 30 minutes I'd spend a chunk asking one thing of the older notes, would I miss this if it were gone, and binning whatever can't answer yes.
> >
> > The review is also where the real value lives, not the capture. Logging takeaways from a book is good, but they only do anything if something drags you back past them later. Same for the ideas you catch in the moment. A note you never return to did its job when it exited your head, everything past that is only worth keeping if you'll actually revisit it.
> >
> > I think there's small tweak, that will make a big difference. Make "what can I delete" a standing line in the weekly review, right next to "what needs attention".
>
> > > **u/andrewmarder · _OP_** · 2 · Jul 3, 2026
> > >
> > > Great insight, thanks!
>
> > **u/New_Dentist6983** · 1 · Jun 19, 2026
> >
> > ever thought about using screenpipe to capture the raw stuff before it turns into notes??
>
> > **u/Senhor_Lasanha** · 1 · Jun 22, 2026
> >
> > I use the "PARA" system (with stuff I added), and recently I partially adopted a documentation structure proposal from Google called OKF. It helped me organize and share knowledge from my vault with LLMs.
>
> > > **u/looktwise** · 1 · Jun 22, 2026
> > >
> > > could you write more details about the OKF-adaption? Thanks!
>
> > > > **u/Senhor_Lasanha** · 1 · Jun 22, 2026
> > > >
> > > > here: [How the Open Knowledge Format can improve data sharing | Google Cloud Blog](https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing)
> > > >
> > > > it's made for coding documentarion, but the way i see it, it is a good start for those who area struggling with standardization. I read the spec document ([here](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md)), and took some of the ideas.
> > > >
> > > > The yaml frontmatter and the index.md thing, I thing are the ones with most impact.
>
> > **u/h4yfans** · 1 · Jun 23, 2026
> >
> > if you ever want the playbook to live in fewer apps, a few that keep notes, tasks and projects on one surface: amplenote, tana, and memrynote (disclosure, i build that last one) for the "a project file whose lines are the actual tasks and dates" flow your routine basically describes. obsidian plus the tasks/dataview plugins gets you there too if you like assembling it. your procedure is tool-agnostic and good, it'll just survive longer with fewer seams between the steps.
>
> > > **u/andrewmarder · _OP_** · 1 · Jun 23, 2026
> > >
> > > Hi Kaan, memrynote looks nice! Right now I'm using org mode. In the past, I've also used Obsidian and Super Productivity.