DEV Community

WorkflowStash
WorkflowStash

Posted on

I built study and research kits for a few months. The systems part was the interesting bit.

I've spent the last stretch building small workflow kits for students and researchers — planners, trackers, template packs. Not apps. PDFs and spreadsheets, mostly. I went in expecting the writing to be the job. It wasn't. The job was systems, and checking my own work.

Three patterns kept showing up.

Review schedules are just queues with dates attached. A study kit I built has a topic tracker: learn something on day 0, and the sheet works out your review dates — +1 day, +3 days, +7, +14, +30. Dead simple formula, =A2+1 style arithmetic. The hard part wasn't the math. It was deciding what counts as "learned." My rule in the kit: you haven't learned it until you've closed the book and written three lines about it from memory. If you can't do that, the topic stays at day 0 and the schedule doesn't start. A queue that starts on a lie produces very organized forgetting.

Citation checking has to run in both directions. Every researcher I know has found, at 11 p.m. before a deadline, a reference in their bibliography that appears nowhere in the text. Or the opposite — a citation in chapter two pointing at a paper that never made it into the list. So the audit sheet I built has two columns that both have to be true: cited in text and in the reference list. A row only passes when both boxes are ticked. It takes maybe twenty minutes for a thesis chapter. It's boring. It also catches exactly the thing that makes examiners quietly lose faith in the whole document.

Group work fails in the dark, not in the open. Nobody decides to free-ride in a meeting. It happens in silence, over weeks. The fix that kept coming up while I made the student kits was embarrassingly low-tech: a contribution log. Date, name, what got done, link to the file. Updated as you go, visible to everyone including the tutor if it comes to that. Once the log exists, most groups never need to argue — the record argues for them, politely, in advance.

One more, smaller thing: students don't run on months, they run on semesters. A budget sheet built on monthly habits falls apart in week thirteen, when the money and the deadlines both run out at once. So the student money kit I made works in semester blocks — money in at the start, the twelve or fifteen weeks laid out, the expensive weeks (books, society fees, the train home) marked before they ambush you. Same spreadsheet skills, completely different shape. The calendar is part of the system.

Then there's the verification part, which nobody sees and which ate a surprising amount of my time. Every spreadsheet formula in these kits got recalculated in LibreOffice and compared against hand totals — if the budget sheet says the semester adds up, I add it up myself first. Every count in a listing got checked against the finished file: if I claim 100 journal prompts, I count to 100. If the capsule wardrobe says 33 pieces, the categories have to sum to 33 (they do: 8+4+5+3+6+4+2+1). This sounds obvious. It is obvious. It's also where most digital products quietly lie to you, usually by accident, usually because someone edited the file after writing the description.

What I didn't build: anything that promises grades, citations, or publications. A tracker can't make a thesis good. It can make the work visible early enough that you still have time to fix it, which turns out to be most of the battle.

The finished kits live in my shop — Study System Kit, Literature Review System Kit and about sixty others at https://ko-fi.com/workflowstash/shop — and the automation side of what I make is free, as always, over at https://github.com/newbeechong-glitch/free-n8n-workflows. If you build study systems of your own, I'd genuinely like to hear what your review intervals look like. Mine are probably wrong in an interesting way.

Top comments (0)