This PKM tool decision map helps you compare five ways to organise, connect and use your notes before choosing an app. Begin with the work you need to do: keep shared reference pages, build a personal archive, think in linked blocks, connect structured information or study through regular recall.
PKM means personal knowledge management: the system you use to keep notes, sources, ideas and questions available for later work. For example, a solo researcher may need a local archive of source notes and emerging questions, while a small editorial team may need shared briefs and an article-status database. The map separates those jobs before you compare apps.
When you know what kind of work the tool must support but still need to check a practical constraint, see the note-taking system constraints reference. It compares tools by data location, offline use, note structure, links, export, collaboration and reliance on a vendor service.
The tools shown are examples, not an exhaustive list. Some fit more than one category; use the map to identify approaches worth investigating.
The decision map
Five ways to organise knowledge work
Choose how you want to work with notes before comparing apps
Explore tools grouped by the work they are designed to support.
01
Workspace documents and databases
Shared docs, project references and flexible hubs.
Notion · Craft · Evernote
02
Local-first notes and files
A durable personal collection close to your files.
Obsidian · Logseq OG · Joplin
03
Outlines and linked blocks
Nested ideas, daily capture and reusable blocks.
Roam Research · Workflowy · Tana
04
Structured knowledge objects
Linked records for people, sources and ideas.
Capacities · Anytype · Heptabase
05
Study and memory systems
Convert important material into a recall practice.
RemNote · Anki
How to read the map
Start with the work you return to most often. A shared project hub and a personal research archive can both contain notes, but they make different assumptions about ownership, structure and collaboration. Some tools fit more than one group, and your needs may change. Let the work you do most often guide your choice. If the remaining question is whether a folder, a tag or property, or a link should do a particular organising job, read Folders, tags and backlinks: what each is for in your notes before comparing apps.
Compare the five approaches
| Decision dimension | Workspace documents and databases | Local-first notes and files | Outlines and linked blocks | Structured knowledge objects | Study and memory systems |
|---|---|---|---|---|---|
| Information model | Pages, databases and shared spaces | Personal notes and local app data | Nested blocks, references and daily flow | Typed entities, properties and visual context | Notes or cards paired with review |
| Ownership and portability | Check export and workspace controls | Check storage and sync choices first | Check export before committing a large archive | Check object export and deployment choices | Check deck, note and review-history exports |
| Primary work | Team knowledge, projects and documents | Personal research, writing and archives | Thinking in motion and connected capture | Research across people, sources and concepts | Learning material that must be recalled |
| Collaboration and sharing | Often central to the workflow | Usually a separate design decision | Useful selectively; varies by product | Useful when a shared model is intentional | Usually secondary to individual practice |
| Structure and retrieval | Views, properties, pages and search | Folders, links, tags and queries | Indentation, references and search | Types, relations, properties and boards | Decks, prompts and due review queues |
| Setup tolerance | Moderate; model the workspace to the work | Moderate to high; choose structure and sync | Low to high; habits shape the result | Moderate to high; design useful types first | Moderate; consistent review matters most |
Decision categories
Workspace documents and databases
This approach fits work that needs pages, shared reference material and flexible views of structured information. Notion is worth considering when you need a collaborative workspace; Craft and Evernote show adjacent document and organized-note approaches. The trade-off is that export, permissions and workspace design matter more as the system becomes central to a team.
Local-first notes and files
Choose this direction when a personal archive, offline resilience or a deliberate storage model matters before polished sharing. Obsidian, Logseq OG and Joplin illustrate different ways to keep a knowledge system close to local data. OG keeps ordinary Markdown files; the separate Logseq database app is also local but stores its graph in SQLite. The trade-off is not a lack of capability; it is the need to make considered decisions about sync, conventions and, in some cases, extensions.
If the storage, offline and collaboration trade-off needs more attention before you compare a product, read how to choose between local-first and cloud note-taking.
Outlines and linked blocks
These systems make it natural to capture ideas as nested pieces, revisit them through references and let structure emerge while you think. Roam Research, Workflowy and Tana are representatives, but they do not impose the same level of structure. If you are moving away from Roam, use the focused Roam Research alternatives guide to choose by the constraint that changed.
Structured knowledge objects
You can create a record for a person, book, source, meeting or idea, with its own fields and links to related records. Capacities, Anytype and Heptabase show three different approaches to that model. It is useful when connections and context are the work; it can be excessive when you only need to write and find ordinary notes.
Study and memory systems
RemNote and Anki belong here because their central promise is not simply storing information, but returning important material for recall. This is a different commitment from maintaining a general archive: the benefit depends on regular review. Choose it when remembering is a primary outcome, not merely an occasional feature.
How the PKM decision map helps narrow your starting point
See how the work you do can guide a note-taking app comparison.
Want to work through the decision offline? Download the printable PKM decision guide (PDF, 7 pages).
Where the PickTheTool pickers help
The map answers the broad orientation question: “Which kind of system should I investigate?” The existing PickTheTool pickers answer a narrower question when you are comparing Notion, Obsidian, Logseq OG and Roam Research. They do not rank or recommend every tool on this map.
Use the Note-taking Apps Picker for everyday capture and retrieval. Use the Thinking Tools Picker for developing and connecting ideas. Both compare the same four tools.
How to use this comparison
Last reviewed: 27 August 2026. The examples are based on official product documentation and are not an exhaustive list. Use them to identify promising approaches, then check the current storage, sharing and export options of any tool you might adopt.
