Guide
Build it from evidence, not memory. Start with a month of your calendar and sent mail, then keep a three-line daily log and a weekly sort. Obsidian suits you if you want free, local Markdown files; Notion suits you if you want a cloud workspace with databases. Dayflow helps on a Mac when you cannot reconstruct what you did, by recording your screen and exporting Markdown.
Someone asks how you fixed the staging email problem last spring, and you know you fixed it. You remember the relief. You do not remember the cause, which ticket it lived in, or the one setting that mattered. So you spend an afternoon rediscovering your own answer.
Or it is review season, and six months have compressed into a single word: busy. You did things. You shipped things. You just cannot list them, and the notes app you set up in January holds three pages and a grocery list.
This guide is about building a personal knowledge base backward: starting from work you have already done instead of an empty system you promise to fill. It covers why past work slips away so quickly, seven habits that turn it into notes you will actually reuse, and where an app fits. One disclosure up front: this blog is published by Dayflow, a Mac app that appears once near the end, followed by a section on when it is the wrong choice.
Most work happens inside tools, and tools keep outcomes, not reasoning. The finished document shows the final wording, not the three drafts you rejected or why. The merged change shows what changed, not the dead ends that taught you where the real problem was. The reasoning is the valuable part, and it lives only in your head.
Memory keeps the feeling of a week better than its contents. Many people find they can recall that a stretch was hard or satisfying, but not what actually filled the days. Detail fades fast unless something brings it back.
Writing things down in the moment feels like a detour. When you are halfway through fixing something, stopping to document it competes with finishing it, and finishing wins. Afterward, the urgency is gone and so is the motivation.
New notes systems start empty. A fresh app asks you to design folders and tags before you have anything to put in them, so the structure gets built and the content never arrives.
And collecting is not the same as building. Saving articles feels productive, but the notes you will actually look up are about your own work: your fixes, your decisions, your recurring questions.
If the bigger problem is that whole days vanish, not just old projects, the page on where did my day go covers that side of it.
What to do: Set aside one sitting. Open your calendar for the past four weeks, your sent mail, and whatever else your work leaves behind: ticket history, document edit history, code commits, chat threads you started. On paper, write one line for each piece of work you find. Do not organize, rank or tidy. Just list.
Illustration: A product designer scrolling back four weeks finds an onboarding review, a vendor call about icon licensing, two days on an accessibility audit nobody else remembers, and a hiring panel. Those lines become the first raw entries, and the accessibility audit alone turns out to contain three reusable lessons.
How to tell after a week: You should have a page or two of lines, including a few things you had genuinely forgotten. If the list surprised you, the exercise did its job. If it was hard to fill because your trails are thin, step 3 matters more than the rest.
What to do: Go through your list and pick the items where you figured something out. For each, write a card (an actual index card works well) with four lines: the problem, what you tried, what worked, and where the evidence lives, such as a ticket number, file path or document name.
Illustration: “Problem: test emails from staging reached real customers. Tried: checking the mail provider dashboard. Worked: the sending address was set in two places; removed the override. Evidence: ticket in the infra queue, runbook doc under Deploys.”
How to tell after a week: Write a handful of cards from your step 1 list. Then pick one and ask: could I redo this from the card alone? If not, add the missing step. Cards that pass this test are the core of your knowledge base.
What to do: Before you close the laptop, write three lines: what I did, what I learned or decided, and what is unfinished. Use a notebook, a sticky note or the daily work log template. The point is that it takes a couple of minutes, so you will keep doing it. The work journal guide goes deeper if you want more structure later.
Illustration: “Did: finished the pricing page copy, reviewed two pull requests. Learned: the legal team needs 48 hours for any wording about refunds. Unfinished: FAQ section, waiting on support’s answers.”
How to tell after a week: Read all five entries on Friday. If you can tell what each day was about within a few seconds, it is working. If entries say only “meetings” or are blank, make them smaller: one concrete noun per line is enough.
What to do: Take fifteen minutes at the end of the week. Read your daily logs and pick one item that would save future you, or a colleague, real time. Rewrite it as a standalone note with a plain, searchable title. A weekly work log is a good place to do the reading.
Illustration: From “Learned: legal needs 48 hours for refund wording,” the weekly note becomes “How to get refund wording approved,” with who to send it to, the lead time, and the last version they accepted.
How to tell after a week: You have one finished note. After a month, you have four. The real test comes later: when you next face that situation, did you look the note up instead of asking around? If yes, keep going.
What to do: Use the back page of your notebook. Every time someone asks something you answer from experience, write down the question in a few words. The second time the same question appears, it becomes a note.
Illustration: “How do I get access to the analytics dashboard?” shows up twice in one week. Ten minutes of writing turns it into a note you can paste as a reply, and you stop retyping the same explanation in chat.
How to tell after a week: Look for repeats. Even one repeat is worth a note. If nothing repeated, keep the list running; recurring questions often take a few weeks to show themselves.
What to do: Title every note as a plain phrase or question, add the date, and keep a single index page that groups notes under a small number of topics. Then store everything somewhere you will open again without friction. That might be a ring binder, a folder of text files, or a notes app.
Two common options, described from each vendor’s own pages as checked on October 4, 2026 (this is a reading of their documentation, not a hands-on review):
Illustration: An index page with five headings: Deploys, Customers, Legal and approvals, Hiring, Tools and access. Under each, a short list of note titles.
How to tell after a week: Pick a fix you wrote down and try to find it. If it takes more than a minute, your titles are too clever or your topics too many. Rename and merge until retrieval is quick.
What to do: A knowledge base that is never used stops getting fed. Once a month, use it for something real: a status update, a brag document, or prep for a performance review. Pull directly from your cards and weekly notes.
Illustration: Writing a quarterly self-review, you open the index, scan three months of weekly notes, and list the accessibility audit, the staging email fix and the refund approval process, each with evidence attached.
How to tell after a week: The first time you use it, notice how much digging you skipped compared with last time. That difference is the reason to keep feeding it.
The hardest part of every step above is the raw material: knowing what you actually did on Tuesday. Calendars show meetings, not the two hours spent tracing a bug.
Dayflow is a free, open-source Mac app (MIT license, macOS 14 or later) that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. You do not start a timer or remember to log anything. At the end of the week, instead of reconstructing Tuesday from memory, you read it.
For a knowledge base, the useful part is export: you can export a date range as Markdown from Settings → Export, then copy what is worth keeping into your notes. The export work history workflow shows the steps. The timeline is raw material, not finished notes. You still choose what matters and write down the why.
Recordings and the local timeline are stored on your Mac. With Local AI, a model runs on your Mac through Ollama or LM Studio and screenshot analysis stays on-device. You can instead send selected screenshots to your own provider, or use Dayflow Pro at $20 a month, which deletes screenshots after processing and may retain activity data for sync, per the privacy policy. The local and cloud processing page explains the difference. AI summaries can miss or misinterpret work, so check before reusing.
Dayflow publishes this article, so weigh the recommendation with that in mind.
It is not a notes app. Dayflow records and summarizes. It does not hold your written notes, link them together or give you an index page. For the knowledge base itself, Obsidian or Notion wins: Obsidian if you want free local Markdown files on any platform, Notion if you want a cloud workspace with databases.
It is Mac only. It needs macOS 14 or later. On Windows or Linux, a paper log plus Obsidian, which runs on both, covers everything in this guide.
It only sees the screen. Whiteboard sessions, phone calls, paper sketches and the idea you had on a walk never show up. Often the most valuable part of a note, the reasoning, happens away from the computer.
It does not do the thinking. It cannot decide which fix is worth a note or explain why a decision was made. Steps 2, 4 and 5 are still yours.
Screen recording is not for everyone. If you would rather not have your screen captured, or your employer does not allow it, the three-line paper log does the job.
It does not handle billing or teams. Dayflow has no invoicing, payroll, team reports or website blocking. If you need those, compare other Mac time trackers.
A personal knowledge base is easiest to build from what already happened. Rebuild last month from your calendar and sent mail, write a card for each problem you solved, keep three lines a day, and promote one item a week into a note you could hand to someone else. Store it wherever you will open it again: paper, a folder of Markdown files in Obsidian, or a Notion workspace. If your real obstacle is not remembering what you did on your Mac, Dayflow can supply the record, but the notes, and the judgment about what is worth keeping, still come from you.
A personal knowledge base is a collection of notes you write for your future self: how you solved problems, decisions you made and why, and answers you keep giving colleagues. It can live in a notebook, a folder of text files or a notes app. What makes it useful is not the tool but whether you can find an answer in it quickly when you need it.
Start with problems you solved, decisions and the reasons behind them, steps you had to figure out the hard way, and questions people ask you more than once. Add a pointer to the evidence, such as a ticket number or file path. Skip clipped articles at first. Your own work is what you are most likely to look up again.
Rebuild it from trails you already have: your calendar, sent email, ticket history, document edit history and code commits. Write one line per piece of work on paper before organizing anything. From then on, a three-line log at the end of each day keeps the gap from reopening, so next time you read the past instead of reconstructing it.
It depends on where you want your notes to live. Obsidian is a free app that stores notes as Markdown plain text files in a folder on your computer, and it runs on Mac, Windows, Linux, iOS and Android. Notion keeps content in its cloud workspace and adds databases, forms, sites and calendar, with a free plan for individuals. Pick the one you will actually open.
According to Obsidian's pricing page, the app is free with no sign-up required, including for work use. A commercial license at $50 per user per year is optional; Obsidian encourages organizations using it for work to buy one but does not require it. Sync and Publish are separate paid add-ons, and Sync Standard is $4 per user per month billed annually or $5 billed monthly.
No. Notion content lives in Notion's hosted workspace in the cloud rather than as local files, though it offers desktop apps for Mac and Windows plus mobile and web. Notion states that information used to power Notion AI is shared with AI subprocessors under contracts that prohibit training on customer data. If you want plain files on your own disk, Obsidian's local vault is the closer fit.
No. For writing and organizing a knowledge base, Obsidian or Notion is the better tool. Dayflow records your Mac screen at one frame every 10 seconds and has AI write a timeline of the day. It does not hold your own written notes, link them or give you an index. At most it supplies raw material that you then turn into notes somewhere else.
In Dayflow, go to Settings → Export and export a date range as Markdown. You can read it during a weekly review and copy the parts worth keeping into your notes. Since Obsidian keeps notes as Markdown files in a folder, the export can sit alongside them. Treat it as a draft: AI summaries can miss or misinterpret work, so check before reusing anything.
Less than most people expect if you skip the setup phase. A few minutes at the end of each day for a three-line log, and a short weekly session to turn one log item into a proper note, is enough to start. The one-time catch-up on the previous month takes longer, so do it once, in a single sitting, on paper.
Yes. Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month where Dayflow manages the cloud analysis. It runs only on macOS 14 or later. The free app can analyze screenshots with a local model through Ollama or LM Studio, or with your own cloud provider, whose charges and terms apply. It has no invoicing, payroll, team reports or website blocking.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required