Manage Stakeholder Expectations

Introduction

This lesson covers Task 1.6 of the People domain of the July 2026 PMP Examination Content Outline (ECO), a domain that carries 33% of the scored questions. Lesson 5 explained how to find and align expectations at a point in time. This lesson deals with what happens next: expectations of customers, internal and external, keep moving while the project runs. A requirement that was agreed in month one may be misunderstood in month five; a customer who was enthusiastic at kick-off may become anxious after a delay; a competitor may launch a product that changes what the customer wants. The project manager must keep the outcomes of the project aligned with what the customer expects, measure satisfaction, and respond quickly when a gap appears.

The exam presents this task as scenarios: a customer is unhappy with a demo, an internal client keeps adding wishes, a satisfaction survey drops, a delivered feature does not match what a user imagined. You must identify the best action, which is nearly always to understand the gap with facts, communicate honestly, and use the proper process (backlog, change control, escalation) rather than promise or ignore.

After this lesson you will be able to distinguish internal and external customers, align and maintain project outcomes with their expectations, monitor satisfaction with several instruments, and respond to expectation gaps.

Learning objectives

• Distinguish internal and external customers and explain why their expectations differ.
• Keep the outcomes of the project aligned with customer expectations throughout delivery.
• Select and apply techniques to monitor customer satisfaction (surveys, demos, NPS, feedback loops, acceptance results).
• Diagnose an expectation gap and choose among converting, adjusting or declining an expectation.
• Communicate bad news early and in a way that preserves trust.
• Distinguish expectation management from scope creep and from gold plating.

1. Internal and external customers

A customer is the person or organisation that will use or pay for the product, service or result. The ECO speaks of internal and external customer expectations, which is a deliberate distinction.

The distinction matters in exam scenarios. If an internal customer "just asks" the team for one more report, the project manager does not simply say yes because they are colleagues: the request is assessed and routed through the same change mechanism. If an external customer's expectation is not covered in the contract, the project manager cooperates with the contract owner (procurement, legal, account manager) before promising.

A project may also have an end user who is neither the payer nor the decision maker. A hospital buys a scheduling system (the customer, with a purchasing manager), but nurses use it daily (end users). Satisfying only the buyer can leave the users dissatisfied and the product unused.

2. Align and maintain outcomes with customer expectations

Alignment is not a single event. It is maintained through a cycle:

1. Define the outcomes in measurable terms: acceptance criteria, success measures, service levels, benefits.
2. Make progress visible: demos, prototypes, dashboards, burn charts, milestone reports. People cannot confirm expectations on something they cannot see.
3. Collect feedback at regular points and after each increment.
4. Compare the feedback with the agreed outcomes and with the objective of the project.
5. Decide what to do with each gap: confirm (still aligned), adjust the product, adjust the expectation, or process a change.
6. Record and communicate the decision, and update the relevant artefacts (backlog, scope, risk register, stakeholder register).

In predictive projects the checkpoints are the milestone reviews, stage gates, design reviews and acceptance tests. In adaptive projects the checkpoints are the sprint review, the backlog refinement and the retrospective, and the product owner keeps the customer voice present every day. In hybrid projects, both appear: for example, a fixed regulatory scope with agile delivery inside each release.

Example: keeping outcomes aligned with a customer over time

A logistics company (external customer) orders a warehouse-tracking application from a software supplier. The contract states: "mobile scanning, real-time stock levels, integration with the ERP". During month three, the customer's operations director sees a demo and says, "Real-time means that I see stock changes within seconds." The team had assumed "within five minutes" because the ERP interface works in batches. The project manager does not argue about the word; he asks what decision the director takes with the data, learns that dispatchers need seconds-level accuracy only for fast-moving items, and proposes an event-based update for the 200 fastest items and batch for the rest. A change request quantifies two extra weeks and a modest cost; the customer approves; the contract annex is updated. The customer is satisfied because the gap was found early, in a demo, with a concrete proposal.

3. Monitor customer satisfaction

Satisfaction cannot be assumed from silence. The project manager chooses indicators that fit the project and combines quantitative and qualitative sources.

A single measure is rarely enough. A customer might score a deliverable well (CSAT 4.5) while quietly worrying about the timeline; a survey shows a decline in NPS, but only a conversation shows that the cause is not the product but a poor handover with the support team.

