Welcome. This is a field guide to organising what you know, written for people who have a laptop full of folders called misc, a notes app with four thousand untitled entries, and a growing suspicion that the AI assistant they just hired is as lost in their files as they are. It has a hundred short chapters. Each one is meant to teach you a single thing you can do this week, ideally before the kettle has finished.
Start with a distinction that sounds pedantic and turns out to be the whole game. Information is what you store. Knowledge is what you can act on. A PDF of your pension terms is information. Knowing that you can move the money without penalty after a certain birthday, and remembering to do it, is knowledge. The first sits in a folder. The second changes what you do on a Tuesday.
Most personal and team systems are built as if the two were the same. We save, bookmark, export, screenshot and forward, and the pile grows, and because the pile grows we feel informed. Then someone asks a simple question, what did we decide about the supplier contract, and the answer is somewhere in a thread, a call recording, two documents and a colleague's head. The information exists. The knowledge, in the sense of something you can act on within a minute, does not.
A librarian is a machine for turning things that were kept into things that can be used.
That is the job this book describes, and it is older than any software you own. The librarian's work has always been conversion: taking material that arrived in whatever shape it pleased and making it findable, understandable and trustworthy at the moment someone needs it. The tools have changed from card catalogues to search boxes to language models that will cheerfully summarise your entire drive. The conversion has not become optional. If anything, a machine that can read everything makes the difference sharper, because it will act on whatever it finds, including the stale draft you meant to delete in March.
Here is the exercise for this week. Write down five things you believe you know about your own work: a process, a decision, a password policy, a client preference, the reason a particular system is configured the way it is. Then, for each, ask whether you could act on it tomorrow without asking anyone and without searching for more than a minute. Mark the ones that pass. Most people find two. The other three are information you own but cannot use, which is a polite description of clutter.
Do not panic about the ratio. It is normal, and it is the starting line rather than a verdict. The rest of the book is about moving items from the second column to the first, cheaply and repeatably, so that what you have kept becomes something you can rely on. Storage is a fact. Knowledge is a habit.
Fig 1 · Knowledge Is Not Information. Five things you think you know pass the one-minute test; usually only two do.
Chapter 2 · Part I
The DIKW Ladder
There is an old diagram that information scientists draw on whiteboards when they want to look wise. It is a pyramid with four layers: data at the bottom, then information, then knowledge, then wisdom at the narrow top. It is often mocked for being too tidy, and it is too tidy. It is also the most useful single picture of what organising actually does.
Data is raw marks. A column of numbers, a log file, a recording of a meeting, four hundred photos of a whiteboard. Information is data with a frame around it: these are last quarter's sales, by region, in pounds. Knowledge is information connected to other information and to purpose: sales in the north fell because the distributor changed, and the new one ships on Thursdays. Wisdom, if we must use the word, is knowing what to do about it, and when not to bother.
Notice what happens as you climb. Each rung has less volume than the one below and more value. A day of logs becomes one paragraph; a year of paragraphs becomes three decisions. Organising is nothing more than the discipline of climbing, and every tool you use either helps you climb or helps you pile up more data at the bottom. Cloud storage, on its own, is a very efficient way of building a larger ground floor.
The ladder also explains a familiar frustration. You save something, it feels productive, and months later it is useless. That is because saving is a ground-floor act. Nothing has been framed, connected or decided. The item has been moved from one pile to another, and the second pile happens to be yours. Real progress up the ladder always involves writing something in your own words: a title that says what the thing is, a sentence about why it matters, a link to the decision it informs.
Every rung you climb, you throw away more than you keep. That is the point.
AI tools are tempting here because they appear to climb the ladder for you. Point a model at a folder and it will summarise, and a summary looks like information or even knowledge. Sometimes it is. But the model can only frame what it has, and it does not know which questions you will ask next month. It can carry the material up a rung. It cannot decide which rung matters to you, which is the part that turns information into knowledge in the first place.
Try this on one messy folder. Sort its contents into the four rungs. Most of it will be data: drafts, exports, attachments you never opened. Some will be information. A little may be knowledge, usually a document someone wrote to explain something. Then write one paragraph at the top of the folder saying what it all adds up to. That paragraph is the most valuable file in the folder, and it took you ten minutes. The pyramid is a cliché because it is true. Climb it anyway.
Fig 2 · The DIKW Ladder. Each rung up the ladder has less volume and more value than the one below.
Chapter 3 · Part I
Tacit Versus Explicit
Most of what you know is not in your files. It is in your hands, your habits and your sense of when something looks wrong. You know which client needs a phone call rather than an email. You know that the build fails on Mondays because of a timezone quirk. You know how to calm a particular stakeholder. None of this is written down, and if you left tomorrow, most of it would leave with you.
Knowledge researchers call this tacit knowledge, the kind you have but cannot easily say, and contrast it with explicit knowledge, the kind that has been put into words, diagrams or procedures. The distinction is useful because the two behave so differently. Explicit knowledge can be copied, searched, shared and handed to an AI agent. Tacit knowledge can only be demonstrated, imitated or slowly absorbed by working alongside someone.
Writing is the bridge. It is not a perfect bridge, because some skills resist words, and you will never fully describe how you know a bad estimate when you see one. But writing gets much further than people expect. The trick is to describe cases rather than principles. Be careful with the payments service is useless. Last spring we deployed on a Friday, the retry queue doubled every charge, and we spent the weekend refunding people, so we no longer deploy payments after Wednesday is knowledge someone else can use.
If it only exists in your head, it is not knowledge the team has. It is a dependency on you.
This matters more now than it did five years ago, because a growing share of the work is done by agents that have no hands, no habits and no memory of last spring. An AI assistant can only use what has been made explicit. If your team's real rules live in people's heads, the agent will follow the written rules instead, and the written rules are usually the optimistic version. The gap between what is written and what is true becomes a gap between what the agent does and what you wanted.
So here is the week's exercise, and it is uncomfortable on purpose. Pick one skill you use regularly and have never documented. Write three hundred words explaining it to a capable stranger. Use examples. Say what you check first, what you ignore, and what makes you stop. Notice where the words refuse to come. Those are the spots where your knowledge is genuinely tacit, and they are worth marking with a note that says, in effect, ask me, or watch me do it.
You will not convert everything, and you should not try. But each paragraph you write moves a piece of your judgement from a place where only you can reach it to a place where others, human or otherwise, can. Writing is slow. Forgetting is faster.
Fig 3 · Tacit Versus Explicit. Writing concrete cases moves tacit know-how into explicit, shareable knowledge.
Chapter 4 · Part I
Findability Beats Storage
A hoard you cannot search is not a library. It is a landfill with good intentions. This is the most important principle in the book, and it has a convenient property: it reduces every organising decision to a single question. Will future-you, or a colleague, or an agent, actually find this again?
Storage used to be the hard part. Paper took space, filing cabinets were expensive, and a library's first problem was where to put things. That problem has been solved so thoroughly that it now creates the opposite difficulty. You can keep everything, forever, at almost no marginal cost, and so everything is kept, and the cost moves silently to the moment of retrieval. Every extra item makes every future search slightly worse.
Think about what finding requires. You need to remember that the thing exists, or at least suspect it might. You need a route to it: a name you can search for, a folder you would think to open, a link from somewhere you already visit. And when you arrive, you need to recognise it as the thing, which means it must say what it is. A file named scan0034.pdf in a folder named stuff fails on all three. It is stored perfectly. It is found never.
The test of a system is not what goes in. It is what comes back out, when asked.
The findability question is useful because it cuts through arguments that otherwise go on for ever. Should you use folders or tags? Whichever you will actually use when looking. Should notes be long or short? Whichever size returns a useful answer when searched. Should you keep the fourth draft? Only if someone will ever need it and could tell it apart from the fifth. Every structural debate in this book is, underneath, a debate about findability. Notice that the question also covers machines. An AI agent searching your drive needs exactly the same three things you do, and it is less forgiving of vague names, because it cannot shrug and ask the person at the next desk.
Make this concrete. Pick something you know you saved in the last year but have not looked at since: a contract, a recipe, the slides from a talk. Time yourself finding it. If it takes more than a minute, do not just find it; fix the reason it was hard. Rename it, move it, or add a line to an index you already use. Then, the next time you save something important, ask the question before you press save, not after. Where will I look for this? Put it there, and call it that.
It feels like a small habit, and it is. Most good systems are a stack of small habits held for long enough. Keep less, find more. The landfill does not need another bag.
Fig 4 · Findability Beats Storage. Finding needs three steps: remember it exists, have a route, and recognise it.
Chapter 5 · Part I
The Cost of Organising
Organising always costs something, and the cost always lands at one of two moments. You can pay at capture, by filing carefully, naming precisely, tagging and linking. Or you can pay at retrieval, by searching, scrolling, opening things and asking around. There is no third option where the cost disappears. There is only the choice of when to pay, and how much.
People get this wrong in both directions. The tidy temperament overpays at capture: elaborate folder trees, twelve tags per note, a template for everything. Their systems are beautiful and slightly paralysing, and they quietly stop saving things because saving has become a chore. The untidy temperament overpays at retrieval: everything goes into one heap, and every search is an archaeological dig. Both are making an unexamined bet about which moment is cheaper.
The right answer depends on how often something will be retrieved and how painful a failed retrieval is. A receipt you will need once, at tax time, deserves almost no effort at capture beyond a sensible name and a single folder. A procedure your team runs every week deserves real care: a clear title, a canonical home, an owner, a date. A passing thought deserves nothing more than a line in an inbox. Match effort to expected use and you will spend far less time overall than either the hoarder or the perfectionist.
Filing is a loan from the present to the future. Do not lend to people who will never collect.
Search has shifted the balance, and AI has shifted it further. When full-text search arrived, the value of elaborate folder structures fell, because you could find a document by its contents. Now that a model can read a pile of documents and answer a question across them, the value of capture-time effort has shifted again. It has not vanished. It has moved. The things worth doing at capture are the things search cannot reconstruct: what this is, where it came from, whether it is current, and what it is for. A machine can find the word invoice. It cannot know that this invoice was disputed and superseded unless somebody wrote that down.
This week, look at the last ten things you saved and estimate, honestly, how often each will be retrieved. Then look at how much effort you spent on each at capture. You will almost certainly find a mismatch: careful filing of things you will never need, careless dumping of things you will need often. Adjust the next ten. Spend thirty seconds more on the frequent ones and thirty seconds less on the rare ones.
There is no virtue in organising for its own sake. Tidiness is pleasant, but it is not the goal. The goal is the lowest total cost of having knowledge available when needed. Pay where it is cheapest, and pay once.
Fig 5 · The Cost of Organising. Capture effort should rise with how often an item will actually be retrieved.
Chapter 6 · Part I
Everything Is a Collection
Books on a shelf, files on a drive, contacts in a phone, tabs in a browser, recipes in a drawer, memories in your head and messages in a team channel. They look like different problems. They are the same problem wearing different coats. Every collection, whatever it holds, faces four questions, and most organising trouble comes from answering only one of them.
The first is selection: what is in it? A collection is defined as much by what it excludes as what it includes. A browser with ninety open tabs has no selection policy; it has accumulated rather than collected. The second is arrangement: how is it ordered? Alphabetical, chronological, by subject, by project, by frequency of use. Some order is always present, even if it is only the order things happened to arrive. The third is access: who can reach it, and how? A shared drive with the wrong permissions is a private collection in disguise, and a private notebook nobody can read after you leave is a collection with a single, mortal user. The fourth is departure: when do things leave? This is the question almost nobody answers, which is why almost every collection grows until it is unusable.
Thinking in these four terms is clarifying because it lets you diagnose problems quickly. A team wiki that nobody trusts usually has an arrangement problem and a departure problem: pages are hard to find and old pages are never removed. A photo library that overwhelms you has a selection problem: you kept every burst shot. A downloads folder is all four problems at once, which is why it is the most frightening folder on most computers.
A pile becomes a collection the moment someone decides what does not belong in it.
The framing also helps when you hand a collection to a machine. If you ask an AI agent to work with your project documents, it will face exactly these questions. What is in scope? How is it ordered? Can it reach it? Which of these are obsolete? An agent with no answers will treat a three-year-old draft as equal to yesterday's decision. You will have to answer the questions eventually; it is cheaper to answer them before the agent does something confident with the wrong file.
Pick one collection this week, preferably a small, annoying one. Your downloads folder is ideal. Write down, in one line each, your answer to the four questions. What belongs here? How should it be ordered? Who needs to reach it? When should things leave? Then act on the fourth answer, because that is the one you have been avoiding. Delete or move anything older than a month.
You will notice something pleasant. Once you have answered the four questions for one collection, the answers transfer. Your inbox, your notes and your team's shared drive have the same shape. Learn the shape once. Recognise it everywhere.
Fig 6 · Everything Is a Collection. Diagnose any collection by which of its four questions has gone unanswered.
Chapter 7 · Part I
The Librarian's Oath
Librarianship has no formal oath, but if it had one it would contain three verbs: preserve, describe, provide access. Those three duties predate computers by a couple of thousand years. They described the work in ancient libraries, in monastery scriptoria, in Victorian reading rooms and in today's research collections. They survive every technology shift because they are about people, not tools.
Preserve means keeping things intact and available over time. It is not the same as hoarding. A preserved item is protected from loss, corruption and silent change. For your purposes, that means backups, version history and a refusal to keep the only copy of anything important on one laptop. It also means preserving context, because a document without its surrounding explanation is only partly preserved, like a letter without the envelope that tells you who sent it. Describe means saying what a thing is, so that someone who has never seen it can decide whether it is what they need. Titles, summaries, dates, authors, subjects and status are all description. Description is what allows finding without opening, and it is the duty most personal systems neglect, because describing feels like admin and saving feels like progress. Every chapter in Part Three of this book is a chapter about description.
Provide access means getting the right thing to the right person at the right time, and no further. Access has two edges. Too little, and knowledge is trapped: the only person who knows how the deployment works is on holiday. Too much, and knowledge leaks: the salary spreadsheet is shared with the whole company because someone clicked the wrong button. A good librarian is generous and careful at once.
Preserve, describe, provide access. If a tool does not help with one of the three, it is decoration.
The oath is a useful filter for the endless supply of new tools. Every few months a product arrives promising to transform your knowledge, and some of them genuinely help. Ask which of the three duties it serves. A sync tool preserves. A tagging assistant describes. A search layer provides access. An AI that answers questions across your documents provides access in a remarkable new way, but only if the description underneath is decent and the preservation is trustworthy. A tool that serves none of the three is a hobby, which is fine, provided you know that is what it is.
Try a small audit. Take your most important collection, the one you would most hate to lose, and score it on each duty out of five. Is it preserved: backed up, versioned, with more than one copy? Is it described: could a stranger tell what each item is without opening it? Is it accessible: can the people who need it reach it, and only them? The lowest score is this month's project.
Libraries outlived scrolls, codices, printing presses and microfilm. The duties came through untouched. They will survive the current wave too. Tools change. The oath does not.
Fig 7 · The Librarian's Oath. Preserve, describe and provide access hold up a collection, and each has its tools.
Chapter 8 · Part I
Entropy Is the Default
No system stays organised on its own. This is not a moral failing; it is physics, or at least the office equivalent. Every hurried save, every file named new document, every tag invented on the spot because the right one did not come to mind, nudges the collection towards disorder. Nobody ever decides to make a mess. The mess arrives one reasonable shortcut at a time.
People respond to this in a predictable way. They let the mess grow until it becomes unbearable, then declare a great reorganisation. A weekend is lost to new folder structures, colour-coded tags and a fresh notes app. For a few weeks everything is lovely. Then the shortcuts resume, and within months the new system has decayed to roughly the state of the old one, except that it now contains two incompatible structures layered on top of each other.
The lesson is that the initial design matters much less than the maintenance loop. A modest system maintained weekly will beat a brilliant system maintained never. This is true of gardens, codebases and teeth, and it is true of knowledge. The question to ask of any organising scheme is not how elegant it is on day one. It is how much effort it takes to keep it elegant on day three hundred, and whether you will actually spend that effort.
Design is a single event. Maintenance is a habit. Only one of them is still there next year.
A good maintenance loop has three properties. It is small, so that skipping it feels silly rather than reasonable. It is scheduled, so it does not depend on your noticing the mess. And it is specific, with a short list of things to do rather than a general intention to tidy. Something like: empty the inbox, rename anything called untitled, merge any duplicate tags, archive anything finished. Fifteen minutes on a Friday afternoon. Part Seven returns to this ritual in more detail, because it turns out to be the habit that separates people with a knowledge system from people with a folder.
Machines help with entropy and also accelerate it. An AI agent can do much of the weekly tidy for you: suggest names for untitled files, spot duplicates, flag stale pages. It can also generate a startling volume of new material, from meeting summaries to drafts to research notes, each of which arrives with no particular home. Agents are a faster shovel. Whether the shovel moves the pile or builds a bigger one depends on the loop you put around it.
This week, do not reorganise anything. Instead, write down a fifteen-minute maintenance routine with no more than five steps, put it in your calendar as a recurring appointment, and do it once. Next week, do it again. Resist the urge to redesign. Most systems do not fail because they were badly designed. They fail because nobody swept up.
Fig 8 · Entropy Is the Default. Big reorganisations decay back to mess; a small weekly loop keeps it low.
Chapter 9 · Part I
Organise for the Question
The most common mistake in organising is to sort things by what they are rather than by how they will be asked for. People arrange their files the way a museum arranges exhibits: by type, by origin, by some property of the object. Then they need something, and the question they ask has nothing to do with any of those properties. The shelf is beautiful and answers nothing.
Consider a freelancer who files everything by document type: contracts in one folder, invoices in another, briefs in a third, correspondence in a fourth. It looks orderly. But the question they actually ask, over and over, is what is going on with this client? Answering it requires opening four folders and mentally reassembling the story. A structure built around the question, one folder per client with everything inside, answers it in one click. The objects are the same. The questions decide the shelf.
This principle scales up to teams and down to single notes. A team wiki organised by department reflects the org chart, which is the structure people inside the company already know and therefore the one they least need help with. A wiki organised around the questions newcomers ask, how do I get access, who approves spending, how do we ship, is far more useful, even though it cuts across departments untidily. A single note can be organised the same way: lead with the answer to the question someone will bring to it, then the supporting detail.
Shelves are answers to questions. Make sure they are the questions someone actually asks.
How do you find out which questions matter? Listen to them. For a fortnight, keep a running list of every question you or your team asks that requires looking something up. Not the answers, just the questions. Where is the brand logo? What did we agree on pricing for the renewal? How do I reset the staging database? After two weeks you will have a list of perhaps thirty questions, and you will notice that about a third of them come up repeatedly. Those repeated questions are your real taxonomy. Design the shelves, folder names, index pages and templates around them.
The same thinking applies when you prepare material for an AI agent. Agents arrive with questions too: where is the code for this feature, what are the conventions, what must I never touch. A project whose structure answers those questions directly, with a clear index and plainly named sections, will be navigated well. A project organised around its own internal history will be navigated by guesswork, and guesswork from an agent is fast, confident and expensive.
Do not try to anticipate every possible question. That way lies a taxonomy committee. Organise around the dozen questions that come up most, accept that rare questions will need search, and revisit the list every few months. Objects are what you have. Questions are why you have them.
Fig 9 · Organise for the Question. Filing by document type scatters each client; filing by client answers in one click.
Chapter 10 · Part I
A Library Is an Argument
Every way of arranging knowledge is a claim about what matters. Put two things on the same shelf and you are saying they belong together. Put one at eye level and another in the basement and you are saying one is more important. There is no neutral shelf. Choosing an order is choosing a worldview, and the only question is whether you choose it deliberately or inherit it from whoever set up the folder before you.
Librarians learned this the hard way, and Part Two tells some of those stories. The great classification schemes of the nineteenth century reflected the assumptions of the people who designed them: which religions got whole sections and which got a single number, which countries were subdivided in detail and which were lumped together, which subjects were considered serious. None of this was malicious, exactly. It was simply the view from where the designers stood, frozen into a structure that outlived them by a century.
Your own systems make arguments too, smaller but no less real. A project folder with subfolders called Strategy and Admin has decided which work is strategic. A team wiki whose home page lists engineering docs first has decided whose knowledge is central. A tagging scheme with forty tags for technical topics and one for people has an opinion about what kind of knowledge counts. Newcomers read these arguments instantly, even if nobody ever stated them.
The structure tells everyone what you think matters, whether or not you meant to say it.
This is not a call for paralysis. You have to pick some order, and a reasonable one held consistently is far better than an endless debate about the perfect one. It is a call for awareness. When you design a structure, ask what it makes easy to see and what it makes easy to miss. Ask who would arrange it differently and why. Occasionally, the answer will reveal a blind spot worth fixing: the customer support knowledge that has no home because the wiki was designed by engineers, or the decisions that are never recorded because there is no shelf called decisions.
AI models make this sharper rather than softer. When an agent searches your documents, it inherits your arrangement. If your structure buries a category of knowledge, the agent will under-weight it. If your structure gives pride of place to old material, the agent will treat it as current. You are not just organising for human readers any more. You are writing the briefing that machines will act on.
This week, look at the top level of your main knowledge collection, whether a drive, a wiki or a notes app, and write one sentence describing the argument it makes. This collection believes that the most important thing is... If the sentence surprises you, that is useful. If it embarrasses you, that is more useful. Every shelf is an opinion. Make sure it is yours.
Fig 10 · A Library Is an Argument. A folder tree makes claims about what matters, and reveals shelves that are missing.
Free preview · Part I
Keep reading
You have read the first 10 of 100 chapters of The Librarian. The full book has every chapter and plate, as PDF and EPUB in English, French, Polish and Spanish.