A Weekly Review System for Researchers Who Juggle Experiments and Code

Use a short weekly review to keep experiments, analysis, and tool-building work visible without creating another complex system.

Review outputs, not busyness

Begin with what changed: samples prepared, measurements collected, figures revised, code tested, or decisions made. A list of hours and tasks can hide whether a project moved forward. Outputs reveal the next bottleneck and make it easier to plan a realistic week.

Keep one small project table

Use a compact table with project, current state, next evidence, blocker, and next action. “Next evidence” is especially useful in research: it asks what measurement, comparison, or test would change your confidence. This keeps planning connected to scientific reasoning.

Separate deep work from maintenance

Experiments, analysis, reading, and writing need protected blocks. Email, file cleanup, ordering, and software maintenance also matter, but they should not consume every available interval. During the review, choose a few deep-work blocks and batch the smaller tasks where possible.

Close open loops

Rename stray files, move exports into the correct sample folder, capture a parameter choice, and write the question that emerged during analysis. Small unresolved loops create friction when work resumes after several days. A weekly review is a good moment to preserve context for your future self.

Choose a deliberately short list

Finish with three outcomes for the next week. Keep them specific and evidence-oriented. A short list encourages completion and makes trade-offs visible when new work arrives. Productivity in research is not maximum activity; it is sustained progress without losing the reasoning trail.