Leading and lagging indicators. Complaints and escalations are lagging: the problem has already occurred. Leading indicators include the frequency of customer contact, the number of unresolved questions, the number of rejected demo items, and the customer's participation in reviews. A customer who suddenly stops attending reviews is a warning sign even if no complaint is raised.

Worked example: reading a satisfaction signal and acting on it

Scenario. You manage the migration of a bank's internal HR portal for 4,000 employees (the HR department is the internal customer). After release 2 of 4, the pulse survey shows CSAT falling from 4.2 to 3.4. Open comments mention "slow search" and "I cannot find my payslips". The HR director also forwards an email: "The team is not listening". Defect statistics show that all release-2 acceptance tests passed. The budget and schedule are on track.

Step 1 - Do not dismiss the signal because the tests passed. Acceptance criteria measure conformance to the agreed requirements; satisfaction measures fit with what people expect. A gap can exist even when requirements are met.

Step 2 - Analyse the data. Split the comments by theme: search (46%), payslips location (31%), other (23%). Check the usage analytics: the payslip page is four clicks from the home page. Search response averages 6 seconds against an unwritten expectation of "instant". Neither point was in the requirements, but both are reasonable user expectations (unstated).

Step 3 - Talk to the customer. Meet the HR director and two user representatives. Confirm the findings, acknowledge the perception that the team did not listen, and ask what a good result looks like (search in under 2 seconds; payslips on the home page).

Step 4 - Decide and process. Navigation changes are small and are added to the backlog for release 3 after prioritisation with the product owner. The search performance work needs two weeks of a specialist: the cost is assessed through change control and the HR director approves the use of contingency reserve for the extra work, after the steering committee is informed.

Step 5 - Communicate and follow up. Send a short note to all users explaining what will change and when; run another pulse after release 3 to confirm the trend.

Why not other choices? Defending the result by pointing out that acceptance tests passed would harm the relationship and leave the real problem. Immediately promising all improvements with no impact analysis would endanger schedule and budget. Waiting for release 4 to see whether satisfaction recovers would let the problem grow. The best response is to investigate with data, confirm with the customer, and use the correct process.

4. Respond to expectation gaps

A gap exists when what the customer expects differs from what the project will deliver. Causes include ambiguous requirements, a changed business context, poor communication, undisclosed constraints, overpromising by sales, and a customer who has seen a competing product.

A structured response:

1. Describe the gap precisely: what is expected, what is planned, what is the size of the difference?
2. Find the root cause: ask "why" several times; check the contract, requirements, communication records and decisions made.
3. Assess impact on scope, schedule, cost, quality, risk and benefits.
4. Generate options: deliver as expected (with a change), deliver a reduced version now and the rest later, offer an alternative that serves the same goal, or explain that the expectation cannot be met.
5. Discuss with the customer and decision makers using facts, not blame.
6. Process the decision through backlog prioritisation or change control, and update the artefacts.
7. Confirm in writing and monitor that the gap closes.

The three standard answers to an unplanned expectation, as in lesson 5, are convert, adjust or decline. In expectation management the second answer is especially important: the project manager can often change the expectation by showing the customer the cost, the trade-off or an alternative that serves the underlying need.

Bad news

Bad news (a delay, a defect, a cost overrun, the departure of a key person) does not improve with time. Good practice:

• Tell the customer early, before they discover it, and in person or by call for serious matters.
• Present facts, the cause, the impact, and options or a recovery plan, not only the problem.
• Take responsibility for what is yours; avoid blaming the team, supplier or customer.
• Agree on the next communication point, and keep it.

An exam answer that hides information from the customer, delays it to "wait until we have a solution", or only informs the sponsor of a problem that affects the customer's own decisions is almost never correct.

5. Expectations, scope creep and gold plating

Managing expectations does not mean saying yes to everything. Three behaviours should be kept distinct:

A project manager who allows the team to "give a little extra" to please the customer raises expectations for the future, creates unplanned risks and can break the contract. The preferred behaviour is to deliver the agreed value, and to propose extras formally.

Example: gold plating that damages expectations

A developer adds an export-to-Excel function to a reporting module because "customers will love it". The customer enjoys it, then expects it in every module, including the one built by another supplier. When the project manager explains that it is not planned, the customer is annoyed: "You gave it to us before." Because the first extra was never approved, it was not tested, documented or budgeted, and it now causes a defect in the next release. The right behaviour would have been to suggest the function as a change, with its impact.

