Managing research like a project: PMP habits that survived my PhD
Research is famously unplannable. That's exactly why a few project-management disciplines matter more in a lab than in industry — and why most of the PMP toolkit should stay at the door.
I earned my PMP before starting the PhD, and for the first year I tried to run my dissertation like a project: work breakdown structure, Gantt chart, the lot. Most of it collapsed on contact with research reality — you can't schedule a discovery. But three habits survived, and they're the ones I now teach students I mentor.
1. A real definition of done
"Analyze the data" is not a task; it never finishes. "Produce a figure comparing modeled vs. observed demand, with a one-paragraph interpretation" is a task. The single biggest improvement to my research throughput was writing every task with an artifact as its endpoint — a figure, a table, a paragraph, a script that runs.
2. A stakeholder register, even for a dissertation
A PhD has more stakeholders than most industry projects: committee members with different priorities, co-authors, data providers, funders. Writing down who cares about what — and how often they expect to hear from you — prevents the classic failure mode of surprising your committee at month 40.
3. Timeboxes instead of estimates
Estimating research tasks is fiction, so I stopped. Instead: "I'll give this literature thread two days, then decide whether it earns two more." The decision point is the deliverable. This is the piece of Agile thinking I use daily, and the reason I'm now formalizing it with an Agile certification.
Detailed Gantt charts (obsolete in a week), earned-value tracking (meaningless without stable scope), and formal change control (a PhD is one long change request). Tools should reduce uncertainty, not document it.
If you're a student trying to bring structure to your first research project, start with definitions of done — it's the habit with the highest return and the lowest ceremony.