The decision is what job your organisation needs to do
Before choosing a note-taking system or adding more structure to the one you have, name the job you need help with. Are you trying to give a note a dependable home, surface a group of notes by a shared state, or show why two notes belong together? Folders, tags or properties, and links or backlinks can all make notes easier to reach, but they do different work.
It is also worth separating this from choosing an app. A tool may offer several of these mechanisms, but its presence does not tell you which job should lead in your own notes. The decision here is about the meaning you want a mechanism to carry, not about copying somebody else’s setup.
If your next question is how different note systems make these organisation mechanisms structurally available, see the note-taking system constraints reference.
A folder answers a location question. A tag or property answers a filtering question. A link answers a relationship question. Treating them as competing camps makes the choice harder than it needs to be. There is no universal winner, and a note does not need every mechanism. Once you can name the job, you can compare the broader PKM workflow territories without asking one feature to decide the whole system.
Three distinct organisation jobs
- 01
Folders
Primary job: Containment / location
Where does this belong?
- 02
Tags / properties
Primary job: Filtering / state
What kind of item is this, or what state is it in?
- 03
Links / backlinks
Primary job: Relationships / context
What is this connected to?
Use all three when each has a different job. A minimal system can combine them without making one mechanism carry every meaning.
A simple way to remember the difference: folders answer where a note belongs, tags or properties help you filter by type or state, and links show what a note connects to.
Folders give notes a bounded home
Folders are useful when a note needs a primary location: a project area, a client space, a subject, or another bounded context you expect to browse. A small hierarchy can make that location visible and gives related material a shared home. This is especially practical when you return to an area by navigating through the same places.
The limitation is not that folders are wrong. One note can reasonably matter in more than one context, and making every one of those contexts part of a single path can make the hierarchy brittle. Use a folder when location is the main job; do not make it carry every possible meaning a note may have.
Tags and properties surface notes across contexts
Tags and properties are useful when the important question is which notes should appear together, even though they live in different places. They can describe an intentionally repeatable dimension such as type, status, or context. A note can remain in its primary location while also appearing in a filtered set such as “to review”, “reference”, or “meeting note”.
This works best when the labels have a clear purpose and are used consistently. An uncontrolled collection of near-duplicate labels can become noisy: the reader has to remember which label was chosen and whether it means the same thing as another one. Add a tag or property because you expect to filter or group by that dimension again, not because every note needs a label.
Links and backlinks expose relationships and context
A link says that one note has an explicit relationship to another. It can create a route from a project note to a decision, from a source note to an idea, or from a question to supporting material. A backlink shows the reverse side of that explicit link, making it easier to see which notes already point to the current one.
That relationship is valuable only when it is meaningful enough to state. It does not automatically give the linked note a primary home, a state, a filter, or a complete organisation system. A link can connect two notes that are stored in different folders or share no tag. If your unresolved question is whether a local linked-note workflow fits your wider needs, you can explore a local linked-note route after deciding what role links should play.
Use a hybrid when the jobs are genuinely different
A hybrid is not a fourth method. It is simply a division of responsibilities when the jobs differ. You might keep a small folder structure for primary location, use a limited set of tags or properties for state or recurring context, and add links only for relationships that matter. Each mechanism remains easy to explain because it has a distinct reason to exist.
Do not turn that example into a rule that every note must follow. A short project may only need a folder. A collection that must be filtered across places may only need a property. A pair of connected ideas may only need a link. If you want a workspace where structured properties and relations are a relevant next question, you can explore a structured workspace route.
Choose the smallest system that solves the problem
Use the problem you can name to choose a neutral organising outcome:
- Folder-led: you mainly need a stable primary home and bounded context.
- Tag/property-led: you mainly need to filter across locations by repeatable state, type, or context.
- Relationship-led: you mainly need to navigate meaningful connections between notes.
- Hybrid: the jobs are different and a small division of responsibilities is clearer.
- Simplify first: you cannot yet name a retrieval or navigation problem that needs more structure.
Start with the outcome that describes the problem you face now. You can keep it small and revise it only when a concrete retrieval, filtering, or navigation need appears. The aim is not to create a complete system in advance; it is to make the next choice easier to explain.
These are organising outcomes, not app recommendations. When you are ready to turn the outcome into a focused shortlist, narrow a four-tool shortlist by workflow. If the remaining question is specifically about the way you develop and work through ideas, you can instead choose by your thinking workflow.