How do I handle a highly influential stakeholder who is constantly pushing for out-of-scope features?

All answers to this question.

You need a rigorous Change Control Board (CCB) process. When the "small" request comes in, document its impact on the budget, timeline, and resources. Present this "impact analysis" to the stakeholder. Usually, when they see that their "small" feature will delay the launch by three weeks, they back off. In 2023, I handled a similar executive by creating a "Phase 2" backlog. I never said "no," I said "not now." This validates their idea while keeping the current project on track. It transforms the conversation from a confrontation into a strategic roadmap discussion.

   Answered 2024-06-17 by Heather Collins

Does your project charter explicitly define the escalation path for when the CCB and a high-ranking stakeholder disagree on the priority of a new feature?

   Answered 2024-06-20 by Jason Scott

• Jason, the charter does have an escalation path, but it usually leads back to the CEO. To avoid that, I’ve started using a "MoSCoW" prioritization matrix in our monthly reviews. By showing the stakeholder where their request sits (Must have vs. Could have), it forces them to trade off one of their other features for the new one. This visual trade-off usually stops the rank-pulling because they realize they are only hurting their own project goals.

     Commented 2024-06-22 by Steven Adams

Use a visual "Burn-up" chart. Show them how the total work is increasing relative to the deadline. Sometimes a picture of a growing workload is more convincing than any email or spreadsheet.

   Answered 2024-06-25 by Laura Martinez

• I agree with Laura. Visuals are powerful. When a stakeholder sees the "scope line" moving away from the "completion line," the reality of the delay usually hits home quite quickly.

     Commented 2024-06-27 by Kevin Peterson