Skip to content

Align Stakeholder Expectations

Step 9 of 57

PMP Stakeholder Alignment: Expectations, Workshops, and Mentoring

Introduction

PMP stakeholder alignment means finding out what each group expects and bringing those expectations into a decision the group can act on. A prototype might reveal that a claims handler expects to view photos while completing a form. Before adding a feature, check what that workflow needs, who can approve the work, and how it affects delivery.

Aligning stakeholder expectations is Task 5 in the People domain of the July 2026 PMP Examination Content Outline (ECO). People accounts for 33% of exam coverage. You will practise eliciting expectations, facilitating trade-offs, recording decisions, and using mentoring to help people participate in those decisions. Start with stakeholder identification and analysis when you are unsure who should be involved.

Learning objectives

  • Categorise stakeholders in ways that support the alignment effort.
  • Elicit stated, unstated and conflicting expectations using several techniques.
  • Prepare and facilitate an alignment discussion or workshop that ends in documented agreements.
  • Distinguish expectations, requirements and objectives, and treat each properly.
  • Organise mentoring opportunities for team members and stakeholders and act on what they reveal.
  • Recognise when misaligned expectations must go through change control or escalation.

1. Group stakeholders by role, impact, and decision rights

Categorising stakeholders turns a long list into groups that can be handled with the same approach. Use the power/interest assessment as a starting point and group people by what you need to decide.

Category Question Example of use
Role in the project Sponsor, customer, user, supplier, regulator, team Decide who must approve, who must be consulted
Decision rights Who decides, who recommends, who is affected Avoid asking the wrong person to confirm a scope
Attitude Champion, supporter, neutral, sceptic, opponent Prepare the right conversation
Type of expectation Business results, functional, quality, schedule, cost, experience Compare stakeholders on the same dimension
Internal or external Employees versus customers, partners, public Choose channels and confidentiality
Impact of the project Gains, loses, indifferent Anticipate resistance and sensitivity

Categorisation is useful because it makes visible where conflicts of expectation are likely. For example, if finance expects lower service costs and product expects a broader release, ask what success measure each group is using. If the release moves work between teams, involve the people who will own that work. The project manager can then arrange the alignment sessions by pair of groups that disagree, rather than lumping everyone into a long general meeting.

2. Identify stakeholder expectations

An expectation is what a stakeholder believes will be true when the project is done: features, quality, timeline, cost, ways of working, even the amount of involvement they will have. Expectations may be stated or unstated. They can conflict in either case.

  • Stated expectations: expressed by the stakeholder, in conversation or in writing. Some are already formal commitments, such as requirements in an approved contract.
  • Unstated expectations: obvious to the stakeholder, never said ("of course the new app works offline", "of course the old data is migrated").
  • Conflicting expectations: beliefs or requests that cannot both be met under the current constraints. They may become clear only when stakeholders compare what they expect.

Unstated expectations can emerge late, when changes are costly. Use several techniques to surface them early.

Technique How it helps
Structured interviews Ask about success: "How will you know in a year that this project was worth it?"
Workshops Let several groups hear each other, which exposes conflicts
Observation or job shadowing Reveals real behaviour behind what people say
Surveys and questionnaires Reach many people and compare stated priorities or assumptions
Prototypes, wireframes, demos Give something concrete to react to; people notice what is missing
Examples and scenarios ("a day in the life") Make the abstract concrete and bring out edge cases
Review of previous projects and complaints Show repeating disappointments
Pre-mortem After briefing people on the proposed plan, ask them to imagine that it failed and identify plausible reasons. Follow up on any expectations the exercise reveals.

Expectations should be recorded in a form that can be traced: the stakeholder, the expectation, its priority, whether it is already a requirement, and its status (agreed, to negotiate, rejected, out of scope). This record may sit in the stakeholder register, the requirements documentation or the backlog.

Example: a hidden expectation found with a prototype

An insurance company commissions a claims portal. The requirements say "customers can submit a claim online". During a clickable-prototype session, a claims handler asks, "Where do I see the photos at the same time as the form?" Nobody had written that the handlers expected a split screen with the customer's photos. The prototype reveals the need to see photos while reviewing a claim. The team compares split screen with a photo preview, then records the approved interaction and acceptance criteria. In this example, the prototype takes two days to revise. Once the screen is built, a similar change could also affect implementation and testing.

3. Facilitate alignment discussions and workshops

When expectations differ, the project manager (or a neutral facilitator) leads a structured discussion. A good alignment session has five parts.

  1. Prepare. Define the purpose ("agree on the release-1 scope and success measures"), invite the right people (those with decision rights and those affected), share a short pre-read, and gather the known expectations in advance. Use a short preliminary discussion when an issue needs private clarification before the workshop.
  2. Open. Restate the objective of the project and the purpose of the session, set ground rules (listen, speak about interests, decisions recorded), and agree how decisions will be made.
  3. Surface. Ask each group to state its expectations and success criteria, and make them visible: sticky notes, a shared board, a table. Ask for the reasons ("Why is that important?"), because positions hide interests.
  4. Align. Group the expectations, find overlaps and conflicts, and compare with the objectives, the constraints (budget, time, regulation) and the business value. Use prioritisation methods such as MoSCoW (Must Have, Should Have, Could Have, and Won’t Have this time) or weighted scoring. A vote can surface preferences. Confirm decisions with the people who hold approval authority. For conflicts, search for options that satisfy both interests; if impossible, apply agreed criteria or escalate to the person with decision rights.
  5. Close. Summarise the agreements and open points, assign owners and dates, send a decision record promptly, and confirm decisions with the authorised stakeholders.

