A Drum Practice Journal That Takes Two Minutes
A drum practice journal works when it takes two minutes and fails when it takes twenty. You only need three fields — a number, a sentence, and tomorrow's target — and if you write more than that you will quit within two weeks, usually without noticing.
Why most practice journals die in two weeks
Most drummers start a practice journal as a diary and abandon it as a chore, and the failure is structural rather than personal. A diary asks you to describe your session in prose, prose takes ten minutes you would rather spend playing, and by week two the pages are blank. A practice journal is not a diary. It is a logbook — the thing a pilot fills in after a flight, not the thing a novelist writes at night. A logbook records only what the next session needs to know: how fast you went, where it broke, and what to attack tomorrow. Cut everything else and the habit survives. Keep it as a diary and it dies, every time, right around day twelve.
The three fields that do all the work
Every useful entry has exactly three parts. First, a number: the tempo you reached on one specific exercise, in BPM. Second, a sentence: the precise point where that exercise stopped being clean. Third, a target: the single thing tomorrow's session will try to fix. That is the whole system, and it fits on a sticky note. Notice what is missing — mood, effort ratings, how you felt, how many minutes you played. None of that changes what you do next, so none of it earns a line. Three short fields take under two minutes, which is exactly why you will still be filling them in three months from now, long after the diary crowd has stopped.
Step 1 — Log one number, not a feeling
Write down a tempo, not a verdict. "Singles felt good today" is unreadable a week later, while "singles clean at 116 BPM" tells you exactly where to start tomorrow. Pick one exercise, run it against a click (how to practice with a metronome covers the setup), and find the fastest tempo you can play for a full minute without the pattern falling apart. That number is your entry. The free Rudiment Trainer is built for exactly this: you set a starting tempo and it steps up on a schedule, so the tempo where it stops you cleanly is the tempo you log. Keep it honest — a number you rounded up will send tomorrow's session to the wrong starting point.
Step 2 — Write one sentence about where it broke
The sentence is the part that makes the number useful. Not "it broke," but where and how: "left hand rushed the last two notes of bar three at 120," or "double-stroke second bounce collapsed on the turnaround." One clause, specific, physical. This is the field people skip, and it is the one that turns a log into a diagnosis. A number tells you the ceiling; a sentence tells you which wall you hit it against. Keep it to one line, because if you find yourself writing three sentences you are describing the session instead of logging it, and you are already on the road back to the blank-pages problem.
Step 3 — Set tomorrow's single target
End the entry by naming one target for the next session: one exercise, one tempo range, one thing to watch. "Singles, 108 to 120, keep the left hand even through the turnaround." A single target beats a to-do list, because a list lets you do the easy parts and call it progress. When tomorrow arrives you open the journal, read the last line, and start — no warm-up decisions, no deciding what to practice, no negotiating with yourself at the kit. This is the quiet payoff of the whole system: the two minutes you spend today remove the ten minutes you would otherwise waste tomorrow figuring out what to play.
::: warn
Do not log a tempo you have not actually played for a full minute. A fantasy number is worse than no number at all, because it aims tomorrow's practice at a wall your hands cannot touch yet, and you will read the miss as failure instead of bad data.
:::
What to leave out
Leave out anything that does not change the next session. Ratings out of ten, mood, energy level, how motivated you felt — cut all of it. So do totals like "practiced for 45 minutes"; the clock is not the metric, the tempo is. Also cut the urge to log every exercise you touched. Log the one that is currently blocking you and let the comfortable material go unrecorded. A journal that records everything is a journal nobody rereads. The test for any line is one question: will this line change what I do tomorrow? If the answer is no, it does not belong, and deleting it is what keeps the two-minute promise alive.
The mistake that turns a journal into a chore
The mistake is copying someone else's template. You find a detailed practice spreadsheet with ten columns and color coding, you fill it in for four days, and you stop — because you are now maintaining a system instead of playing the drums. A journal has to be shaped like your practice, not like a stranger's. That is why the three-field format wins: it is small enough that you cannot hide inside it. The smaller the journal, the longer it lives — that is backwards from how it feels, and it is true every single time. Build the smallest thing you will actually maintain, then add a fourth field only if you catch yourself needing one.
How to tell it worked
Give it fourteen days, then answer four questions without guessing: what tempo did singles reach on day one versus day fourteen, which exercise broke first most often, what did you fix in the last week, and what is tomorrow's target? If you can answer all four from the journal in under a minute, the system is working — that readback is the entire point, and it is the one thing memory cannot do. If you cannot answer them, your entries were too vague or too long, and the fix is to go back to one number, one sentence, one target. Check the pattern against a real drum practice routine and tighten anything that drifted long.
::: verdict
Two minutes, three fields, fourteen days. If you can answer four questions straight from your own journal, you have the only progress-tracking system a working drummer needs, and you built it for the price of a sticky note.
:::
Frequently asked questions
The questions readers send us most about drum practice journal.
No. A notebook, a notes app, or a plain text file all work, and none of them is better than the others. The format is what matters, not the container. Paper has one real advantage: it cannot send you a notification, so it never becomes a source of guilt. If you already carry a phone, a single notes file is fine. Avoid anything that asks you to create an account, because a login screen is one more reason to skip the two minutes.
Three lines: a number, a sentence, a target. Read it back to yourself — if it takes more than fifteen seconds, it is too long. The length limit is not a style preference; it is the survival mechanism. Every field you add is a field you will eventually skip, and a skipped field is the first sign of a dead journal. When in doubt, cut the entry in half and log only the number and the target.
Log whatever tempo you reached clean for a full minute on the exercise currently blocking you. Usually that is singles or one specific rudiment, not a whole song. Log the same exercise day to day so the numbers stay comparable; bouncing between different exercises every session makes the log unreadable after a week. If two exercises are both blocking you, pick the harder one and let the other wait its turn.
Nothing breaks, and you do not need to catch up. Write the next entry when you next play and leave the gap empty. A journal is not a streak you are protecting; it is a tool you pick up when you practice. Trying to reconstruct missed days turns it into homework, which is exactly the failure mode that kills journals in the first place. Missed entries cost you nothing, but guilt over missed entries costs you the habit.
No. The Rudiment Trainer runs entirely in your browser using the Web Audio API. There is no server, no account, and no upload — it does not save your tempos or anything else, and it works with cookies blocked. Refresh the page and it resets to its defaults. Your journal lives wherever you choose to write it, and the tool never sees a line of it.