ProjectManager.co

Most scope creep is locked in during the first two weeks of a project — before the charter is even signed. This episode explains exactly how to stop it with one targeted pre-project exercise.

Show Notes

Scope creep rarely sneaks in mid-project. For most teams, the damage is already done during requirements gathering — when stakeholders are still being polite, assumptions go unstated, and nobody wants to slow things down by drawing a hard line. This episode of ProjectManager.co tackles the pre-project window that most methodologies treat as a formality, and offers a concrete technique for closing the gaps before work ever begins.

The episode centers on a single, high-leverage tool: the scope boundary document. Unlike a scope statement — which defines what a project will deliver — a scope boundary document forces explicit decisions on what is out, what is in but limited, and what is genuinely undecided. The host walks through a realistic example (an internal finance dashboard) to show how easily unspoken assumptions — real-time vs. end-of-day data, regional coverage, export formats — quietly become month-two change requests or go-live blockers. Key points covered include:

  • Why scope creep is a definition problem, not an execution problem — and why tracing it back to its origin almost always lands in the pre-charter phase.
  • The three-category framework for a scope boundary document: explicit exclusions (named, not vague), bounded inclusions (in scope, but only to a defined limit), and open decisions that must be resolved before sign-off.
  • The political value of collaborative scoping — when stakeholders help write what is out of scope, they own that decision, turning future change-request conversations from arguments into references.
  • A practical 90-minute working session to run with key stakeholders before the charter goes to the sponsor — and how to handle the inevitable "it's too early to know" pushback.
  • Why the open-decisions column matters most — deferring ambiguity feels safe in week one and becomes expensive in month three.

For PMs who want to formalize this kind of upfront work, the scope creep resource hub goes deeper on patterns and prevention strategies, and the project charter template is built to be paired with exactly the kind of boundary document described in this episode. Teams who want a structured approach to capturing risks and ambiguities before kick-off will also find the RAID log a natural companion for the open-decisions column. If this episode resonated, check out Stage Gates Are Broken — Here's How to Make Them Actually Work for a related look at how governance checkpoints can be redesigned to catch the problems that pre-project scoping misses.

ProjectManager.co

What is ProjectManager.co?

Project management for people who deliver, not people who certify. Estimation that survives contact with reality, scope and dependency management, status reporting nobody has to decode, and where self-hosted and AI-assisted tooling genuinely helps.

Each episode takes one practice — a re-estimate mid-project, a dependency nobody owns, a status meeting that produces nothing — and works through a better way to handle it. Written for delivery leads and PMs running real projects, with no methodology evangelism. Five or six minutes, one practice at a time.

Topics include estimation that survives reality, dependency and critical path management, scope negotiation, status reporting nobody decodes, resource planning, retrospectives that change something, and self-hosted versus SaaS tooling.

Produced by ProjectManager.co, self-hosted AI project management. Full details, services and further reading at https://projectmanager.co