A facilitator stays neutral about the options, gives each affected group time to speak, and checks that people understand what they are agreeing to. Ask someone to restate the decision and its practical consequences before closing the meeting.

Worked example: aligning expectations for a release

Scenario. A software company builds a subscription-billing platform for a telecom client. The sponsor wants go-live in four months to catch the sales season. The finance director expects automatic tax calculation in 12 countries. The customer-care head expects a self-service portal. The development lead says the three cannot all fit in four months. Each stakeholder has said privately that their item is "essential", and each assumes the others will give way.

Step 1 - Prepare. The project manager collects estimates, categorises the expectations (time, functional/finance, functional/service), and checks the contract and charter: the contract mentions billing and tax for 3 countries, and a "customer portal" without detail. He meets the sponsor beforehand to confirm that the deadline is a business target and to learn what is flexible.

Step 2 - Run the workshop. All three attend with the development lead. The facilitator asks each stakeholder to explain what happens if their item is absent at go-live. Findings: tax calculation in the three contracted countries is needed for the first invoices; the remaining nine countries start billing only in month nine. The self-service portal is needed to reduce call volume, but a basic version (view invoice, update address) covers 70% of the expected calls.

Step 3 - Align. The group uses MoSCoW: must have = billing for the 3 countries and invoice viewing; should have = address update; could have = remaining features of the portal; later release = tax for nine other countries. The team estimates that the Must Haves fit within four months, with some capacity for uncertainty. It checks the Should Haves against that capacity as estimates improve.

Step 4 - Close. The facilitator circulates a decision record. The contract owner confirms what the existing portal commitment covers. The authorised decision-makers approve any changes to the baseline or contract before those documents are updated. The product owner reflects the agreed order in the backlog and schedules a review at the end of month two.

Why not other choices? Letting the sponsor decide alone would have ignored legitimate needs and probably produced complaints later. Promising everything and relying on overtime would have created risk of failure and quality issues. Negotiating privately with each stakeholder would have kept the conflicts hidden. The workshop exposed the interests behind the demands and led to a documented compromise.

4. Expectations, requirements and objectives

Separate the result the project seeks, the conditions it must meet, and the outcomes that people expect.

Term Meaning Typical handling
Objective The approved purpose and measurable result of the project or phase Record in the appropriate authorisation or planning documents. Use the applicable decision process if the objective changes.
Requirement A condition or capability that must be met, agreed and recorded Record in requirements documentation or the backlog. Changes to approved baselines or commitments follow the applicable approval path.
Expectation What a stakeholder believes will happen or be delivered Discovered, discussed, then turned into a requirement, adjusted or declined

Treat an unconfirmed expectation as a possible gap. Assess its value, feasibility, and impact. Then work with the stakeholders to turn it into an approved requirement, agree on an alternative, or explain why it cannot be met. Use the agreed authority for the decision and record the rationale.

Also separate expectations about the product from expectations about the project: for example, how often a stakeholder wants to be consulted, how decisions are communicated, how quickly issues are escalated. These process expectations belong in the communication and stakeholder engagement plans and in the team agreement.

5. Organise and act on mentoring opportunities

Mentoring is a relationship in which a more experienced person shares knowledge, perspective and encouragement with a less experienced one. Mentoring draws on the mentor’s experience. Coaching may focus more narrowly on reflection or a specific performance goal, while training gives structured instruction. In practice these approaches can overlap. In a project, mentoring has three practical roles related to alignment:

  • Developing team members. An experienced engineer mentors a junior colleague on design decisions; a senior analyst mentors a new analyst on how to elicit requirements. The result is better quality and fewer misunderstandings about what stakeholders want.
  • Building stakeholder understanding. The project manager or a senior team member explains the project approach to a stakeholder who is new to it: an executive new to agile, a user group unfamiliar with iterative delivery. Better understanding leads to more realistic expectations.
  • Developing the project manager. Seeking a mentor, or being one, increases the leader's perspective and contacts.

To organise mentoring: identify needs (skills matrix, performance conversations, retrospective topics), match mentor and mentee on experience and style, agree on goals, frequency (for example 45 minutes every two weeks) and confidentiality, review progress, and recognise the mentor's time in the plan. To act on mentoring, use what emerges: a mentee may reveal that a stakeholder's request is misunderstood, that the team lacks a skill, or that a rule of the working agreement is unclear. Agree what can be shared before acting on mentoring feedback. Follow the organisation’s policies when an issue requires reporting.

Example: mentoring that changes an expectation

