Case Study 1 — Scope Creep, Caught and Narrowed
A composite, realistic scenario built from common dissertation patterns. Names are fictional.
The setup
Eighteen months into her PhD, Amara Bello had a problem she didn't recognize as a problem. Her thesis was going well — that was the trouble. Her proposal, signed two years earlier, had promised something tidy:
"This dissertation develops and validates a humidity correction for low-cost optical PM2.5 sensors. Scope: PM2.5 only; extension to other pollutants and to sensor manufacturing is future work."
One claim, one correction, one pollutant, a clear boundary. But research is generative, and good results breed ideas. By month 18 Amara's working outline had quietly grown to six contribution chapters:
- The humidity correction (the proposal's actual promise).
- A second correction for sensor drift — discovered along the way, genuinely useful.
- A comparison of three sensor brands ("for fairness").
- A temperature correction ("the sensors report it anyway").
- An ozone pilot ("reviewers will ask about other pollutants").
- A second deployment city ("one site isn't convincing").
Each had arrived as a reasonable sentence. None had been checked against the calendar.
The trigger
The reckoning came at a routine committee meeting. Amara presented her outline, proud of its scope. Her advisor, Dr. Okonkwo, listened, then asked one question: "When do you defend?"
Amara said spring — eight months out. Dr. Okonkwo did the arithmetic out loud. The ozone pilot alone needed a new sensor deployment and a reference instrument she didn't have. The second city meant another year of data collection. Three sensor brands tripled the validation work. "You've designed three more dissertations," he said, not unkindly. "Which one are you defending in the spring?"
The diagnosis: Amara hadn't been lazy or unfocused — she'd been too productive, and every addition had sounded helpful in isolation. Scope creep is rarely one bad decision. It is a dozen good-sounding ones, none weighed against the deadline. Her "what this is not about" sentence from the proposal had quietly stopped being true, and she hadn't noticed.
The two-question test, applied
That evening Amara ran every chapter through the test from §16.5 — does the claim fail without it? does the timeline survive it? — with the signed proposal open on the desk.
| Chapter | Claim fails without it? | Timeline survives it? | Verdict |
|---|---|---|---|
| 1. Humidity correction | Yes — it's the core claim | Yes | Keep |
| 2. Drift correction | Yes — accuracy claim depends on it | Yes (data already collected) | Keep |
| 3. Three-brand comparison | No — one brand proves the method | No — triples validation | Future work |
| 4. Temperature correction | No — humidity is the dominant effect | Borderline | Future work (note in discussion) |
| 5. Ozone pilot | No — proposal says PM2.5 only | No — needs new deployment | Future work |
| 6. Second city | No — one city answers the question | No — another year of data | Future work |
The claim — low-cost sensors, corrected for humidity and drift, produce PM2.5 estimates good enough for neighborhood public-health decisions — survived with only chapters 1 and 2. Everything else was interesting and out of scope. She wasn't deleting the ideas; she was moving them to the one honest place they belonged.
The narrowing
Amara rewrote her outline back down to two contribution chapters plus the standard frame (introduction, literature review, methodology, discussion, conclusion). Then she did the move that made the cut generous rather than merely defensive: she wrote a strong Future Work section that named all four deferred ideas explicitly — three-brand comparison, temperature, ozone, multi-city — and sketched how each would be done. Far from looking like gaps, the deferred ideas now read as a mature researcher mapping a program of work beyond the thesis. Reviewers reward that. A defense that says "here is exactly what I did, why, and the four next questions it opens" is stronger than one that tried to do everything and finished none of it well.
She emailed Dr. Okonkwo the revised scope with one line: "Defending the humidity-and-drift claim in spring; temperature, ozone, three-brand, and multi-city are written up as future work, per the original proposal's PM2.5 boundary. Confirming that's the right call." He replied in an hour: "Yes. Go finish."
What it cost — and saved
The cut cost Amara one afternoon of ego and a working outline she'd been fond of. It saved her, by Dr. Okonkwo's estimate, somewhere between one and two years. She defended that spring. The drift correction (chapter 2) — the thing she'd discovered by accident and almost buried under four other ambitions — turned out to be the contribution the committee found most novel.
Lessons
- Scope creep is invisible from inside. Each addition is a reasonable sentence; the danger only appears when you total them against the deadline. Amara needed an outside question — "when do you defend?" — to see it.
- The signed proposal is your anchor. The PM2.5 boundary, written down two years earlier, made the cut a matter of honoring an agreement rather than a painful judgment call in the moment.
- The two-question test is mechanical, not heroic. Does the claim fail without it? Does the timeline survive it? You don't need willpower; you need the questions.
- Future work makes the cut generous. Naming deferred ideas — and sketching how you'd pursue them — turns "I didn't do this" into "I mapped this for later." That reads as command of the field, not as a hole.
- The contribution you almost cut may be the best one. Amara nearly drowned her drift correction under bigger ambitions. Narrowing surfaced it. Less scope, done well, beats more scope done thinly — every time.