Journal

Keep a light record of what changed, what shipped, and what you learned.

Keep the Reason, Not Just the Result

Journal is a place for your project's notes and decisions. It's especially useful for the stuff you'd otherwise forget: why you changed a price, what users misunderstood in a beta, or which audience you decided to focus on.

Some entries arrive automatically when you answer a task. Those notes stay connected to the task that prompted them, so you can look back at your reasoning after the task is done. You can also add entries yourself whenever there's something worth hanging on to.

Write an Entry

Choose New Entry, give it a title, and write your note. You can set the date, which is handy when you're writing up something that happened earlier.

You don't need to write a polished report. A few sentences covering what you noticed, what you decided, and what you'd like to check later are plenty. For example: "People thought the free plan included exports. I've clarified the paywall, and I'll check next week's support messages."

That gives you a much more useful record than "Updated paywall."

Find and Update Old Notes

Entries are arranged by date, and search looks through both titles and text. Use it to dig up your earlier thinking before repeating an experiment or reopening a decision you've already made.

You can edit notes as you learn more, or delete entries you no longer need. Task-linked entries keep their task title; entries you've created yourself let you change the title too.

Make It Part of Your Workflow

After a release or marketing experiment, jot down a short note about what changed and what happened. Over time, you'll build a record of your app's progress that helps with future planning, release notes, and build-in-public posts.

The useful habit is writing things down while the context is still fresh in your head. Two honest sentences today beat a detailed explanation you never get around to writing.