Track It Yourself

Status tracking gets a bad reputation because it is usually imposed — a burdensome report someone else asked for. Flip that. The point of tracking is to make your work legible to you: what is in flight, what is stuck, and what a “how’s it going?” actually answers. Done lightly and owned by you, it takes minutes a week and makes every advisor meeting sharper. The evidence from labs that adopt agile-style tracking is consistent on one condition — it helps when the student runs it, and becomes overhead the moment it is someone else’s compliance form.

Three small habits do the job. None should take more than fifteen minutes.

1. A board with a limit

A board is nothing fancy: a task list split into columns — Backlog (everything you intend to do), Doing (what you’ve actually started), and Done — where every task sits in exactly one column and moves left to right as it progresses. Sticky notes on a whiteboard, a Trello board, and a spreadsheet with a Status column are all the same board (if you’ve heard the word kanban, this is that); yours is already set up on the planning sheet.

The part that makes a board work is the WIP limit: cap Doing at two or three tasks, maximum. The limit is the whole trick. Research tempts you to have ten things half-started; capping work-in-progress forces you to finish before you start, which is how things actually reach Done.

Each task needs a Definition of Done — the concrete condition that ends it — so “analysis” does not linger as a task forever:

On the sheet, this is Tab 3, Section A: a Status dropdown (Backlog / Doing / Done / Blocked) that color-codes each row, a Definition-of-Done column, and a Blocker column. The WIP counter turns red when more than three tasks are Doing — a visible nudge to finish before you pull more.

2. A fifteen-minute weekly log

Once a week — pick a fixed time; Friday afternoon is a natural one — write four lines:

Four lines a week becomes your project’s memory. Six weeks in, it is the honest record of where the time went — invaluable when a timeline needs re-planning, and half of your methods section already written.

3. A 1:1 you drive

Walk into your advisor meeting with the agenda already written, in three parts: Did / Blockers / Next. Did since we last met, Blockers you need help clearing, Next you plan to do. This does two things: it puts you in charge of the meeting, and it aims the scarce time at the blockers, where an advisor’s input is worth the most.

If you want more structure, wrap the whole thing in sprints — fixed 2–6 week cycles with a short plan-at-the-start and a review-and-retro at the end, where the retro asks not “did we finish” but “how should we work differently next cycle.” That cadence is the Scrum idea adapted to a lab; the weekly log and board are the lightweight version of the same loop.

When the work is shared

The moment more than one person touches the same data or analysis, tracking has to cover coordination, not just your own tasks — who is coding which transcripts, when you reconcile, and by when. That last one changes character when other people are involved: your collaborators have their own courses, deadlines, and lives, and a date you set for them is a date they never agreed to. Shared deadlines are arrived at together, not announced.

For the mechanics of shared analysis, do not reinvent anything here; the qualitative module already covers them:

• Coordinating a coding team, dividing the work, and reconciling → Codebook & Team Coding.
• Quality and agreement checkpoints, and whether a reliability statistic is even appropriate → Inter-Rater Reliability.

Where this lives

Tab 3 · Status Tracking of the companion sheet holds the board and the weekly/1:1 log. Keep the header’s Last updated current — the norm from the overview is that you update the tracker before the meeting, so the 1:1 starts from a shared, current picture instead of a reconstruction.