**Author:** [[3. Resources/Authors/Derek Reinhard|Derek Reinhard]] # Book Overview ![[GTD With The Bullet Journal Visual.excalidraw]] ## About the Author Derek Reinhard brings a distinct background to productivity writing. He spent years as a USAF pilot and staff officer, then became a Franklin-Covey instructor -- so he's been teaching people organizational systems long before GTD and Bullet Journaling existed in their current forms. He lives in Northern Virginia and has practiced GTD for years. The book grew from a specific frustration: he discovered the Bullet Journal method, loved its tactile simplicity, but found that most BuJo guides ignored the hard-won principles of serious productivity methodology. So he set out to reconcile the two systems, keeping GTD's structure intact while letting the Bullet Journal serve as its physical home. ## Central Thesis Reinhard's central argument is blunt: GTD is the methodology, and the Bullet Journal is just a tool. When the two conflict, the tool bends. Not the method. He calls this "bend the tool, not the methodology," and it runs through every page of the book. The Bullet Journal's rapid logging, collections, index, and migration features make it a surprisingly capable GTD implementation -- but only if you resist the temptation to let the notebook's limitations shape how you practice GTD. The moment you skip a context list because it's hard to maintain in a bound notebook, or collapse your horizons into a single page because you're running out of room, you've broken the system. The book walks through exactly how to map each GTD component onto BuJo structures. Next-action lists become collections organized by context. The someday/maybe list gets its own collection. Each of GTD's five horizons (ground level through 50,000 feet) gets a dedicated "Horizon Page." The standard BuJo Future Log gets replaced by a Calendex -- a more flexible date-reference system. And the Daily Log becomes the operational center where you actually work from each day. It's prescriptive and specific, which is exactly what a book like this needs to be. ## Why This Book Matters Most people who try to combine GTD with a Bullet Journal do it intuitively and end up with a hybrid that compromises both systems. Reinhard's contribution is showing that GTD's rules aren't suggestions -- they're load-bearing walls. Remove them and the whole structure collapses. The book matters because it takes two popular-but-often-misapplied systems and shows how they fit together without losing what makes each one work. For anyone who's tried GTD and drifted away, or who loves their Bullet Journal but feels like it's not actually making them more productive, this is the missing manual. --- # Chapter Summaries ## Introduction: Why Combine GTD and BuJo Reinhard opens with the observation that both GTD and the Bullet Journal have massive followings, but almost nobody talks about how to combine them properly. He positions the book as a bridge. The BuJo community tends to emphasize creativity and personalization; the GTD community tends to emphasize process discipline. Both are right, but the BuJo crowd often sacrifices process for aesthetics, and the GTD crowd often bounces between digital tools without finding one that sticks. The Bullet Journal, Reinhard argues, is the ideal GTD tool -- if you know how to set it up. ## GTD Overview: The Essential Rules This section distills GTD into its non-negotiable principles. Reinhard identifies three essential rules that most GTD practitioners eventually break: 1. **Maintain hard edges** -- every list in GTD (next actions, waiting for, someday/maybe, projects, calendar) must remain distinct. The moment items bleed across lists, you lose trust in the system. 2. **Scan/scan/scan** -- you must review your lists regularly, or they become graveyards of forgotten commitments. The lists only work if you look at them. 3. **Keep clearing inboxes** -- capture everything, then process it to zero. Stuff that stays in the inbox isn't in the system; it's noise. He also introduces the concept of "being ruthless" -- the willingness to delete, defer, or delegate items that don't earn a place in your system. Most people hoard tasks out of guilt. Reinhard says that's a system-killer. ## Bullet Journal Overview Reinhard covers the BuJo basics for readers who might be new to the method: rapid logging, signifiers, the key system, the index, and the concept of flow (migration and scheduling). He's careful to note that the Bullet Journal is a framework, not a fixed system. That flexibility is both its greatest strength and its biggest risk when pairing it with GTD. The BuJo doesn't tell you what lists to keep or how to organize your projects -- it just gives you a fast way to log and index information in a notebook. That's a blank canvas, and a blank canvas can become a mess. ## Putting It All Together: Setup This is the operational heart of the book. Reinhard walks through setting up a GTD-ready Bullet Journal from scratch: - **Index**: He uses a numbered index system that lets you track where every collection lives, even as the notebook fills up. Threading -- BuJo's technique for linking related pages across the notebook -- becomes essential here. - **Calendex**: Instead of the standard Future Log, Reinhard uses the Calendex method. It's a compact calendar grid where you note the page number of future items next to their date. This solves one of BuJo's biggest limitations: you can't easily move things to future dates in a bound notebook. The Calendex gives you a date-indexed reference without wasting pages. - **Horizon Pages**: Collections dedicated to each of GTD's five horizons. Ground level is your next-action lists. 10,000 feet covers your projects. 20,000 feet maps to areas of responsibility. 30,000 feet is goals (1-2 years out). 40,000 feet is your vision (3-5 years). 50,000 feet is purpose and principles. Most BuJo users skip this entirely, which means they're operating at ground level without any sense of direction. - **Context Pages**: Collections organized by GTD contexts -- @home, @computer, @errands, @calls, @office, @waiting-for, and so on. These are your actual working lists, the pages you scan when you have a few minutes and want to know what you can do right now given where you are and what tools you have. - **Daily Log**: The day-to-day operating page where rapid logging happens. Reinhard treats it as the command center. You start each day by reviewing your context lists and calendar, then use the Daily Log to capture what comes at you during the day. ## Start Living GTD: Projects and Worry-Free Living Reinhard covers how to handle GTD projects in the BuJo -- each project gets its own collection, threaded through the index. He emphasizes that a "project" in GTD is anything that takes more than one action to complete. Most people dramatically undercount their projects. He also discusses the BuJo's limitations honestly: it's a bound notebook, so you can't reorganize. You can't drag and drop. You can't search. The workarounds are good indexing, consistent threading, and the discipline to migrate items rather than let them rot on old pages. The "worry-free living" section connects back to David Allen's core promise: when everything is captured and organized in a trusted system, your mind stops trying to track it all. That mental release is the real payoff of GTD, and Reinhard argues the Bullet Journal's physicality makes it more trustworthy to your brain than a digital app you might forget to check. ## Staying On Track: The Weekly Review Reinhard calls the Weekly Review the most important habit in GTD, and the one most people skip. He maps it onto a BuJo-specific workflow he calls the "Weekly Frame" -- a structured weekly spread where you review all your horizon pages, context lists, calendar, and project collections. The tactile nature of flipping through physical pages, he argues, makes the review more engaging than scrolling through a digital list. You touch every page. You see your own handwriting. It's harder to skim past things. The Weekly Review process he outlines includes: clearing all inboxes, reviewing the calendar (past week and two weeks ahead), scanning every context list, reviewing the projects list, checking waiting-for items, and reviewing the horizon pages from ground level up through 50,000 feet. ## Getting Back On Track This short but honest chapter addresses what happens when your system falls apart -- because it will. Life gets busy. You skip a Weekly Review. Then another. Your inbox overflows. Your Daily Log becomes a dumping ground. Reinhard's advice: don't try to recover by going back through everything. Instead, start fresh. Set up new context pages, do a brain dump, and process it. The old pages are still in the notebook; you can thread back to them later. The goal is to get back to a trusted system as fast as possible, not to achieve archaeological completeness. ## Additional Tools Reinhard addresses two questions readers often ask. First: does this approach work without a Bullet Journal notebook? His answer is yes, in theory -- any notebook could serve as the physical tool -- but the BuJo's index and rapid logging conventions make it particularly well-suited. Second: he covers GTD's 43-folder tickler system and how to adapt it for the BuJo. The Calendex largely replaces the need for a physical tickler file, but he walks through alternatives for people who want that level of date-specific triggering. ## Final Thoughts Reinhard closes by reinforcing the book's core message: GTD is the system; the Bullet Journal is the container. Don't let the container's limits shrink the system. He encourages readers to start small, trust the Weekly Review, and give the combined system at least three months before evaluating whether it works. --- # Key Themes and Highlights ## Placeability and Findability Every organizational system faces two problems: where do I put this thing, and how do I find it later? Reinhard calls these "placeability" and "findability," and they shape every design decision in the book. GTD solves placeability through its category structure (next actions, projects, waiting for, someday/maybe, reference). The BuJo solves findability through its index and threading system. When both work together, items have a clear home and a clear retrieval path. When either breaks -- when you can't decide where something goes, or you can't find it after you've filed it -- the system fails. ## The Sacred Status of Hard Edges Reinhard is emphatic about this: GTD's lists must remain distinct. A next action is not a project. A someday/maybe item is not a next action. A calendar item is not a to-do. The moment you start mixing categories, you lose the ability to scan your lists with confidence. Hard edges are what make GTD trustworthy. Every time you look at your @computer list, you know that everything on it is a concrete action you can do right now, at your computer. No projects masquerading as actions. No aspirations pretending to be commitments. The Bullet Journal makes it easy to blur these boundaries -- after all, it's just a notebook, and you can write anything anywhere. Reinhard's setup instructions are designed specifically to prevent that blur. ## The Two-Notebook Principle One of the book's most practical recommendations is the two-notebook system. The GTD BuJo is your organized system -- context lists, horizon pages, project collections, Daily Log. The second notebook is your inbox/idea box, a separate capture tool you carry everywhere. The inbox notebook is messy and disposable. You write down whatever comes to mind, then process it into the GTD BuJo during your regular review. Mixing capture and organization in a single notebook violates GTD's hard-edges principle. It turns your organized system into a junk drawer. ## The Bullet Journal's Limitations (and Workarounds) Reinhard doesn't pretend the BuJo is perfect. It's a bound notebook. You can't reorder pages. You can't search. You can't easily share. Context lists fill up and need to be migrated to new pages. Projects sprawl across non-contiguous pages. These are real limitations. The workarounds -- indexing, threading, the Calendex, migration discipline -- add overhead. Reinhard's argument isn't that these tradeoffs are costless; it's that the benefits of a physical, analog system (focus, engagement, reduced digital distraction, tactile satisfaction) outweigh the costs for many people. ## The Weekly Review as Survival Mechanism If there's a single practice that determines whether a GTD system survives or dies, it's the Weekly Review. Reinhard has watched people build elaborate productivity systems and abandon them within weeks because they never established a review habit. The BuJo's physical nature helps here -- flipping through pages is more engaging than scrolling through an app -- but it's not automatic. The Weekly Frame gives the review a concrete structure: specific pages to check, a specific order, specific questions to ask. Without that structure, the review becomes a vague intention that you'll "get to this weekend." --- # Analytical Reading ## Main Arguments 1. GTD's principles are non-negotiable; the implementation tool must adapt to the method, not the reverse 2. The Bullet Journal is an excellent GTD tool because its rapid logging and collection system map naturally onto GTD's list structure 3. Every organizational system must solve both placeability (where does this go?) and findability (can I retrieve it?) 4. Hard edges between GTD lists are essential -- mixing categories destroys trust in the system 5. You need two notebooks: one for capture (inbox), one for the organized system 6. The Calendex replaces the standard BuJo Future Log and provides better date-indexed reference for GTD 7. Horizon Pages (ground through 50,000 feet) give you strategic perspective that most BuJo users lack entirely 8. Context lists (@home, @computer, @errands) are essential for GTD and map naturally to BuJo collections 9. The Weekly Review is the single most important habit for keeping any GTD system alive 10. When the system falls apart, start fresh rather than trying to reconstruct what you missed ## Methodology Reinhard's approach is prescriptive and experience-based rather than research-driven. He draws on decades of personal productivity practice, his background as a Franklin-Covey instructor, and his years practicing GTD. The book reads as a practitioner's guide -- here's what I do, here's why it works, here's how to set it up. He references David Allen's original GTD framework extensively and Ryder Carroll's Bullet Journal method, but the synthesis is his own. It's practical instruction, not theory. ## Strengths The book's greatest strength is its specificity. Instead of vague advice about "combining" GTD and BuJo, Reinhard gives exact setup instructions. Here's how to build your index. Here's what goes on your Horizon Pages. Here's the order of your Weekly Review. That precision makes the book immediately actionable. It's also honest about the Bullet Journal's limitations -- he doesn't oversell the tool. The two-notebook principle is a smart, practical solution to the capture-vs-organize problem that plagues most analog systems. And the emphasis on hard edges gives readers a clear diagnostic: if your lists are blurring together, you know exactly what's wrong. ## Limitations The book assumes familiarity with GTD's core concepts. If you haven't read David Allen's original book, some of Reinhard's shorthand (horizons of focus, the five phases of workflow management, the two-minute rule) won't land with full force. The book is also short -- around 76KB of extracted text -- which means some topics get compressed treatment. The digital-vs-analog question deserves more nuance; some GTD practitioners successfully use hybrid systems (analog capture, digital storage) that Reinhard doesn't explore deeply. The BuJo-specific setup instructions are detailed, but readers using other notebook formats (Traveler's Notebooks, disc-bound systems, loose-leaf) may need to adapt significantly. The book also doesn't address team or collaborative GTD in any meaningful way -- this is a solo practitioner's guide. --- # Personal Reflection ## Key Takeaways The "bend the tool, not the methodology" principle hit hard. I've been guilty of exactly what Reinhard warns against -- letting my notebook's physical constraints shape my productivity practice instead of the other way around. When a context list fills up, I tend to stop maintaining it rather than migrating it to new pages. When my index gets unwieldy, I stop using it. Both are symptoms of bending the methodology to fit the tool. Reinhard's framework gives me a clear rule: if the notebook can't accommodate a GTD practice, find a workaround in the notebook. Don't drop the practice. The two-notebook principle also clarified something I've struggled with. I've been using a single notebook for capture and organization, which means my "system" is constantly polluted with raw input that hasn't been processed. Separating capture (inbox notebook) from organization (GTD BuJo) creates the hard edge I've been missing. It's such a simple fix. The capture notebook can be messy, fast, and disposable. The GTD BuJo stays clean and trustworthy. ## Questions Raised - How does the Calendex handle recurring events and tasks? Reinhard covers one-time date-specific items well, but routines and habits seem harder to manage with this approach - What's the realistic lifespan of a single GTD BuJo before it fills up? And what's the transition process when you start a new notebook? - Could a disc-bound or Traveler's Notebook format solve some of the "bound notebook" limitations without sacrificing the analog benefits? - How does this system handle digital inputs? Email, Slack messages, and browser tabs are major capture points that don't naturally flow into a paper inbox - Is there a minimum number of items needed in a context list before it justifies a dedicated collection, or should every context always have its own page? - What role does the reference filing system play in the BuJo context? Reinhard mentions it briefly but doesn't offer a complete solution for non-actionable reference material ## Connections to Other Works - [[Getting Things Done]] by David Allen -- The foundational methodology. Reinhard assumes you've read it, and his book is essentially an implementation guide for Allen's system - [[The Bullet Journal Method]] by Ryder Carroll -- The other parent system. Carroll's book covers the BuJo philosophy and mechanics; Reinhard shows how to apply them within GTD's structure - [[Building a Second Brain]] by Tiago Forte -- Forte's PARA system (Projects, Areas, Resources, Archive) maps loosely onto GTD's horizons, but takes a digital-first approach that contrasts with Reinhard's analog commitment - [[Indistractable]] by Nir Eyal -- Eyal's timeboxing approach complements the Daily Log structure Reinhard describes - [[Feel-Good Productivity]] by Ali Abdaal -- Different angle on sustainability; Abdaal asks how to make the work feel good, while Reinhard asks how to make the system trustworthy enough that your brain lets go --- # Reading Notes - "Bend the tool, not the methodology" -- the book's thesis in six words. Every design decision flows from this principle - Three essential GTD rules: hard edges, scan/scan/scan, keep clearing inboxes. If you're only going to remember three things from GTD, these are the three - The two-notebook system (GTD BuJo + inbox/idea box) solves the capture-vs-organize confusion that plagues single-notebook approaches - Calendex as Future Log replacement -- a compact date-indexed reference grid that handles the "I need to do this on March 15th" problem without wasting pages - Horizon Pages for each of GTD's five levels are something almost no BuJo practitioner sets up, but they provide the strategic context that makes ground-level actions meaningful - Context Pages (@home, @computer, @errands, etc.) are the actual working lists -- the pages you scan when you're deciding what to do next - The Daily Log is the operational center, not a diary. It's where you work from, not where you reflect - Threading is BuJo's answer to the bound-notebook problem. When a collection fills a page, start a new page and note the connection in the index and on both pages - Migration discipline is essential: items that don't get done need to be actively moved forward or deleted, not left to rot on old pages - The Weekly Review process Reinhard describes: clear inboxes, review calendar (past week + two weeks ahead), scan all context lists, review projects, check waiting-for, review horizons from ground up to 50,000 feet - The "Weekly Frame" gives the review a physical structure in the notebook -- specific spreads for the weekly check-in - When the system falls apart, start fresh. Don't try to reconstruct. Set up new context pages, brain dump, process. Thread back to old pages later if needed - Placeability (where does this go?) and findability (can I retrieve it?) are the two core problems every organizational system must solve - Hard edges matter because they're what make scanning possible. If your @computer list might contain projects, aspirations, and reference material alongside actual next actions, you can't trust a quick scan - The book is honest about BuJo's limitations: no search, no reordering, no easy sharing. The workarounds (indexing, threading, Calendex) add overhead but preserve the analog benefits - GTD's 43-folder tickler system can be largely replaced by the Calendex in a BuJo context - Paper systems have a focus advantage over digital ones: you can't accidentally open Twitter while scanning your @errands list - The BuJo's physicality makes the Weekly Review more engaging -- flipping pages is more immersive than scrolling - Reinhard's USAF and Franklin-Covey background shows in his emphasis on discipline and process. This isn't a "make your notebook pretty" book; it's a systems engineering book wearing a notebook cover