Scope Creep

Scope creep describes the slow widening of a project's boundaries after work has already begun. Each individual addition may seem small — an extra section in a policy brief, one more stakeholder to consult, a sidebar analysis a supervisor casually requests — but cumulatively these changes can blow through deadlines, budgets, and the energy of the team.

In a think-tank or research setting, scope creep typically takes a few recognizable forms:

• Mandate drift: a paper commissioned on, say, EU energy policy gradually absorbs questions about transatlantic relations, climate finance, and industrial policy.
• Stakeholder accretion: new reviewers or co-authors are added late, each requesting changes that pull the argument in different directions.
• Deliverable inflation: a 2,000-word memo becomes a 10,000-word report, plus a webinar, plus a podcast appearance.
• "While you're at it" requests: small add-ons from a principal that individually feel trivial but compound.

For junior researchers and MUN secretariat staff, scope creep is particularly dangerous because the costs are usually borne by the person with the least authority to push back. The standard countermeasures borrowed from project management are: a written statement of work or terms of reference agreed at the outset; a change-control habit, where new asks are acknowledged but explicitly traded against existing deliverables or deadlines; and regular check-ins where the current scope is re-stated aloud so deviations become visible.

Scope creep is distinct from scope change, which is a deliberate, negotiated revision of the project's goals. The difference is governance: scope change is decided; scope creep just happens. It is also distinct from gold-plating, where the team itself adds unrequested polish. Recognizing which pattern is occurring helps determine whether the fix is a conversation with the client, with the team, or with oneself.