Research project management for PhD students: a practical system

The most reliable way to manage a PhD is to stop treating the thesis as one task. Split it into separate projects, give each project a few goals with visible end points, plan only the coming week in detail, and keep the papers, notes and drafts for each project in the same place as its tasks. Review the whole thing once a week. The system below works in a paper notebook, a spreadsheet or a kanban board, and takes about an hour to set up.

A thesis is several projects, not one

"Write thesis" cannot be planned, because it has no next step. What you actually have is a set of projects that run in parallel and finish at different times: a literature review, two or three studies, perhaps a methods paper, a conference talk, a fellowship application. Each has its own reading, its own collaborators and its own deadline.

Start by listing them. A project is anything with a distinct output that will take more than a few weeks. Most PhD students have between three and six running at once. Write down, for each one, the output (a chapter, a submitted paper, a talk), the rough date it is due, and who else is involved. That list is the top level of your system, and everything else hangs from it.

Three levels: goals, milestones, weekly tasks

Inside each project, plan at three levels. Each level answers a different question, and mixing them is what makes to-do lists unmanageable.

• Goals answer "what does finished look like?" A goal is a result, not an activity: "Search documented and screening complete", not "work on the search". A project usually has three to six.
• Milestones answer "how will I know I am on track?" A milestone is a dated checkpoint someone else could verify: "Send the methods section to my supervisor by 14 March".
• Weekly tasks answer "what do I do on Tuesday?" A task is small enough to finish in one sitting and starts with a verb: "Extract sample sizes from the eight trial papers".

Plan goals for the whole project, milestones for the next two or three months, and tasks for the coming week only. Research changes too quickly for a detailed plan to survive much longer than that, and a task list written three months ahead is fiction you will have to maintain.

Keep papers, notes and drafts with the project

Research tasks are rarely self-contained. "Revise the discussion" depends on a draft, three papers and the comments from your last supervision meeting. If the task is in one app, the draft in another, the papers in a reference manager and the comments in your email, every task begins with ten minutes of finding things.

The fix does not require special software. It requires one rule: everything that belongs to a project is reachable from that project. In practice:

• One collection or folder of papers per project, not one library for everything you have ever saved. How to organize research papers explains how to set this up.
• Reading notes kept with each paper, so that opening the paper opens what you thought of it.
• Drafts linked from the project, with one current version.
• Tasks that point at their material. "Read Rivera 2021 for the sampling approach" should link to the paper. "Revise section 3" should link to the document.
• Meeting notes filed with the project, with the agreed actions copied into its task list the same day.

The weekly review

The review is what keeps the system alive. Put 30 minutes in your calendar at the same time each week, for example on Friday afternoon or Monday morning.

1. Clear your inboxes: notes from meetings, emails with requests, ideas written on paper. Each becomes a task in a project or is dropped.
2. Go through the projects one by one. Tick off what is done and delete tasks that no longer matter.
3. Check the next milestone for each project. Is it still realistic? If not, change the date now and tell whoever is waiting.
4. Choose the coming week. Pick the three to five tasks that move the most important milestone, then a few smaller ones. Give each a day.
5. Note anything you are blocked on, and who can unblock it. That becomes the agenda for your next supervision meeting.

If a project has had no finished task for three weeks, decide deliberately: pause it and say so, or schedule one small task to restart it.

Working with a supervisor and co-authors

Supervisors and co-authors do not need your task list. They need to see milestones and to know what you need from them. A few habits make this smooth:

• Agree the goals and milestones for each project together, and write them where both of you can see them.
• Send a short update before each meeting: what was finished, what is next, what you need a decision on.
• Turn every "I will send you comments" into a task with a name and a date, including tasks that belong to other people.
• Share the project reading list, so co-authors cite from the same set of papers and the same versions.
• Record decisions in one place. "We agreed to drop the third condition" is easy to forget and expensive to rediscover.

Common failure modes

• One giant to-do list. Two hundred items from five projects in one column gives you no way to see what matters this week. Group by project, then by goal.
• Tasks detached from papers. "Read more on measurement invariance" is not actionable. Name the papers, link them, and say what you are reading them for.
• Tool sprawl. Tasks in one app, notes in a second, papers in a third and drafts in a fourth means four places to check and nothing connected. Fewer tools used consistently beat a perfect stack.
• Planning as procrastination. Rebuilding the system feels productive. If setup takes more than an afternoon, it is too elaborate.
• Goals with no end point. "Improve the introduction" never finishes. "Introduction approved by both supervisors" does.
• No review. Without the weekly half hour, any system is out of date within a month, and you stop trusting it.

A template: goals for a literature review chapter

Here is a set of goals you can copy and adapt. Each one has a clear end point and a few example tasks. How to write a literature review explains the work behind each step.

1. Question and scope agreed. Tasks: write the review question in one sentence; list inclusion and exclusion criteria; get supervisor sign-off.
2. Search documented. Tasks: choose databases; write and test the search strings; record the date and number of results for each.
3. Papers screened and collected. Tasks: screen titles and abstracts; get full texts for the shortlist; remove duplicates.
4. Reading and notes complete. Tasks: read five papers a week with a structured note for each; flag the key sources.
5. Synthesis outlined. Tasks: group notes into themes; draft a one-page outline with the claim each section makes; discuss it at supervision.
6. Draft written. Tasks: draft one section per week; fill citation gaps as they appear.
7. Draft revised and approved. Tasks: send to supervisor by an agreed date; revise; check every citation against its source.

Put a date on the end of each goal, and you have milestones. Break only the current goal into tasks.

How this looks in Mosaic

Mosaic is a research workspace organized the way this guide describes: by project. Each project has its own library of papers, its documents (Google Docs or Word files that you create or link), its tasks, and a briefing of new papers matched to it, so the material for a task is already in the same place as the task.

In the Tasks section, goals group related tasks and show how many are done. Tasks can have a due date, a priority, members and a lead, and you can attach a paper or a document to a task, which keeps "read this for that" connected. Create goals and tasks shows the steps. The same tasks can be viewed as a table, as cards in "To do", "In progress" and "Done" columns, or on a timeline with a bar for each dated task (Track work in Table, Cards and Timeline). A "Mine" filter shows only the tasks you lead or belong to, which is a quick start for the weekly review.

For supervision and co-authored work, you can invite people by email and choose which projects and sections each person sees, so a co-author on one paper does not see the rest of your thesis. Mosaic is in an invite-only beta with a waitlist; the product page shows the workspace in more detail.