6. Common pitfalls and exam tips

Pitfalls

• Believing that signed requirements and passed acceptance tests mean the customer is satisfied.
• Treating internal customers as informal and skipping change control.
• Measuring satisfaction only at the end of the project.
• Using one metric (for example NPS) and ignoring the reasons behind it.
• Hiding or softening bad news to protect the relationship.
• Promising something to calm a customer before assessing the impact.
• Letting the team add features to please the customer (gold plating).
• Confusing the buyer with the user.

Exam tips

• When a customer expresses dissatisfaction, the best first step is usually to understand the cause with facts (data and conversation), before choosing a solution.
• When an expectation is not in the scope, assess its impact and use change control (or backlog prioritisation in agile projects); do not simply refuse and do not simply accept.
• Early, honest, fact-based communication beats delayed, polished communication.
• Regular demos, reviews and feedback loops are preferred to waiting until the end.
• If a customer wants something that conflicts with the objective, ethics or regulations, escalate to governance and explain the limits.
• In agile projects, the product owner represents the customer voice; the project manager or servant leader supports regular reviews and helps the team respond to feedback.

7. Mini case study

Situation. You lead a project for a regional airline (external customer) to deliver a new mobile app for check-in and boarding passes. The contract describes "check-in, boarding pass storage and flight notifications" for iOS and Android, delivery in 6 months. At the month-four demo, the airline's marketing director says she expected a loyalty-points display and one-tap rebooking, because "all competitors have them" and the sales team had mentioned "a complete digital experience". The contract does not mention either. The CSAT for the demo is 3.1 out of 5. Your team estimates the loyalty display at three weeks and one-tap rebooking at seven weeks. The date is linked to a marketing campaign that is already scheduled.

Question. What should you do?

Model solution.

1. Do not dismiss or promise. Acknowledge the expectation and thank the director for the feedback.
2. Understand the gap. Ask what outcome she wants (more engagement, fewer calls) and how important each feature is. Check the contract and the pre-sale communication with the account manager to understand what was said.
3. Assess the impact of the options: loyalty display only (3 weeks), both (10 weeks), neither but with a roadmap. Compare with the campaign date and the contract terms.
4. Present options and trade-offs to the airline's sponsor and marketing director: for example, release 1 on the planned date with the contracted features, plus a quick loyalty display if the airline accepts a three-week extension or removes a lower-priority item; rebooking in release 2.
5. Process the decision through change control, with the price and schedule effects, and update scope, schedule and risk register.
6. Improve the process. Align with the account manager so that future promises are checked against the contract; add a short monthly satisfaction pulse with the airline.
7. Confirm in writing and schedule a follow-up demo to check that the gap has closed.

The wrong answers: adding both features quietly to please the customer (scope creep, risk to the date), refusing because "it is not in the contract" with no discussion (relationship damage and missed value), or waiting for the final delivery to see the reaction.

Key terms

• Customer: the person or organisation that pays for or uses the result; internal or external.
• End user: the person who uses the product, who may differ from the buyer.
• Expectation gap: the difference between what a stakeholder expects and what will be delivered.
• CSAT: customer satisfaction score for a specific interaction or deliverable.
• NPS: Net Promoter Score; percentage of promoters minus percentage of detractors.
• Leading indicator: a measure that warns of a likely problem before it appears (for example, falling attendance at reviews).
• Scope creep: uncontrolled growth of scope.
• Gold plating: adding features not requested or approved.
• Feedback loop: a regular mechanism to obtain, evaluate and act on feedback.

Summary checklist

• I can distinguish internal and external customers and the end user, and explain how change handling differs (formal for external, still controlled for internal).
• I keep outcomes aligned through measurable criteria, visible progress and regular feedback.
• I use several instruments (demos, pulse surveys, NPS, CSAT, acceptance results, conversations) and watch leading indicators.
• I diagnose a gap with facts, assess impact, present options and use change control or backlog prioritisation.
• I communicate bad news early, factually and with options.
• I avoid scope creep and gold plating, and propose extras formally.
• I confirm decisions in writing and verify that the gap has closed.

Official sources

• PMI, PMP Examination Content Outline (July 2026), People domain, Task 1.6: https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, New PMP exam: https://www.pmi.org/certifications/project-management-pmp/new-exam (opens in a new tab)
• PMI, PMP exam change: https://www.pmi.org/blog/pmp-exam-change (opens in a new tab)