What Is Citation Management? A Plain-English Guide
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
Knowledge Concepts
What is fleeting notes? A clear explanation of the temporary capture layer in Zettelkasten and PKM systems — what fleeting notes are, how to use them, and when to process them.
Fleeting notes are temporary, rough captures of ideas, observations, and reactions — jotted quickly in the moment with the intent to process later — the first layer in a PKM workflow like Zettelkasten, where they serve as inputs to more refined permanent notes rather than as end products themselves.
The term comes from Niklas Luhmann's Zettelkasten system and was popularized in the digital PKM community by Sönke Ahrens in How to Take Smart Notes (2017).
In Niklas Luhmann's Zettelkasten, he distinguished between different types of notes based on their purpose and longevity. Fleeting notes were the quick captures — ideas that came to him while reading, in conversation, or in the shower. These were temporary. Their purpose was to serve as reminders until he could sit down and process them into proper permanent notes (Zettels) that would live in the slip-box.
Sönke Ahrens made this distinction widely known in How to Take Smart Notes, where he formalized Luhmann's implicit practice into an explicit three-note-type system:
The fleeting note category gave a name and a home to the experience most knowledge workers have: you have an idea, you write it on whatever's nearest, and then either you process it or it disappears. Fleeting notes acknowledge this reality and build it into a workflow.
Fleeting notes are:
Fleeting notes are not:
The process:
Capture (fleeting note): You're reading an article and notice an insight that connects to something you've been thinking about. You write in your phone: "behavioral economics and pricing — the decoy effect works here too - check the SaaS pricing article." This is a fleeting note.
Process (within 24-48 hours): You sit at your desk for a scheduled processing session. You open your fleeting notes inbox. You see the note from earlier. You ask: what is the actual idea here? You write a proper permanent note: "Decoy pricing works by making the middle-tier option appear as the best value through deliberate structuring of a dominated option." You link it to your existing notes on behavioral economics and SaaS pricing. You delete the fleeting note.
Result: The idea is captured, refined, and integrated into your knowledge system. The fleeting note served its purpose and is gone.
The ideal fleeting note capture tool is: fast, always available, low friction, and connected to wherever you'll process.
| Tool | Best for | Speed | Friction |
|---|---|---|---|
| Apple Notes / Google Keep | Mobile quick capture | Very fast | Very low |
| Obsidian mobile (daily note) | Obsidian users | Fast | Low |
| Paper notebook | Offline / pen preference | Very fast | Very low |
| Voice memo | Walking, driving | Very fast | Near zero |
| Inbox in Notion or Roam | Already in these tools | Medium | Medium |
| Dedicated inbox note in Obsidian | Daily note workflow | Fast | Low |
Many PKM practitioners use their phone's default notes app (Apple Notes, Google Keep) as their fleeting notes inbox, then process into Obsidian or Roam during dedicated processing sessions.
The failure mode for most fleeting note systems is clear: the notes accumulate without being processed. A year later, you have 847 unprocessed notes and the capture habit has decayed because you've learned, implicitly, that saving things doesn't actually help.
The processing step is what makes the system work:
Schedule it. Ahrens and most PKM practitioners recommend daily processing — 15–30 minutes to clear the fleeting notes inbox. If daily is unsustainable, every 48 hours is the maximum before notes lose enough context to be worth processing.
Be ruthless. Most fleeting notes don't survive processing. "This was interesting but I don't have a clear permanent note to write from it" is a valid outcome — delete and move on. The percentage of fleeting notes that become permanent notes is typically 10–30%.
Rewrite, don't transfer. The point of processing isn't to copy the fleeting note into a permanent note. It's to think about what the idea actually means and write it clearly in your own words. The permanent note should be better than the fleeting note, not just cleaner.
"Fleeting notes are just a fancy name for jotting things down." The distinction is that fleeting notes are explicitly temporary, with an expected processing step. Most note-taking doesn't have this expectation — notes are saved and often never revisited. Naming them "fleeting" is a commitment: these notes will be processed or discarded, not accumulated indefinitely.
"I should make my fleeting notes better so I don't have to process them." This defeats the purpose. Trying to write good permanent notes in the moment of capture forces you to stop the flow of reading or thinking to do writing work. Low friction capture now → high quality processing later is the intended workflow.
"If I don't process all my fleeting notes, the system doesn't work." Missing a processing session is recoverable. Abandoning the capture habit because processing feels overwhelming is not. If your inbox is overwhelming, delete everything older than two weeks (the context is gone anyway) and restart.
"Fleeting notes are only for Zettelkasten users." The concept applies broadly. Any PKM system that distinguishes capture from processing uses something like fleeting notes, even if it's called an "inbox" or "raw notes" or "capture bucket." GTD's "inbox" is functionally a fleeting notes container.
For knowledge workers whose primary fleeting note content is web research, WebSnips handles the capture layer with some processing built in:
For users who process web research into a Zettelkasten or evergreen note system, WebSnips can serve as the web-specific capture and processing layer before permanent notes go into Obsidian, Roam, or similar tools.
How long should I keep fleeting notes before processing? Ahrens recommends daily processing. The practical limit is 48 hours — beyond that, notes lose enough context that processing becomes hard. Notes older than a week are usually not worth processing; the moment they were relevant has passed.
What's the best app for fleeting notes? The one you'll actually open in the moment. Apple Notes and Google Keep are popular because they're default apps with zero setup. Voice memos are good for walking. The app doesn't matter; the habit of opening it immediately when an idea occurs does.
Do I need to have a full Zettelkasten to use fleeting notes? No — the fleeting notes concept is useful even with a simple notes inbox. Capture quickly, review daily, keep what's worth keeping. This is valuable even if you never write a single linked permanent note.
What's the difference between a fleeting note and a to-do? A fleeting note captures an idea or observation that will become knowledge. A to-do is an action to be done. "Read the article about behavioral economics" is a to-do (action). "Behavioral economics might explain why the free trial CTA works differently from the discount CTA" is a fleeting note (idea to develop). Mixing these creates confusion; most PKM practitioners keep them in separate systems.
Fleeting notes are the first, roughest layer of a knowledge management practice — temporary captures designed to preserve ideas in the moment and be processed into something more permanent within 24–48 hours.
The concept is simple. The discipline is the hard part: capture freely, process regularly, delete what doesn't survive processing. The notes that do survive become the raw material of your permanent knowledge base.
The key distinction: fleeting notes are a means, not an end. They work when they're processed. When they accumulate unprocessed, they're a graveyard of good intentions.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and practical methods to make it explicit.
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital version for writers and researchers.