Minimalist, project-oriented, research-oriented, and PKM-oriented setups each trade a specific strength against a specific cost, and they can live side by side in separate files.
A style is a coherent set of choices about which features you lean on. Four are common enough to name, and naming them helps you pick deliberately instead of drifting.
Minimalist
A few files, Capture, Agenda, links, and no external packages. This is the lowest-maintenance option and the best starting point. Its cost is modest: less automated backlink discovery, because you are not running a tool that builds the graph for you.
Project-oriented
Properties, deadlines, dependencies, effort estimates, clocking, and dashboards. Strong for individual execution when you actually read the numbers. It becomes bureaucracy the moment the metadata stops driving decisions: effort values nobody consults, dashboards nobody opens.
Research-oriented
Citations, Babel, tables, figures, export, and immutable inputs. Its strength is provenance: you can trace a figure back to the data and the code that produced it. The cost is that external runtimes and reproducibility discipline add real complexity to maintain.
PKM-oriented
Many small notes, IDs, maps of content, and optionally Denote or org-roam. Strong associative retrieval. You find your way back to ideas by their links. The failure mode is accumulating fragments without synthesis: a large vault of notes that were never connected into anything.
Let them coexist
These styles can live in separate files without conflict. The real mistake is forcing journal entries, operational tasks, academic sources, and permanent notes into identical templates. A daily log does not want citation keys; a source note does not want a clock table. Match the template to the work, and keep the pieces apart.
Summary. Four recognizable Org styles suit different work. Each has a real advantage and a real failure mode. They coexist across files; the mistake is forcing journal entries, tasks, academic sources, and permanent notes into one identical template.
Exercises
- Basic: Name the four styles and state each one's single greatest strength in your own words.
- Practical: Classify your own current or planned Org use into one of the four styles, and write down the failure mode you are most at risk of.
- Advanced: Design a two-file setup that combines two styles (for example a minimalist `inbox.org` alongside a research-oriented `sources.org`) and justify why they stay separate rather than merging into one template.