Project Scope Creep

What is this situation?

Project Scope Creep starts when a project with agreed deliverables quietly becomes a container for every new request. At kickoff, the timeline, budget, and responsibilities look settled; then a stakeholder asks for one extra screen, a client adds another revision round, or a manager slips a new requirement into Slack and calls it a quick change. Each addition sounds small on its own, so work begins before anyone records what moved, who approved it, or what should come off the list. Meetings keep producing fresh action items while the deadline, fee, headcount, and launch date remain fixed. Because the requests arrive from people who control approval, payment, or performance feedback, saying no can carry more risk than absorbing the work, and the original brief stops functioning as a boundary. Your calendar fills with follow-ups, your shoulders stay raised over the laptop, and you spend late afternoons reconciling versions, redoing finished work, and explaining delays created by deliverables that were never in the first plan. The project may still be described as "almost done" even as the finish line moves again, much like the figure on the Ten of Wands, bent beneath a bundle that fills his view as he walks toward town.

Why it's not you?

This is not a failure to plan or work fast enough. Project Scope Creep is created when other people keep adding deliverables without changing the time, budget, staffing, or priorities around them, especially when they also control approval, payment, or performance feedback.