I’ve started a Notion journal four times. The first three died quietly, usually around day nineteen, and every time I blamed myself. Too inconsistent. Not a real journaler. Then I looked at what I’d actually built and understood the problem: I’d made a database that demanded data entry, not a journal.
The version I’ve kept for over a year is smaller and stranger than the ones that failed. It has three fields. It has no streaks. It has a page called “boring Tuesday” that I open more than any other. This post is the whole build, in order, including the parts I got wrong first.
## Start with one database, not five
Every guide tells you to separate journaling, mood tracking, and gratitude into different databases. Don’t. Separate databases mean separate places to fall behind, and falling behind in one makes you avoid all of them. One database called Journal. One template. Everything else is a property.
My properties are Date, Type (daily, weekly, note), and Mood. That’s it. Mood is a single select with six options and no emoji — emoji selects slow me down because I scroll looking for the perfect one. Words are faster and more honest.
Why so few properties? Because every extra field is a tiny decision, and decisions are what kill a daily habit. You want opening the page to feel like sitting down, not like filling out a form.
## Build a template that takes ninety seconds
The template matters more than the database. Mine is a heading with the date, then three prompts, then blank space. The prompts are: What’s here today? What am I avoiding? One good thing. That last one is deliberately plain. “Gratitude” makes me write for an audience; “one good thing” lets me write “the bread was good” and move on.
I set the template to auto-apply on new pages in the database, and I pinned the database to my sidebar. Two clicks from anywhere in Notion to a blank page. If it’s three clicks, I skip it on tired days, and tired days are most days.
Here’s the counterintuitive part: leave the bottom half of the template empty. When your template fills the whole page, a short entry feels like a failure. When there’s room, two lines look complete. Most of my entries are two lines.
## Use a dated index so old entries stay findable
The thing that made me quit journals in notebooks was never rereading them. In Notion you can fix that cheaply. Create a linked view of the Journal database on your home page, sorted by date descending, showing only the Date and a short summary property. It becomes a reverse-chronological index you scroll like a feed.
Every few weeks I scroll that list and open something from a month ago. Sometimes I add a line in italics at the bottom: reading this now, I notice… That habit turned the journal from a chore into a conversation with a past version of myself, which is the entire point.
One warning: don’t make the summary property required. Required fields turn a gentle log into a database with incomplete records, and incomplete records feel like debt.
## Weekly pages do the work daily pages can’t
Daily entries are weather. Weekly reviews are climate. Once a week — Sunday for me, but the day doesn’t matter — I make a Type: weekly page and answer four questions. What actually happened? What did I finish? What’s dragging? What’s next?
The “what did I finish” question is the one that changed things. Daily pages are full of open loops: emails half-written, projects mid-flight. The weekly page is where things get to be done. I list even small finishes, like “renewed the domain” or “sent the invoice I’d been avoiding.”
If you only have energy for one journaling habit, make it this one. A weekly review takes fifteen minutes and holds more signal than seven daily entries. The daily pages become raw material for it.
## Make it pretty, but not precious
You’re allowed to care how it looks. A page you find beautiful is a page you open. I use a soft off-white background, one accent color, and a small cover image that changes monthly. That’s the whole aesthetic system.
What I avoid: elaborate callout blocks with icons, progress bars, and multi-column layouts inside journal entries. They take time to build and they break the moment you type something long. Save the decoration for your home page, where you look at it, not your entries, where you write in them.
One more thing. If a day goes by and you don’t write, the page just sits there. No red badge, no missed-day counter. The fastest way to kill a journal is to make it keep score.
## What to do this week
Build the database tonight. Three properties, one template, auto-applied. Pin it. Write two lines before bed and don’t reread them. Next Sunday, make your first weekly page.
That’s the whole system. It’s less impressive in a screenshot than the elaborate setups, and it’s the only one I’ve kept. Start smaller than feels satisfying — you can always add a field later, and you probably won’t want to.