What Is Knowledge Transfer? A Plain-English Guide
Knowledge transfer is the deliberate process of moving knowledge from where it exists — an individual, team, or system — to where it is needed, in a form
Knowledge Concepts
Daily notes is a PKM practice of creating one note per day as a time-stamped journal entry, capture inbox, and scratch pad — giving every thought, meeting
Daily notes (also called daily pages or journal notes) is a PKM practice where you create one automatically-dated note per day. This note serves as a time-stamped capture inbox, meeting notes hub, and scratch pad — a frictionless place to write anything without deciding where it belongs. The daily note becomes an anchor for the day's thinking, with links to deeper notes created as you decide what merits its own permanent note.
The daily note is not a to-do list, a diary, or a calendar. It's the place everything lives until it earns its own dedicated note.
The concept is rooted in journaling — the long-standing practice of dated daily writing. What PKM tools added is the connection layer: daily notes in Roam Research, Logseq, and Obsidian aren't isolated journal entries; they're linked nodes in your knowledge graph, automatically dated and backlinked to the concept notes you create.
Roam Research made daily notes the central organizing principle of their app — every session begins on today's daily note. Logseq followed a similar approach. Obsidian implements daily notes as a core plugin (requiring a keyboard shortcut to open; Ctrl+Shift+T by default).
The practice draws on longstanding traditions of morning pages (Julia Cameron's "The Artist's Way"), GTD's capture habit (David Allen), and the German intellectual tradition of Zettelkasten — but adapts them to digital, linked note-taking.
The basic structure:
When you open your PKM tool at the start of a day (or any time during the day), a new note is created automatically with today's date: 2026-08-24. This note is blank and ready for whatever comes.
What goes in the daily note: There's no prescription — that's the point. Typical uses:
Read [[Atomic Habits]] chapter 3 — key point about habit stacking.Processing: At some point (during the day, at the end, or periodically), you process your daily note: anything that deserves a permanent note gets moved or linked to a dedicated note. What doesn't need a permanent home stays in the daily note — dated for reference if ever needed.
A product manager uses daily notes in Obsidian. Their 2026-08-24 daily note:
Morning planning:
10:00 meeting with design:
Reading notes:
Ideas:
To do later:
End of day:
**What this enables:**
- Tomorrow, they open today's daily note and can see exactly what happened on August 24.
- The links ([[Q4 Roadmap]], [[User Research - Navigation Usability]]) are recorded automatically — when they open those notes, today's daily note appears in the backlinks panel.
- The "worth a full note" prompt for AI Enterprise Adoption creates the note when they have time.
**What they don't need:**
A folder system for "meeting notes from August" or "ideas from Q3." The daily note is both the capture mechanism and the chronological index.
---
"Daily notes are a journal." Daily notes can include journaling, but they're not the same thing. A journal is primarily reflective writing about personal experience. Daily notes are a capture tool for professional and intellectual life. You might journal in your daily note, but the point is capture and linking, not reflection.
"I have to write every day." No. Daily notes are there when you need them. If you're on vacation and not working, there's no obligation to open the daily note. The practice is useful for workdays and active thinking periods; it doesn't need to be daily in a strict sense.
"Daily notes will become my permanent notes." Daily notes are the inbox, not the archive. They capture everything. Permanent notes are the processed output — the specific insight, idea, or reference that deserves its own dedicated note. Not everything in the daily note earns a permanent note; that's fine. Most things can stay in the dated daily note as a time-stamped log.
"This is just journaling dressed up as productivity." Daily notes are primarily a capture tool that reduces friction and provides a time-indexed log. The journaling tradition is one influence, but the linked structure and processing workflow are distinct from traditional journaling.
Step 1 — Open a daily note at the start of any working session. In Obsidian: Ctrl+Shift+T. In Logseq: it's the default opening page. In Roam: click the daily note icon.
Step 2 — Write everything in the daily note first. Quick thought? Daily note. Meeting insight? Daily note. Reference to follow up on? Daily note. Everything goes here without deciding where it belongs.
Step 3 — Link to existing notes while writing.
When your daily note mentions a concept, project, or person that has an existing note: use [[Note Name]]. This creates the backlink automatically. The daily note becomes a time-stamped link in the history of your permanent notes.
Step 4 — Process periodically. Once a day or once a week: scan your recent daily notes. Anything that deserves a permanent note: create it and link from the daily note. Anything that's done: mark as done or leave it. Anything that needs follow-up: add to your task system.
Step 5 — Don't over-clean. Daily notes don't need to be tidy. They're the inbox, not the filing cabinet. Messy, stream-of-consciousness daily notes with lots of links are working correctly.
When you save content with WebSnips — an article, a research page, a resource — that's a capture action. Your daily note is the natural place to record "saved this to WebSnips today" and what you thought about it: "Captured FT article on AI adoption to [[AI Research]] collection — key argument: enterprise AI adoption will outpace consumer adoption by 2026 because enterprise risk appetite has shifted. Worth developing into [[AI Strategy]] note."
The daily note links to the concept (via [[AI Strategy]]). The concept note backlinks to the daily note. WebSnips has the captured content. The three layers — capture tool, daily note, permanent note — form a complete workflow.
Zettelkasten: The permanent note system that daily notes feed. Zettelkasten notes (atomic notes on single ideas) are what daily notes process into.
Fleeting notes: In Zettelkasten terminology, a "fleeting note" is a quick capture — equivalent to a daily note entry. Fleeting notes are processed into permanent notes or discarded.
Progressive summarization: A technique (from Tiago Forte) for processing notes by highlighting, summarizing, and extracting key insights over time. Daily notes are a natural input for progressive summarization.
How long should a daily note be? No target length. Some days produce a note with 30 lines; some produce a note with 3. The daily note reflects the day's actual work, not a target.
How do I find a specific thing I captured in a daily note from three months ago?
Search. In Obsidian: Ctrl+Shift+F → search the full text of all notes including daily notes. In Logseq: full-text search. If you used a specific wiki-link ([[Q4 Roadmap]]) when capturing it, the backlinks panel of that note also shows it.
Should I use templates for my daily notes? Templates are useful if you have a consistent daily structure you want to start with (morning questions, time blocks, recurring sections). The risk: templates become rigid when they don't match the day. A minimal template (date heading, maybe 2-3 sections you actually use daily) is better than an elaborate one you'll abandon.
Daily notes solve the PKM setup problem that stops most people: "where do I put this?" The answer with daily notes is always: "in today's daily note." Everything gets a home immediately. Processing happens later, when you have time and context to decide what deserves a permanent note. The result is a chronological log of your intellectual life, linked to the permanent notes it generated — a searchable record of when you were thinking about what, and what came of it.
See also: Web Clipping for Research Papers.
More WebSnips articles that pair well with this topic.
Knowledge transfer is the deliberate process of moving knowledge from where it exists — an individual, team, or system — to where it is needed, in a form
A browser extension is a small software add-on installed in a web browser that adds features or modifies behavior — blocking ads, saving passwords
A content calendar is a planning tool that schedules what content will be published, when, where, and by whom — turning a content strategy from vague
A context window is the maximum amount of text an AI language model can process in a single interaction — everything in the prompt, the conversation
A knowledge silo is a condition where knowledge, information, or expertise is isolated within a team, department, or individual — inaccessible to others
A large language model (LLM) is a neural network trained on massive amounts of text to predict and generate language.