Research project management is the work of coordinating a research project so it actually finishes: planning the stages, tracking what is active, and keeping track of who owes what. Universities sometimes hire a dedicated research project manager for this, but most researchers, from a first-year PhD student to a four-person lab, run it themselves. A kanban board is a good fit, because a research project is really a set of tasks moving through a small number of stages, and that is exactly what a board is built to show.
What makes a research project different from a normal project
Most project management advice assumes a fairly linear path: plan, build, ship. A research project rarely works that way. A single finding can send you back to the literature. A reviewer can send a finished paper back to the analysis stage months after you thought it was done. Data collection can stall for reasons outside your control, while writing on a different section continues in parallel.
A generic task list handles none of this well, because it has no concept of stage and no way to show a task moving backward without looking like a mistake. A kanban board handles it naturally: a card just moves from Under Review back to Revision, and the board still makes sense.
What research project managers actually do
At research-heavy universities, the role is a real job title. Duke's Research Project Management Core, for example, describes the work as protocol development, team facilitation, proposal support, and hiring help, billed at $700 to $1,200 a month per 10 percent of a person's time, with a 10 percent minimum commitment. Boise State's research project management group frames the same role around strategic planning, risk management, and workflow documentation, distinct from the administrative staff who file the paperwork.
Both descriptions are accurate, and both describe a service that most researchers cannot access. A solo grad student, a postdoc between grants, or a small lab without an administrator does not get a dedicated project manager. What they need is the underlying practice, not the hire.
A column layout for a research project
Six stages cover most research projects without forcing every project into the same shape:
- Ideas - questions and half-formed directions not yet committed to
- Literature Review - papers to read, summarized findings, gaps identified
- In Progress - the current experiment, survey, or analysis step
- Under Review - sent to an advisor, co-author, or journal, waiting on feedback
- Revision - changes requested and being made
- Done - finished, published, or formally accepted
A real card in that board is specific: "Summarize the three attrition-bias papers from last week's search" in Literature Review, or "Address reviewer 2's concern about the control group" in Revision. Vague cards like "work on paper" hide the actual state of the project and are the first thing worth splitting up.
Under Review and Revision are the two stages a generic project template does not have, and they are the ones a research project actually spends the most time cycling between. A manuscript can pass through that loop three or four times before it is Done, and each pass is worth its own card rather than a note buried in an email thread.
Keep Ideas separate from the plan
Ideas is a parking lot, not a queue. A research project generates far more directions than it can pursue, and mixing "maybe worth trying" with "currently doing" makes the active work harder to see. Move a card out of Ideas only when you have decided to actually start it.
Running it solo versus with a lab
A solo researcher uses this board as a personal system: one person, one set of columns, updated a few times a week. The value is mostly visibility. It answers "what am I actually doing right now" without opening three documents.
A small lab adds people to the same board instead of running separate ones per member, the same idea behind simple project management for any small team. EasyKanban supports up to three team members per board on the free plan, which covers most lab groups and advisor-student pairs, so a student's board and an advisor's view of it can be the same board rather than a status update sent by email. Assigning a card to a specific person keeps Under Review honest: a card waiting on a co-author's feedback should say so, not just sit in an ambiguous middle state.
Handling the parts that repeat
Some research work is not a one-time task but a recurring one: a weekly lab meeting update, a monthly progress report to a supervisor, a recurring data backup. A card that reappears on a schedule keeps the routine parts of a research project from depending on memory, rather than recreating it from scratch each time. A WIP limit on In Progress matters here too: research is easy to spread across five half-started analyses at once, and a limit of two or three active items forces at least one of them to actually finish.
Starting without setting anything up first
The fastest way to test this is a kanban board with no signup: six columns, a handful of real cards from whatever you are currently working on, and no account required to try it. If it holds up after a week, save it and add your advisor or labmates. For a broader introduction to how kanban columns and cards work before building your own, see what a kanban board is.
Frequently asked questions
Do I need special research project management software?
No. A general kanban board covers the core need, which is seeing what stage each task is in. Purpose-built research software adds citation management and lab inventory features that most projects do not need just to track tasks and revisions.
How do I track a literature review on a kanban board?
Give it its own column. Add one card per paper or per theme, and move each card to Done once you have pulled out the relevant finding. A literature review that lives only in a folder of PDFs gives no sense of how much is left; a column does.
What is the difference between research project management and general project management?
The stages differ. General project management assumes mostly forward motion toward a fixed deliverable. Research project management has to account for a project moving backward through review and revision, sometimes more than once, and for early stages that may not lead anywhere.
Can a PhD student use this for a thesis?
Yes. A thesis is a research project with a longer timeline and higher stakes, but the same six columns apply. Chapters or studies can be tracked as separate cards within the same board rather than as one card for "the whole thesis," which is too large to move meaningfully. For the coursework and exam side of student life alongside the thesis, a personal kanban board for students covers a layout built for that.
Do I need a dedicated project manager for a small research project?
Usually not. Dedicated research project management support is real and useful at the scale institutions like Duke offer it, but it is built for large, multi-year, multi-person grants. A student project or a small lab study can run on a shared board and a short weekly check-in instead.
Try it on your current project
Pick whatever you are working on right now and write down its actual stages: probably some version of Ideas, Literature Review, In Progress, Under Review, Revision and Done. Add three or four real cards for tasks that exist today. Start a board for free and see whether the six columns above fit your project as written, or need one changed to match how your work actually moves.