Taste Memory · Taste · 6 min read

How to keep a tea journal: steeps, infusions, taste memory

A tea journal is not a rating. It is a record of what happened across a session: the leaf, the water, the vessel, the steep time, and how each infusion tasted.

Key takeaways

  • How to keep a tea journal: steeps, infusions, taste memory is about saving context that can be reused later.
  • A useful record should preserve the situation, the reason, and the next action.
  • Start small: one repeatable record type beats a complicated system.

Log the setup, not just the tea

Save the tea name, vendor, leaf amount, water temperature, vessel, and date. The setup is what you will change next time, not the tea name alone.

Track each infusion

For gongfu, log each round on its own line: steep time, aroma, taste, body, and finish. For western brewing, log a single steep and taste.

Mark the best round

Most teas peak at a specific round. Save the round number and the time that produced it. That is the most useful field for repeating a good session.

Use simple taste language

Pick a small set of words: floral, creamy, vegetal, mineral, sweet, dry, thin, heavy, bright, soft. Consistent words make records comparable across sessions.

Notice preferences over time

After a few sessions, you will start to see which temperatures and steep times you actually prefer. A tea journal makes those patterns visible without scoring.

How this becomes an OmniSaver record

The practical output of this guide is not another long note. It is a compact record with enough structure to help you act later: the source, the situation, the important fields, the reason it mattered, and the next step.

For Taste, that means choosing the smallest Saver that matches the moment and saving only the fields that will help you compare, repeat, prove, decide, or reuse the context later.

A simple workflow

Start by saving one real example while the context is fresh. Review it after the outcome is visible. Compare it with the next similar record. Reuse the best version when the situation appears again.

This save, review, compare, reuse loop is the reason OmniSaver uses tiny apps instead of one giant database. Each Saver keeps the record close to the behavior it supports.

Practical template

Record
TeaSaver record
Save
The key fields, source, date, and why it mattered
Review
What changed, what worked, and what to try next
Reuse
Bring the record back into the next decision or workflow

FAQ

What should a tea journal include?

Tea name, vendor, leaf amount, water temperature, vessel, steep time, and a short note per infusion. Mark the best round.

Is this only for gongfu tea?

No. The same record works for gongfu, western brewing, matcha notes, herbal tea, and daily tea.