The fix: Log six fields per brew — coffee + roast age, dose/water, grind, time, one taste line, a verdict — while the cup cools, then review per bag. Patterns appear by week two; recipes compound forever.
Memory loses a brew's details within hours — a 20-second log keeps them forever. What to record, the minimal template, how patterns emerge by week two, and how to read your own data.
The fix: Log six fields per brew — coffee + roast age, dose/water, grind, time, one taste line, a verdict — while the cup cools, then review per bag. Patterns appear by week two; recipes compound forever.
Here's an experiment you've already run: three weeks ago you made a genuinely great cup — you remember that it was great. Now: what was the grind setting? The dose? How many days off roast was the bag? The data that would let you do it again on purpose evaporated within hours, and with it the entire lesson. That's the case for a brew journal in one paragraph: memory keeps the verdicts and discards the evidence, and improvement lives in the evidence.
Brewing improvement is a feedback loop: change something → taste the result → keep or revert. Unlogged, the loop is broken in both directions — you can't connect today's great cup to its cause, and you can't stop re-making last month's mistake because you don't remember making it. Logged, every brew becomes a data point in your personal experiment series, run on your grinder, water, and palate — which is why a month of logs teaches more than a year of articles (including this one).
The compounding payoffs, roughly in order of arrival:
The trap is over-logging — a 14-field form lasts four days. The sustainable core is six items:
| Field | Example |
|---|---|
| Coffee + days off roast | "Kenya AB — day 12" |
| Dose / water (or yield) | 15g / 250g |
| Grind setting | 14 clicks |
| Time | 2:50 drawdown |
| One taste line | "sweet, bit thin late" |
| Verdict | keep / finer / coarser |
That's 20 seconds while the cup cools, and it's enough — every diagnostic on this site runs on those six fields. Add water temp, bloom notes, or bed observations only when actively troubleshooting that thing. The verdict field is the secret ingredient: it converts a note into an instruction for tomorrow-you.
The log earns its keep when you look backward, so schedule the look: once a bag (or weekly), skim the entries and ask three questions —
Every expert brewer you've ever envied is running this loop, on paper, in an app, or — after enough years — in trained intuition that was built by the earlier records. The journal isn't homework about coffee; it's the part of brewing where the learning actually happens. Start with tomorrow's first cup: six fields, twenty seconds, and three weeks from now you'll know exactly what your best cup was made of.
Use brew sessions and quick logs to build your history