We are halfway through a 6-month infrastructure project, and stakeholders are suddenly requesting "minor" features that are ballooning our resource requirements. I’m worried about the triple constraint. What are some professional ways to push back or manage these requests without damaging stakeholder relationships? Should I be looking at a formal Change Control Board or just re-baselining?
3 answers
The first thing you need is a robust Change Management Plan. Never say "No" immediately; instead, say "Yes, and here is the impact." Use the Triple Constraint—Scope, Time, and Cost—to show that adding these features will either delay the launch or require more budget. A formal Change Control Board (CCB) is essential because it moves the "rejection" or "approval" away from the PM and onto a committee. This protects your relationship with the stakeholders. If they approve the change, make sure to formally re-baseline the project immediately so your performance metrics remain accurate.
In your experience, does a formal CCB process slow down the project too much for fast-paced digital projects, or is the safety it provides worth the delay?
Always document everything. If a stakeholder makes a "quick request" in a hallway, follow it up with an email documenting the potential impact on the timeline and budget.
Documentation is the PM's best friend. It’s not about being petty; it’s about having a trail of evidence when someone asks why the project is over budget or behind schedule in three months.
Mark, it’s a trade-off. For high-velocity projects, you can implement an "Expedited CCB" where small changes are approved by a single owner, while major ones go to the board. The goal isn't to slow things down, but to ensure that every decision is conscious and funded. Without that pause, you end up with a project that is 90% done for six months straight because the finish line keeps moving.