I’m managing a digital transformation project and the executive sponsors keep adding "small features" that are ballooning the budget. How do you say no to a C-suite executive without damaging the professional relationship or risking your position? I need phrases or strategies that work.
3 answers
The key is never to say a flat "no," but rather "yes, and here is the impact." Use a formal Change Control Board (CCB) process. When a stakeholder asks for a new feature, present them with a "Change Request" form that outlines the additional cost, the impact on the timeline, and the risks to existing features. This forces them to make a conscious decision about trade-offs. If they want X, they must understand that Y will be delayed or the budget must increase. It shifts the burden of the decision from you back to the sponsor, where it belongs.
Are you currently using a "MoSCoW" prioritization list that the stakeholders have already signed off on? Having that baseline makes it much easier to show them what will have to be moved to the "Won't have" category to accommodate new requests.
Try using a "Parking Lot" for new ideas. Acknowledge the value of their suggestion but suggest it for "Phase 2" so that the current launch remains on track and successful.
The Phase 2 strategy is a lifesaver. It makes the stakeholder feel heard without derailing the current sprint or compromising the project's immediate integrity.
Daniel, we did a Moscow at the start, but they seem to have forgotten it. I've started bringing that printed list to every meeting now. It serves as a visual reminder of our original agreement and makes the conversation about priorities much more objective and less emotional.