Don't Use Obsidian the Wrong Way 🔗 **Source:** [Don't Use Obsidian the Wrong Way](https://www.youtube.com/watch?v=kwvLCSmUDbg) > [!note]+ Document Notes > tags: [obsidian, note-taking, knowledge-management] > author: Nick Milo > source: YouTube > reference: https://www.youtube.com/watch?v=kwvLCSmUDbg > date created: 2024-12-19 10:30 > > # 🏷️ Title: Don't Use Obsidian the Wrong Way > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Reorganize current folder structure using broad categories — 00:00 #obsidian - [H2] Implement ACE framework for knowledge organization — 00:30 #structure - [H3] Create atlas, calendar, and efforts folders — 00:35 #setup ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Don't Use Obsidian the Wrong Way](https://www.youtube.com/watch?v=kwvLCSmUDbg) - [ACE Framework Details](MISSING) ## 📝 Summary - Nick Milo explains common Obsidian organization mistakes and provides better alternatives - Why it matters: Poor folder structure leads to difficulty finding notes and decision paralysis when organizing - Key stakeholders: Obsidian users, knowledge workers, note-takers - Risks and tradeoffs: Over-categorization vs. under-organization, complexity vs. simplicity - Bottom line takeaway: Start with broad folder categories and evolve to the ACE framework for better knowledge management ## 📖 Main Content The video addresses a fundamental problem in digital note-taking: creating overly specific folder structures that become counterproductive. Milo argues that random topic-based folders create friction when saving and retrieving notes, as users struggle to decide where notes belong and later have difficulty locating them. The recommended approach involves starting with the broadest possible categories (people, things, questions) and then evolving to a more sophisticated system called ACE: Atlas (for knowledge maps), Calendar (for time-based notes), and Efforts (for active projects). This progression allows users to develop organizational skills gradually while maintaining a functional system throughout the process. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=0) — [H1] Common Obsidian Mistake - Key idea: Users create too many specific topic folders - Evidence: "Don't just do this, making folders for random topics" #### ⏱️ [00:05](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=5) — [H2] Problems with Over-categorization - Key idea: Specific folders create long-term usability issues - Evidence: "it's actually pretty hard to find your notes or decide where they should go" #### ⏱️ [00:15](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=15) — [H2] Start Simple Strategy - Key idea: Begin with broad, inclusive categories - Evidence: "Start simple with big folders like people, things, questions" #### ⏱️ [00:20](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=20) — [H3] Maximize Category Size - Key idea: Create the largest possible folder categories - Evidence: "Make the biggest folder categories possible" #### ⏱️ [00:25](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=25) — [H2] Evolution Over Time - Key idea: Folder structure should mature as user experience grows - Evidence: "Over time, you can upgrade to a structure like this" #### ⏱️ [00:30](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=30) — [H1] ACE Framework Introduction - Key idea: ACE represents an advanced organizational system - Evidence: "My favorite ACE, the atlas for your knowledge" #### ⏱️ [00:35](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=35) — [H2] Atlas Component - Key idea: Atlas serves as knowledge mapping system - Evidence: "atlas for your knowledge" #### ⏱️ [00:37](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=37) — [H2] Calendar Component - Key idea: Calendar organizes temporal information - Evidence: "calendar for your timebased notes" #### ⏱️ [00:40](https://www.youtube.com/watch?v=kwvLCSmUDbg?t=40) — [H2] Efforts Component - Key idea: Efforts track active work and projects - Evidence: "Efforts are the things you're working on" ## 📚 References - [Don't Use Obsidian the Wrong Way](https://www.youtube.com/watch?v=kwvLCSmUDbg) - [Linking Your Thinking](https://www.linkingyourthinking.com/) - [Obsidian Documentation](https://obsidian.md/) ## 🗣️ Paraphrase - Avoid creating numerous specific topic folders in Obsidian as this leads to organizational confusion and difficulty retrieving information later - Begin with broad categorical folders like people, things, and questions to minimize decision friction when organizing notes - Gradually evolve your system toward the ACE framework which separates knowledge maps (Atlas), time-based information (Calendar), and active projects (Efforts) ## 📰 Newsletter **Better Note Organization in Obsidian: Start Broad, Evolve Smart** Many Obsidian users fall into the trap of creating overly specific folders, leading to decision paralysis and lost notes. Nick Milo's approach offers a better path: start with broad categories like "people," "things," and "questions," then evolve to the ACE framework (Atlas, Calendar, Efforts) as your system matures. This progression approach reduces friction while building organizational skills over time. Whether you're managing WordPress documentation, client projects, or personal knowledge, the principle remains: optimize for retrieval, not perfect categorization. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Documentation: Implement broad categorization for developer resources, avoid over-specific topic folders - Education: Create simple folder structures for workshop materials using people/things/questions approach - Developer experience: Organize API documentation using ACE framework principles #### Community - Contributors: Set up knowledge base with broad initial categories that can evolve - Maintainers: Use efforts folder for tracking active governance and technical initiatives #### WordPress - Documentation: Reorganize HelpHub and DevHub content using progressive categorization - Training: Structure lesson plans with Atlas (knowledge maps), Calendar (scheduled content), Efforts (active curricula) - Meta: Apply ACE framework to .org project documentation and team knowledge bases ## 🧪 Hypotheses - Broad initial categorization reduces note-taking friction compared to specific topic folders - Users with ACE framework organization retrieve information faster than those with random topic folders - Progressive folder complexity correlates with user skill development and system sustainability - Decision time for note placement decreases with broader category structures ### 📊 Methodology - A/B test comparing broad vs. specific folder structures measuring note retrieval time - Longitudinal study tracking user satisfaction and system evolution from simple to ACE framework - Comparative analysis of search success rates between organizational approaches ### ❓ Questions - What metrics best indicate when users are ready to evolve from simple to ACE framework? - How does folder structure complexity affect long-term system maintenance and user adoption? - Which broad categories work best for different types of knowledge work and professional contexts? ### 🔮 Future Research - Optimal timing for transitioning between organizational complexity levels - Integration patterns between ACE framework and other productivity methodologies - Cross-platform knowledge organization strategies for distributed teams ### 💡 Implications - Practice: Immediate reorganization of existing folder structures for better usability - Policy: Documentation standards should prioritize broad categorization over topic specificity - Education: Training programs should teach progressive organizational complexity rather than advanced systems first - Funding: Investment in knowledge management tools should consider evolutionary user needs ### 🧠 Learning Styles Assessment Reading level estimate: 8th grade #### 👀 Visual learners - Present: Folder structure examples, before/after comparisons - Improve: Diagram showing evolution from simple to ACE framework, visual taxonomy trees #### 🔊 Aural learners - Present: Video format with clear narration - Improve: Audio summary of key principles, podcast-style explanation #### 🗣️ Verbal learners - Present: Clear definitions of ACE components, analogies to physical organization - Improve: More detailed explanations of why each approach works #### 🧩 Kinesthetic learners - Present: Step-by-step folder creation guidance - Improve: Interactive folder restructuring exercise, hands-on practice templates #### 🧠 Logical learners - Present: Clear progression from problem to solution - Improve: Decision trees for categorization choices, metrics for measuring improvement #### 🧑‍🤝‍🧑 Social learners - Present: Community sharing of organizational approaches - Improve: Collaborative folder structure reviews, team organization workshops #### 🧘‍♀️ Solitary learners - Present: Self-directed implementation guidance - Improve: Personal assessment checklist, individual reflection prompts #### 🌿 Naturalistic learners - Present: Organic evolution metaphor for system growth - Improve: Ecosystem analogies for knowledge organization, natural categorization principles ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear video title and basic structure - Improve: Transcript with proper headings, alt text for any visual examples #### Keyboard navigation - Present: Standard YouTube controls - Improve: Chapter markers for easy navigation, keyboard shortcuts documentation #### Contrast and readability - Present: Standard video format - Improve: High-contrast thumbnail, readable font sizes in any text overlays #### Text resizing and reflow - Present: Video scales appropriately - Improve: Responsive transcript layout, resizable interface elements #### Media and captions - Present: YouTube auto-captions available - Improve: Professional captions, downloadable transcript, audio description #### Forms and interactions - Present: Basic video controls - Improve: Accessible like/subscribe buttons, clear focus indicators ### 🌍 DEIB Assessment #### Cultural breadth - Present: Universal organizational principles - Improve: Examples from different cultural approaches to categorization, global knowledge management practices #### Inclusive language - Present: Simple, clear terminology - Improve: Define technical terms, avoid productivity culture assumptions #### Neurodiversity support - Present: Short format, clear structure - Improve: Consistent pacing, predictable information hierarchy #### Representation - Present: Individual perspective - Improve: Multiple organizational style preferences, diverse use case examples #### Psychological safety - Present: Non-judgmental tone about current practices - Improve: Explicit validation of different organizational preferences ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear logical progression from problem to solution - Inductive strength: Generalizes from specific folder organization issues to broader principles - Causal reasoning: Establishes cause-effect relationship between folder structure and usability - Analogical strength: Limited analogies used appropriately #### Fallacies - False dichotomy: Presents only two approaches (wrong way vs. right way) without acknowledging valid alternatives - Appeal to authority: Relies on presenter expertise without substantial evidence #### Tone of voice - Overall tone: Authoritative but helpful, directive without being condescending ### 🛡️ DARVO Analysis - Deny: No denial present - Attack: No attacks on users or alternative approaches - Reverse victim/offender: Not applicable - Emotional cues and rhetoric: Positive, solution-focused language without manipulation ## 🎯 Conclusion The key takeaway is to start with broad categorical folders rather than specific topics when organizing notes in Obsidian, then evolve to more sophisticated systems like ACE framework as experience grows. This approach reduces decision friction while building organizational skills over time. Practitioners should immediately audit their current folder structures and consolidate overly specific categories into broader, more functional groupings. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Broad categorization reduces organizational friction > [!quote] [Don't Use Obsidian the Wrong Way](https://www.youtube.com/watch?v=kwvLCSmUDbg) by [[Nick Milo]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "Start simple with big folders like people, things, questions. Make the biggest folder categories possible." Establishes principle for initial knowledge organization structure avoiding decision paralysis. [view highlight](https://www.youtube.com/watch?v=kwvLCSmUDbg#H1) #xref #articleseed ID:rw_001 ### [H2] ACE framework provides mature organizational structure > [!quote] [Don't Use Obsidian the Wrong Way](https://www.youtube.com/watch?v=kwvLCSmUDbg) > "My favorite ACE, the atlas for your knowledge, calendar for your timebased notes. Efforts are the things you're working on." Advanced system separating knowledge maps, temporal notes, and active projects for experienced users. [view highlight](https://www.youtube.com/watch?v=kwvLCSmUDbg#H2) #xref ID:rw_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Over-categorization creates retrieval friction - Applies to any hierarchical information system - Pointer to 00:05 timestamp - Links: [[Knowledge-Management]] [[Information-Architecture]] #### [Z2] Progressive complexity matches user capability growth - Relevant for any skill-based system design - Pointer to 00:25 timestamp - Links: [[User-Experience]] [[System-Design]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Review personal folder structure for over-categorization — https://www.youtube.com/watch?v=kwvLCSmUDbg #fleeting #inbox - [F2] Research ACE framework implementation details — video reference #fleeting #inbox - [F3] Test broad category approach with current notes — immediate action #fleeting #inbox <!-- deep-read:sections end -->