Getting Started With A Mechanical Keyboard Journal
A lot of people build keyboards without writing anything down. They assemble the board, type a few things, move on. Six months later they can't remember what switch lubing setup they used on the middle row, or which plate material made that one build feel different. This is exactly the problem a keyboard journal solves. It's not complicated. You just need a place to log build details so you actually use it next time instead of guessing. I've tracked maybe two dozen builds over the last few years. The early ones I did without any record-keeping, and I completely messed up re-creating a build I actually liked because I couldn't recall whether I was using 30g or 50g lube on the stabilizers. Once I started writing things down, the whole process got noticeably faster. Rebuilding takes about half the time because I'm not reverse-engineering my own memory.
Journal For Mechanical Keyboard Quick
There are a few ready-made templates floating around under names like Journal For Mechanical Keyboard Quick. They're usually Notion templates or Google Sheets setups designed to minimize the friction of logging your builds. The quick versions strip out most of the fluff — switch type, lubes, tape mod, plate material, case, keycap profile, and a basic sound clip link. That's enough for most people. I went with a simple Notion setup myself. Each build gets its own page. I drop in a spreadsheet table for the parts list, a text block for notes, and I keep a rolling audio log of the typing sound. That last part matters more than you'd think. Your ears remember a sound your brain won't. If you type on a build and don't record it, you'll forget how it actually sounded within a month.
What To Actually Track
Don't overcomplicate it. The core fields that matter are: Switch type and variant — including the manufacturer batch if you're buying from multiple sources. Switches from different production runs can feel noticeably different even within the same model. Lube and method — lube weight, brand, whether you hand-lube or use a train method, and the brush type. I once logged my lube as "Krytox 205g0" and forgot to note the train method. Coming back to it later, I couldn't tell whether the smoother feel came from the lube or from doing the train setup versus hand-lubing.
Get the Full Details
Plate material and thickness — polycarbonate, FR4, aluminum, steel. Thickness changes the flex profile. Writing just "polycarbonate" isn't enough. Note the mil or mm measurement because 1.5mm polycarbonate feels meaningfully different from 2mm. Case and padding — foam type, foam placement (top, bottom, or both), and any gasket setup details. The amount of foam and where you put it changes the acoustics more than most people realize. Stabilizer setup — plate lubed, case lubed, wire type, any mod done to the housing. This field alone saved me from repeating a rattle I thought was fixed.
Keycap profile and material — PBT or ABS, SA, XDA, OEM, whatever. Material matters for longevity and feel. I once built two keyboards with the exact same switches and layout, just different keycap profiles, and couldn't tell them apart in my notes until I went back and added that field.
Practical Workflow
Here's how I actually do it without it turning into a chore. I set up a quick entry before I start disassembling the old board or opening the new parts. Five minutes tops. I fill in the template with what I know — part numbers, links, whatever's handy. Then after the build is done and I've typed on it for a couple of days, I go back and fill in the subjective stuff: sound profile, actuation feel, any issues that came up during assembly. Audio recording is a habit worth keeping. I just use my phone on a desk stand, hit record, and type about thirty seconds of mixed typing. That file gets linked in the journal. The file itself isn't stored in Notion — it's on my drive. Notion just holds the link. I also keep a master table at the top level of my journal. It's a simple database with columns for date, keyboard name, switch type, plate material, and a thumbs-up or thumbs-down rating. When I want to decide what to build next, I filter that table instead of scrolling through individual pages. It takes me about thirty seconds to find builds that match criteria I'm interested in, like "show me all builds with 50g linear switches and gasket mount."
Common Mistakes
The biggest mistake I see is people treating the journal like a receipt folder. They log part numbers and links but skip the subjective experience entirely. A journal without notes on how the build felt and sounded is just a parts list. It won't help you make better decisions later. Another issue is inconsistency. You'll start strong for three builds and then stop writing down the lube method because "it felt the same." It never feels exactly the same, and you'll forget the detail when it matters. Even a quick note like "same lube as last time" is better than nothing. I also recommend against making the template too detailed upfront. I had a version with fourteen fields per build and stopped using it within a month because filling it out took longer than the build itself. Strip it down to the essentials and add fields only when you find yourself wishing you'd tracked something.
A Specific Problem I Hit
During one build I used Krytox 205g0 on the stabilizers with the train method, but I also switched to a different foam setup at the same time — moving from 3mm PU foam on top to 5mm memory foam. When I reviewed the build later, I couldn't tell whether the sound improvement came from the lube method or the foam change because I hadn't separated those notes clearly enough. After that, I started logging lube method and foam separately, each with their own field. That way when you change two variables at once, you at least have data on both independently. Search for Journal For Mechanical Keyboard Quick on Notion public templates or on sites like NotionWay or Notion VIP. The quick versions usually cost between free and ten dollars. The paid ones often include pre-built databases, automations, and sound clip integration. Honestly, the free ones work fine. The structure matters more than the polish. If you don't want to use Notion, Google Sheets works just as well. Create columns for each field I listed above and you're set. Some people use Obsidian with a markdown-based journal template. Any tool works as long as you actually write in it consistently. The tool itself isn't the hard part. Staying consistent is.
At the end of the day, a keyboard journal isn't going to make your builds sound better on its own. But it will save you from making the same mistakes twice, and it'll cut your next build time down significantly once you start cross-referencing past entries. I'd say the average time saved per rebuild is somewhere around twenty to forty minutes depending on how detailed your notes are. That adds up fast over a year.
