Personal knowledge management without apps

Updated: October 29, 2026

Personal knowledge management, or PKM, is often reduced to choosing an app. In practice, it is a system for working with knowledge: how you capture, find, revisit, and connect ideas. An app can help, but it does not replace the system. Here is a practical setup that does not depend on a service.

What PKM is

PKM answers a few questions. Where do notes live? How do you find the right one a year later? How do you return to an idea and develop it? How do you connect new information with what you already know? How do you avoid losing what matters in the flow of information?

An app solves only part of this. It provides storage, search, and sometimes connections. The habit of writing, the review, and the ability to ask good questions remain with the person.

So a system without apps starts not with a tool but with a few simple rules.

Capture

Capture must be fast. If there are too many decisions between a thought and a record, some thoughts never get written down.

• One inbox file for new notes.
• A date and a short context.
• No category at capture time.
• A source link when the note comes from an article, book, or conversation.
• Simple markers: Idea:, Question:, Quote:.

Do not try to sort everything into folders immediately. Capture first, process later.

Search and structure

Search is usually more useful than a complex hierarchy. Full-text search finds a word, date, or project name even if you forgot where the note was stored.

Structure matters when it answers a real question. For example, when you separate work from personal life or keep several long projects apart. If there is no such question, folders and tags become extra work.

The minimal set is search across the file, dates, and a few markers. If you have many files, rg across a folder helps. See the article on search and automation for more.

Review

Without a review, the archive turns into a pile. Knowledge does not work on its own if you never return to it.

1. Day. Write thoughts and tasks as you work.
2. Week. Review new notes, close finished tasks, and mark topics worth returning to.
3. Month. Find repeated ideas, delete what is no longer useful, update links and the archive.
4. Year. Go through old notes and move what matters into summary notes.

A review does not need an app. It needs time and a few questions: what did I learn, what changed, what should happen next.

Connections without a graph

A graph and backlinks are useful, but not mandatory. Connections can be maintained manually with links to dates, project names, and recurring themes.

• Reference older notes by date or title.
• Keep summary notes for important topics.
• Move repeated ideas into one section.
• Do not create a connection just for the sake of it. It should help you return to a thought.

If connections and research take most of your work, Obsidian or a similar tool may be more convenient. See the comparison One Big Text File vs Obsidian vs Notion.

AI as a reader of the archive

Language models are useful not only for generating text. They help read a personal archive: find themes, make summaries, answer questions, and compare notes.

For small files, search and manual context are enough. For large archives, you need an index and RAG. One rule matters: the model helps you read, but your text remains the source. Answers must be checked against dates and entries.

More on this: RAG over a personal text file and a paper notebook, OBTF, and LLMs.

The minimal stack

• One text file or a small folder.
• An editor that opens plain text.
• Search with Ctrl+F, rg, or grep.
• Sync across devices when needed.
• A backup and, when necessary, encryption.
• A calendar for tasks with deadlines.

This is enough for a personal knowledge system. Add an app only when a specific task cannot be solved with this set.

When an app is still needed

An app is justified when you need collaboration, shared databases, permissions, complex projects, recurring reminders, or mobile capture. If those features are used every day, the tool pays for itself.

If they are needed rarely, an app often adds work. See the article on overrated note-taking and to-do apps.

How to start

1. Create one file for notes.
2. Create one inbox file for new ideas and links.
3. Set up search and a backup.
4. Run the first weekly review.
5. After a month, decide what is missing: connections, tasks, AI, or an app.

A ready example is in the starter file. For a broader overview, read plain text note-taking. To go deeper, start with the main OBTF guide and the OBTF philosophy.

Checklist

• There is one inbox file for new notes.
• Notes have dates and a short context.
• Search works across the whole archive.
• A short review happens every week.
• Connections are maintained manually and with purpose.
• AI is used as a reader, not as a source of facts.
• An app appears only for a specific job.