A key stakeholder says they were never consulted. How should I respond?
Stakeholder engagement gapCheck whether their needs or decision rights were missed, then involve them in a focused review of affected outcomes. A mailing-list entry is not evidence of meaningful consultation.
What to do now
- Understand their role and concerns
- Identify decisions that affect them
- Assess any genuine requirement gaps
- Agree their involvement from this point
When to escalate
Escalate when
Their missing input changes acceptance, authority, or a material commitment.
Who decides
The stakeholder decision owner and project sponsor
Example
A support manager joins a readiness review after identifying an operational requirement absent from the design.
Mistake to avoid
Defending the distribution list instead of understanding the missed need.
Prevent a repeat
Check stakeholder understanding at important decisions rather than counting messages sent.
Suggested ApprovedFlow setup
- Projects
- Documents
- Approvals
Keep stakeholder decisions and supporting records with the project and assign follow-up actions to named owners. See the platform
Related cases
- How can we tell whether stakeholder engagement is working?Activity-focused engagement measures
- A stakeholder resists the project but will not explain why. What should I do?Unexplored stakeholder concerns
- The team built features that were never requested. What should happen?Gold plating
- The vendor says knowledge transfer is not included. How do we respond?Missing supplier transition scope