PARA was designed to increase and simplify creative output. It can be used for other things as well, but it’s not optimized for that. In ±PEAKER, we have a more holistic system where creative output can be part of the equation, but so can direction-setting (Protocols), identity work (Arcade), creative entropy (Keep), long-memory incubation (Exclave), and inert retrieval (Records), all of which fall short in a plain PARA setup.
Migrating from PARA to ±PEAKER is straightforward once you make the mental shift from an output‑centric buckets to a living system for becoming. Here, I want to provide a practical, step-by-step guide on migration away from PARA only. I’ve written an in-depth series on the rationale behind ±PEAKER and how it evolved from my modded PARA method. So if you are interested in the more meaty version, read:
Step 0 — Create the ±PEAKER org spaces
Create eight org spaces (top‑level folders/groups/directories) as follows:
+
-
1 Protocols
2 Efforts
3 Arcade
4 Keep
5 Exclave
6 Records
💡 Use the number prefixes to get the right sorting (if needed)
💡 If you already have an Inbox, you can simply rename it to+(if possible)
💡 Immediately add these to Finder/Explorer favorites or sidebar for muscle memory.
Step 1 — Initiation
Bulk‑sweep your current PARA spaces into + (the Inbox). That’s all it takes to have a first working ±PEAKER implementation.
Option: PKM bankruptcy. If you truly want a clean slate, put everything from + into a single subfolder (e.g., PARA-Archive-2025-09-22) and move that one folder into Records. You’re done.1
Step 2 — Redistribution
Work through the Inbox one PARA space at a time, routing contents with the rules below. Keep this guide visible while you do it.
Move every Project container into the Efforts space.
For an Area container that encodes a role/identity (e.g., Father, Partner, Employee, Author, Home Owner), move it to Arcade. Keep only role‑enabling artifacts here: rituals, reviews, checklists, playbooks, standards, and reflections. Do not stash lifeless documents (bills, certificates) here. Move those to Resources.
For an Area container that is a broad topic (Health, Finance) with mixed stuff: First, try to re‑express it as one or more roles (Strong Avatar, Family Provider) — if possible, this goes to Arcade. Move all all inert paperwork to Records.
For Resources & Archive, we have to split them up to Keep / Exclave / Records
Records: static artifacts for retrieval only (invoices, contracts, templates, manuals, exports, backups, IDs, warranties).
Exclave: heavy or multi‑file clusters that are not active but not dead (PDFs, datasets, long‑form references, dormant but promising clusters, paused areas/efforts you might revive). Think of it as your digital greenhouse.
Keep: notes, quotes, sketches, half‑formed ideas, concept maps, article clippings with your highlights or commentary. Short: everything else!
Rule: The Keep has no subfolders. Navigate by links, tags, and search.
💡 If you’re unsure, default to Exclave. You can always promote to Efforts or demote to Records later.
💡 If you have custom PARA mods (e.g., Incubator) route with the same thinking/activity heuristics above.
Checkpoint: At the end of Step 2, your top level should have only the eight ±PEAKER spaces. + and Protocols should be empty for now.
Step 3 — Tuning (the fun part)
Now make the system yours. This is where the migration pays off.
3.1 Protocols: stand up your compass
With a fresh mind and short-term memory of all the stuff you just moved, brainstrom and populate Protocols with lightweight, high‑leverage artifacts:
annual-themes/(past + current focuses)principles/,core-values/goal-setting/(rituals, OKRs/OGSM, quarterlies)SOPs/(personal checklists and playbooks)realms/(major arenas of life)codex/(naming conventions, emoji legends, highlight codes)favorite-quotes/(small curated trove)
💡 Keep Protocols crisp. This space guides decisions; it’s not a scrapbook.
💡 Tip: do a second pass after you finished the rest of Step 3.
3.2 Efforts: get visibility
Try to bring convert your efforts down to a single note and a status (WIP, pending, done, …). If you identify clear clusters in your Efforts folder, add org containers for them. Exile heavy reference/support material to the Exclave.
3.3 Arcade: encode your roles
For each role, add: Standards, Rituals/Reviews, Scorecards or Prompts. Keep role‑irrelevant admin out (move to Records). Brainstorm other roles you have but are not currently represented in your system. Feel free to add empty containers for them.
3.4 Keep: enforce oneness
Don’t group; confirm there are no subfolders left.
3.5 Exclave: curate the greenhouse
Group by meaningful clusters (e.g., Readwise/, Book Summaries/, Talks/, Workshops/, Articles).
3.6 Records: make it boring (on purpose)
Group by type, not topic. Examples: tax-receipts/, manuals/, templates/, backups/, insurance/, employment/, config/, images/.
3.7 ± Flow: wire intake & release
Create quick‑capture shortcuts that drop into + (share sheets, email rules, mobile shortcuts). Use - as your out‑tray for drafts to ship, items to archive/delete. Sweep it regularly.
3.8 Reviews & rhythms
Ideally, opt for the following reviews:
Weekly: Empty
+, triage-, update Effort statuses.Monthly: Light Exclave pass; one role spot‑check in Arcade.
Quarterly: Protocols refresh (themes, goals), consider if a Vault has emerged.
3.9 Vaults (±PEAKER‑V mode)
Create a Vault when a cluster is big, sensitive, or product‑bound enough to deserve its own world (e.g., a client project, a public codebase, your book). Signals you’re ready:
Many inbound links from elsewhere; few outbound.
Concepually standalone topic.
Could be packaged up and sold as a product.
Use Vaults sparingly to prevent fragmentation.
Step 4 — Iterate
After all this work, you will have a working system but you won’t be finished. Even if your file base is small and everything were perfectly sorted now, your mind surely hasn’t yet followed. Rest assured, it will take a few weeks until you unlearn PARA thinking and learn ±PEAKER thinking. In the next few days and weeks, focus mostly on keeping ±PE alive, AKER will follow. The idea of The Keep and The Exclave may need the longest to get used to.
I hope this was useful!
Let me know in the comments if this guide left any questions unanswered 👇
Not recommended. You likely have a lot of value worth recapturing during redistribution—but it’s valid if you’re time‑starved or your previous system has been abandoned for months.