Today tells you what's new; your library, what you know
- A daily view and a library do different jobs. The first answers what changed since yesterday; the second answers what you know about a subject after months of reading.
- Filing by source records how information arrived, not what it is about. One development usually spans several sources, so a source-shaped library scatters it.
- Folders freeze the categories you had when you set them up. Grouping by theme should follow the material, and some items should stay ungrouped until a pattern appears.
- Keep developments with their provenance, drop repetitions, and let quiet days stay empty. The gaps in a theme's timeline carry information of their own.
- A library earns its keep when it feeds new work: the meeting prep, the decision memo, the article that starts from a theme instead of a blank page.
Why do you need both a daily view and a library?
You need both because they answer different questions. A daily view answers "what changed since yesterday?"; a library answers "what do I know about this subject?" after months of reading, and no amount of the first adds up to the second on its own.
The daily view is built for recency. It should be short, it should be gone tomorrow, and it should leave you knowing what moved. The library is built for retrieval. It should grow slowly, keep its shape over time, and be ready when a question arrives that you did not plan for.
Most reading setups do one of these jobs. Many do neither: an inbox full of newsletters is not a good daily view, because nothing is selected, and it is not a library either, because nothing is organized.
What goes wrong when one tool tries to do both jobs?
When one tool does both jobs, it usually does the daily job and fakes the library. The result is a long scroll sorted by date, where "what do I know about X" becomes a search box and a hope.
The failure shows up in a few recognizable ways:
- The library is the feed, scrolled backward. Finding last spring's development means remembering roughly when it happened.
- Search returns items, not understanding. A keyword query lists forty matches in no meaningful order, and the reader has to rebuild the story by hand.
- The daily view gets heavy. To make the archive useful, people start keeping everything, and the daily view fills with items that were only saved "just in case."
The two jobs need different shapes. A daily view is a list ordered by time. A library is a set of themes, each with its own history.
Why is organizing by source not enough?
Organizing by source is not enough because a source tells you how information arrived, not what it is about. Subjects cross sources, so a library shaped like your subscriptions scatters every story it holds.
Consider a reader following power demand from data centers. In one month, the relevant material arrives from a utility's regulatory filing, a chipmaker's earnings call, a regional planning notice and an energy analyst's posts. Filed by source, that single development sits in four drawers, and none of them tells the story.
Vannevar Bush named this problem in "As We May Think," his essay on the memex. Under conventional indexing, he wrote, an item "can be in only one place, unless duplicates are used", while the mind "operates by association." A source folder is that single place.
Source still matters. It belongs on every item as an attribute you can filter by and click through to, not as the shelf the item sits on.
Folders or automatic grouping: which organizes a library better?
Automatic grouping by theme organizes a growing library better than folders, provided the reader can see and correct the groups. Folders work at small scale and decay as subjects shift.
Folders have two costs. They ask for a decision at the moment of reading, when you know least about where a story is going. And they freeze the categories you had on the day you created them, so a subject that splits in two, or merges with another, stays filed under an outdated map.
Grouping by theme follows the material instead. Items that describe the same development or question gather together, and a theme can split when it grows two distinct threads. The risks are real: groups that are too broad to be useful, or an item placed in the wrong theme. A good system shows its groupings openly and lets the reader move, rename or merge them.
Why should some items stay ungrouped?
Some items should stay ungrouped because forcing a single unusual item into the nearest theme corrupts that theme. A strange development that fits nothing is often the start of something new.
An ungrouped shelf is where new themes are born. One item is an anomaly; three related items arriving over a few weeks are a pattern worth naming. A library that files everything immediately never gets to notice that moment.
What should a library keep, and what should it let go?
A library should keep developments with their provenance and let go of repetition. The difference between an archive and a living library is that the archive keeps everything, and the living library keeps what helps answer a question.
Worth keeping:
- The development itself, stated plainly: what changed.
- The link to its source, so any line can be checked in seconds.
- The date it was reported, so the theme can be read in order.
- Your own short note, when you drew a conclusion at the time.
Worth letting go: the tenth retelling of a story you already hold, commentary that restates the news without adding to it, and items saved with no reason attached.
Quiet days deserve a specific rule. When nothing happened in a subject, nothing should be filed. Filler entries dilute a theme, while an honest gap in its timeline tells you something: the subject went still, and any later movement stands out against that stillness.
How do you see how a topic evolved?
You see how a topic evolved by reading one theme in chronological order, start to finish, with the sources attached. A timeline shows turning points that no single entry reveals.
The sociologist Niklas Luhmann kept a card index of roughly 90,000 notes written over more than four decades. Bielefeld University, which holds his estate, describes the collection as a record of how his theory developed, one that can be read as his intellectual autobiography. Few readers need a system on that scale, but the principle carries: a library worth keeping shows how your thinking moved, not only what you collected.
A simple practice makes this concrete. Once a month, pick one theme and read it in order. Then write three lines: what you thought at the start, what changed it, and what you now expect next. Those three lines are often the most valuable entry in the theme.
How does a library turn into decisions and writing?
A library turns into output when you start new work from a theme instead of from a blank page. The evidence is already gathered, dated and linked; the work becomes deciding what it means.
Three uses come up again and again:
- Preparing for a conversation. Before a meeting with a supplier, an investor or a candidate, read the relevant theme for ten minutes and arrive with the last three developments and their sources.
- Writing a decision memo. A theme read in order supplies the "what we knew, and when" section that most memos reconstruct from memory.
- Writing for an audience. An article, a newsletter or a post that starts from a theme comes with its citations attached, which is the difference between a view and a claim.
Some tools build this loop directly. Kindal, for example, files every brief in a Library organized by theme and searchable, and its Analyst answers questions across everything you follow, citing the briefs and posts behind each answer.
What makes a library better every day?
A library gets better every day when each day's reading adds a development to the right theme and nothing else. The daily view does the selecting; the library does the remembering.
Read the daily view for change and close it. Visit the library when a question arrives, and read a theme end to end when a decision depends on it. Over months, the gap between the two widens in your favor: the daily view stays short, and the library becomes the clearest account you have of your own subjects.
The measure is not how much you saved. It is how quickly you can say what you know, and show where you learned it.
Frequently asked questions
What is a personal knowledge library?
A personal knowledge library is a durable collection of what one person has read and learned about their subjects, organized so it can answer questions later. It differs from a feed, which shows what arrived most recently, and from a reading queue, which holds what you plan to read. A useful library groups material by theme rather than by source or date, keeps a link to where each item came from, and lets you read a subject in order to see how it developed. The practical test is whether you can answer "what do I know about this?" for any of your subjects in a few minutes, with the sources attached.
Should I organize research by source, by date or by theme?
Organize research by theme, and keep source and date as attributes of each item rather than as the structure. Filing by source mirrors how information reached you, so a single development reported by a filing, a trade publication and an analyst's post ends up in three places. Filing by date works for a daily view but makes a library hard to query, because questions are asked about subjects, not about Tuesdays. A theme groups everything about one development or question together, and the source and date on each item still let you filter, check provenance and read the theme in chronological order.
Should you save everything you read?
You should not save everything you read, because a library that keeps every item becomes an archive that nobody consults. Keep developments, the distinct things that changed, along with a link to the source that reported them first or best. Drop retellings of a story you already have, commentary that adds nothing new, and items you saved without a reason. Quiet days should not produce filler entries; a stretch with nothing filed under a theme is itself useful, because it shows the subject went still. The goal is a collection where each entry earns its place by helping answer a question you are likely to ask.
How is a knowledge library different from a read-it-later app?
A knowledge library is organized around what you know, while a read-it-later app is organized around what you intend to read. A read-it-later app holds articles you saved, usually sorted by when you saved them, and its job ends when you finish reading. A library starts where reading ends: it holds the developments and conclusions worth keeping, grouped by theme, with sources attached, so that months later you can reconstruct how a subject unfolded or pull evidence into a memo or an article. Many readers use both: the app as a short-term queue, the library as the long-term record.
