3.6. Manage Stakeholder Expectations
💡 First Principle: This task extends alignment into ongoing monitoring — internal and external customer satisfaction isn't assessed once and assumed stable; it's tracked continuously and responded to as it shifts.
Enablers: identify internal and external customer expectations, align and maintain outcomes to those expectations, and monitor internal/external customer satisfaction and respond as needed.
The internal/external customer distinction matters: an internal customer (e.g., another department depending on your deliverable) and an external customer (e.g., a paying client) can have divergent — sometimes conflicting — expectations from the same project, and the PM is expected to actively reconcile both, not favor one by default.
The expectation gap
The expectation gap is the difference between what a stakeholder believes the project will deliver and what it is actually planned or able to deliver. Gaps rarely announce themselves; they form quietly around four things:
| Gap type | Example |
|---|---|
| Scope | The sponsor still thinks a feature descoped months ago is included |
| Timeline | A stakeholder expects delivery two months earlier than the schedule shows |
| Quality | The customer expects polish beyond anything specified or budgeted |
| Resourcing | An executive assumes a team is still assigned after it was reassigned |
Naming the type tells you what the reset conversation must address.
Meeting requirements is not meeting expectations
A feature can satisfy every written requirement and still miss the operational need behind it. When an internal department says a delivered feature does not solve their real problem, investigate the gap and work to align the outcome with the genuine need rather than pointing at the signed specification. The same pattern shows up at project level: a project delivering on time and on budget while satisfaction scores fall is usually one where the customer's expectations are evolving faster than requirements management can capture — the project is hitting a target that has moved.
⚠️ Exam Trap: "The requirements were met and signed off, so the customer's complaint is out of scope" is a tempting distractor. On-time, on-budget, and to-spec are necessary, not sufficient — the enabler is aligning outcomes to expectations.
Monitor continuously, respond deliberately
Satisfaction confirmed at kickoff is a snapshot. A PM who aligned expectations at the start and never checked again will eventually discover a stakeholder who has been quietly dissatisfied for weeks — the missing piece was ongoing monitoring, through regular check-ins, reviews and demos, and satisfaction feedback.
When a customer's business priorities shift mid-project, recognize the shift, engage them to understand the new expectations, and realign outcomes going forward — routing through formal change control if scope is affected. Realigning a drifted stakeholder follows a clear sequence:
- Recognize that their expectations no longer match actual scope or timeline.
- Understand why the expectation drifted.
- Have a direct conversation to reset it against current reality.
- Confirm their understanding now matches reality.
⚠️ Exam Trap: Absorbing a customer's new expectations informally to keep them happy is scope creep, not expectation management. Engaging the customer is right; changing the baseline without change control is not.
⚠️ Exam Trap: Assuming the external (paying) customer's expectations always take precedence over internal stakeholders'. PMI's scenarios often test whether you recognize an internal stakeholder's legitimate, unaddressed expectation as the actual root cause of a described problem.
