> [!khiip-reddit] Reddit · Text
> <span class="khiip-mark"><svg viewBox="-1 -1 50 50" width="15" height="15" fill="none" stroke-linecap="round" stroke-linejoin="round" aria-label="Khiip"><g stroke="currentColor" stroke-width="3.8"><path d="M14 16 L1.27 28.73"/><path d="M17.33 19.05 L7.48 37.6"/><path d="M20.67 20.89 L16.09 42.4"/><path d="M24 21.5 L24 44.5"/><path d="M27.33 20.89 L31.91 42.4"/><path d="M30.67 19.05 L40.52 37.6"/><path d="M34 16 L46.73 28.73"/></g><path d="M14 16 Q24 27 34 16" stroke="currentColor" stroke-width="4.8"/><g fill="currentColor"><circle cx="8.27" cy="21.73" r="2.3"/><circle cx="4.83" cy="25.17" r="2.3"/><circle cx="12.90" cy="27.40" r="2.3"/><circle cx="10.24" cy="32.41" r="2.3"/><circle cx="18.61" cy="30.57" r="2.3"/><circle cx="17.37" cy="36.38" r="2.3"/><circle cx="24" cy="31.85" r="2.3"/><circle cx="24" cy="38.06" r="2.3"/><circle cx="29.39" cy="30.57" r="2.3"/><circle cx="30.63" cy="36.38" r="2.3"/><circle cx="35.10" cy="27.40" r="2.3"/><circle cx="37.76" cy="32.41" r="2.3"/><circle cx="39.73" cy="21.73" r="2.3"/><circle cx="43.17" cy="25.17" r="2.3"/></g></svg></span>
> # My Second Brain Playbook
>
> r/PKMS · [u/andrewmarder](https://www.reddit.com/user/andrewmarder) · Jun 19, 2026 · Method
>
> 50 points · 21 comments
>
> 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!
>
> ## Comments
>
> > [!tip] 🔒 **Upgrade to Khiip Plus** for the full thread
> > Base captures top-level comments only (21 total comments). Khiip Plus expands every reply into the complete nested tree.
>
> **u/bobiq_ai**
> 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/Emergency_Lemon_8659**
> 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/secondgamedev**
> 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/WillGreenAI**
> 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**
> 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/New_Dentist6983**
> ever thought about using screenpipe to capture the raw stuff before it turns into notes??
>
> **u/Senhor_Lasanha**
> 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/h4yfans**
> 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.