why I stopped bullet journaling for 6 months
Based on Mariana Vieira's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Simplify the journal’s visual style to keep logging fast; perfectionism can make the system collapse during busy weeks.
Briefing
Bullet journaling can work as a powerful planning system, but six months of stopping it came down to five recurring friction points: perfectionism, weak note capture, missing structure for future events, overbuilt monthly layouts, and an indexing system that didn’t reliably help her find information. The biggest drag wasn’t the method itself—it was how she tried to make it look “right” and how that slowed logging until the journal stopped being useful.
Perfectionism set the tone early. She disliked crossed-out words, mistakes, templates that didn’t fit, and the time spent filling space with perfect handwriting, ruler-straight lines, and careful drawings. When weeks got busy, she couldn’t keep up with the visual standards, so she “slacked” and eventually abandoned the journal. Over time, she realized the journal’s value comes from simplifying the look so logging stays fast and efficient—less Instagram-style artistry, more reliable capture.
A second issue was how she handled notes. She didn’t use the slash to mark notes, treating task logging as separate from random thoughts and snippets. That separation left her without a dedicated way to store information gathered from reading. After revisiting Reiner Carroll’s bullet journal method, she adopted the idea that notes should be captured like tasks—then migrated later if they can become actionable.
She also stopped using the Future Log, the early pages meant to hold scheduled events that don’t require immediate planning. Without it, her journal lacked a proper repository for upcoming commitments, and she felt pulled toward building a planner-like structure that could schedule by date rather than by priority.
Her monthly workload became the final breaking point. She tried to create complex spreads every month—monthly and weekly reviews, goal-setting, wishlist projects, and planning—so the journal became “high maintenance.” When a busier week or month arrived, she couldn’t complete the setup to the standard she expected, and the system felt useless.
Finally, she struggled with indexing. She didn’t like numbering pages or writing down what each page contained, and she also described a more robust approach: numbering pages and adding continuation page numbers for multi-page collections (for example, noting that a project spans three pages so it can be referenced later). The takeaway is clear: bullet journaling works best when capture and retrieval are quick, structure is consistent, and the system doesn’t demand perfect execution every month.
Cornell Notes
After six months away from bullet journaling, Mariana Vieira traced the failure to five practical problems: perfectionism that slowed logging, not using the slash for notes, skipping the Future Log, building overly complex monthly spreads, and an indexing system that made information hard to retrieve. She learned that notes should be captured like tasks and migrated when they can become actionable. She also emphasized simplifying the journal’s look so it stays fast and efficient, especially during busy weeks. The Future Log matters because it provides a place for scheduled events that don’t need immediate planning. Finally, reliable numbering and indexing—especially for collections spanning multiple pages—turns the journal into a usable reference tool.
How did perfectionism undermine bullet journaling’s usefulness?
Why did she change how she handled notes from reading?
What role does the Future Log play, and what happens when it’s skipped?
Why did complex monthly spreads lead her to stop bullet journaling for months?
What indexing approach improved her ability to find information?
Review Questions
- Which specific behaviors made logging slow for her, and how did she adjust them to keep the system usable during busy weeks?
- How does capturing notes with the slash support migration, and why does that matter for turning ideas into actions?
- What are the consequences of skipping the Future Log, and how does indexing affect retrieval when collections span multiple pages?
Key Points
- 1
Simplify the journal’s visual style to keep logging fast; perfectionism can make the system collapse during busy weeks.
- 2
Use the slash to mark notes so random thoughts and reading takeaways have a dedicated capture method.
- 3
Treat notes like tasks: lock them down, then migrate them when they can become actionable.
- 4
Include a Future Log for scheduled events that don’t need immediate planning; skipping it leaves the system incomplete.
- 5
Avoid building overly complex monthly spreads that require perfect execution every month.
- 6
Use a reliable indexing and page-numbering approach, including continuation page numbers for multi-page collections, to make past information easy to retrieve.