Mission creep grows an initiative's scope one step at a time, each step inside existing approvals, until it covers ground that a single proposal for the whole would not have won.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Under a charter to improve project delivery, the program director of an operational excellence initiative at a commercial construction firm had authority to spend inside an approved budget. She started with standardized site reporting, which the division presidents welcomed. Within the same budget she then added a project-controls office, and a year later a central estimating group, each reported to the steering committee in the quarterly update with its cost and purpose. Neither step needed new approval under the charter, and she did not ask for one. When she wanted to pool superintendents across divisions, a change outside the charter, she brought it to the committee as a new proposal, with eighteen months of results from the earlier steps behind it. The committee approved a pilot in two divisions.
Why it works
Sized to fall below the threshold for formal review, every expansion looks easy to approve, little more than ratifying the next step. Rolling back looks costlier: it strands sunk costs, disrupts active work, ends roles hired against the bigger budget, and contradicts earlier approvals, while the expanded scope builds its own constituency. When the charter is aspirational and vague, approving it takes one meeting and demanding definition looks distrustful. Broad charter language makes it possible, along with weak oversight between phases, plausible small steps, and turnover in the oversight body.
The thinking behind it
Barry M. Staw Staw's Knee-Deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action (1976) found that personal responsibility for a course of action makes people commit more to it, which he interpreted as self-justification. Steering committee members who approved the charter and received each report are tied to the program's success, so they lean toward approving the next step and resist unwinding earlier ones.
Hal R. Arkes Arkes and Blumer's The Psychology of Sunk Cost (1985) describes the tendency to continue once money, effort, or time has been invested, partly to avoid appearing wasteful. A project-controls office and an estimating group represent staff hired and money spent, and stopping them would look wasteful. That is why growth inside approvals is hard to reverse, and why the defense concentrates on the charter, before the costs are sunk.
When it fits
Incremental scope growth suits a program leader holding a broad charter and a budget, working on a change that would draw opposition as a single proposal but can earn support step by step. You need results to show from each step, and a steering body that receives regular reports.
How to use it well
Grow inside the charter and report every step as you take it, because the record is what makes the eventual larger ask credible. The edge of the charter is where discipline matters most: a sponsor who crosses it without approval loses the credibility the reported steps built.
- Sequence the steps so each produces visible results before the next.
- Report each addition, its cost, and its purpose in the regular update.
- Stop at the charter's edge, and bring anything beyond it as a new proposal.
- Use the results of the earlier steps as the case for the next approval.
What it costs and where it backfires
Each step builds a constituency, so the program becomes hard to stop even when it should be, and that can turn against you if results falter. Opponents who notice the cumulative growth may push for a reset that freezes everything. The move needs no hiding, and it crosses the line when expansions are kept out of reports, described as smaller than they are, or pushed past the charter without approval, because the oversight body is then deciding on facts it was never given.
When it is used on you
Keep an authoritative copy of the original scope and compare the current scope with it at regular intervals. At chartering, ask for named deliverables, exclusions, a budget cap with re-approval triggers, and a time limit, since the charter is the decisive moment, before sunk costs start arguing for the sponsor.