What would be the best PKM for a sysadmin?

Knowledge management
2

I am not sure what exactly you are looking for, as in the title, you search for “the best PKM for sysadmins”, and later on, you mention “want to mush together” different areas :slight_smile: … but - this is my current folder structure (don’t want to show too much) …

image
image460×701 22.2 KB

When putting it together, I had PARA and CODE in my mind. I hope I can describe it with those words:

PARA Method:

  1. 000 Index:

    • Role: This is my Capture folder in the CODE method and an “Inbox” for PARA. It’s a place for temporary notes or ideas before sorting them into appropriate folders.

  2. 100 Projects:

    • Role: Clearly corresponds to the Projects category in PARA. I’ve subdivided it into actionable areas like Family, Personal, and Other, which is great for keeping projects organized and focused.

  3. 200 Knowledge Library:

    • Role: This is my Resources repository in PARA. Subfolders like Personal Growth (ToDo) and Harvested Knowledge organize non-actionable reference material, while Obsidian Help focuses on a specific topic.

  4. 400 Journal:

    • Role: Part of Areas in PARA, mostly using for running journal.

  5. 500 Life Areas:

    • Role: These align directly with the Areas category in PARA. Subfolders like Personal and Workspace represent ongoing areas of responsibility or focus.

  6. 900 Archive:

    • Role: This folder is my Archive in PARA, where inactive or completed items are stored.

  7. 999 Assets:

    • Role: This is a specialized resources folder, likely supporting all other PARA categories by providing templates, images, or other reusable assets.

CODE Method:

  1. Capture:

    • The 000 Index is my capture point, where ideas, notes, or inputs are temporarily stored before sorting.

  2. Organize:

    • The clear subdivision of folders into actionable (e.g., Projects), referential (e.g., Knowledge Library), and ongoing (e.g., Life Areas) categories aligns well with this step.

  3. Distill:

    • Folders like 200 Knowledge Library and 400 Journal support the distillation of ideas into actionable insights or references.

  4. Express:

    • Notes under 400 Journal (e.g., Running) and 100 Projects represent outputs, where distilled information is used to create content or track progress.

Observations:

  • Structure is robust and logical (for me!), blending elements of PARA and CODE effectively.
  • The only potential overlap is between Knowledge Library and Life Areas, as both could contain ongoing or passive resources. I might want to clarify their distinction further (e.g., Life Areas is actionable, Knowledge Library is purely referential).
  • The 999 Assets folder is a nice addition for shared resources, templates, and files that complement all categories.

Further ideas:

  1. Ensure notes in Knowledge Library and Life Areas don’t overlap in purpose. Use Knowledge Library strictly for static references.
  2. Regularly clear the 000 Index folder to avoid clutter.
  3. To maintain consistency, consider creating templates for project notes, journal entries, and resource organization.

As I said, this answer could not benefit you at all. But a not long time ago I was also searching for ideas for the “2nd brain” and from all those videos, articles, and books, … I came to the conclusion - no brain is the same, so also 2nd brand can’t be and the rule “one fit them all” doesn’t apply here :slight_smile:

I hope you find some great solutions for you, but keep in mind that this is an ongoing project which you’re adaption all the time.

Cheers, Marko :nerd_face:

1 Like