How to handle demands from influential stakeholders: balancing relationships and project boundaries
When an influential stakeholder requests something new, clarify the result they want, compare it with the approved project arrangements and explain what additional work would change. Then bring the choice to the person who actually has authority to decide. Listening carefully and accepting a delivery commitment are separate actions. A working relationship can be maintained through timely replies, accurate understanding and clear follow-up.
Turn an emphatic statement into a request
“We must include this” is not yet a usable description of work. Ask who needs the result, in what situation, and which agreed outcome is affected by its absence. Establish whether this clarifies an existing requirement, corrects a delivery that does not meet an agreement, or adds scope. Work already promised but unfinished should not be relabelled as an extra request.
Here, influential describes the person’s position or the force of this particular conversation, rather than a label for their character. Record the request, its reason and the desired decision date. Keep judgments about the person out of project records. If they propose one implementation, ask whether another approach could meet the same purpose.
Explain impact using the current agreement
Open the confirmed scope, delivery date and acceptance description. Identify the work the request adds or changes and the existing commitments affected. If effort or resources have not been assessed, say so. Do not invent a precise estimate simply to keep the conversation moving. Saying that the team is busy does not explain the actual choice.
The Association for Project Management describes change control as capturing and evaluating changes to an approved baseline before approval, rejection or deferral. Its impact categories include scope, quality, time, resources, cost and risk. Use the process your project already has. A small project does not need a newly invented committee just because someone has asked for a change.
Bring back choices that can be compared
For example, a page due on Friday is suddenly expected to include registration reporting. After checking the facts, compare keeping Friday’s agreed delivery, meeting the immediate information need with an existing authorised tool, or changing scope and timing to add reporting. This example does not authorise a new tool or a different way of handling information. Each option must fit the project’s actual permissions and requirements.
You might say: “I understand that you need registration information. The Friday version does not include reporting. I will check the additional work and existing alternatives, then bring options tomorrow afternoon. That is the time for the assessment, not a promise to deliver the new feature.” The purpose is acknowledged while the commitment remains specific.
Check who decides and who contributes
Seniority, insistence and approval authority are not interchangeable. Consult the project’s recorded responsibilities or approval arrangements. If the authority is unclear, ask the project lead to establish it before making assumptions. Atlassian’s DACI approach distinguishes the person moving a decision forward, the approver and contributors who provide expertise. Those distinctions can clarify a conversation without reorganising the team.
APM’s consultation principle also discusses working relationships, boundaries, success measures and handover requirements. If a discussion needs a more senior participant, the existing project sponsor may help explain the consequences. The purpose is to get information to the appropriate person, not to embarrass the requester through escalation.
Update the agreement after the decision
When approved, update affected scope, dates, ownership and acceptance details, then inform people who depend on the revised arrangement. If rejected, record the current reason. If deferred, record the condition or date for reconsideration. An informal “yes” in a chat should not coexist with an obsolete commitment in the task system.
If requests for speed continue, return to the outstanding facts: which assessment is missing, who has not decided and when an update is due. Avoid adding promises that cannot be carried out. The process is complete when the request has a clear disposition and affected people know the current version. Universal satisfaction with the trade-off is not a required outcome.