A new product owner expects all 80 items on a wish list next quarter. Her mentor helps her compare the team’s recent delivery of similarly sized work with its available capacity and dependencies. Together they identify the most valuable outcomes and ask the team to forecast a range for the work needed. She presents a smaller release forecast, explains the assumptions, and agrees to review it with stakeholders after the next demonstration. Continue with monitoring customer expectations and satisfaction to see how to test that agreement during delivery.

6. Common pitfalls and exam tips

Pitfalls

  • Assuming that a signed requirements document contains all expectations.
  • Holding separate private conversations and never bringing opposing stakeholders together.
  • Letting the loudest or most senior person define the expectation of the whole group.
  • Agreeing in the meeting and not documenting or confirming.
  • Accepting expectations beyond the scope informally.
  • Setting up mentoring without agreeing on a learning goal or time for follow-up.
  • Giving stakeholders good news only, to keep expectations high.

Exam tips

  • When the scenario reveals two stakeholders with conflicting expectations, the best answer usually brings them together in a facilitated session using objective criteria.
  • Assess an unplanned request and use the approval path for any baseline or commitment it would change.
  • A prototype, a demo or an example is often the best tool to discover unstated expectations.
  • When a stakeholder is new to the approach (for example, agile), explaining and mentoring is usually better than imposing.
  • Record decisions, open issues, owners, and dates in a place stakeholders can use.
  • Check whether the disagreement concerns the approved objective, a delivery choice within the team’s authority, or a decision that belongs elsewhere.

7. Mini case study

Situation. You are managing a project to build a new e-learning platform for a university. The academic dean (sponsor) expects the platform to be ready by the start of the autumn term, which is in 7 months. The IT department expects to host it on the university's existing servers and to approve all design decisions. The faculty representatives expect to upload their own existing videos and tests without changes. Students' association members, interviewed for the first time in month two, say that they assume the platform will work well on phones and with low-bandwidth connections. The requirements document does not mention mobile use or hosting. The team estimates that supporting the full set of functions on mobile would add six weeks. It will estimate a native app separately.

Question. What should you do?

Model solution.

  1. Categorise. Confirm who owns each decision. The sponsor may approve scope and schedule changes, IT may own hosting and security constraints, faculty own content, and students bring evidence about access needs. Note the types of expectation: schedule, technical, functional, experience.
  2. Record the unstated expectations (mobile and low-bandwidth use, hosting on existing servers, reuse of existing content) in the register, with the stakeholder and a proposed priority.
  3. Prepare data. Estimate options: responsive web design for essential functions (two weeks), a native app (eight weeks), content conversion effort and the hosting constraints. Find out from the sponsor what is fixed (the date, the budget) and what can flex.
  4. Facilitate an alignment workshop with the four groups. Ask each group about the consequences of not having its expectation met, use MoSCoW, and compare against the charter's objectives (improve access for students). Likely agreement: responsive design for the main functions in release 1, if the group agrees that is necessary for student access, and a native app for later consideration. Agree which existing content can be used as is and assess whether conversion is feasible for the rest. Ask IT and the team to compare hosting options before seeking the appropriate approval.
  5. Process changes. Assess changes to approved scope, schedule, and cost. Submit affected baselines for approval before updating them. If the date is fixed, present scope trade-offs to the authorised decision-makers.
  6. Document and confirm. Send minutes, obtain written approval from the sponsor and IT, and update the stakeholder register and communication plan. Schedule a review in six weeks and a demo with student representatives.
  7. Support understanding. Offer faculty representatives a mentor who can help them practise converting, checking, and uploading a sample of their own material. Agree on a follow-up after the first uploads.

Why this is best. It brings hidden expectations to the surface, aligns the conflicting ones with the facts and the project objective, and uses the formal process for changes. Quietly adding mobile support would break the schedule. Telling students that mobile use is out of scope without discussion would risk the project's main objective.

Key terms

  • Expectation: a stakeholder's belief about what the project will deliver or how it will run.
  • Unstated expectation: an expectation that is obvious to the stakeholder and was never communicated.
  • MoSCoW: a prioritisation method for agreeing what is essential, important, desirable, or deferred for a specified time frame.
  • Alignment workshop: a facilitated session where stakeholders agree on expectations and priorities.
  • Pre-mortem: an exercise that imagines a failure to find its causes in advance.
  • Mentoring: a relationship in which an experienced person guides the development of another.
  • Change control: the process that reviews and approves changes to baselines.
  • Success criteria: measurable conditions that show that an expectation has been met.

Summary checklist

  • I can categorise stakeholders by role, decision rights, attitude and type of expectation.
  • I look for unstated and conflicting expectations with interviews, prototypes, observation and pre-mortems.
  • I prepare, run and close an alignment workshop with documented, confirmed agreements.
  • I distinguish objectives, requirements and expectations and handle each properly.
  • I assess unplanned expectations and follow the approval process for changes to approved commitments.
  • I organise mentoring, match mentor and mentee, and act on what it reveals.
  • I tell stakeholders early when an expectation will not be met.

Official sources