> [!tldr] My own observations from changing my [[Obsidian]] to mimick [[Kepano's Vault]] In October 2026 I moved away from [[My Obsidian-Based Project Management System]] and started mimicking [[Other Bloggers#Steph Ango|The CEO of Obsidian]]'s vault (aka [[Kepano's Vault]]). ## About Leaving the [[PARA Method]]... Moving away from the [[PARA Method]] has been fine. I used it for... 5+ years, fairly effectively. But I think one of its "killer features" was the idea that the structure was meant to be mimicked *across your tools*. Thus it was a completely independent of tooling (much like my [[Simple Interchange Grammar for Identity and Linking|SIGIL]] idea), and (also like my [[Simple Interchange Grammar for Identity and Linking|SIGIL]] idea) was **not** necessarily a [[Local Maximum]] within any given tool. Since I only really use Obsidian - it made sense to [[What are You Optimizing For|optimize for]] [[Obsidian]]. ## Existing Problems Solved [[My Obsidian-Based Project Management System]] was great, but not perfect. Perfection is impossible, but this is new approach to the [[Tradespace]] of workable options solves some issues with my old approach: ### Partitioning is removed [[Cardinality is Always One of the Most Important Architectural Decisions]]. If you have multiple folders with the same type of information in them, you've made a 1-to-many association. In effective, you've saved a particular [[Pivoting]] view: "pivot by status", which you cannot easily undo. The [[PARA Method]] says you should have a top-level "Archive" that houses now out-of-date versions of your Projects, Areas, and Resources. That makes a **ton of sense – *unless* you have better means of filtering things by lifecycle state**. A simple and [[Systems Composability|Composable]] "status" property or `#archived` tag can achieve filtering without bifurcating similarly-typed things into multiple partitions. Also, adding new statuses (e.g. `#backlog`) is much easier. ### Miscellaneous Notes have a better home In the [[PARA Method]] you have the notion of "[[PARA Components#Resources|Resources]]". However, keeping that organized and relevant was always somewhat [[Anxiety]]-inducing. I didn't want to clutter my Resources with one-off notes that would otherwise drown out things that were "important". The new approach uses types and tags to enable to enable "floating" things to the top. ### [[Defining Project|Project]]s can more naturally consist of many files Projects are [[Markdown]] files in both systems. However in my old system I ran into issues with projects that got too large. Did I break them into smaller projects? Sometimes I needed a more general note to spawn out of a project. That note didn't have a place to go, unless I "promoted" it to being a *resource* **** # More ## Source - self